Dear all,
I have just downloaded GCDC source code and the Makefile inside "src/kernel" has no "install" target, as the manual provided suggests...
Sorry, as TNO failed to provide the stack as open source (though they promised to do so), the licensing issues around this repository became...
We are not in this challenge. But we are very interested in implementing 802.11p on UNEX DCMA 86P2. Is there any help regarding linux driver for...
Hi Dr. Holger.
Can you make your improvements available?
I tried at git://github.com/SirVer/GCDC.git but the repository no longer exists.
Best...
Hi,Anton,
Quite surprised that you could see this message and replied.I followed your advice and tried the compat*2.6.33* version and patched it...
Hi Elin,
There are no specific requirements wrt the look-ahead time/distance for speed intent. The use of these messages is entirely optional.
Note also that there is no explicit demand for the VehicleSpeedIntent message. I admit this may be a bit confusing in light of the message summary in Chapter 4: Here is says that the frequency is "On Demand", but we only meant to say that this message is not "Periodic".
Use of the VehicleSpeedIntent message is for exchanging short-term planning information in terms of velocities (positions). For instance, if a platoon leader discovers that he has to wait for a traffic light ahead, he may send out a speed profile to his followers. The followers then:
* Know the speed will change; causing no surprises;
* May take actions in preparation for the speed changes.
As you notice, there are many "may"/"could"/"might"/"optional" annotations in the previous section. To put it simply: we do not enforce the use of speed-intent, but would love to see some use for it.
Best regards,
Jan