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

@FIREBIRD Sure, reach out at https://modalai.com/contact

Yes, it's supported in production volumes

@QSL Hi, thank you for reaching out. There are many ways to achieve what you are trying. Starling 2 is the best starting point. You can then learn about what will work and what will not work and build out your system design from there.

@Ege-Yüceel You can find our warranty information at https://www.modalai.com/warranty

You can find the STEP file for the design here: https://docs.modalai.com/starling-2-datasheet/#starling-datasheet

Starling 2 replacement parts can be found here: https://www.modalai.com/products/starling-2-replacement-parts

If there is a part you need, we can make it available for purchase.

@dguido2023 Sorry you are struggling with your Ghost Receiver. Can you please help with an explicit issue or question? We don't have a problem configuring these in the factory, so maybe we can get you setup quickly.

Have you looked through this guide? https://docs.modalai.com/orqa-ghost/

Which SKU of Starling 2 do you have? Was it preconfigured with a Ghost receiver?

What version of SDK are you using?

If you installed the receiver yourself, how is it connected to the VOXL 2?

Are there specific configuration steps you tried that failed?

@Käptnzursee There is no restriction for voxl-mapper running on VOXL 2 Mini. Is there any reason to believe it shouldn't?

@yardy Folks recover using that tool all of the time. When it doesn't work, it's due to hardware damage. Often from ESD, or simply crashing the drone. See https://modalai.com/handling

@wen-max On the datasheet it says take-off weight of 566g https://docs.modalai.com/starling-2-max-datasheet/

Take off weight includes the battery

@Aaron-Porter That's not really the point of voxl-logger. voxl-logger saves the data as close to native as possible so it can be used with voxl-replay for simulation. PNG is often used as it's lossless compression. You could fork the project and add a new format. We're always interested in pull requests for new future additions

@wen-max Yes, the 500g payload capacity is in addition to the battery.

If you double the weight, flight time will be cut in half

The 3000mAh packs use Sony VTC60 LiIon cells and the 4000mAh packs use Amprius Silicon Anode cells