Open federicobenna opened 1 month ago
Hi @federicobenna,
the status generation indeed made no sense at all. Thank you for reporting this.
You may find a fix here. This fix will be added to the upcoming release.
Hi again @thomasemter, Thank you for your quick reply.
The status reported is still quite incosistent across messages. I tested again using the suggested patch and got no fix on /gpsfix
status, "normal" fix on /navsatfix
and proper RTK fix in GGA
msg. Receiver reported RTK fix the whole time instead ...
I suspect the issue is in the way the last_insnavgeod_
or so for other types is parsed or updated?
Sorry, the mask was missing for the status of the /gpsfix
. It should be correct now.
I have mobile robot setup with INS receiver + dual antenna setup and an active subscription with a local RTK provider over internet.
I have been observing a discrepancy between reported status/ gps quality from ros msgs
/gpsfix.status.status
/navsatfix.status.status
and what the Septentrio web ui and the actual NMEA msg logged on the receiver itself.On my tests I see msgs published with status 0 most of the time and jumps to 2 (augmented fix) a couple of times over multiple experiments while the frontend shows Fixed pose and GGA NMEA shows quality indicator 4 (
RTK Fixed
) and GNS mode indicator RRRN (Real-Time Kinematic. Satellite system used in RTK mode with fixed integers
):I gave a quick look at how the messages are generated on the rosdriver and noticed for
GNSS
receiver the status bit is masked while this is not applied forINS
receivers. How should I interpret the data on the nav rostopics?