Skip to content
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

Closed
zirinisp opened this issue May 26, 2022 · 9 comments
Closed

GPS Location Reported to Signal K Incorrect #90

zirinisp opened this issue May 26, 2022 · 9 comments

Comments

@zirinisp
Copy link

zirinisp commented May 26, 2022

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:

FIX TIME LATITUDE LONGITUDE
5/26/2022, 7:28:05 AM 37.857509 24.782490

Which is in line with the one reported from the first 2 devices.

@nmbath
Copy link

nmbath commented Jun 30, 2022

I am having the same issue. Any ideas?

@nmbath
Copy link

nmbath commented Jun 30, 2022

The issue lies in line 99 and 100. The data is being read as little endian and is actually in big endian. Changing the two lines too

const modemLat = Buffer.concat(data.slice(0, 2)).readFloatBE();
const modemLon = Buffer.concat(data.slice(2, 4)).readFloatBE();

fixes it for me.

image

@bergie
Copy link
Member

bergie commented Apr 27, 2023

This is weird, I'm unable to reproduce:

Screenshot 2023-04-27 at 11 12 39

@sillymander
Copy link

Confirmed that code should be bigendian for the RUT 955

@nmbath
Copy link

nmbath commented Jul 22, 2023

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.

@msirolla
Copy link

I have the exact same issue, using latest software. Server running on Cerbo GX, wired via LAN into a Teltonika RUTX11 with latest firmware.
Would it be possible to have a fix?

dsuckow added a commit to dsuckow/signalk-teltonika-rutx11 that referenced this issue Jan 6, 2024
@dsuckow
Copy link
Contributor

dsuckow commented Jan 6, 2024

Have a RUTX11 and it seems also provided as big endian, added a config parameter to switch between big endian and little endian.

@msirolla
Copy link

msirolla commented Jan 6, 2024

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 🙂

bergie added a commit that referenced this issue Jan 7, 2024
read gps data as big or little endian (issue #90)
@bergie
Copy link
Member

bergie commented Jan 7, 2024

Should be fixed in 0.6.0 thanks to #125

@bergie bergie closed this as completed Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants