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
{{ message }}
This repository has been archived by the owner on Jul 18, 2020. It is now read-only.
The novatel_span_driver reports a error with the new OEM7: Invaled Message...
And no coraviation data will send to ROS... the covariance data stay at 0.0
Is it possible to send both command and add a parse for the INSSTDEVS data. So the novatel_span_driver support OEM6 and the new OEM7 firmware.
The text was updated successfully, but these errors were encountered:
@littleprojects - Would you mind submitting a Pull Request which contains the functionality to pass a "Receiver Model" parameter with valid values being OEM6 and OEM7 as well as parsing this message if OEM7 is chosen? There are other differences as well, especially on the command side.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The new Novatel software OEM7 dont support the command: INSCOVS
See changlog: https://docs.novatel.com/OEM7/Content/Integration_Guide_OEM6_OEM7/Logs_OEM6_to_OEM7.htm?TocPath=New%20for%20OEM7%7COEM6%20to%20OEM7%20Integration%7C_____2
The command: INSCOVS is replaced by INSSTDEVS
The novatel_span_driver reports a error with the new OEM7: Invaled Message...
And no coraviation data will send to ROS... the covariance data stay at 0.0
Is it possible to send both command and add a parse for the INSSTDEVS data. So the novatel_span_driver support OEM6 and the new OEM7 firmware.
The text was updated successfully, but these errors were encountered: