|Applicable Versions||NetSim Standard||NetSim Pro|
Note: From v12 of Netsim, the user can directly model V2V and V2I communications through Netsim GUI.
NetSim VANET module currently supports V2V communications directly. V2I communications involving components such as RSU/RTU's can be modeled in your VANET network with a few customizations done to the NetSim UI related files as explained below:
1. Download the attached VANET_Update.zip folder and extract to obtain a VANET_Update folder which contains NetSim_Simulation_Update and Settings folders.
2. Based on whether the system has NetSim 32-bit build/64 bit Build of NetSim v10.2 Copy NetSimSimulation.exe from 32bit or 64-bit folders present inside the NetSim_Simulation_Update Directory and place it in the <NetSim_Install_Directory>/bin folder after renaming the original NetSimSimulation.exe that is already present, as a backup.
3. The Settings folder contains Configuration.xsd and Property.xml files which are suitably modified.
4. Place the Configuration.xsd in the <NetSim_Install_Directory>/bin folder after renaming the original Configuration.xsd file already present as a backup.
5. Place the Property.xml file in the <NetSim_Install_Directory>/Docs/xml folder of NetSim after renaming the original Property.xml file already present as a backup.
Creating a VANET network in Single MANET module:
1. Open the NetSim Single MANET module in NetSim.
2. Click on the Environment Settings button and reset the grid length as per the SUMO network requirements.
3. Place the devices in the GUI as per the number of vehicles you have configured in SUMO. The devices can be placed in the GUI randomly, since initial positions and movement will be as per the device placement and routes taken, in SUMO.
4. Device icons can be changed optionally to make it more realistic. To change icons right-click on any device and select Change Icon. NetSim supports any jpe, jpeg or png images as icons.
5. Right-click on any device and select properties. Under General Properties set the Mobility_Model as SUMO. Set the path of the SUMO Configuration (sumo.cfg) file along with the file name in the Sumo File text box. In the Device_Name text box enter the vehicle name as per the vehicle id configured in the sumo routes file (rou.xml) file. Do this for all devices that were dropped.
The device naming is important since the mapping between the vehicle in NetSim GUI and the vehicle in the SUMO network is done using the Device Name.
6. Go to the Interface1_WIRELESS in the device properties and set the DATALINK_LAYER and PHYSICAL_LAYER protocol to IEEE1609 from the Protocol drop-down list.
Adding RTU/RSU to NetSim VANET Network:
1. In VANETs, vehicles and roadside units (RTUs) are the communicating nodes, providing each other with information, such as safety warnings and traffic information. Both types of nodes are dedicated short-range communications (DSRC) devices. To have roadside units in NetSim you can add additional wireless nodes in which you can set the MAC and PHY protocol as DSRC (IEEE1609).
2. You can then set the mobility model to default (RANDOM_WAY_POINT) and set velocity to 0.
You can further change the icon of the road side units as per your requirement. You can configure applications from road side units (either broadcast or unicast).
Upon doing this, the mobility of vehicles alone will be modeled using SUMO whereas the RTUs will only be part of NetSim's network. The communication between vehicles, vehicles and RTUs, etc will be handled by NetSim.
Configuring Traffic, advanced feature and running simulations:
1. Click and drop the application icon and select properties after right-clicking on it.
2. Configure traffic between the vehicles or between vehicles and RTU/RSU's as per your requirement.
3. Enable advanced features - Packet Trace, Event Trace and Dynamic Metrics optionally.
4. Click on the Run Simulation button. It is preferable to specify the simulation time less than or equal to the end time specified in the sumo configuration (sumo.cfg) file.
5. As simulation starts SUMO interface(Vanet.exe) command line will be initialized in parallel and will be displaying the step calculations done in SUMO during runtime. SUMO interface window will be terminated before simulation in NetSim is over since SUMO takes care of road traffic conditions whereas NetSim takes care of the Network Communication and instantiates the TCP/IP stack for each device taking part in the simulation.
18. At the end of the simulation, NetSim will provide detailed performance metrics along with packet trace, event trace, link, and application throughput plots based on the user configuration done. NetSim animation window which appears at the end of the simulation can be ignored and closed.
Note: After saving the simulation performed, place all the SUMO network-related files such as *.sumo.cfg, *.net.xml, *.rou.xml, etc in the saved directory containing NetSim Configuration file (Configuration.netsim). Upon reopening the saved network scenario in NetSim, the SUMO FILE path will be reset in the device properties to point to the path from where the scenario was loaded.