@dan64 Unsure if you have resolved this issue, but I am going to add some more information to anyone that stumbles across this. There was a bug in the voxl-mavlink-server setting and sending all System ID numbers to 1. The deb file below should solve this issue where the MAV_SYS_ID can be changed an reflected on the VOXL2. http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mavlink-server_1.4.12-202509181025_arm64.deb

Hi @VictorG Our team sent another batch out... FedEx tracking 884700036314 They claim Monday you should get it ... sorry for all these delays. We tried!!! I do not have visibility into our product shipment status, but this issue and experience has escalated the need for me to have that visibility, so I will explore that. We'll try better next time Keep me posted. Thanks!

@luisgb , all of ModalAI ESCs can be controlled via UART using two modes power : command 0-100% power, which controls the average duty cycle for that motor RPM : (requires calibration for the motor + propeller type): controls rpm directly Commands to the ESC are sent via UART and normally that UART port is connected to VOXL2 UART, which is mapped directly to the DSP. The DSP is where most of PX4 runs. If you are looking for the easiest integration / testing, you can connect the ESC directly the VOXL2 CPU (using non-DSP UARTs) and use either python or c++ code to interface to the ESC (or similarly from a Linux Desktop / laptop). It is also possible to communicate with the ESC while the ESC is connected to the DSP UART. This is how the voxl-esc tools work on VOXL2 (while PX4 is not running). This works by bridging the connection between the DSP and CPU and accessing the DSP UART from the CPU. However, this path has extra delay and is not recommended for any real-time feedback control applications. If you provide more information about your use case, I can suggest the best path. Alex

@holmeslice Regarding having the external flight controller, it's really only needed if the I/O limitations of VOXL 2 are a problem. For example, if you need CAN bus then you should probably use the external flight controller since VOXL 2 has no CAN bus support.

@Vinny Thank you for your valuable feedback. I’ll keep the points you mentioned in mind while doing the bench testing.

@gestrada1150 We have an experimental fork of betaflight running on VOXL 2 now. However, there are no official plans to support this.

@Daniel-Rincon I'm hoping you are still around as we might be having a similar issue. When you say documentation, do you mean these: https://gitlab.com/voxl-public/support/voxl-train-yolov8 What specific helpers did you add with what model conversions? (Reference: I also have a custom yolov8 model trained for an output of two classes.)

Hi @smiley We don't offer longer ones and we have not tested them. Sorry I can't be of much more help here. Usually in this situation, I suggest our customers to go and challenge their Mechanical and Industrial Design Engineers to better constraint image sensor placement in the drone given these fundamental constraints.

@Alex-Kushleyev Thanks for the explanation — I now understand how to use the TOF sensor. I’ll use the ROS point cloud directly for my research.

@jonathankampia There is some relevant info here: https://docs.modalai.com/voxl2-external-flight-controller/ M0062 is more rare of a product for us so isn't listed there but you can find more info here: https://docs.modalai.com/m0062-datasheet/#j9---2w-uart--i2c-port

@Andrew-Jue , you can find the latest firmware for the IO board in /usr/share/modalai/voxl2-io-tools/firmware/modalai_m0065_firmware_v0_2_RC1_f94baad1.bin on your VOXL2 or on gitlab: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl2-io/-/tree/master/voxl2-io-tools/firmware You can update the firmware using our voxl-esc tools, as documented here : https://docs.modalai.com/voxl2-io-firmware/#how-to-update-firmware This version of the firmware is the latest and has been stable for over one year. Alex

@wifa799 , Please see the following post : https://forum.modalai.com/topic/4274/hadron-boards-to-order/ (at the end) In short, Hadron works in J8 only using the kernel variant that works with M0173. I need to update the documentation. So you can have 3x tracking, 1x hires, 1x TOF, and Hadron (IR + OV64B hires). That is 7 cameras which is the maximum number of MIPI cameras that VOXL2 supports. I know you did not ask for the other hires camera (recommended IMX412 M0161 module), but just wanted to mention that. This set up is not standard, but you would just need to set up for a standard Starling camera setup (C27) then go from there.. copy the sensormodules (camera drivers) for Boson in slot 4 and ov64b in slot 5 and update your voxl-camera-server.conf. I can help you with that if needed. Alex

@Jetson-Nano YES!!! So happy to hear that.

@Moderator got it. Thanks!

@Federico-Wyrwal , thank you for the reply. More debugging would be needed to figure out the root cause and it looks like you already submitted an RMA for the inspection / repair, so we will take care of it. Thank you. Alex