Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Highway-police scenario messages #279

Open
MartinaBarbiFivecomm opened this issue Apr 7, 2023 · 1 comment
Open

Highway-police scenario messages #279

MartinaBarbiFivecomm opened this issue Apr 7, 2023 · 1 comment

Comments

@MartinaBarbiFivecomm
Copy link

Good afternoon,

I would like to ask you why in the highway-police scenario the cars which are not police (node[0], node[1], node[2]) are exchanging messages among them and with the police (as shown in the attached screeshot)?

The way it should work is that the police is transmitting to the others, and the other cars reacting to the message if not in the same lane as the police. But as you see in the attached picture they are exchanging messages between them and with the police. In the ClearLaneService.cc there is no trigger () call so they should send nothing right? Am I missing something?

Messages_Police_Scenario

Thank you very much in advance,

Martina

@riebl
Copy link
Owner

riebl commented Apr 7, 2023

The GeoNetworkwing protocol demands that stations send a so-called beacon roughly every 3 seconds if no other single-hop broadcast (SHB) is sent. Thus, if the vehicles were equipped with CaService, a CAM would be sent by them at least once per second and thus no beacons need to be generated by the network layer. In the highway-police scenario, the vehicles are not equipped with CaService though. Hence, their routers generate beacons according to the ETSI GeoNetworking rules.
However, you can disable beaconing explicitly in Artery:

bool disableBeaconing = default(false);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants