Yes, after adding some foam, The UAV now are stable than a bit. Do you think the battery should be problem? Our 3S battery are quite old.

Edit: reverting to original driver returns the functionality to default (upside down feed)

voxl-i2c should be pretty straightforward. Just send the i2c commands and get the data. The VOXL platform has a large amount of flexibility and expandability, you should be able to do what you need with a few i2c commands.

Hi @Kaiba-Kun , Hmm, we normally use voxl-configure-vision-px4 when setting up the vehicle. For the m500, we have a -f option which will set it to factory state with respect to voxl-vision-px4, so voxl-configure-vision-px4 -f The camera configs in the ENV variables should be fine after this. I'd try that option above, if you've configured your GCS IP address in the config file needs to be updated, eg. vi /etc/modalai/voxl-vision-px4.conf and setup your GCS IP after running with the -f flag. After that, I'd then reboot the system, and then do a 'hand flight' validation, where you can pick the vehicle up and move around, validating local position NED in QGC. Here's a video where I do this: https://youtu.be/gTuSaHLCz8w?t=571

@Chad-Sweet oh my godness. My mistaken, i didn't realise that before that i had configured UAV off board mode. when I check the /etc/modalai/voxl-vision-px4.conf the offboard_mode ="figure_eight" => so that's why it's cause the problem here. anyway, it's work again, thank you so much for the effective support

@Vũ-Văn-Long wow amazing goodjob

@Chad-Sweet hi. i am reading mavros document now. Thank for your guide.

That aligns with what we have posted on the datasheet here

Little more detail, we've validated with FrSky X8R reciever and Taranis X7 transmitter with the following setup: [image: 1601652797927-3c237719-e867-4ed7-908c-cb2db6cef7d1-image.png] We have a new cable about to come out to assist with this wiring as well: https://docs.modalai.com/cable-datasheets/#mcbl-00018