omnet++

I am trying to implement a VANET model for smart parking simulations. Trying to fully understand the TraCIDemo11pp.cc and files relevant to it and its proving quite difficult to get my head around the general structure of each module and the communications between them despite understanding the TicToc tutorial. I understand how SUMO and OMNETPP are run in parallel, TraCIScenarioManager from OMNETPP communicates with the TraCI server in order to exchange information to SUMO etc. But I'm finding it hard to get my head around how the TraCIDemoApp is utilised. The question is quite specific, but

I am wondering how to correctly set the transmission range of a node under Veins 2.0, i thought that i was doing it right, but i am afraid to be wrong. So, i need some clarifications regarding parameters defined in *.ini file: *.connectionManager.pMax = 24.34mW # =>>> parameters to set the max interference distance by the global manager module *.connectionManager.sat = -80dBm # =>>> parameters to set the max interference distance by the global manager module *.**.nic.phy80211p.maxTXPower = 24.34mW # =>>> what is the role of this parameter ? is it affecting the transmission range or only

in my simulation using OMNeT++, Veins, and SUMO i want run multiple applications according to their vehicle type, as specified in the .rou.xml file using type="XXX" For example: <vehicle ... type="private" ... > runs APP_private (using something like *.node[*].applType ="APP_private" ) <vehicle ... type="bus" ... > runs APP_bus (using something like *.node[*].applType ="APP_bus" ) How can I define this in omnetpp.ini ? Veins 4.6 allows you to set any or all of the moduleType , moduleName , and moduleDisplayString parameters not just to a string (which will set the OMNeT++ module type, module

I am working on Veins framework, inside OMNET++. I set the property of RSU inside .ned file as follow: @display("p=150,140;b=10,10,oval;r=90"); The tkenv shows a circle around RSU, but the vehicles received beacons outside the range (circle). How can I adjust the transmission range of RSU to the Circle? Adding a display string tag of r is just adding a circle to the graphical output; it does not influence the simulation. If you define the "transmission range" as the point where the probability of reception is zero, you can calculate this point based on the transmission power at the antenna and

I'm doing a scenario where there is 1 route at the beginning and then it splits into 3, then merges into 1 again. I'm stopping the car in the first lane, the second car stops also, the third one reroutes in the middle lane, the fourth goes to the queue, the fifth reroutes, the sixth goes to the queue, the seventh reroutes.....why is it behaving like that? I can't understand where to change this "balancing" or "threshold". Any suggestion? The Veins 4.6 sample application behaves as follows: if a vehicle is stopped (and has been driving) and has not yet sent a warning message, it sends a message

Does setting length of WSM via setWsmLength or adding a large payload via setWsmData makes any difference during simulation? I am trying to simulate a heavily used network, but changing any of those two values doesn't seem to make any difference. I found this , but wanted to confirm this. And If I wanted to change the size of the WSM do I have to implement it? You can implement a packet for your application in a .msg file as follows: cplusplus {{ #include "veins/modules/messages/WaveShortMessage_m.h" }} class WaveShortMessage; message MyAppsPacket extends WaveShortMessage { string