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.

@dvz , The lens in the MSU-M0149 camera module should come with IR filter installed, which means that you will not be able to detect IR light. You can test with an IR LED or a phone that has an IR scanner (many phones do) or explicitly check for the filter by unscrewing the lens. The IR filters installed in the lenses inside MSU-M0149 are not designed to be easily removable. Attempting to do so will void the warranty and may cause damage to the camera / lens or personal injury. Small pieces of the glass filter could come loose. Do not do it. I just tried to remove the IR filter and i was able to remove it, the filter was broken in process. I unscrewed the lens from the lens holder. The adhesive holding the lens in lens holder, if present, is not permanent and can be scraped off if needed. Then I used a sharp point of an x-acto knife to pry the IR lens off. See images below. We do not have an option to purchase M0149 camera without an IR filter. However, a newer version of this camera (https://www.modalai.com/products/msu-m0166) has an option to select a lens without IR filter. Please note that M0166 camera uses different (ucoax) cables and adapters for connecting to VOXL2, so this is something to consider if you do decide to switch. If you would like to purchase a lens without IR filter (it is very similar to the one in MSU-M0149, but without IR filter, similar overall specs), please send us a request, the part number is JSD5501-C0 (mention no IR filter, just in case). This is the lens shipped with M0166 with no IR filter option. https://www.modalai.com/pages/contact-us Warning : Attempting to remove the IR filter will void the warranty and may cause damage to the camera / lens or personal injury [image: 1761619962288-m0149_ir_filter_removal1.jpg] [image: 1761619969078-m0149_ir_filter_removal2.jpg]

@Jetson-Nano Regarding question #1, Yes, you can attach an external FC over the UART.

@jameskuesel , it looks like EIS was merged to the main branch shortly after SDK 1.5.0 was released. If you have not updated you camera server, please do so : https://docs.modalai.com/camera-video/electronic-image-stabilization/#latest-source-code . You may also need to update libmodal-pipe library. Alex

Hi @Jetson-Nano Here is our info for Doodle Labs support: https://docs.modalai.com/cable-datasheets/#mcbl-00085 Sorry it's buried in a cable page, but it makes the case clear (we think) how to support Doodle [image: 1761072142690-b1fa4a9a-f883-4566-b3e2-ae9ab14b7264-image.png] regarding probing USB signals, unless you had a USB decoder on the scope, I do not think that will prove anything useful. You may be better off running usbview: Windows: USBTreeView by Uwe Sieber — uwe-sieber.de/usbtreeview_e.html It shows enumeration hierarchy, configuration descriptors, endpoints, VID/PID, power requirements, etc. Linux equivalent: Use usbview — it’s essentially the same utility (GTK front-end to lsusb). Hope that helps!

@emarcphera Huh, interesting. Okay, thanks for posting the update!

Hi @will-huang-oksi Are you willing to share some pics? Might be a cabling issue (GND loop or lack of a common GND), or some other intermittent connection causing your problems. It really is hard to debug without seeing the setup. Thanks! Vinny

@tom Thank you for your quick response. Do you have a model with these dimensions and technical specifications that is also waterproof, or is it possible for you to develop one? Thank you again in advance for your response.

@nickrobbins I would take at stinger as a place to start: https://www.modalai.com/products/stinger-vision-fpv?variant=48373207695664 It is on the Blue UAS list: https://www.diu.mil/blue-uas-cleared-list (Stinger Vision FPV)

Hi @Riccardo-Benedetti and @paul-foley , This issue is not common. There is a potential condition (which we are going to look into) when a MPA client crashes and does not close the pipes properly, the MPA server side will keep the allocated resources open. If the client crashes repeatedly, eventually there will be no more memory for the Kernel to allocate for the new pipes. Please check to make sure that you have no client processes that are subscribing to image streams and are crashing and restarting (perhaps restarting automatically by systemd). It is possible that a process that is not your test app is misbehaving for some reason and is causing this memory leak by continuous crashing and re-starting. Also, what if you just use voxl-inspect-cam to inspect the single camera stream and no other camera clients running, does the same issue happen? Alex