You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't looked at the raw data, but according to the engineers at Teltonika the TAT140 reports cell tower (LBS) positioning data along with the standard GNSS data, in the same way that the TAT100 does. It would be great if Traccar servers would use this positioning data when the device report "no fix" for its latest satellite position.
Additional Information
It appears that you already decode cell tower positioning data (here). I'm not certain how this data is then processed, however from testing with a device it appears to stop updating the position (on your server dashboard) when a satellite position can't be fixed, even though it should be able to use the cell tower positioning data as a fallback.
Alternatives
Any secondary positioning data could be stored separately. That way the server dashboard could remain the same (only showing satellite positions on the map) by default and you can offer the option to use fallback data when it seems more accurate (maybe when the device hasn't been able to get a fix since the last time it reported back).
Notes
I'm not sure if this is an issue with decoding the data or using the data as a fallback. If it is an issue with decoding the cell tower positioning data then this datasheet will probably help: https://wiki.teltonika-gps.com/view/TAT140_AVL_ID_List
The text was updated successfully, but these errors were encountered:
Description
I haven't looked at the raw data, but according to the engineers at Teltonika the TAT140 reports cell tower (LBS) positioning data along with the standard GNSS data, in the same way that the TAT100 does. It would be great if Traccar servers would use this positioning data when the device report "no fix" for its latest satellite position.
Additional Information
It appears that you already decode cell tower positioning data (here). I'm not certain how this data is then processed, however from testing with a device it appears to stop updating the position (on your server dashboard) when a satellite position can't be fixed, even though it should be able to use the cell tower positioning data as a fallback.
Alternatives
Any secondary positioning data could be stored separately. That way the server dashboard could remain the same (only showing satellite positions on the map) by default and you can offer the option to use fallback data when it seems more accurate (maybe when the device hasn't been able to get a fix since the last time it reported back).
Notes
The text was updated successfully, but these errors were encountered: