Hi @tom, That's exactly what I was looking for, thank you!

There are likely 2 issues here. One was a floating point math fix that is in newer versions of PX4. Can you update to latest px4: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.146-202607161052_arm64.deb and try again? The other issue is that sending in trajectory setpoints from your external application, even when in altitude mode, will go straight into the position controller and affect flight. So, I would only send those in when in offboard mode.

Hi @alraj, 05c6:900e QUSB_BULK is not EDL (that is 9008). It is the SoC crash-dump mode, so the board is attempting to boot and failing before the OS comes up. Since Sahara/Firehose completed with the correct M0054-2 image, the flash contents are unlikely to be the problem. In past cases a board that returns to 900e after a successful QDL has not been recoverable by reflashing (https://forum.modalai.com/topic/1468 and https://forum.modalai.com/topic/3263), and a similar Sentinel case came back from RMA as a damaged main board (https://forum.modalai.com/topic/2131). Two things worth ruling out first. Pull the VOXL 2 out of the drone and boot it bare with every camera and add-on disconnected, since a mis-seated camera connector produced this same 900e state once (https://forum.modalai.com/topic/3230). Then re-check the steps at https://docs.modalai.com/voxl2-unbricking/#if-the-device-still-shows-900e-or-boot-loops-after-a-successful-flash and repeat the flash once. If it still comes back as 900e, an RMA is the next step: https://www.modalai.com/pages/rma. Include the serial number and QDL log. Keep the crash dump private, support can request it if needed.

The ExpressLRS receiver requires* one additional wire. The ghost atto only connects one wire to the VOXL RC RX pin, but the ELRS receiver will also require a connection to the VOXL RC TX pin, otherwise the wiring is identical. Pre-crimped wires can be found easily for the JST GH connectors (J19) to make adding connections simple. *You could leave the receiver's RX line (the VOXL's RC TX) disconnected; this would make updates and other control using the voxl-elrs application impossible but basic RC functionality would work.

@alex-kushleyev Thanks for the response! A control model is a simple MLP (multi-layer perceptron) Input observation space: PX4 odometry topics, ToF depth/Depth estimation model, object detections. Output action space: PX4 offboard commands ( position and yaw for now, but we might extend to velocity/Collective thrust and body rates)

I want to develop a battery management system to read live battery data and use it into a software that plans launch, path, return and control of the drone

RMA'd the VOXL2 board, it was found to be unrepairable.

The specific leg in question has a number on it - 1460. The legs in the CAD for the C28 show 868B.

Please reach out here: https://www.modalai.com/pages/blue-uas-cleared-fpv-customer-intake-form

Wanted to check in again. Any advice on swapping spektrum RC for ghost atto on voxl2?

Hi, I would like to know what wifi module is on the drone. The one mounted on the drone is different than AlfaNetworks? Adam

Hi Christopher We currently support two forms of recording, both at the pilot internal to the VRX onboard storage on goggles to the SD Card We do have on our list to implement recording at the UAS itself, but that will need to be in a future software update.

Similarly, I cannot find the model for the new "slim" VTX mount, only the older, taller one.