Timeline for open-vins documentation

[Zachary Lowell 0]

@Viktor-Gal said in Timeline for open-vins documentation:

i can run the imu_apps calibration and retry OV.

1 Reply Last reply about 15 hours ago Reply

a day ago

@Zachary-Lowell-0 so those params are after running voxl-configure-mpa; i still dont understand why there's a diff between the apparently same v2 starlings.

i can run the imu_apps calibration and retry OV.

RE: No you are sending the PX4 parameters not the voxl2 parameters. Runnign voxl-configure-mpa will configure some px4 parameters, but after you open up qgc and then calibrateall the sensors in there, it will change some of those parameters, hence why those specific to imu calibration and mag cal are different from drone to drone. I highly recommend sticking to qvio with single camera tracking for now as OVINS is still heavily in development.

[Viktor Gal]

@Zachary-Lowell-0 i hear you, but could you maybe give some pointers how one could make the qvio more stable? as i said it is at the moment only has 25% success rate: meaning 1 out of 5 flights i dont have problems with the qvio, the rest of the time the drone becomes unstable and crashes.

[Moderator]

@Viktor-Gal have you read through the troubleshooting VIO documentation? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

[Viktor Gal]

@Moderator yep, back and forth. unfortunately no change.

[Viktor Gal]

@Moderator et.al. i just want to follow up that switching to the nightly builds that uses out of box the openvins implementation for VIO, is significantly better than the qvio. in other words, it actually fixed all the problems that we were facing with the QVIO.

[Eric Katzfey]

@Viktor-Gal Excellent, thanks for the feedback!

[star123]

I'll put a question here since it's open-vins documentation related. I also am successfully running nightly builds of open-vins, and it is working well for me.

I would like to add image masks to the tracking cameras to block out certain areas. I see the option "use_mask" in voxl-open-vins-server.conf, which I can set to true. I can't figure out where to put the mask files, or how to specify their path and file name?

If this should be a separate thread, please let me know and I can move my question elsewhere, cheers!

[dlee]

@star123 What does nightly mean? The latest version of voxl-open-vins-server or voxl-suite. Thanks.

[tom]

@dlee We publish "nightly" SDK builds at https://storage.googleapis.com/platform-nightlies/voxl2/voxl2_SDK_nightly_20250213.tar.gz (URL will match yesterday's date, PST)

This takes the latest of each repo's dev branch as well as the latest system image built every night

[Cliff Wong]

@star123 At this time masks are supported through programmatic means only.

I'll add it to our feature list for the next release and should be in our nightly builds by mid-next week. If you take a look at /data/modalai/zero_ref.jpg is an example format to give you an idea when the feature is ready.

[dlee]

@Viktor-Gal I am troubling localization with QVIO. So I wanted to change vio algorithm to OpenVINS. I flashed my drone to nightly version but openvins still very unstable. Could you give me some guidance for openvins?

Questions

1. openvins configuration & versions
2. Did you enable the voxl-feature-tracker?
3. camera settings (single or multi, camera model, etc)

My status

• voxl-suite: 1.4.1-202502132201
• Camera: old-version of tracking camera (640x480) - link
• voxl-open-vins-server: 0.3.0-202502061726
• voxl-feature-tracker: 0.5.2-202412171357