@SKA , I am not sure. please disable all streams except preview and try again. specifically disable:

small_video large_video snapshot

Double check to make sure:
en_raw_preview: true
en_preview: true
en_misp : true

It seems you have at least small_video enabled.

What camera resolution are you requesting? (preview_width, preview_height)

Alex

@ey , please send us a request via http://www.modalai.com/pages/contact-us

Alex

@Catalystmachine , for questions regarding orders, please reach out here : https://www.modalai.com/pages/contact-us

@jh81306
Hello there,
Yes, real time performance is achievable with 3 cameras at 30fps, evidencing the benefits of our hardware accelerated GPU feature tracker. From this perspective, if you plan on using GPU-heavy applications, QVIO may be the second best option, as it uses remote procedure calls between the linux processor and the DSP, freeing GPU usage. However, due to the inherent nature of the DSP (L2 Cache, etc) and timing considerations, running QVIO on 3 Cameras may not guarantee a consistent update rate depending on the processor load/scheduler priorities. In essence, choosing one or the other is a trade-off that should be based on user use-case.

In terms of estimator robustness, our branch of OpenVINS has been considerably modified to support accurate estimates under degraded conditions, and all ModalAI UAV platforms have gone through extensive calibration in order to obtain the optimal parameter set. Hence, in terms of estimator quality, OVINS outperforms QVIO, but requires carefully calibration of your visual-inertial sensors. Finally, If you opt to acquire a ModalAI Vision drone, OpenVINS should be fully functional out-of-the-box, facilitating a potential pipeline transition.

Hi @austin-c
yeah, and it will not.
There are dozens of changes between the two boards.
It's just easier and cheaper to order the correct version. We have no documents showing how to convert it is simply not doable for the cost and risk and time.

Not the news you wanted, but please trust me on that one. 🙂

@Catalystmachine

https://www.modalai.com/products/m0155
https://www.modalai.com/products/m0188 (fixed link)
https://www.modalai.com/products/m0194

If you need M0195, you can contact us directly for a custom order (it's not in the shop yet).

https://modalai.com/contact

Alex

@yashpatel ,

Please see some responses below:

i2c_geni a84000.i2c / 884000.i2c: i2c error :-107

This is likely due to a service that is enabled for a sensor that's not present, so the service is restarting and trying to detect the sensor.

please make sure the voxl-rangefinder-server is not running and also voxl-lepton-server. you can disable the service using systemd : systemctl disable voxl-rangefinder-server. CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22

this one is usually present when you have a sensormodule driver in /usr/lib/camera for a camera that is not actually plugged in, so the probe fails. Double check the cameras that you have plugged in vs sensormodules peresent in the directory above. However, this is usually harmless, if all of your cameras are working properly.

Pin conflict.. We will double check that, but GPIO 130 is on a Board to Board connector that you are most likely not using, so that should not be an issue.

VIO performance..

please review : https://docs.modalai.com/flying-with-vio/ try to identify the condition that caused the low feature count (look at the actual images, if possible). may need some hand-held testing and looking at the output.

Please let us know if you have any other questions.

Alex