@Sean-Hickey that great, just making sure, did you use optical flow with FC?

Also could you let me know which branch you used, or the Px4 built file. i want to test it out in my setup.

@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.

@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?

@Eric-Katzfey We reinstalled the QGC in a new laptop and it is working fine now.

@Eric-Katzfey
I am able to build, my build is not able to have both collision prevention and uavcan working. if i go to the latest version the hearding error is showing up, prearm check is not passing.

I checked with px4 mainline as well as modalai fork,

branches including - voxl-fpv-dev, version 1.17-dev
main branches - release/1.17, 1.16, 1.15

None of the above have the UAVCAN enabled, I do it manually, and the UAVCAN error is solved.

If you could guide me to a version of PX4 where both of this works with Flight core v2, or share the px4 build, if you have it working, i could test it out .

@astro_phil ,

Which camera connector (J6 or J7) are you using on VOXL2 mini? Also, have you sensormodule (camera driver) to /usr/lib/camera (assuming you are doing a manual configuration). See some details here : https://docs.modalai.com/configure-cameras/#connect-a-new-camera

Since the kernel is reporting that camera probing is failing, this could mean one of several things:

correct sensormodule for the camera and slot id is not present incorrect kernel variant is used (should be 2.0.0) a hardware issue in the interposer / camera

You can also check if the tracking camera works in the upper slot (where you have the IMX214 plugged in right now) and vice versa. Swapping the camera slots would require making sure you have correct mating orientation of the connectors and correct sensormodules available.

I just checked on voxl2 mini, we have the following sensormodules available:

voxl2-mini:/usr/share/modalai/chi-cdk/imx214$ ls com.qti.sensormodule.imx214_0.bin com.qti.sensormodule.imx214_3.bin com.qti.sensormodule.imx214_2.bin com.qti.sensormodule.imx214_4.bin voxl2-mini:/usr/share/modalai/chi-cdk/ov7251$ ls com.qti.sensormodule.ov7251_0.bin com.qti.sensormodule.ov7251_2.bin com.qti.sensormodule.ov7251_4.bin com.qti.sensormodule.ov7251_1.bin com.qti.sensormodule.ov7251_3.bin com.qti.sensormodule.ov7251_5.bin

So you would not be able to get this combo to work on J6 (slot ids 0 and 1) because the imx214 sensormodule for slot 1 is missing (we did not add it by mistake), but J7 should work (slots 2 and 3). If you put IMX214 into lower slot, and tracking camera in upper slot, then you could use J6 : imx214 : slot 0, ov7251 : slot 1.

Additionally, make sure that you are using the correct kernel for voxl2 mini (it should be 2.0.0, not 2.0.2 when you are using the non coax cameras / interposers). you can check the kernel version using voxl-version and look at the top of the output, under mach. var (machine variant), should be 2.0.0. if not, re-install SDK and select the correct kernel variant during install.

Alex

@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.

@ralinaresg , can you please clarify a few things:

what type of vehicle was the ESC a part of? what was the behavior of the motor that was not functioning properly? did the whole ESC stop working or only one channel, which was originally struggling? did you notice the burned component when the ESC arrived or did it burn after arrival? was the black paint already on the ESC when you received it?

Those questions can help us figure out what happened - please provide the details if you are able to.

In any case, if the system arrived in a non-functioning state, you should request a replacement : https://www.modalai.com/pages/rma

Alex