https://github.com/PX4/PX4-user_guide/blob/main/en/flight_modes/follow_me.md

I am not sure about that adsp.service error.. Hmm. Would need to actually look into what it's doing. but it seems like if you just (re)move the firmware, the GPIO works.

@hmlow It might be useful to open voxl-portal and have a look at what the tof is reading when you are seeing this phenomenon. If you would like something more in detail you could Would you be able to turn on Computer/Collision Avoidance under sdlog: SDLOG_PROFILE [image: 1679429073812-6694f651-226f-4b94-8a9f-b0558b76e87a-image.png] recreate the issue verify that PX4 is getting a detection that there is something infront of it through the logs. the message you are looking for is OBSTACLE_DISTANCE

Thank you so much.

@suvasis Unfortunately, motor testing using the QGC motors tab is not supported on VOXL2.

Thanks for the info! Just to confirm, I am asking about this post ModalAI made on LinkedIn - https://www.linkedin.com/posts/modal-ai_voxl-tof-pmd-activity-7010997849232474112-VV6a?utm_source=share&utm_medium=member_desktop This update is almost a year out? Thanks.

hi @suvasis #test voxl-esc tools cd /home/root/voxl-esc/tools ./voxl-esc-scan.py #perform ESC testing / calibration #... this was just a place holder for any testing you want to do with the voxl-esc tools. #when done, restore original libpx4.so cd /usr/lib/rfsa/adsp rm libpx4.so cp libpx4.so.bak libpx4.so systemctl enable voxl-px4 reboot This part restores the PX4 functionality, because in order to use voxl-esc tools on VOXL2, the instructions told you to disable PX4 while using voxl-esc tools. Soon we will not require disabling PX4 to use voxl-esc tools, but currently you have to do it. Please note that we just made some updated to the voxl-esc tools and directory structure has slightly changed. Also, you no longer have to download the binary tools package and add it to the voxl-esc/tools directory. Please see an example params file here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-params/old/esc_params_modalai_4_in_1_revb.xml

@tom It's probably normal afterall since the voxl-vision-hub service's config file contains a parameter "reset PX4 on error". I set it to "false" and now this behaviour disappeared.

I updated to the beta 1.5.3 image and this camera now works with it on its own. Thanks!

@luca-di-laudo There you go! https://gitlab.com/voxl-public/flight-core-px4/px4-parameters

@Chad-Sweet Thank you for the guide. Noted that the workaround to get decent video quality is to increase the bitrate - 3Mbps (h/w encoding) gives comparable quality to 1Mbps (s/w encoding). Hope that the upcoming fix could overcome this problem (using encoded source from qmmf?). Looking forward to it. Thanks

@Nicolas-Ethan-Blanchard I also re-loaded PX4 parameters from the provided file in the GitLab, so that could have helped as well. Although, I do think that the IMU orientation parameter was set correctly initially, because it matched the parameter in the working drone.

@JustinDev23 Great! Thanks for your patience, I just generated an official release of v0.16.2 to ensure that it makes it into our next SDK release.

@modaltb, thanks for the follow up. it ended up being a driver issue. I am not doing any kernel changes. I am using the Sentinel and it was not purchased with the wifi module or cabling. I have an assortment of the wifi usb adapters, using one of the older ones (AWUS036NHV) worked.

Please refer to the M500 factory parameters here: https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/M500