You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have observed that the filter LLH message always reports a status of -1, or NO_FIX, even when the filter has an accurate fix and reports a stable status in /ekf/status. This causes issues with a downstream component we are using that is looking for a valid NavSatFix message.
We are using the CV7 INS on ROS2 with a GPS connected directly to the device GPIO.
To Reproduce
Steps to reproduce the behavior:
Set up a GPS device to send NMEA messages to the CV7.
Launch the ROS2 node with the attached params.
Inspect the status.status field of the NavSatFix message on topic /ekf/llh_position.
Expected behavior
The status field should report 0 (STATUS_FIX) when the filter has a valid fix.
Environment (please complete the following information):
Describe the bug
We have observed that the filter LLH message always reports a status of -1, or
NO_FIX
, even when the filter has an accurate fix and reports a stable status in/ekf/status
. This causes issues with a downstream component we are using that is looking for a valid NavSatFix message.We are using the CV7 INS on ROS2 with a GPS connected directly to the device GPIO.
To Reproduce
Steps to reproduce the behavior:
status.status
field of the NavSatFix message on topic/ekf/llh_position
.Expected behavior
The status field should report 0 (
STATUS_FIX
) when the filter has a valid fix.Environment (please complete the following information):
Modifications
None.
Launch Parameters
microstrain_params.txt
The text was updated successfully, but these errors were encountered: