@Abdullah01 , OK this is strange. So it seems like all the cameras are functional, because originally you were able to detect TOF and Hires camera, but not tracking camera. However, now you can detect hires and tracking but not TOF. I am not sure why this is happening. Are you able to do a clean install of SDK 1.1.2 and follow the same configuration option as you originally tried (TOF + Hires + Tracking). Make sure to plug the cameras as instructed here : https://docs.modalai.com/voxl2-camera-configs/#c-14-tof-hires-and-tracking

@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.

@david-devassy Hey David, We do support deep learning inference on VOXL2! You can check out this page on our docs to read more about our deep learning capabilities. Out of the box our YoloV5 model gets around 30 frames per second. You also mention object avoidance and SLAM using path prediction. We have our own implementation of Visual Object Avoidance (VOA) which you can read about here. You could certainly create custom implementations of both of these on VOXL! However I want to highlight that our code for both of the above is C/C++ and not in Python for speed reasons. I can't give you a reasonable estimate about Python performance but it would likely be slower. Hope this helps! Let me know if you have any other questions. Thomas Patton thomas.patton@modalai.com

@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.

@ejohnson01 Can you try bringing this commit into your build and see if it resolves the issue: https://github.com/modalai/px4-firmware/commit/f945d29064b4ab26617a3fb15fc770f5dcb993e9

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.