@Seungjae-Baek [image: 1763679737134-image.png] [image: 1763679737747-img_0429-resized.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

@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).

Hi @dylangresham Stinger is intended to be a complete drone package for developers, integrators, and system providers who do not require additional customization. We believe it includes all the necessary functionality for the FPV use case. Starling 2, Starling 2 Max, and the PX4 Developer Editions, on the other hand, are designed to be customizable platforms that developers and integrators can modify to suit their specific products and use cases. By design, these are not fully Blue List–certified turnkey drones, since any additions, removals, or changes made by the end developer would require recertification. That said, because most (if not all) of the subcomponents used in these platforms are already listed on the Blue UAS components list, the end-user certification process should be straightforward. ModalAI parts will pass screening easily thanks to their existing certifications. I hope that clarifies the rationale.

@Eric-Katzfey Thank you for reverting back. I am trying to proceed with the same approach. I am facing some errors while going with this approach , I am trying to debug them. Another approach :- I am also thinking to hardcode the joystick based turtle mode to the voxl_esc.cpp. The manual control values will be monitored and once the value of the assigned button is clicked, the turtle mode will be enabled. Do you think it is a good approach?

You will need the SKU supporting the TOF to accurately run current versions of voxl-mapper and VOA. Zach

The system has an HDMI out so you can plug it into an external monitor yes: https://docs.modalai.com/vrx-ground-unit-developer-guide/

@Ido-Goldstein to run yolov8 run voxl-configure-tflite-server and then when it prompts you to select your model, you can select yolov8. YOLOV11 is also currently supported however is still CPU bound so I would recommend using yolov8 for GPU processing

@Eric-Katzfey hey, I observed something while the above behaviour still persists. The modem and the camera server is showing not running while checking through the inspect services command. I do not know whether this is related to this issue, but the voxl 2 is rebooting after sometime, the reboot is not constant and I am not able to able to find the reason for the reboot. Can everything be related to each other. I am using the Microhard modem [image: 1762769045502-screenshot-from-2025-11-10-15-27-45.png] [image: 1762769045568-screenshot-from-2025-11-10-15-30-27.png]

Also, a quick note.. regarding what preview resolution to use with IMX412 camera with MISP enabled.. For best quality (non-EIS applications, where the output is 16:9 aspect ratio, such as 3840x2160, 1920x1080, 1280x720), you should select 3840x2160 as the preview resolution. For EIS applications, the full frame 4040x3040 resolution should be used because it will allow more stabilization margin. selecting 3840x2160 will tell the camera to crop this region from the full frame 4040x3040, since we don't need the rest of the image. For low latency applications, you can use input resolution of 1936x1080. Note that this is slightly non-standard (as opposed to 1920x1080 because the 1936x1080 resolution allows faster processing. So you could have input resolution of 1936x1080 and output resolution of 1920x1080, 1280x720, etc. Alex

@alan123 If it keeps reporting changing to a new UART baudrate then that's an indication that it isn't connecting at all to the GPS unit. You could also put an oscilloscope on the lines to see if you can detect traffic from the GPS and from VOXL 2.

Hi @snowt33nshi All of our ucoax based image sensors use the same cables. Be careful mating adapters to sensors as they are not all compatible as noted here: https://docs.modalai.com/micro-coax-user-guide/ Hope this helps.