@aspen Can you provide the log file? There is a version of px4 v1.16 available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.4-202509030932_arm64.deb

@Hunter-Scott If you delete all logs then fly you don't see any log files afterwards?

@Peter-Milani , it looks like Qualcomm CPU device is not supported by OpenCL library from Qualcomm.

clinfo may be confused, but installing and running clinfo natively on voxl2 does not return any platforms - the opencl libraries that may get installed by apt are most likely not compatible with the VOXL2 GPU.

Alex

Actually, I see from the log that your FPV camera is IMX214 (please confirm).

So then my next questions are:

• which Voxl2 SDK are you using?
• does the crash happen if you only view the Hadron EO stream (this is OV64B camera)
• can you please check the cpu temps when you view many cameras (using voxl-inspect-cpu)

The dmesg error suggests some sort of low level error during MIPI transmission, but it could be tied to the SoC overheating.

When voxl-portal is used to view images (especially in multi-view), the images on VOXL2 are converted from YUV to Jpeg using a software Jpeg encoder (which is very taxing on the cpu for large images). This can cause the cpu to overheat and start throttling operating frequencies to reduce the temperature). We are aware of this issue and it is on the list to fix the multi view to be more efficient and not overheat the CPU.

Alex

@ravi , can you please let me know which FPV camera you are using? also can you share the entire voxl-camera-server.conf ?

Alex

@Muqing-Cao Here you go: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/dev/src/vio_manager.c?ref_type=heads#L450

@Muqing-Cao Just the standard Mavlink ODOMETRY message is what we have used. Not exactly sure how that translates into ROS land. But it isn't anything ModalAI specific.

@latif You should be able to disable the model match feature on the same screen which displayed the "Model Mismatch" error. By setting the model match id to 0, it will ignore the model match id set on the receiver and connect. The ExpressLRS documentation has more detail about how to set up the RC connection here.

@Muqing-Cao Yes, definitely. The applications are auto started using systemd services and can be stopped / disabled using standard commands as desired.

@ashley-miller , for this motor (28xx class), you should use the following ESC M0138 FPV ESC :

https://www.modalai.com/products/m0138
https://docs.modalai.com/voxl-fpv-esc-datasheet/

The mini ESC (M0129) is designed for small and lightweight drones and mini FPV racers (750g or less for slow flyers and 500g or less for mini FPV drones).

The peak power for one of these motor is almost 1kW each - the mini ESC cannot handle that for several reasons, such as peak current capacity, thermal.

If you would like to use the 2808 motor, please choose the M0138 FPV ESC and perform motor calibration using voxl-esc tools : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md

Also, please review the following FAQ: https://docs.modalai.com/voxl-escs/faq/

Alex