@Eric-Katzfey Thank you so much

@jedeloya Can tolerate wind gusts of 15 m/s https://docs.modalai.com/starling-2-max-datasheet/

@Mouhamed-Ndoye What is the interface to control these propulsion units? Is it standard PWM? VOXL does not have a flight controller integrated, it is only a companion computer. But VOXL 2 and VOXL 2 mini support either PX4 or ArduPilot. They, however, do not have any PWM outputs. You would need to use our VOXL 2 Digital IO expander board (https://www.modalai.com/products/voxl2-io?variant=40610514206771) in addition to the VOXL 2 to get that added capability.

@tkddnjs825 , since you already have M0062, you should be able to use it. As you already identified, J9 on M0062 has /dev/ttyHS2 Linux UART device. You can also find more information here : https://docs.modalai.com/voxl2-external-flight-controller/ regarding configuring mavlink server. It looks like you are doing the right things here. However, the use case for "autopilot_uart_bus" maybe different from what you need - in your case your autopilot (px4) is actually on VOXL2 and the uart connection is for the path to GCS. You may need to modify mavlink server depending on what you want to pass on this UART connection.. This goes beyond my knowledge of mavlink server - please try to see if you can get it to work, otherwise post a follow up question with details of what you would need to be sent using the UART connection. Alex

Hi @scosgrove, Thanks for the details. On the DSP there is a dedicated HW block for each UART (similar for the UARTs connected to the application processor). All the UARTs supported on DSP have hardware FIFOs. Since you asked about the size: DSP UART2 has 64-byte low level FIFO on RX DSP UART6, 7 have 128-byte low level FIFO on RX When fifo is close to filling up, there is an ISR that triggers on the DSP which transfers the data from FIFO to other memory, and then the data propagates to the user. I wonder if there is some issue when fifo is read while another byte is incoming into fifo at the same time. Which uart port are you using for this test? I can do some testing with bursts of 70-250 byte packets. In the past we have tested continuous data transfers of several KB but not at high rates. Also, what baud rate are you using now? Alex

Agreed! thanks for noticing, Tom. Definitely should be tested on a recent SDK.. Alex

Hi @tkddnjs825, In addition to Alex's question above, could you also please share which version of voxl-elrs is being used on each voxl2? The voxl-version command should list the versions of each installed package. Can you also please confirm that in the voxl-px4 configuration file on the voxl2 that is not able to communicate with the ELRS receiver that the RC type is set to CRSF_RAW, like this: RC=CRSF_RAW. Furthermore, if you could share the output of voxl-elrs --scan from the voxl which is unsuccessful that would be helpful. Thanks, Max

@Peter-Milani Hi Peter, it's not possible for us to answer comprehensively about NDAA compliance. We can answer country of origin questions though. Our M0107, M0161, M0166 for instance are built by ModalAI in the USA M0149 is built by a partner in Taiwan

@Pete Starling 2 Max is probably easier to configure for this. You could mount the Doodle radio on the bottom. The M0151 is a good expansion board for this.

@Gary-Holmgren Haha your way is a little more robust than mine. I just manually added the qshell start command to the extra commands section of the voxl-px4.conf file.

@Gary-Holmgren Figured it out, I hope this helps others with a similar setup. I didn't notice before but in the usr/bin/voxl-px4-start script there is a comment: # qshell vl53l1x start -X -b 4 Which you can make or replace to change the DISTANCE_SENSOR condition to: if [ "$DISTANCE_SENSOR" == "VL53L1X" ]; then # Make sure to set the parameter SENS_EN_VL53L1X to 1 qshell vl53l1x start -X -b 4 # qshell lightware_laser_serial start -d 7 Then you can change the voxl-px4-conf to: DISTANCE_SENSOR=VL53L1X After setting the relevant distance sensor / EKF2 params in QGC you should be able to restart voxl-px4 and the distance sensor will appear!

Hi @Karl-pan. There was a big refactor done on voxl-tflite-server not too long ago. Would you be able to test this on the dev branch? Also please share your /etc/modalai/voxl-tflite-server.conf. I found a bug where the model path wasn't getting updated for custom models. I just made a PR to fix this, but you can manually edit it until that gets merged in. Lastly, I'm not getting any seg fault with my custom models so if you're able to share an example model that could help narrow it down to the way you're exporting it. Best, Ted

@Gary-Holmgren , Our voxl-esc tools use a python wrapper around qrb5165-io library, which is pretty easy to use. The wrapper provides an api that is almost the same as the standard serial port class in python : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/voxl_serial.py. The usage of this wrapper can be seen here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/voxl-esc-neopixel-test.py?ref_type=heads#L114 . You should use the port name such as /dev/slpi-uart-2 , which is a fake name (it does not exist in the Linux /dev/ folder) but the wrapper class will extract the port index at the end. Technically any name with -2 at the end will tell VoxlSerialPort class to use the DSP's uart port 2. You could write a service that uses a python3 script to comunicate with the serial port and expose the data via UDP using other python tools. The limitation of only one concurrent DSP uart port usage still applies here. Alex

@Zachary-Lowell-0 Would definitely be a useful function. I am probably gonna stick with voxl2 running px4 for now since it simplifies things.

@Zachary-Lowell-0 Yes this did the trick, thankyou!