@Matt-Turi Thank you for your quick response. After updating to v0.0.5, it worked!

@tom After playing around with CP_DIST, it seems any value > 0 causes position mode to no longer want to allow x/y translation. From what I understand, any value < 0 disables object avoidance. Is this true? As far as I'm aware, my settings should be in parity with Modal provided guidance in regards to seeker setup with additional configurations overridden to support voxl-mapper. Thanks for the stabilized advice @mohammednaveed, I've gone as far to replace manual mode with this setting.

@Todd-Humphreys Hi Todd, I believe they are replacing them with almost identical motors but with a slightly higher KV value. If you can source those then they would be a drop in replacement. If you're interested in something else, then here's some that I've tested before. The only thing is you'd need to solder the 3 male 2mm bullet connectors onto each motor. Otherwise they're drop in replacements. https://usa.banggood.com/Racerstar-Racing-Edition-2216-BR2216-810KV-2-4S-Brushless-Motor-For-350-380-400-450-RC-Drone-FPV-Racing-p-1083206.html?utm_source=googleshopping&utm_medium=cpc_organic&gmcCountry=US&utm_content=minha&utm_campaign=minha-usg-pc&currency=USD&cur_warehouse=CN&createTmp=1&ID=521309&utm_source=googleshopping&utm_medium=cpc_bgcs&utm_content=sandra&utm_campaign=sandra-SSC-usg-sku-1019-xp-cvrcart-11sale-21&ad_id=554267045258&gclid=CjwKCAiAjoeRBhAJEiwAYY3nDF7t6brTndAN6m0qocX3YTDihgCK1dw6y2-u2YtW9OWuC_Xq_bipZxoCnv8QAvD_BwE

@Chad-Sweet I can confirm that we can communicate with the pddl900 inserted into the ModalAI USB Carrier board...thanks!

@Nathan-Sullivan Awesome, great to hear! Yeah, that's a sneaky one that's gotten me a few times Thanks, Rich

@Chad-Sweet Thanks for your reply. I am currently running firmware FCv1 - v1.11.3-0.2.3 from that link. I downloaded the image and then uploaded it through QGC as a custom firmware. Thanks, Karl

@Alex-Gardner all right, thanks for that

voxl-cross 1.7 is a build containing some new gcc toolchains for projects that are not yet on stable. The cross image is meant to be able to be easily built by any user, hence why it was built and installed when you installed the docker image. We've just pushed that image to the downloads page should you need to download it from there. As for the docker image docs, you are correct they are out of date right now, we're planning to update them soon and have been delaying doing so because we've been making changes to them.

If you've made specific changes to specific config file you'll need to back them up manually either to a host pc or the data partition, otherwise the data partition will be saved which contains the camera calibration files and the factory settings for the config files which can be restored on a new system with voxl-configure-mpa --factory-reset

@modaltb All right, I see. It does sound tough. Instead, I think I may have a chance to only enable the stabilization by manually pre-set a fixed angle for the gimbal. If so, I don't need to connect to VOXL-flight, and I could just need to think about a separate power supply for the gimbal, right?

@Chad-Sweet Thanks, I see. I had the debug board, but it may not be able to work for special expansion. Anyways, I will think about that.

@Jimk_Aero Please ignore the previous question. I just needed to reboot the Flight Core and all is OK.

ModalAI does not produce fixed wing aircraft, but it is possible to use our technology for fixed wing aircraft. We do not have any documentation or direct references as of now though.

Hi @Chad-Sweet Thank you so much! Will have try it out first on the flight deck. Thanks & Regards, Mohammed Naveed

@Matt-Turi I wanted to try the resnet architecture as the accuracy/speed ratio is a bit better than the mobilenet architecture. But it's not a hard requirement, so I'll just use the mobilenet architectures. Thanks!

@Chad-Sweet said in QGC obstacle display bug?: Hi, we have not actually used QGC to debug collision prevention ourselves. The tools we use to debug collision prevention can be found on our docs here If you find anything related to QGC integration, a follow-up would be appreciated! Thanks. Will probably report this to the QGC dev team as an issue

For GPS flight, the m500 performance is similar to most PX4 GPS Flight. The performance is subject to standard GPS position accuracy, which is generally ~1.0 to 1.5m accurate. For VIO flight, in a reasonably environment the typical accuracy is 1.0 to 1.5% drift over distance traveled.