Closed ozzdemir closed 3 years ago
@ozzdemir this should be handled as a support case with NovAtel Customer Support. You may start a case by reaching out to us at support.novatel@hexagon.com. Please reference this issue (https://github.com/novatel/novatel_oem7_driver/issues/14), so we can refer to the original information you provided in GitHub. Once the support case is open I'll send you a link to a location where you can also upload sample data such as bag files.
Thank you, talk to you soon, NovAtel Customer Support
Describe the bug When we are using novatel_oem7_driver, we observed that corrimu log is continuously conflicting. It can be seen in the two figures below. First one is timeseries plot of it and second one is the datapoint only version of it.
Expected behavior IMU should report correct acceleration and rotational velocities.
Screenshots
Environment (please complete the following information):
Additional context Following init command is used to initialize the driver using both from eth, and serial; no change. std_init_commands.zip