-
Notifications
You must be signed in to change notification settings - Fork 132
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
Receive messages - RSU #59
Comments
Hi @danieladriano, I have just checked GBC reception with Regards, |
Hi @riebl , In my service, when the message have the vehicle as origin and a RSU as destine, the communication via GBC don't work. But the inverse (RSU to Vehicle) its working and V2V too. If I change from GBC for SHB, the communication works fine. About the security entity, I don't have This is my code for send a packet from vehicle to RSU.
Thanks for the helping. Regards, |
Router depends on emitted PositionFixObject to set its position vector. If this signal is missing then the position vector of RSU routers is never set correctly. Thus, any position based routing involving RSUs fails in this case (bugfix #59). Change-Id: I57fa44139501bdcad1db9c41ea3320c1f4bdee9b
Okay, based on your detailed problem description I have been able to find and fix the problem. |
Hi @riebl , Thanks for the help and the bug fix. I will test my application again and give you a feedback. I have no experience with test cases, but if I have any ideas, I will pass on to you. Thanks again. Regards, |
Hi @riebl its me again :-)
I'm update my Artery fork for the newest version. I have a service running in a RSU (purely an OMNeT++ module) with send and receive messages for some vehicles using GBC. After the update, the application on RSU can send messages but no more receive.
The service running in the vehicle, can send messages V2V but not for my RSU.
I have tested with SHB and then works fine.
My initial Artery fork is from September and I see there is a lot of changes since then. I'm trying to find the problem, but without success.
Do you have any idea what possible is wrong ?
Regards,
Daniel
The text was updated successfully, but these errors were encountered: