ModalAI Forum

Alex Kushleyev

@patkirkmartin , so sorry for the delay. We are ready to proceed with sharing the source code for M0065 board and I just wanted to double check that you are still interested. Please let me know and we will get this going right away.

If you use our APM, it will provide power for VOXL2 and the APM also includes voltage and total current sensing and has PX4 support for that. The information is delivered to px4 via I2C.

If ModalAI ESCs are used, such as M0129 (mini esc) or M0138 (larger / racing ESC), they both provide power for VOXL and measure voltage and total current and provide this information to PX4 via telemetry via UART.

Alex

tom

We do. I will send you your calibration files via email.

Moderator

This is not currently supported. Right now the only data going to the UAS from the ground is via ELRS. We do have plans to support MAVLink over ELRS in the future.

Moderator

Most power issues with VOXL 2 relate to MCBL-00001 connector becoming dislodged. People often pull the cable instead of depress the connector for proper removal. Is there any chance you have a cabling issue? This is the most common cause of failure.

Assuming you don't have major software changes, we're not tracking any issues that cause random flight reboots.

Moderator

The source code you're referencing is a good starting point as an example for what you want to develop. We do not have a ready made tracker for use today and do not have plans to implement one. We just have those references as a development starting point

Moderator

Thanks for the detailed report. A few notes based on what's in the log:

The missing intrinsics files are not the cause of the abort — those ERROR in json_from_yaml, failed to open file / tracking_front_intrinsics.yml warnings are expected if you haven't run camera calibration yet, and voxl-camera-server falls back to default intrinsics. That's noise, not the crash.
The actual "Aborted" with no further message is what we need to isolate. The docs' Debugging Camera Issues page is the right starting point for this class of failure, but the excerpt we have doesn't show the specific abort signature you're hitting, so I don't want to guess at root cause here. Can you get us:
- dmesg output right after the crash (look for a segfault/kernel oops around the same timestamp)
- Whether there's a core dump generated (check /data/core* or wherever core dumps land on your image) — if so, a backtrace via gdb would tell us exactly which line aborts
- Run voxl-camera-server under gdb directly (gdb --args voxl-camera-server, then run, then bt once it aborts) — this is the fastest way to get a real stack trace instead of guessing
The "works after a couple of systemctl restart calls" behavior strongly suggests a race/init-order issue rather than a config problem — since your config itself (both the custom_camera_config.txt and generated voxl-camera-server.conf) looks structurally correct for two independent ar0144 cameras. One thing worth double checking: you're using ar0144-fsin-combo on J6_LOWER_COMBO1 for tracking_down, but I don't see a J6_LOWER_COMBO1_NAME2 or combo-mode field set — since this is a combo slot, confirm whether that flex is truly running in single-sensor mode. If the combo detection is flaky on init (i.e. it doesn't always see the second physical sensor consistently), that could cause a transient failure on cold start that clears on restart.
Please also confirm which mach.var / carrier board (M0054) revision and whether tracking_down is on a combo flex physically wired for single-sensor use — a photo of the flex connection would help us rule out a physical/timing issue on that port.

Moderator

We've recently ordered two Starling 2 Max units with M0062 add-ons. We want to attach an external USB 3.0 drive off the VOXL 2, and want to be sure we're using the right port and the right cable before we order anything.

A few questions:
The M0062 user guide says USB3 isn't reliable on the Type-A port (J10) and to treat it as USB2, and that J11 is the USB3 host port. Is J11 where we should be plugging in?
MCBL-00022 is in your cable datasheet but we can't find it in the store. It's not on either page of the cables collection. Is it still available? If so, how do we order it?

Also our Starling order included cables we never itemized. If you can see from the order whether a 10-pin USB3 cable was in it, that would save us buying a duplicate.

And if MCBL-00022 is discontinued, is there a replacement? Failing that, the mating connector part number and pinout would let us get one made.

Eric Katzfey

Most of this can be answered by our documentation here: https://docs.modalai.com/. If after reading through that you still have any specific questions feel free to reach out here on the forum. The short answer to most of your questions is "yes".

Eric Katzfey

That's kind of pointing to VLC as the issue. Can you try with QGC?

Jetson Nano

@Eric-Katzfey ,
Please excuse me for the confusion caused by me.

Goal -
my goal is to achieve continuous video stream from lepton camera connected through USB cable. the USB port I am using is Microhard.

Issues I faced -

During my initial testing, I was able to stream the lepton video through VLC, but the camera stream kept on getting interrupted (the camera stream ended), once I restart the uvc-service and the stream-service , it starts again. This observation was in loop.
I wanted your help to solve this issue.
Once you asked for the log file, I tried to replicate this test, but the stream was not working through VLC.
I attached the log file.
To verify the camera is working fine I tried with ffplay, the stream was working fine.
I verified the MIPI camera, I was able to see the video on the voxl-portal, but while using the stream-service, it was not working on VLC.

Now, I would like your help to solve the following problems

Get the video stream on VLC
Get the video stream to work continuously with out any interruption.
Also it would be great if you clear one more query of mine, whether I can setup the USB port with any camera(which supports USB protocol), If I make necessary changes to the codes or UVC-service and Stream-service.
Thank you for your patience and looking forward to response.

ModalAI Forum

Veteran

Posts

Member List