Closed ladrians closed 10 months ago
Hi, currently rotation vector is not enabled in the driver, will add option to use it's data this week.
ok cool will be waiting for that. Can you detail if the magnetometer will be available as a separate Rostopic?
Hi @ladrians , you can find details here, in short there will be an option to choose different message types when publishing, either with a custom message that contains both imu and magnetic field message or to have those messages split into two different topics
lgtm! is there a change to port it to noetic branch?
@Serafadam is there a change to backport it to the noetic
branch?
Hi, sorry for the delay, I was away for some time, yes, the newest Noetic branch also has those changes
Closing since the issue was resolved.
Noticed the IMU orientation vector is not calculated.
To reproduce it is just to check the
/oak/imu
topic where the orientation is0 0 0 1
.I am using a
OAK D PRO W
device with a BNO085 IMU.based on the docs I naively did a modification on the
stereo_inertial_publisher.cpp
sample addingBut there are no visible results, finally I could check the orientation is still empty, I am using noetic but the same happens with humble.
Would like to know the plans to integrate a orientation value, or to publish a standalone magnetometer topic? Currently we are using a 9 axis external IMU and using the madgwick filter node to get and absolute reference for the IMU output. We want to use the integrated IMU from the camera to keep configuration as simple as possible, the expected output for us is to get an absolute orientation for outdoor navigation.
Is there a sample code I could integrate to check if the information can be published?
Related information I could find, here and here.
system log
depthai-ros
built from sourcedepthai/depthai-core
library installed from rosdep