@James-Strawson Quick update. I was able to lower the value to 300 and it seems to work as well.

@Eric-Katzfey Yes the Mavlink Packets will be sent form PX4 running on the VOXL2 through the Trip Module and then to the Doodle, and vice versa for the data flow from the GCS to PX4.

My understanding is that the Trip is just running a extension of Mavlink to allow for specific gimbal and camera commands. Also it is performing Video compression.

@Eric-Katzfey Should it be possible to use the Trip2 with VOXL2 as I showed above? Would also be interested in hearing how you went about using the camera/gimbal without the Trip module with VOXL1. Do you think this approach would would work with VOXL2 as well?

I am working on integrating a Next Vision Trip2 Module to one of our systems that has a VOXL2. The VOXL2 is currently running the PX4 service for flight control. So I am assuming this would be slightly different than running a external AP.

I currently have the Trip2 module connected via UART to the VOXL2 via J3 on MDK-M0151-1-00 (USB3.0/UART Expansion Board)

The Graphic below shows the desired architecture of the system.

I have seen in a older post on the forums that the engineers at ModalAI have experience with integrating with the Next Vision ecosystem. I would like some guidance on this integration project. I have been able to get this working using a Cube running PX4 but this will be the first time trying to get it working with VOXL2.

@McMason and @Vinny Was there ever a solution to this found. I am working on a similar setup where I am using a DragonEye2 and Trip2 Module connected to the VOXL2. Just wanted to see if you were able to get the MAVlink routing setup up correctly.

I have been starting to integrate a companion computer/external flight controller to the VOXL2. Documentation says the preferred method would be to use the USB 3.0 Expansion Board (MDK-M0151-1-00). I have already placed an order for one of these. While waiting for this to come in I am trying to use (M0078), which I already have in my lab. I see in the datasheet for M0078 that J5 is a UART port that is not populated. If I populate the connector would I be able to use this for communication with a external flight controller?

@tom I was able to try another power module and cable I had here. I still received the same results.

@pthomason I am using USB-C to USB-A on my host machine.

@tom No. I do not see a change in lsusb when the Voxl is connected via USB-C.

I have a QRB5165 VOXL2 running SDK 1.1.2 that will not allow me to connect to it through ADB. This VOXL2 has been operational for some time now until we were unable to connect over ADB.

All cameras, add on boards, etc have been removed from the VOXL2 and I only have the power connection and USB-C hooked up. I have tried to go through the unbricking process, however once I initiate the flash using qdl I receive "Waiting for EDL Device". I have made sure the SW2 is in the on position and made sure to follow the unbricking procedure here ( https://docs.modalai.com/voxl2-unbricking/). I have tried multiple USB-C cables and multiple Host Machines running Ubuntu 20.04 and 22.04 (Not VM).

Are there any suggestions or tips to help me solve this issue.

@tom I checked wire harness going from the VOXL 2 to the Doodle Labs. Everything seems in check there. Haven't noticed anything wrong with the connector or solder joints on the pcb located on top of the Doodle Labs. Would you recommend getting a RMA going for this radio?

@tom I am not able to ping the Doodle Labs Radio from the VOXL2 that is connected to it.