we encountered big issues regarding lap-time recognition on the DEKRA Lausitzring again last weekend.
The GPS signal is very good, but only every 3rd or 4th lap is correctly timed since the GPS signal has such a wide spread.
The Lap-recognition works fine on other tracks with the same car. Only the Lausitzring bothers us and other ADU users every year…
I attached a picture of the GPS signal during the race and the same thing from the same car a few months earlier on the Nurburgring. I hope that makes the problem clearer…
can the lap-timing in DataMaster and the ADU be improved to be more robust against a bad GPS signal?
As I recall Lausitzring, there are perimeter walls all around it. GNSS signal reflections (multi-path reception) can cause incorrect position calculations and high-update receivers are particularly susceptible to this. Which version of the GPS2CAN are you using?
@mfudala_ECUMASTER Are the GPS2CAN v1 and v2 multi-band/frequency* receivers?
Multi-band receivers are more resistant to false path/multi-path errors.
*) Multi-band/frequency is different from multi-constellation (GPS, Galileo, GLONAS, BeiDou)
@kaihp These are multi-constellation receivers, not multi-band.
These errors can be caused, as @kaihp wrote by multipath reflections that contaminate the base signal from the satellite.
Your logs and project would be valuable to help find a way for the ADU lap timing algorithms to recognize this scenario better. Generally, laps in ADU are not counted, and the whole lap timing goes bad because the start/finish line is not recognized, due to GPS path drift.
Using your logs, we can try to find a solution for this kind of issue.
Second question: Would you show us a photo of how your GPS antenna is mounted?
