Closed MCFurry closed 2 years ago
Hi @MCFurry thank you for your comment. To clarify, right now there is no value of any type populating the NavSatFix Status field?
Exactly, it seems that the other fields are filled, except for the Status struct. ROS will therefore create the message with default field-values of zero. So in this case, the driver is actually claiming to always have an 'unaugmented fix' without any gps services used (gps/glonass/glaileo) as per definition of the NavSatStatus. Which is why I found it appropriate to issue this as a bug.
Hi @MCFurry thank you for the additional details. Can you confirm this bug is present in the most recent release? Recently there was work done to address issues similar to what is described.
Can you please confirm the issue is present in the most recent release @MCFurry ? Thank you!
Excuse my late answer, but yes, I can confirm the issue is still present!
This issue is now fixed as of 4.0.0. If the issues seems to persist, please collect a rosbag with all topics and send it to support.novatel@hexagon.com for further evaluation. Any questions or concerns please let us know.
It would be really helpful if the
status
field of the NavSatFix message (/gps/fix) would actually be populated. This field is of type NavSatStatus and hence resembles the fix-status and gnss-services in use. At this moment it is not and we have to get this information from other Novatel topics.