Fixed the problem already, had to disable channel mapping in the configurations of the protocol in the controller. Thank you.

@A-Evans You're welcome, glad I could be of assistance. You do have to tighten the nuts well, but not white knuckle tight. You will feel it tighten and then give it an extra little after that. We have been trying to source any of the nuts but they are all out-of-stock. You can check any hobby store or Amazon. If you're trying to get the lock nuts, look for the aluminium ones. There's a lot of steel ones available. You're looking for M6's

@modaltb Thanks for this, managed to just reinstall a few packaged from there, bit nervous to go the factory reset, we've had the drone for a while now but we are going to try a first flight soon. seems okay.

Hi @mkwan , I'm not positive if resolved but there's newer SDK available, any chance you can try to update? voxl2_platform_0.9.tar.gz https://developer.modalai.com/ https://docs.modalai.com/platform-releases/#install I can have someone test this out on 0.9 release next week as well.

@tangotoo You can see the specs here: https://docs.modalai.com/sentinel-functional-description/

Thank you very much I'll try that

@McMason That is how we usually calibrate our sensors, you should have no issue doing so. I will send your camera calibration files to the email you have registered with the forum.

Thank you @Chad-Sweet. Have you seen any issues with connecting a graupner receiver output to pin11(uart rx) on J19? Just looking for RC input without taking up more space with the IO board, and due to specifics we cant use certain radios. I cant find too much data on if the receiver has an inverted signal like the FrSky does.

Yes, the Sentinel 3D STEP files can be found here: https://docs.modalai.com/sentinel-functional-description/#3d-step We do not have the 3D STEP file for Seeker available, but the CAD model for VOXL-CAM can be found here: https://docs.modalai.com/voxl-cam-datasheet/

@Alex-Gardner said in Sentinel VOA software not available: platform 1.3.1-0.8 Yes, it worked! I am able to see correct data via voxl-vision-px4 -s and use PX4's Collision Prevention feature. The drone was shipped with system-image: 1.2.1-M0054-14.1a-perf and voxl-suite: 0.7.0, but after flashing to Voxl2 Platform 1.3.1-0.8, VOA worked out of the box as described. (Note: during the flashing, I noticed the Sentinel documentation does not list this newest release.) To others reading this, some tips: Use your /data folder to backup any files you don't want wiped, such as changes to /home/root. In QGroundControl, save your factory params so you don't have to recalibrate your sensors. (Parameters -> Tools -> Save to file...) Run and save apt list --installed in case there's some apt packages you don't want to forget. Don't forget to redo the parameters in QGroundControl as mentioned in the VOA documentation. Thanks, @Alex-Gardner!