-
Notifications
You must be signed in to change notification settings - Fork 141
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
Repeated messages from gpsd_client #3
Comments
I am also having the same issue. @hordurk , were you able to verify that your solution works reliably? |
This patch no longer applies, |
Are you using NMEA or binary? gpsd tends to want to use binary with ublox. |
The issue occurs in binary mode, according to gpsd logs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if this is a result of my gpsd configuration or my gps units (u-blox 5 series), but I've been getting repeated (not identical) ROS messages published by gpsd_client with use_gps_time off:
As can be seen in the above, messages 15 and 16 are sent at almost the same time but have different lat,lon values, while 16 and 17 have the same lat,lon but are a second apart. The same goes for the extended fix.
I've tracked down the cause of this and it seems that libgps is receiving the full fix in two separate messages as can be seen using gpspipe:
This results in two gps->read() calls in quick succession and therefore two calls to process_data and then publish. What should happen instead is that the first message (GSV) needs to be read but process_data not called, instead calling it on the second message (GLL). I've done a quick fix for this on my part with the following patch:
But since I don't have another GPS to test with, I'm not sure if this is a good solution to the problem (doubt it).
The text was updated successfully, but these errors were encountered: