Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GX5 publishes incorrect data on EKF topic #371

Open
ilansmolySR opened this issue Jan 1, 2025 · 2 comments
Open

GX5 publishes incorrect data on EKF topic #371

ilansmolySR opened this issue Jan 1, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@ilansmolySR
Copy link

Describe the bug
Problem in /ekf/imu/data topic with 3DM-GX5-AHRS:
The robot is not moving but the linear accelearion is far from 0.
The roll, pitch are fixed to 0, and the yaw is fixed to 90.

image

When we connect 3DM-GV7-AHRS everything seems normal
image

But we need compatability with both types of sensors.

To Reproduce

  1. Launch Node with command roslaunch microstrain_inertial_driver microstrain.launch
  2. See Error

Environment (please complete the following information):

  • OS: Ubuntu
  • ROS Version: noetic
  • Sensor(s): 3DM-GX5-AHRS
  • docker environment

Launch Parameters
If you have an updated params.yml file, please attach it to this issue.

@ilansmolySR ilansmolySR added the bug Something isn't working label Jan 1, 2025
@github-actions github-actions bot added the New This issue is new, and should not be marked as stale label Jan 1, 2025
@ilansmolySR
Copy link
Author

params.txt

@robbiefish
Copy link

Hi @ilansmolySR,

The reason you are seeing different behavior between the sensor has to do with the fact that the heading for the two devices is initializing differently

In your params.txt, you have the following line:

# This line sets the heading source for the GX5-AHRS to None
filter_heading_source : 0

You also have this line:

# This line sets the heading source for the GV7-AHRS to Magnetometer
filter_auto_heading_alignment_selector : 4

Since you are looking at the Linear Accel data quantity which attempts to factor out gravity, the device needs to have a somewhat reasonable estimate for the device's orientation in order to properly factor out gravity.

In order to resolve this issue, I would suggest setting filter_heading_source back to 1

@robbiefish robbiefish removed the New This issue is new, and should not be marked as stale label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants