I suspected probably it is because of the fused local position by vision and searched in parameter. It sounds EKF2_GPS_CTRL is probably relevant. So, I set it to be 0 from 7. After trying that, my outdoor missions were all smooth without any accident. I then set it back to 7 and tried flying in position mode. This error happened again and with altitude mode was forced. So, anybody here know how to fix the problematic local position estimate? This is an AI drone and it shouldn't perform worse than drones without any vision.

@soraminds https://forum.modalai.com/post/19601

@Animeshs said in Tracking Camera Sync: Are the tracking cameras on Starling 2 with C26 (dual tracking) and C27 (triple tracking) configs synchronized? @Animeshs I believe if the fsync parameter in the /etc/modalai/voxl-camera-server.conf is set to true then the cameras will be in sync. Zach

@Zachary-Lowell-0 Hello! I was able to reinstall 1.3.5 and that somehow fixed it! I am not going to question it lol. Now I'm trying to find out how to install voxl-mapper and I can't find documentation for it. I am flying the drone inside a test lab. Today when I was flying it around the room, the drone was not mapping anything. The 2D/3D map was blank when I went to plan a point. I think it's blank because I am missing voxl-mapper especially since I have camera-server, vision hub, voxl-px4 and qvio enabled/running. All I have seen is that I have to change "offboard_mode": "trajectory", in order to plan a point on the map and have the drone fly to it. Is there any documentation on getting voxl-mapper and planning a point?

@tom I found the voxl-modem script in usr/bin, thanks! Swapping out the logic in the microhard_configure function with the v1.1.0 sdk revision worked for me. My only suggested change would literally be reverting to the exact same logic for that function as was used in the previous version. I'm assuming it was changed for a reason,but idk what that reason is. I guess my question was more "why did this change and can we just change it back?". Is that more something I should raise as an issue on the gitlab repo or should I just submit a merge request like you said and let you guys figure it out? Sorry not sure what best practices are when raising these kinds of things

@Usama-Hamayun you can order the drone without battery. The Starling 2 and Starling 2 Max both use the same battery packs. They can be either Sony VTC6 or Amprius 18650 cells

@tpavlic did you find the CAD files?

@smilon The parameter EKF2_REQ_SACC sets the maximum allowable speed accuracy. If you increase that value does the warning go away? Can you post a log?

@Thomas-Eiszler , As long as you dont actually have the APM connected, having the power manager driver enabled in PX4 will not conflict with the mini ESC also reporting battery_status. This is because even though the APM driver in PX4 will attempt to start, it will fail to find the actual hardware device (via i2c probe) and will exit the driver. However, it is best to disable the power manager (APM) driver. Starling 2 MAX uses two 2-cell packs in series, so it is a 4-cell pack. when you run voxl-esc spin test, it should report voltage reported by each ESC. Does that match the actual battery voltage or is it also wrong (as is reported in your battery_status ? Alex

@Moderator Hi thank you for the link, may I check if the original 4921 green propellers are not supported anymore? And instead the DJI 4726 are the recommended replacement propellers? Also, would an ESC recalibration be necessary after the switch? Thanks.

@ayrric yes, you can find it here: https://www.modalai.com/products/m0155

Did the trick btw

@Moderator Yes, I did see that. However I expected this to work out of the box. I haven't changed anything.