@Eric-Katzfey thanks mate!

@tom Ah. This is a simple config file change. Thank you!

libmodal_cv contains some qualcomm proprietary code for interfacing with the computer vision DSP so we are not able to open source that particular project.

@Syed-Omair This image here: https://docs.modalai.com/images/m500/vehicle-overview-right-144-1024.jpg shows where to look for the connector on m500, labeled "USB for VOXL (Under)"

@IFTEKHAR-HASAN It appears as though you're on SDK 0.9. Since then we've released SDK 0.9.5. However, I'd recommend loading an even newer voxl-modem package from here: http://voxl-packages.modalai.com/dists/qrb5165/staging/binary-arm64/voxl-modem_1.0.4_arm64.deb This one hasn't made it into an official SDK release yet but contains the quectel-CM updates I mentioned earlier.

@dlee Sent!

Hi @kimmy I am sorry for your observed issue. Those ports on the Microhard design are USB2 rated at 500mA and meet USB2 specs of 5V +/- 10%, which allows for 4.5V and still be considered in-spec. You are not the first to hit USB2 power delivery limitations. If your system really requires that precise of a voltage, and less of an allowance to the drop, you may need to consider pulling power directly off of our Power Module 5V, and not VBUS. Many of our solutions that require higher power than USB can handle do this, and many of our newer boards have new circuits that provide more than 500mA on VBUS to help with these higher demanding use cases. If you want to explore that type of test, you can use this board which has a jumper option to bypass VBUS and instead provide the 5V power supply voltage to the USB connector: https://docs.modalai.com/usb-epxansion-with-fastboot-v2-datasheet/ That will provide a good test for you to ensure your system operates the way you need before committing to a custom wire harness. Let me know if that helps!

Thank you both @Chad-Sweet and @tom for being super responsive on this technical forum.

@tom Filepath noted, and fortunately we did just update to 0.9.5 SDK. Files received! Thank you.

@IFTEKHAR-HASAN I have used this AT command at!selrat=06 to force only LTE mode on a Sierra cellular modem in the past.

Hi @Jack-Bishop , We're working on something that allows you to access the UART that is mapped to the DSP from the applications processor through a 'bridge'. We are successfully using this for our ESC tools but it's not abstracted yet into a clean example so I'm waiting on that for further possible guidance here that's more 'mainline'. This is what I'm referencing for short term, e.g. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/voxl_serial.py#L5

@Jagatpreet-Singh-Nir Oh, no. Sorry to hear that. Which landing gear does your M500 drone have? There are the tube legs, which are the older design and then we have the landing skids, which is our current design.

Thanks for the lead! Those both include this comment: # This is NOT a complete set of PX4 parameters. These are non-default parameters # specific to the airframe and are meant to be loaded over the defaults. A little bit of searching turned up this reference: https://docs.px4.io/main/en/advanced_config/parameters.html#tools Looks like my path is to follow that guide to restore all parameters to default values, then load parameters from the files you linked to. The drone we have shipped with a 4s battery, and ModalAI branded motors. Looks like that leaves us needing portions of each of the two parameter files. My plan is to modify RB5_Flight_V1_param_ModalAIMotors_3s_rev_A.params to include the battery configuration from RB5_Flight_V1_param_HolyBroMotors_4s_rev_A.params, and load the resulting file on top of defaults.

@suvasis You cannot modify the code on our ESC. But you can certainly add a new driver to PX4. I would start with the PX4 documentation: https://docs.px4.io/main/en/development/development.html

I am also trying to understand this. I was able to forward the mavlink messages from voxl to the station via wifi (using voxl-wifi station), but I am not able to specify the port as it streams everything to the default port 14550. How can I specify the port to which I can send the telemetry?