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
Create a script to track the drivetrain positioning over time. Ideally, it would be something that gives us the gps coodinates as well as the tilt angle (maybe acceleration measurments too? Whatever you can pull) as measured from the IMU - and just have an easy way of streaming in all of that data. You can look into using RVIZ for that, maybe you won't need to create anything externally.
This involves choosing a 'correct' orientation for our IMU. We should define how it should be oriented according to the ROS convention: https://www.ros.org/reps/rep-0145.html.
The text was updated successfully, but these errors were encountered:
Is your IMU frame defined anywhere? In order to see something happening, ros needs to know about your fixed "IMU" frame. You can add that to a urdf file. It would end up looking something like this: https://navigation.ros.org/setup_guides/odom/setup_odom.html (scroll down to the IMU section and see the and tags. Essentially, you define where it is on the robot, then can have it as a fixed frame in rviz, where you will see everything around it moving
Create a script to track the drivetrain positioning over time. Ideally, it would be something that gives us the gps coodinates as well as the tilt angle (maybe acceleration measurments too? Whatever you can pull) as measured from the IMU - and just have an easy way of streaming in all of that data. You can look into using RVIZ for that, maybe you won't need to create anything externally.
This involves choosing a 'correct' orientation for our IMU. We should define how it should be oriented according to the ROS convention: https://www.ros.org/reps/rep-0145.html.
The text was updated successfully, but these errors were encountered: