Topics created by xav04

@xav04 , yes, please see https://docs.modalai.com/voxl2-io-user-guide/

I should have posted this earlier, but I was able to make my IO board work with sbus by building my own version of Px4 based on your guy's master branch. For anyone else coming across this post, @Eric-Katzfey solution should work.

@Eric-Katzfey In my case I am receiving data as @Alex-Kushleyev explains with

stty -F /dev/ttyHS2 115200 cat /dev/ttyHS2

e1b7860f-60b8-4441-a7f9-c4147a44b66c-image.png

and in the script in /usr/bin/voxl-px4-start I see that section @Eric-Katzfey
6bd3d8f4-b89b-4fa6-ad40-5c58260d333b-image.png

but when it comes to running voxl-px4 it autodetects with different bauds to the GPS. Is it necessary to change it somewhere else?
e7941c5d-6d4b-4a0c-b5ab-a9e4130ef09b-image.png

I have no problems with the MAG. It detects it perfectly.
I have the RX and TX of the GPS connected exclusively to the J9 of the 5G, and the rest, to the J19.

I also have the RX and TX of the IO Board connected to the RX and TX of the J19.
I have also tried disconnecting the IO Board and leaving only the GPS on the J9.

SOLVED: I change in the file voxl-px4-start from M0052 to M0054. Thanks!!!

@mzahana VIO will definitely be supported. I don't think we are currently using the dds client in any of our applications but there's no reason why it wouldn't work on our platform.

your image of the voa_pc_out point cloud shows that your voxl thinks the TOF is pointing out the top of the drone. This is confirmed by your extrinsics conf sensor rotation: [180 0 0] which translates to a sensor pointing straight up.