Harry's GPS Suite Forum

I tested all Storage Rate (GPS Rate, 5, 10, 20, 50 Hz) but none of them fixed the problem.

Looking at the OBD data, it looks like you are sampling the OBD data at the GPS rate but most likely you are dropping an OBD sample if the timestamp of the OBD sample gets out of the range of a single GPS sample?

It's odd but this data fusion problem occurs with OBD data but not with G-force data (LATERALG and LINEALG) which is 10Hz from iPhone.
Any idea why only OBD data is affected by the external GPS data?

Any consideration about these "data fusion for certain GPS / OBD update rate combinations" issue or the “steps” in OBD data issue?
viewtopic.php?p=27861#p27861
https://www.youtube.com/watch?v=RKsuf2QNIWo

Tracking days are coming around the corner and currently, the combination of PLX Kiwi 3 (OBD) and DUAL XGPS 160 (GPS) is unusable due to this issue.

Is the 24.9.0 update going to fix this "data fusion" and “steps OBD data” issue, by any chance?

Could you confirm if you have changed anything in 24.9.0 to fix or mitigate these "data fusion" and “steps OBD data” issues?

No - we have not been able to reproduce the issue.

I think PLX Kiwi 3 and DUAL XGPS 160 are some of the most common combinations to be used together, and I can reproduce the problem all the time.
Haven't you reproduced the problem at all?