BNO08x ROS2 driver updated

24 views
Skip to first unread message

Sergei Grichine

unread,
Sep 1, 2026, 2:02:07 PM (10 days ago) Sep 1
to hbrob...@googlegroups.com
Hi All,

I updated my fork of the BNO08x ROS2 driver, incorporating the following pull requests:

CMake changes for Lyrical - future-proofing the driver

Add enable_6dof_mode parameter - covers special use case, when mag calibration fails

Please pull the latest code, let me know if you have any issues.

The driver works fine on my Seggy robot under ROS2 Jazzy. BNO085 seems to be the best IMU available for ROS robots.

Thanks to James Phelan and Marco Walther, who took time and effort to submit pull requests.

Please refer to the following notes for more info:
Best Regards,
-- Sergei

Karim Virani

unread,
Sep 1, 2026, 7:57:45 PM (10 days ago) Sep 1
to hbrob...@googlegroups.com
any plans to implement the uart interface? the bno055 driver does support this.

--
You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CA%2BKVXVN4tjFVSyueHD%3D5jbevTN3tid0aO0%3DcGAMq6Od6Z91BPQ%40mail.gmail.com.

James H Phelan

unread,
Sep 1, 2026, 9:05:58 PM (10 days ago) Sep 1
to hbrob...@googlegroups.com

Sergei,

Pulled your updated repo and cleaned up my own.

Tested update & it hunts.

Enjoyed our collaboration.

Credit for Git skills goes to Claude Opus 4.7.

James H Phelan
"Nihil est sine ratione cur potius sit quam non sit"
Leibniz

Sergei Grichine

unread,
Sep 1, 2026, 10:22:46 PM (10 days ago) Sep 1
to hbrob...@googlegroups.com
@Karim Verani:
"any plans to implement the uart interface? the bno055 driver does support this."

Not sure what you mean. The upstream code mentions UART and SPI interfaces (well, at least in the config yaml) - but I don't have a way (or interest) in exploring those paths, I2C works fine for me on RPi.

Feel free to submit a PR if you've tested those and have some code fixes (or even just test results or notes - I'll add them to the docs). 

@Jim Phelan : Great catch and easy communication - thank you and always welcome! All credits go to the man behind the wheel, not the vehicle ;-)

@Everyone - GitHub is a great place for contributing and improving the Open Source code. Pull Requests are the way to do it. You see something - say (open a PR) something.

Best Regards,
-- Sergei


Reply all
Reply to author
Forward
0 new messages