Is there a way to access the kernel serial debug port on M0090? It seems there are FTDI components but they are not populated.

@tahawaru Here is some documentation on configuring VIO https://docs.modalai.com/flying-with-vio/

PX4 does not currently handle GPS and VIO concurrently. It is something that we have worked with the PX4 developers on for more than 2 years.

It's a complicated problem though that we keep working to improve. To start experimenting, and hopefully helping to develop that feature, read through PX4's documentation on EKF2.

To debug VIO, look to this area of the documentation specifically https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

@Jetson-Nano Looks like MPC_POS_MODE is needed as well per the documentation https://docs.px4.io/main/en/computer_vision/collision_prevention.html

voxl-mapper has been working on VOXL 2 for about a year. It should work out of the box on a Starling.

What you may be referring to is better documentation for using with stereo sensors instead of TOF sensors, but in general the voxl-mapper package is working.

This video shows how it works - https://www.youtube.com/watch?v=gqlSKRP8prc&ab_channel=ModalAI

When making a request for support, there are some key pieces of information that really help speed up the support process. Please try to include the following when making a request:

• What hardware are you using? If you have specific SKU or serial number, that is also helpful
• What version of software are you using? voxl-version is very helpful for determining software version.
• How have you configured the software? What is the output of voxl-inspect-services
• Do you have any logs? Uploading PX4 logs to https://logs.px4.io can be very helpful. See details on PX4 logs here
• Can you share pictures of your setup?
• Have you looked at the source code? If so, can you point to any potential issues?

If you see the sensor in the portal, you have the sensor configured properly.

By fails to calibrate, are you using voxl-camera-calibration ?

if you viewed the data through voxl-portal, it would already be rotated properly.

The Starling's extrinsic parameters can be found here, which should help you configure your URDF

@Amir-Avni On VOXL 2, voxl-mapper runs < 10% of CPU in typical configurations, on VOXL 1 < 30% of CPU

@Sanket-Shah voxl-inspect-cam can be used to verify it's working and see related stats. You need a GUI of some kind to actually view the image, which requires a network

@tiralonghipol if you viewed the data through voxl-portal, it would already be rotated properly. It's not clear which viewer you are using for the data.

The Starling's extrinsic parameters can be found here, which should help you configure your tools

Yes, when MISP is enabled, voxl-camera-server will output a pipe with the suffix _bayer

For IMX412, there should be a pipe named "hires_bayer". That pipe is outputying raw bayer data directly from the sensor

For color measurement and validation on the IMX412 module we require either:

1. Direct RAW image output, or

2. An ISP fixed configuration (with all automatic/adaptive functions disabled).

Could you please confirm whether RAW output is available?

VOXL 2 is a Linux computer, so if you want to write software to coordinate multiple UAS you have open access to do so

For Flir support, you can start here: https://docs.modalai.com/M0153/

For flight I/O, you can refer here: https://docs.modalai.com/voxl2-connectors/

For software support, you can refer here: https://docs.modalai.com/voxl-sdk/

Good morning, I have three Starling 2 Max's with your VOXL Cellular LTE and USB hub add-on. I am struggling to find a sim card / data provider that is reliable. While I could connect with a sim card from Hologram, their network prioritization was not ideal and dropped too often for reliable MAVLINK based control. I have sense tried Mint, and AT&T data cards which never would connect. I am hoping to skip the guess work and inquire to if you have a list of known good sim card providers and plans.

For Mint Mobile, I have tried "wholesale" and a few others for the APN. Can you pass what configuration you used?

Sorry you are running into issues

Can you help with some more information?

• What motor are you using with the M0129 ESC?
• What battery cell count are you using?
• Have you performed the ESC calibration?
• Can you share the ESC params you are using?
• Can you share a video of the issue?

@Idan-Fiksel Is the calibration card mounted to a hard backing piece so there are no warps or wrinkles in the checkerboard?

Did you print with a PDF so that the checkerboard measurements are accurate?

@Breanne-Crockett yes, the depth sensor is pointed straight forward

We do not have support for Realsense

@lohithvamsi it is probably easiest to return

Please reach out at https://modalai.com/contact and reference this post.

You might have both qvio and openvins running? That could lead to issues. Only one should be running at a time

have you looked through the troubleshooting guide? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

Usually looking at the ovins-overlay in voxl-portal offers good insight

The common issues are vibration is too high, the extrinsics are incorrect or there are not enough features to track in the environment

@QSL here is our app note on thermal https://docs.modalai.com/voxl2-thermal-performance/#thermal-performance