Hi,

I had the same problem.

You can try to transfer to the normal operation (& ADB)
by:
fastboot continue

and disconnect-connect the USB cable in order to enable
the USB change to ADB.

Erez

@buem799 Hi, no worries, I am also very new to this space. ffplay is separate thing, part of the ffmpeg program, not something inside VLC. This is the reddit link that I posted in the thread I listed above

https://www.reddit.com/r/reolink/comments/yzhlxp/found_a_solution_for_rtsp_blackno_video_in_vlc/#:~:text=In VLC%2C under the Tools,video stream in VLC player

If you read through it, the fix was for a windows machine, which I was using at the time. It states further down in the reddit post that live555 support was removed in newer versions of ubuntu (linux operating system). From your screenshots, it looks like you are using ubuntu, so it could make sense that VLC may not work. I believe it is more a ubuntu issue rather than VLC. Don't try to dig into that, especially if you are new to linux. I would install ffmpeg on your system and try to access the RTSP stream using that. I just asked ChatGPT for the commands to do that and will paste below:

sudo apt install ffmpeg

Id recommend asking Chat how to access an RTSP stream using ffplay, or read the documentation 🙂

The other thing you could do, if you had a windows laptop, you could connect the windows laptop to the drone wifi and try to access the RTSP stream via VLC on windows and do the fix included in the reddit link

@Matthew-Booker
This worked! Thank you

@Alex-Kushleyev I initially tried using an LCD screen for the checkerboard, but the camera wasn't detecting it. Should I move the camera around when transitioning between boxes on the LCD screen?

Afterward, I reverted to the physical checkerboard and moved slowly during calibration. Additionally, I switched to the stereo camera configuration (https://docs.modalai.com/voxl2-camera-configs/#c-10-front-stereo-only-ov7251). Calibration completed successfully, and I was able to start the voxl-dfs-server (after renaming the intrinsics/extrinsics files to match the DFS configuration).

However, I'm still not seeing valid output data in the VOXL Portal. Both the DFS server status and journal logs appear normal. Any idea what might be causing this?

The orientation was labeled vertical in the extrinsics file, I updated it to horizontal since the cameras are mounted in that direction, I tried both.

voxl2:~$ voxl-calibrate-camera stereo -s 6x9 -l 0.0254 Waiting for valid pipe... Please open voxl-portal in a web browser to view the camera calibrator overlay stream Running Calibration... Calibrating Left Camera using intrinsics guess for ov7251 stereo cam Matrix [512.0490656858071, 0, 317.943082105687; 0, 512.9677676044445, 249.1010817824914; 0, 0, 1] Distortion [-0.2223760024137635; 0.2834698825913266; 0.006375005556120415; 0.001380405690556171; -0.3234049381178579] distortion_model: plumb_bob Re-projection error reported by calibrateCamera: 0.618295 Calibration Succeded! Calibrating Right Camera using intrinsics guess for ov7251 stereo cam Matrix [499.9941123870856, 0, 302.2300515222531; 0, 500.0159138740167, 197.2845691878148; 0, 0, 1] Distortion [-0.1920328131645855; 0.1661211129668493; -9.2603546772169e-06; -0.0005742159007090549; -0.1386842520292771] distortion_model: plumb_bob Re-projection error reported by calibrateCamera: 0.654897 Calibration Succeded! Calibrating Extrinsics 7 frames will be processed Processing non-fisheye stereo R [0.9998717783469182, -0.01301971984148091, 0.009322754990917012; 0.01315096821001574, 0.9998132816974246, -0.01415816995820597; -0.009136678855605861, 0.01427895782876463, 0.9998563059074108] T [-0.09106229154044132; 0.0003557888497092847; -0.01247277836064075] Re-projection error reported by stereoCalibrate: 0.921971 Detected horizontal stereo pair Distance between cameras: 0.0911 Extrinsics Calibration Succeded! Saved intrinsics to: /data/modalai/opencv_stereo_intrinsics.yml Saved extrinsics to: /data/modalai/opencv_stereo_extrinsics.yml Exiting Cleanly

ce4025ae-5114-4473-ae6a-d9e4862c4b13-image.png

cat opencv_stereo_front_extrinsics.yml

%YAML:1.0 --- R: !!opencv-matrix rows: 3 cols: 3 dt: d data: [ 9.9987177834691821e-01, -1.3019719841480912e-02, 9.3227549909170124e-03, 1.3150968210015740e-02, 9.9981328169742456e-01, -1.4158169958205966e-02, -9.1366788556058610e-03, 1.4278957828764632e-02, 9.9985630590741081e-01 ] T: !!opencv-matrix rows: 3 cols: 1 dt: d data: [ -9.1062291540441320e-02, 3.5578884970928471e-04, -1.2472778360640750e-02 ] reprojection_error: 9.2197082833254862e-01 orientation: vertical calibration_time: "2025-04-29 21:24:04"

cat opencv_stereo_front_intrinsics.yml

%YAML:1.0 --- M1: !!opencv-matrix rows: 3 cols: 3 dt: d data: [ 5.1204906568580714e+02, 0., 3.1794308210568698e+02, 0., 5.1296776760444448e+02, 2.4910108178249143e+02, 0., 0., 1. ] D1: !!opencv-matrix rows: 5 cols: 1 dt: d data: [ -2.2237600241376348e-01, 2.8346988259132661e-01, 6.3750055561204149e-03, 1.3804056905561710e-03, -3.2340493811785792e-01 ] reprojection_error1: 6.1829492384868989e-01 M2: !!opencv-matrix rows: 3 cols: 3 dt: d data: [ 4.9999411238708558e+02, 0., 3.0223005152225312e+02, 0., 5.0001591387401669e+02, 1.9728456918781478e+02, 0., 0., 1. ] D2: !!opencv-matrix rows: 5 cols: 1 dt: d data: [ -1.9203281316458551e-01, 1.6612111296684931e-01, -9.2603546772168998e-06, -5.7421590070905486e-04, -1.3868425202927714e-01 ] reprojection_error2: 6.5489679777844001e-01 width: 640 height: 480 distortion_model: plumb_bob calibration_time: "2025-04-29 21:24:04"

@tom Yeah I am on 0.9 platform release

@modaltb Hey, thanks for the quick reply. Unfortunately, none of these work for us since it seems exposing one port prevents us from accessing another (I also can't find a ref to buy the M0130).

We found a workaround by having a USB hub on the m0125 instead of going over the native uart.

Also, if you are using very old SDK on VOXL2, the uart bridge may not be working 100% properly.

When in doubt, the best thing to do is to connect to the ESC using a serial to usb adapter going directly to a Linux PC (and run voxl-esc tools on the PC). do you have that available?

@ijones2 This is great news! It looks like everything is functioning as expected so no need to go through the unbricking process at this point.

It does appear that there is a fairly old SDK loaded on there so I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases"

Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

@Rowan-Dempster No problem! Kind of primitive but effective 🙂

Got it. Thanks.

@Jae-Park You should ship out the entire drone so that the team can verify that all of the components are functional, fix anything else that you may not have seen, and do a final flight test before sending back.

@tom Thank you. It works well

@JustinDev23 Great! Thanks for your patience, I just generated an official release of v0.16.2 to ensure that it makes it into our next SDK release.

@Cai-Bill Can you send a flight log of flying in manual mode and then trying to switch into position mode?

@Matthew-Wellner FYI

@milanerd The added capacitance helps VOXL 2 Mini's USB port achieve USB 3 speeds. We don't have that adapter to confirm a fix for your issue, but with the cable the link should transfer much faster

@Eric-Katzfey ok, Thanks, we tested GPS M10 and the problem solved.

@Alex-Kushleyev Hi Alex, When I hold the drone in hand and move around the room, I see that VIO is at 100%. It only fails when I shake the drone or start flying it. I'm not sure what's going wrong.

No @Matthew-Wellner , Our shipping dept is already done for the day and we missed UPS/FedEx drop-off times for next day delivery.

I can't offer anything other than consolation that we've had some of our customers be amenable to a demo with non-NDAA compliant stuff with our assurance we have a plan to switch over (especially yours since it is available and in-hand, but just not working at the moment).

I only wish I could probe your board remotely to help you figure this out... sorry.

@tahawaru Okay, that shows you have 1.14.0-2.0.78. If you want to build 1.14.0-2.0.63 then you need to check that version out instead.