-
Notifications
You must be signed in to change notification settings - Fork 65
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
Make an ROS 2 topic for BMI088 IMU data (gyro and accelerometer) from Crazyflie 2.1 #601
Comments
Hi! We don't have a default topic for IMU values yet for Crazyswarm2 (see the overview here) So the only way now is to make a custom log in crazyflies.yaml: https://imrclab.github.io/crazyswarm2/usage.html#crazyflies-yaml But if you'd like to add this default topic to Crazyswarm2 it would be a nice addition as a pull request. Let us know if you need any assistance with that. |
Hi,
I have to error :
For the crazyflie_server.py i add this part in the script :
and :
and added a IMU calback :
After that I did :
But no topic /imu_data was published ! Thank you by advance for your help |
Hi! In 1. did you source the terminal where you retrieved the ros2 info with the crazyswarm2 package info? and in 2. It might be that you are hitting the maximum of the crazyflie logging variables, which is only 26 bytes (see the documentation here). I do wonder why the odometry ever worked then... (update: it's before of the FP16 notion, forgot about that! ) Could you try less variables for imu_data? |
Also just to add here, at 1. it probably won't work with that slash, so try it with imu_data instead |
Hi,
I am working with the Crazyflie 2.1 and trying to extract IMU data (gyroscope and accelerometer) under ROS2.
I noticed that variables like gyro.x, gyro.y, gyro.z, and possibly acc.x, acc.y, acc.z are available via LogConfig.
However, I couldn’t find a default ROS2 topic like /imu for these values.
Is there an existing configuration or script in this repository to publish IMU data to ROS2 topics?
Thank you for your assistance!
The text was updated successfully, but these errors were encountered: