@Eric-Katzfey In my case I am receiving data as @Alex-Kushleyev explains with stty -F /dev/ttyHS2 115200 cat /dev/ttyHS2 [image: 1739568773345-e1b7860f-60b8-4441-a7f9-c4147a44b66c-image.png] and in the script in /usr/bin/voxl-px4-start I see that section @Eric-Katzfey [image: 1739568629179-6bd3d8f4-b89b-4fa6-ad40-5c58260d333b-image.png] but when it comes to running voxl-px4 it autodetects with different bauds to the GPS. Is it necessary to change it somewhere else? [image: 1739568685057-e7941c5d-6d4b-4a0c-b5ab-a9e4130ef09b-image.png] I have no problems with the MAG. It detects it perfectly. I have the RX and TX of the GPS connected exclusively to the J9 of the 5G, and the rest, to the J19. I also have the RX and TX of the IO Board connected to the RX and TX of the J19. I have also tried disconnecting the IO Board and leaving only the GPS on the J9. SOLVED: I change in the file voxl-px4-start from M0052 to M0054. Thanks!!!

After trying the web interface as well as command line I am still not able to successfully flash the image. I keep getting the same error above. Regardless of what position the switch is on the device only shows up in QDL mode. If there is no other method for force flashing the device (There does not appear to be any physical switch or button other then the one) do I need to submit an RMA? This device worked fine and was finally able to get the cameras and everything working and it just stopped allowing adb and not showing up on my Linux PC. bummer

@smilon we're still working on it but slower than I had originally planned. we're using it on a feature light product right now without camera support, once we have camera support in place I'll try to get some preview releases in place, 'hoping' that's in Q1/Q2 but as an optimistic engineer speaking

@Gary-Holmgren , oh yeah, I almost forgot about the issue of not being able to use the DSP uart ports while PX4 is running.. To work around that, you could potentially connect M0065 board to one of the UART ports that are actually connected to CPU and access it directly from linux use /dev/ttyHSx devices You can find the linux uart ports here : https://docs.modalai.com/voxl2-linux-user-guide/#uarts - you will need an expansion board, but even something like M0141 or M0151 will do (which is probably the simplest). However, it sounds like maybe you are close to figuring out he pwm output via px4, so perhaps this is not needed, but you can keep it in mind. Alex

@Dhatchayani-L It appears that your board is booting into QUSB_BULK mode, which will require following the unbricking process to resolve: https://docs.modalai.com/voxl2-unbricking/#unbricking-your-voxl-2

@Jetson-Nano, can you please clarify what exactly you are asking?

Hi @Alex-Kushleyev , Thank you very much for such a detailed reply, we will carefully refer to your suggestions to make the purchase. thanks again!

@rogerli or @McMason Were either of you successful in getting the VOXL2 to connect to the NV Trip2? Working the same issue on my end.

@Achyut-Sapariya That all looks normal, I'd recommend submitting an RMA and our team can diagnose the issue: https://www.modalai.com/pages/rma

@jklre , one way to achieve what you need is to set up a VPN client on VOXL2 (and VPN server on your linux server) and create a adb TCP bridge via adb forward or reverse (which you already found). Your VPN client would connect to the VPN server on your linux server via the ADB TCP tunnel. The VPN client / server would then take care of proper data routing (just like regular VPN). I believe guys from Ascend Engineering were able to to achieve this : https://ascend-engineering.gitbook.io/modalai/sharing-internet-over-adb but it requires initial internet connection to set up. Your best bet may be to get all the dependencies downloaded to your linux server, then push them to voxl2 via ADB, and add a local package source for apt on voxl2 (so that it can find new packages) and install. Similarly for python modules, you should be able to do an offline install, i think.. Alex

@voxl-phoenix J19 has pins for 2 UARTs. We put GNSS on one and RC on the other. So if you are able to hook up everything correctly, configure the TBS crossfire receiver correctly, and configure PX4 correctly then it should work.

@Peter-Milani Nothing available for the public just yet but I can tell you we're working extremely hard on this and hope to start publishing builds soon

Hi @cobbp It's the 2.96V directly from the Snapdragon PMIC as you noted, and SD Cards from UHS I and onward negotiate their link speeds and I/O voltage. So, a proper 1.8V SD card will internally use that 2.96V and create the 1.8V I/O rail. For cards that operate at "3.3V", they are claimed to be supported in the Snapdragon chipsets at this lowered ~3V rail. The slot on M0062 actually accepts UFS or uSD. For more details on just the SD portion, please see this design where we opened our Schematics. In this case, this is just uSD, but otherwise matches the M0062 exactly for uSD functionality: https://docs.modalai.com/voxl2-dev-test-board/ Hope this helps!

@Vinny Thank you for your info. I will review with my team and see if it makes sense for us to pursuit that direction/option. Best Regards, -Henry

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

Hi @Chase-Riley Your best bet might be to start a new thread, that will help ensure you get more eyes on it for the best person on our side to help you along! Thanks!

@Chase-Riley the recommended approach is to use J18 ESC port directly: https://docs.modalai.com/voxl2-external-flight-controller/#voxl-2-connecting-an-external-flight-controller