@Seungjae-Baek , the resolution of the camera should depend on the use case. However, it is also important to keep in mind what exactly you are doing with the images coming from the hires cameras. For example, if you set the resolution to 4K and you try to view those uncompressed images using voxl-portal, this process will be very taxing on the CPU for the following reason: when you view uncompressed images in voxl-portal, these images are encoded with a software JPG encoder and then sent from voxl2 to your browser. This process is very cpu-heavy. On the contrary, if you use h264 / h265 stream, it should be perfectly fine to encode 4K30 video to disk or even stream, since H264 / H265 encoding is done by a hardware encoder.

voxl-portal, actually does support showing h264 (but not h265) 30FPS streams, so that would be a lot more efficient for the CPU, since there would be no jpg encoding. Otherwise, if you are using raw frames (not _encoded) in voxl-portal , please keep in mind that you will always have a lot of cpu overhead. voxl-portal is designed for debugging / development purposes, so it's not necessarily the most efficient solution for video streaming. For real video streaming use cases, you would use h264 or h265 encoding and save to disk on voxl2 + stream the encoded video for remote viewing. You could encode the same camera source with two different resolutions / codecs / bitrates.

If you need help setting up a specific use case, please provide some details and I can help you further.

Alex

@cbay ,

We support any camera that is compatible with UVC (plugged into a usb port). Please look into voxl-uvc-server. https://docs.modalai.com/voxl-uvc-server/

Regarding NIR, have you considered using a regular camera (most cameras are sensitive to NIR) and install a lens with a NIR pass filter (if you dont want to see visible light)? Then you could use one of our hi-res cameras like IMX412 or IMX664. I can get you spectral response plot of those sensors if you need.

Alex

@Capstone-0 Our drone crashed and we ditched our project but has ModalAI added support for AT commands for the 5G (I assume EM9291) modem yet? If not, I figured out how to do it and posted instructions here

https://forum.modalai.com/post/19131

Once you get those commands, you can set up a service to query the modem for its signal strength and pump the output somewhere. Someone else in that forum discusses it a bit.

@kabumei
Hello, my name is Naoki, I am keen on this project, could you send me a detail to major.gits501@gmail.com?

@tom Thank you! Submitted the RMA today (22-NOV-2025). Did not get any number or anything, but the following message: a25e2aa8-af17-4b82-8b20-c78ef379e805-image.png

@jmltt SDK testing for Sentinel ended at SDK 1.4.0

That doesn't mean that newer releases won't work, it just means we don't put it through the SW QA testing cycles that we do with our newer platforms.

You likely won't see any major performance improvements on Sentinel with newer SDK releases but there may be some nice quality of life additions such as helper scripts, voxl-portal updates and others.

If you have any questions about any specific packages feel free to ask.

@Seungjae-Baek
image.png IMG_0429.jpg
One more question: Should we use 5G antenna, not LTE? As I know when we buy the 5g modem the default antenna is the one with LTE.

@Cliff-Wong Thanks! I will try this as soon as possible and report how it works out.

@aspen The landing detector in PX4 isn't perfect (obviously) so in this case it didn't detect the landing. I would map one of the switches to toggle between arm and disarm so that when the drone lands you can disarm via switch. Did you try the v1.16 package?

@Peter-Milani , I see. this looks like a generic implementation of OpenCL for ARM from 3rd party (not Qualcomm), and i think it also overwrites the proprietary opencl libraries, disabling the GPU opencl support. However, you could make two separate docker images, one for each use case (cpu and 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

@N-Chen
To anyone reading this, maybe encountering the same issue in the future.
I've tested the board with a guy that has a lot of experience with the voxl2 board,
According to him, the board was faulty, probably some electrical issue, the amperage did not cross 0.1, and the board usually runs on something like 0.5.
I've replaced my board as well as my power-supply cables (which were also under par).

@Maxwell-Schaefer Thank you! I was able to set the model match to off using the controller screen.

@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

@Eric-Katzfey interesting, think you for this information. Once i demo this drone for a couple weeks in its current BNF w/ ndaa add ons configuration I will be looking to move to a smart system and incorporating optical hold and other gps denied search features.

@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

@jeremyrbrown5 we figured it out, we just changed the name of the model to yolov8n_float16.tflite. Pretty spot on now!

@roy-crosthwaite see here: https://www.modalai.com/pages/rma