@Alex-Kushleyev Awesome! Thanks again for all your help with this!

@Jeremy-Frederick , please check the following:

try explicitly stopping PX4 before scanning for the ESC using voxl-esc python tools : systemctl stop voxl-px4 try another 4-pin uart cable, if available test another ESC the same way, if available

Was this ESC + board combination working before at stopped working?

Alex

Nevermind, was being talked about in https://forum.modalai.com/topic/4121/compass-errors

@James-Strawson
"takeoff_cam": Tells OpenVINS which camera to use for takeoff. This should be a camera where "is_occluded_on_ground" is set to false in vio_cams.conf. Besides this setting, what else needs to be configured?

@claw Not at this time as ROS2 takes up a lot of space so we don't include it by default

@swickliff No, it hasn't. Supposedly all of this is fixed in latest mainline but we haven't tested it. But we do have a mainline build available to try: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.0-202502271326_arm64.deb

@Maanav-Iyengar , you can try to move the camera to J6L and use sensormodule with ID 0.

If that does not work, then the issue is most likely not in VOXL2, but somewhere upstream (M0135 or farther up)

If you have another camera, you can try plugging it in instead of IMX412, so this would test the M0135 + M0036 path. Any camera would do, but you would just need to set up the correct sensormodule .

If you use any other camera for testing, which already has a flex on it (unlike M0107 IMX412), then you can skip the M0036 extension flex (you can test with and without it). If you use tracking camera, keep an eye on pin1 orientation, as it is backwards compared to hires cameras.

Alex

@nekolny , please check this post: https://forum.modalai.com/topic/3232/disable-gps-and-compass

you can disable GPS by unplugging it or edit /etc/modalai/voxl-px4.conf and set GSP=NONE , but you also need to set the following params to tell EKF to not use the compass if you unplug the gps module (which has compass on it)

SYS_HAS_MAG to 0 EKF2_MAG_TYPE to 5

@Paul-Handrigan , please see this post, depending on which board you have (M0054 or M0154), it may not be possible to use GPIO 46 as input :

https://forum.modalai.com/topic/4200/issue-reading-gpio-1146-pin-6-on-j10-on-voxl2

@tkddnjs825 Hello, can you post the output from the command voxl-version. We urge all starling users to migrate to SDK 1.4.1.

Hello @Alex-Kushleyev,

Thank you for the confirmation.
It has helped us decide upon the architecture for the current and an upcoming project.
The suggested M0141 add-on is really helpful suggestion as well.

Regards,
Ashwin

@Eric-Katzfey Thank you for your work!
It successfully resolved the issue. The unexpected characters no longer appear on the OSD.
I appreciate your support and quick response.

@dongsup-seo I would recommend flashing the latest SDK (1.4.1) as that will have much better handling for M0054-1/2, I think a lot of that logic was missing on 1.1.3 as that is very old.

Thank you for your detailed response!

It has already addressed much of the urgent information we needed.

We look forward to receiving more details on the props and speed.