@Tjark There is an updated voxl-px4 here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.116-202510301051_arm64.deb. You will also need an updated libfc-sensor library here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/libfc-sensor_1.0.8-202508141142_arm64.deb. Can you try to update with these 2 and see if it solves the issue?

@l05 can you try running the ./make_package.sh script inside docker? also if you are just trying to deploy your app, you can copy it directly from voxl-mpa-tools/build64/tools, to voxl2 using adb or ssh (assuming the build itself succeeded).

Alex

@SKA ,

In your case, the issue should be solved by commenting out one line in https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/eis/src/misp.cpp :

//TODO: FIXME //in roll following mode, the roll is not stabilized to the horizon, so it does not need to be flipped //need to resolve this in a better way because Rout is meant for another purpose if (!follow_roll) rc_matrix_right_multiply_inplace(&eis_ctx.H.m, eis_ctx.Rout.m); //rotate the image according to desired output rotation (nominally identity)

Specifically, comment out the if statement : if (!follow_roll) , so that the Rout matrix is always applied to the full transform H.

The issue is that I tried to solve another use case by using this parameter (when the voxl2 / IMU is flipped upside down while camera is right side up). I just tested and it appears to be working.

I will figure out a better way of handling the upside down IMU in this case so that the output transform can be used correctly, but for now you can just comment out that if statement.

Can you please let me know if that fix worked for you?

Alex

@Robbie-McCue worked, thanks so much!

@Eric-Katzfey

Ok thanks for you clarification, I will try it and see how it goes.

@jimbow77 , regarding #4, there are four batteries (two sets).

#3 - we don't have an option to install FLIR Lepton, but you can purchase it separately (from another vendor) and install it. The adapter is present in Starling 2 Max, so you would just need to install the Lepton sensor into the socket.

Alex

@ravi

Find the VOXL2 app versions.

voxl2:/$ voxl-version ──────────────────────────────────────────────────────────────────────────────── system-image: 1.8.02-M0054-14.1a-perf kernel: #1 SMP PREEMPT Mon Nov 11 22:08:01 UTC 2024 4.19.125 ──────────────────────────────────────────────────────────────────────────────── hw platform: M0054 mach.var: 1.0.0 SKU: MRB-D0006-4-V1-C11-T1-M23-X0 ──────────────────────────────────────────────────────────────────────────────── voxl-suite: 1.4.4-202504302200 ──────────────────────────────────────────────────────────────────────────────── Packages: Repo: http://voxl-packages.modalai.com/ qrb5165 dev Last Updated: 2025-05-01 18:00:20 List: kernel-module-voxl-fsync-mod-4.19.125 1.0-r0 kernel-module-voxl-gpio-mod-4.19.125 1.0-r0 kernel-module-voxl-platform-mod-4.19.125 1.0-r0 libfc-sensor 1.0.7-202503131014 libmodal-cv 0.5.17-202504301813 libmodal-exposure 0.1.4-202504301817 libmodal-journal 0.2.4-202504250956 libmodal-json 0.4.6-202504301809 libmodal-pipe 2.13.0-202504211020 libqrb5165-io 0.4.9-202504291621 libvoxl-cci-direct 0.3.1-202504301829 libvoxl-cutils 0.1.4-202504301826 modalai-slpi 1.1.20-202504131441 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0-202309221318 qrb5165-imu-server 1.2.0-202504241319 qrb5165-mini-tof-server 0.2.2-202504291141 qrb5165-rangefinder-server 0.1.5-202502211754 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.3.5-202503241242 qrb5165-tflite 2.8.0-2-202210071637 voxl-benchmark-vio 0.5.7-202504041555 voxl-bind-spektrum 0.1.1-202403271220 voxl-camera-calibration 0.5.9-202411191414 voxl-camera-server 2.1.2-202504281425 voxl-capture 0.0.1-202206110121 voxl-ceres-solver 2:1.14.0-10-202504291324 voxl-configurator 1.0.1-202504301741 voxl-cpu-monitor 0.5.3-202504231157 voxl-cross-template 0.0.1-202504171512 voxl-docker-support 1.3.1-202404041529 voxl-elrs 0.4.4-202504041253 voxl-esc 1.5.2-202504292017 voxl-feature-tracker 0.5.2-202412171357 voxl-flow-server 0.3.6-202403180603 voxl-fsync-mod 1.0-r0 voxl-gphoto2-server 0.0.10-202210072352 voxl-gpio-mod 1.0-r0 voxl-iim-server 0.0.3-202503210929 voxl-io-server 0.0.5-202502191136 voxl-joystick-server 0.0.1-202504291738 voxl-jpeg-turbo 2.1.3-7-202504301743 voxl-lepton-server 1.3.3-202412171302 voxl-lepton-tracker 0.0.4-202412190958 voxl-libgphoto2 0.0.4-202204111958 voxl-libuvc 1.0.7-202210072357 voxl-logger 0.5.3-202504141224 voxl-mavcam-manager 0.5.8-202504080850 voxl-mavlink 0.1.5-202504301802 voxl-mavlink-server 1.4.7-202504291641 voxl-modem 1.1.6-202504301834 voxl-mongoose 7.7.0-2-202504301848 voxl-mpa-to-ros 0.3.9-202407091506 voxl-mpa-tools 1.3.8-202504221446 voxl-open-vins 0.4.18-202504301757 voxl-open-vins-server 0.3.10-202504071452 voxl-opencv 4.5.5-3-202504301748 voxl-osd 0.1.6-202504241636 voxl-platform-mod 1.0-r0 voxl-portal 0.7.10-202504240926 voxl-px4 1.14.0-2.0.104-202504231041 voxl-px4-imu-server 0.1.2-202205131833 voxl-px4-params 0.7.0-202504301738 voxl-qvio-server 1.1.1-202411151825 voxl-remote-id 0.0.9-202309191605 voxl-reset-slpi 0.0.1-202405130827 voxl-rpx-server 0.0.1-202409271312 voxl-rtp 0.0.1-202206101543 voxl-state-estimator 0.0.5-202504181708 voxl-stitcher 0.0.2-202206161634 voxl-streamer 0.7.5-202412021550 voxl-suite 1.4.4-202504302200 voxl-tag-detector 0.0.4-202206302112 voxl-tflite-server 0.4.1-202504301555 voxl-utils 1.4.7-202504301851 voxl-uvc-server 0.1.7-202405141018 voxl-vision-hub 1.8.21-202504291456 voxl-vtx 1.3.13-202504291344 voxl-wavemux 0.0.1-202503181201 voxl2-io 0.0.3-202405011635 voxl2-system-image 1.8.02-r0 voxl2-wlan 1.0-r0 ──────────────────────────────────────────────────────────────────────────────── voxl2:/$

@wilkinsaf Do you happen to have any experience with this?

@chengyouzen , have you tried building OpenSSL from source (you should be able to do it directly on VOXL1)? That may be the only way..

Alex

@tom Thank you for the assistance on the previous topic. Is there a best way to diagnosis the navigation? The path appears fine, but the drone few straight upward into the ceiling before falling and breaking one of main battery clips next to the LED board.