@Jetson-Nano Which build, specifically, are you looking for? Something from the ModalAI fork of PX4 or from mainline? Are you not able to build firmware yourself?

@voxltester The primary and secondary ip / port configurations are for destinations. voxl-mavlink-server will initiate connections to those. For incoming connections just send to port 14550. voxl-mavlink-server is listening on that port. When an incoming message from a new ip / port combo comes in it will store that and consider that a new connection. If you use drone.connect it is waiting for voxl-mavlink-server to connect to it rather than attempting to connect to voxl-mavlink-server on it's own.

@Jetson-Nano Can you open the question about UAVCAN in a separate post? It has nothing to do with the initial question and we like each separate issue to have it's own posting / title. Thanks!

@gerard I also just remembered we had a stint of bad MCBL-00010's a few months ago...
We have since cleared that up, but there is no telling how long ago you may have ordered that cable...
Please see this thread for guidance and if you do think your MCBL-00010 is at fault, we will replace your M0048, just reference both threads in your RMA (this one and this one -->) https://forum.modalai.com/topic/4632/flight-core-2-firmware-update-through-qgc?_=1781284416780

Hi @gerard
I asked my team for some extra assistance on the SW side, but if you suspect HW failure, we can diagnose with an RMA if you want to pursue that route.
If you had this working at one point, then it did not, it's most likely either a really bad SW change, or the HW got damaged.

https://www.modalai.com/pages/rma

If you want to wait and see if our SW team has any guidance first before doing an RMA, that is your call.

@Mustafa_Cayci You can run PX4 directly on VOXL2. Do you still need the external Pixhawk? When you say USB-C is that the connector that is already on VOXL3 for adb?

@PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.

@PatkirkMartin The ELRS is connected to a DSP UART via J19, correct? That is the link that you want to send Mavlink data on?

@Mustafa_Cayci You would need an accessory board that exposes a USB port for you to connect. Yes, VOXL2 has Ubuntu / Docker capability.

Hi @gerard
Your RPi needs power.
The USB on the Microhard Dongle is a Device/Peripheral Port, needs to connect to a Host PC/SBC.
I do not see any power input to your RPi device.

That can explain your behavior.