Team,
I'm working with the OAK-D on the stingray.
Since in has a built-in IMU, I thought I'd give it a try.
In Rviz2 its orientation is far from that of the robot. (see attachment 1.)
I went a couple rounds in VSCode with CoPilot/Claude-Sonnet-4.5 which assured me that since the IMU published its orientation, the EKF would figure it all all so don't worry about the Rviz2 orientation.
However in practice, the robot appears disoriented and travels in the opposite direction. (see video attachment 2.)
Has anyone else used the OAK-D IMU? Does it line up in Rviz? How did you get it to do so?
Does it behave in action? Any particular configuration tricks?
James
-- James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
attached ekf_odom_params.yaml fyi.
James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
--
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/75d6568b-6df6-4ad9-b547-8e3c57b247fd%40hal-pc.org.
To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/13a49a35-8ba3-4d6c-aaf0-dc2f57789041%40gmail.com.
Sergei,
I could rotate the BNO055 axes to fit easily. The OAK-D is different since it's integral to the camera.
I really don't understand why the OAK-D IMU axes aren't exactly the same as the camera except, perhaps, a final video frame rotation.
I went through all kinds of hoops with VSCode/Claude trying to orient the IMU axes and it just took me deeper into the weeds. Claude is usually the best coder and in VSCode has the advantage of being able to see, modify, run and evaluate the output of the code. I may give another AI a try.
James
James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
On Dec 21, 2025, at 3:43 PM, 'James H Phelan' via HomeBrew Robotics Club <hbrob...@googlegroups.com> wrote:with CoPilot/Claude-Sonnet-4.5 which assured me that since the IMU published its orientation, the EKF would figure it all all so don't worry about the Rviz2 orientation.
Michael,
The EKF just listens to the topic, I think, and, supposedly, that publishes the orientation and it's supposed to figure it all out according to Claude.
The first attached pic in the original message is of the orientation in Rviz.
The EKF .yaml is in the second message.
The AI tried adding links/frames and rotating them but nothing changed in Rviz.
The support for the BNO085 is pending reopening of the Fab Lab after New Years.
But surely (?) someone else has made use of the OAK-D IMU without having to write some convoluted translation node that Claude was attempting?
James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
--
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/55A192D4-B525-4CC9-BB13-2D946E826D84%40gmail.com.
Thanks, Marco!
I'll have to dig into this.
James
James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/b9d66f73-9c90-4329-b5b8-454dea46587d%40hal-pc.org.
Sergei,
I mean the little piece of plastic that supports the IMU between the wheel axles.
The screw spacing for the BNO085 is different than the BNO055 so I'm making a new one.
James H Phelan "Nihil est sine ratione cur potius sit quam non sit" Leibniz
To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CA%2BKVXVMLtRtgSXBB%2BmKanEYkLuKMp%2B6XABEhr%3D57fu%3D3AcxDRA%40mail.gmail.com.