@Moderator Thank you for your reply but I am able reach only the files of latest version of Starling from the datasheet and I need the CAD files of the one below if you have it:
While we so technically support mapping using stereo we almost always use the tof sensor ourselves since it's much more accurate at higher resolutions. The default for our voxl-mapper project uses the tof sensor for mapping with option to enable stereo if that's what you want to use. We generally just use stereo for collision prevention since it's pretty reliable at detecting if something is in front of it or not but can struggle to populate a detailed full-fov image in realtime.
Additionally, the PID loop for position might need some tuning if you want it to stop more aggressively.
Thanks for the suggestion but I'm quite certain it has nothing to do with MPC_POS_MODE nor the tuning of the velocity/position controller. The phenomenon I described only happens sometimes - especially when VIO quality is low for that stretch of journey just before the drone comes to a stop
@ahmed-mustahid Unfortunately the "QUSB_BULK" mode that your VOXL is enumerating in cannot be fixed by our unbricking process and will have to be sent in for an RMA. See here for info on the RMA process: https://www.modalai.com/pages/rma
@Eric-Katzfey Hi Eric. The jpeg compression imposes a lot of load on the CPU, especially we're using the hires camera. Is there any way you can make the HW jpeg encoding available for us to test it?