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

We have updated the M0129 in the past few months to support 2S-6S, it looks like the datasheet is out of date. Thanks for pointing that out.

If it is marked M0129-63 or M0129-65 it supports 6S

M0129-3 and M0129-5 are the older version and they only go up to 4S

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

VOXL 2 Mini USB OTG negotiates automatically. There should not be a special cable required for VOXL 2 Mini

VOXL 1 required a special cable and VOXL 2 OTG does not currently work

@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

@JoonaR can you please provide your order number? Is there a chance you ordered the "no radios" configuration?

@taiwohazeez start with going through the troubleshooting tips: https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

qvio_overlay or ovins_overlay are going to be very informative

@leandro The M0188-1 includes the connectors for the TOF range finders. We have not offered that board before though. Where did you find that information?

What was your order number? We can send you a M0188-1, but it may not be available for small orders in the future

@maddercat The Zorro Blue has a 1W 915MHz ELRS 3.5 radio, configurable with typical ELRS parameters

The hardware is a COTS Radiomaster Zorro where we replace all of the electronics to ModalAI electronics for NDAA-compliance.

It is a stop-gap so we can offer a standard FPV-style R/C controller until we can offer something more fully developed FPV R/C controller

@clange It is technically possible as Stinger is supported by the same VOXL SDK as all of our products. It would likely be a lot of software development to make it happen though

@jbhines929 Hi JB, sorry you are running into issues.

One quick thought, is to update the Orqa goggles firmware - https://orqafpv.com/downloads . There were issues at one point, but we have been updating them in the factory recently before shipping

To further isolate, can you plug a different display into the VRX DisplayPort output? Or, try to connect ADB to the VRX? that would let us know if it's a Goggles or VRX issue. (sounds like goggles if they are clicking)

You can always submit an RMA here: https://modalai.com/rma

@jimbow77 those drones are for aeronautical research. we recommend installing a dronetag or similar

@brandon from the factory, it is typically configured for VIO flight. You should configure for GPS as VIO may not be well tuned for your outdoor flights

You can find some helper parameter files here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/tree/master/params/v1.14/EKF2_helpers?ref_type=heads

@Saleh-Ibrahim the drones come pre-configured for VIO and are flight tested in VIO mode prior to shipping.

To troubleshoot VIO, please start here: https://docs.modalai.com/voxl-open-vins-server/#troubleshooting

VOA does not ship enabled by default

@Arsalan-Sheikh You can find a 3D STEP file here https://docs.modalai.com/starling-2-max-datasheet/

We aren't familiar with the Gazebo requirements so hopefully the STEP file gets you what you need