With VL502 OBD by JimiIOT, (Huabao Protocol).
The messages are handled by the decodeTransparent function.
The Location message and OBD message is sent at a different time interval.
To overcome this and ensure the availability of OBD data in position we use the copy attributes feature.
Question: When the tracker stops sending OBD data, the previously received values are retained in position due to the use of copy attribute. In this case, the OBD-related values shown end up being outdated.
How can we handle this? any suggestions/ideas are welcome.
Additional information: We use Traccar API, so if anyone has suggestions on a way to handle it on the client side would be good too.
Copy attributes work.
I don't think there's an easy way to handle it. You probably need to save a timestamp for last OBD update and not copy attributes if they're too old.
Do you think it's worth implementing this as a feature in Traccar? If yes, I can send you an email.
With VL502 OBD by JimiIOT, (Huabao Protocol).
The messages are handled by the
decodeTransparentfunction.The Location message and OBD message is sent at a different time interval.
To overcome this and ensure the availability of OBD data in position we use the copy attributes feature.
Question: When the tracker stops sending OBD data, the previously received values are retained in position due to the use of copy attribute. In this case, the OBD-related values shown end up being outdated.
How can we handle this? any suggestions/ideas are welcome.
Additional information: We use Traccar API, so if anyone has suggestions on a way to handle it on the client side would be good too.
Copy attributes work.