<![CDATA[voxl-open-vins-server imu_to_cam RPY(deg) different output logs]]>I am currently working with the VOXL 2 and attempting to run the voxl-open-vins-server alongside the voxl-feature-tracker. To configure the system, I set custom RPY (Roll, Pitch, Yaw) values for the drone in the extrinsics.conf file. However, when I attempt to log the values, the output does not match the expected results, and localization is not functioning properly.

Here is the extrinsics.conf file with the custom settings I applied:
78cdf2ea-2c8b-4c26-895c-a8f34c2c215f-image.png

Here is the log output,
8cd64453-6d0b-47bb-bd0a-2a9b90e19206-image.png

]]>https://forum.modalai.com/topic/4051/voxl-open-vins-server-imu_to_cam-rpy-deg-different-output-logsRSS for NodeTue, 19 May 2026 22:10:49 GMTSat, 21 Dec 2024 12:07:58 GMT60<![CDATA[Reply to voxl-open-vins-server imu_to_cam RPY(deg) different output logs on Tue, 21 Jan 2025 16:16:28 GMT]]>Unsure, if you have resolved this so I am going to attempt to help but I am going to need more information if possible. I am unsure how the setup is for the drone seems like you have one camera (Tracking_rear) pointed straight backwards and two cameras (Tracking_front, Tracking_down) facing forward at a 30 degree downward angle?
I am not sure that you are showing with the log output.
Have you tried hand testing using the command voxl-inspect-pose -l and seeing how RPY and translational movement (moving the drone up, right, forward) are behaving for the local frame?

]]>https://forum.modalai.com/post/20550https://forum.modalai.com/post/20550Tue, 21 Jan 2025 16:16:28 GMT