@lattanze , we are not 100% sure, but most likely not. This has never been attempted / tested and unfortunately we cannot provide support for this feature.

Hey Eric, so I ruled out the dsp as the problem since I am getting the same behavior on an nxp nuttx-flashed board. It appears the external device is the issue as it is not responding to i2c commands. From what I can tell qurt uses the same I2C 'transfer' command at least with the same parameters. It can find the device on the bus when I give the command "qshell xm125_evk start -X -b 4" but probing it appears to be impossible right now.

@Vinny Thank you very much for the reply, it is quite helpful. We will review the doc links again and take the lead times into account when making an order. We look forward to our evaluation of these systems.

@Alex-Kushleyev

Thaaaaaaaank you very much. It worked

INFO: ESC Information: INFO: --------------------- ID : 0 Board : version 34: ModalAi 4-in-1 ESC (M0117-1) UID : 0x2037343356435707003E001E Firmware : version 39, hash eb6fb500 Bootloader : version 183, hash 25317f42 Params : ../voxl-esc-params/mavic_mini_2/mavic_mini_2.xml ID : 1 Board : version 34: ModalAi 4-in-1 ESC (M0117-1) UID : 0x2037343356435707003B0022 Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 25317f42 Params : ../voxl-esc-params/mavic_mini_2/mavic_mini_2.xml ID : 2 Board : version 34: ModalAi 4-in-1 ESC (M0117-1) UID : 0x2037343356435707003C0019 Firmware : version 39, hash eb6fb500 Bootloader : version 183, hash 25317f42 Params : ../voxl-esc-params/mavic_mini_2/mavic_mini_2.xml ID : 3 Board : version 34: ModalAi 4-in-1 ESC (M0117-1) UID : 0x2037343356435707003A0057 Firmware : version 39, hash d4fe8e3d Bootloader : version 183, hash 25317f42 Params : ../voxl-esc-params/mavic_mini_2/mavic_mini_2.xml --------------------- successfully pinged ESCs disabling bridge bridge disabled DONE

@nickyblanch thank you so much for the great write up!

We accept pull requests if you think there is a bug or worthwhile improvement.

@aharvey

I believe TFLite Delegate logic is available only in C++ per TFLite Sources. Likely you would want to implement your inference code in C++ anyways as on VOXL your inference times will likely be much faster than in Python.

We have some example of assigning delegates inside our voxl-tflite-server source code, check out these lines: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tflite-server/-/blob/master/src/inference_helper.cpp#L216

Hope this helps,

Thomas
thomas.patton@modalai.com

Hi @Eric-Katzfey eventually we managed to solve the problem by resetting to default the parameter of px4 and performing the calibration from qgc

Thanks @tom much appreciated. Received the file.
Was following the instructions as mentioned here https://docs.modalai.com/calibrate-cameras/ for better understanding of calibration files.

@Alex-Kushleyev thank you so much for reaching out with support. I had to tear down the voxl2 setup and build out a pixhawk unit so I could complete thrust testing for our initial frame design. I will get the voxl2 model back up and running and test out your configuration. I actually don't think we have that cable. I'll have to put in order in for it. I'll post back with verification once I have the result.

I want to add that M0125 is no longer being manufactured and we use M0151 as a direct substitute going forward. I'll try to have our product folks clarify the website for that.

@tiralonghipol , great to hear! if you have this issue again, you should be able to recover the ESC using the steps I described.

@SMRazaRizvi ,

Please see the following post that answers your question : https://forum.modalai.com/topic/2551/add-mask-file-to-qvio-algorithm .

Specifically, you would need to add the name of the static mask file here (ideally full path of the file) : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/main.cpp?ref_type=heads#L384 (staticMaskFileName which is initialized to Null).

See the other thread for explanation what the mask format should be.

HI @iksk
That stiffener on the older units is not a shield. It's just floating metal (stainless steel). We have since moved away from all metal stiffeners due to electrical shorting risks in tight drone assemblies, and all new flexes have the laminate backers now. The laminate is slightly thicker at 0.8mm instead of 0.2mm.

If you are seeing performance issues between the two, it is purely coincidence and likely more result of manufacturing variance or handling resulting in degradation. We have built and tested thousands of the new ones and there are no stability differences between them.

Hope that helps.

@m4v3r ,

I think the ESC params installation failed during an upgrade. Not a big deal. Here is a procedure you should follow to get your ESC to a good state. We have been improving the update process, so hopefully this does not happen in the future.

get the latest voxl-esc tools on your voxl2. You can clone directly to voxl2 or to your PC and copy to voxl2 if your voxl2 does not have internet access git clone https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc.git -b dev stop px4 systemctl stop voxl-px4 make sure you can scan / detect ESCs . Note that based on your current state, the script should find at least one ESC running at 57600 baud rate, which would mean the param install failed (57600 is the fall back baud rate). This is ok. cd voxl-esc/voxl-esc-tools ./voxl-esc-scan.py install the params based on your motor / propeller configuration or any custom ESC param that you created. This script should find all the ESCs even if they are running at different baud rates ./voxl-esc-upload-params.py --params-file <path_to_esc_params_file.xml> install latest firmware (this script will auto detect the board and pick the correct firmware). Please note that if the ESCs are detected at different baud rates, that needs to be fixed with the correct params (command above). This script will not automatically find the ESCs running at different baud rates (we will fix this soon). ./voxl-esc-upload-firmware-all.sh

Then you can start px4 again if needed

systemctl start voxl-px4

Hi @rohitpillai
The intent of the power module is to take direct 2S-6S battery via the XT-60-M, and then pass that power input to two places:

a 5V DC/DC for VOXL / VOXL 2 using the Molex 4-pin with MCBL-00001 (https://docs.modalai.com/cable-datasheets/#mcbl-00001), not the XT-60 Output using the XT-60-F to an ESC/Other VBAT based item in your platform.

Both are measured by the sense resistor when connected properly as we instruct.

In some instances, as in the case of a VOXL 2 Mini, we have configured the Power Module to not output a downstream VBAT using the XT60-F (https://docs.modalai.com/voxl2-mini-power/#voxl-power-module), but a user is easily able to do so.

Hope this helps!

@Vinny Extremely useful. Thanks Vinny!