-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPS Location Reported to Signal K Incorrect #90
Comments
I am having the same issue. Any ideas? |
Confirmed that code should be bigendian for the RUT 955 |
Just done an upgrade, and wondered why things had behaved incorrectly. Seems like this has not been fixed. My system is reporting me as just north of the equator, when I am in the UK. Modified my local install again. |
I have the exact same issue, using latest software. Server running on Cerbo GX, wired via LAN into a Teltonika RUTX11 with latest firmware. |
Have a RUTX11 and it seems also provided as big endian, added a config parameter to switch between big endian and little endian. |
Many thanks! Would you be so kind to please provide basic instructions on how I can get your update into my Signal K system? I’m still new at this 🙂 |
read gps data as big or little endian (issue #90)
Should be fixed in 0.6.0 thanks to #125 |
I am getting the following positions reported under the data browser on my signal k server.
The first 2 are from my plotter and the gps antenna attached to my raspberry. The last one is the one reported from teltonika and the values are incorrect or have a different format than the one expected.
navigation.position | { "longitude": 24.78245, "latitude": 37.8575033 } | | 05/26 10:24:56 | 1.1 (129039)
navigation.position | { "longitude": 24.78244, "latitude": 37.85752333333333 } | | 05/26 10:24:57 | gps_pi.GP (RMC)
navigation.position | { "latitude": 7.693130305972483e-25, "longitude": -3.7512190583080584e-32 } | | 05/26 10:24:32 | signalk-teltonika-rutx11.XX
When I go to the teltonika interface and check my position I get the following:
Which is in line with the one reported from the first 2 devices.
The text was updated successfully, but these errors were encountered: