@taiwohazeez , the image is indeed blurry. Did the camera come like this or did something happen to the camera / lens?

Also, i am assuming that the blur is not coming from the camera moving around (that is to say the camera is stationary during those image captures).

Please inspect the lens on the outside to make sure it's not scratched or damaged, as this can also contribute to the issue.

In any case, adjusting focus on a camera is usually as simple as turning the lens slightly CW or CCW. Since the image is almost focus, i expect that the adjustment would be within 1 full turn from the existing lens position in the lens holder. If the camera lens is being held by a plastic mount, it should have a screw on the side of the plastic mount, which clamps the mount around the lens. The screw needs to be loosened and then you can use the focus tool to turn the lens slightly while looking at the image view in voxl-portal. For this particular camera with a wide lens, the hyperfocal distance will be around 10cm, meaning that when properly focused, everything beyond 10cm away should appear in focus. With this in mind, you should some target (checkerboard is fine) 0.3 - 0.5m away and turn the lens back and forth (with the plastic tool) to try achieve the best focus. If you cannot achieve good focus (the best focus is still blurry), it probably means that either the lens is damaged dirty (front or back side of the lens).

If you do unscrew the lens all the way out (by turning counter-clockwise until the lens comes out), don't leave the camera exposed like this for a long period of time, so that dust does not get on the camera sensor.

Also, what is the exposure and gain reported in the stats below the image in the voxl-portal view, when you view the camera stream (without the calibration). The environment seems pretty dark, i would recommend more lighting, but let's double check the reported exposure and gain (from auto exposure). Also, please make sure your checkerboard pattern is as flat as possible (this is unrelated to blurry image, but will result in better calibration results).

Please try focusing the camera and let me know if you have any questions.

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