@Manu-Verma , please see the details in the link below. Please note that Modalai ESC calibration is not the same thing as the typical ESC calibration. QGC does not support calibrating ModalAI ESCs and it needs to be done using voxl-esc tools running either directly on VOXL2 or a Linux PC. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-tools/calibration.md

@Moderator thank you I appreciate it.

Hello, I am trying to get pretty much the same thing working on the VOXL 2 with a Yolov5 model that only has one class. I am seeing similar outputs when I deploy it to the drone. @Siyu-Chen, what steps did you go through to get this working on your device? The model inferences just fine on my computer. I think it has something to do with the pre/post-processing. Thanks in advance for your help.

@boga If SDLOG_PROFILE doesn't have what you are looking for then you can set up a custom set of log topics / rates from a file. You don't need to recompile PX4 to use it. https://docs.px4.io/main/en/dev_log/logging.html#sd-card-configuration

@Wei-Cui How did you wipe the /data?

@david-devassy I'd recommend sending in an RMA: https://www.modalai.com/pages/rma and we'll get things sorted

Hello LaborzaubererTHI, You can see the video now as it has been set as unlisted. https://www.youtube.com/watch?v=jjCKZmrqrVQ Sorry for that. Regards

@Ajay-Bidyarthy Only the inference time should be affected by your choice of hardware. The other two should be the same regardless of your choice. Thomas

@Eric-Katzfey So you probably just need to do the magnetometer calibration procedure to be ready for flight.

@Eric-Katzfey said in Take-Off and Land command each fly to xy=[0,0] location instead of on the spot: @LaborzaubererTHI Sounds like it may be similar to: https://forum.modalai.com/topic/2533/failsafe-landing-bug-in-px4-1-14/19?_=1713800679314 Indeed it does.

@Dawid-Mościcki Perhaps you can ask the QGC development team for some help in narrowing down what is causing QGC to crash. If you think there is a missing parameter then in your /usr/bin/voxl-px4-start script add a new line to touch the parameter so that QGC will see it. (e.g. param touch SDLOG_MODE)

I reflashed firmware and reconfigured drone manually (not using automatic scripts which platform detection) and problem vanished. Probably there is something wrong with detecting actual drone version in those automated scripts.

If any1 will have similar problems in future don't follow guide : https://docs.modalai.com/sentinel-user-guide-pre-flight-setup/ See those docs : https://docs.modalai.com/voxl-elrs/ All You need to do is voxl-elrs -b, then on aperture go to ExpressLRS and choose bind Can be closed.

@Eric-Katzfey thanks mate for your answer!

@Dawid-Mościcki Wow amazing I will give this a try very soon. Thank you so much!

@Alex-Kushleyev Thank you! This worked perfectly, got all of the motors spinning

@enrico-bandera-0 OK got it. You alluded to this, modifying something like hub.c (Generally if it's not showing up, we need to find some flags to add. For example, we added some USB modems like this: https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/patches/005-telit-option.patch https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/qrb5165-ubun1.0-14.1a/recipes-kernel/linux-msm/files/patches/004-quectel-usb-wwan.patch ) We'll likely need to find similar for TUSB8041 and then try to add if it's not showing up by default. Are you plugging this TUSB8041 hub into a USB port or using custom hardware? Have you located anything from TI that tells us what flags to enable? That's where I'd go next, see if vendor has clues and then we can try it out.

@wilkinsaf No, they are exactly the same