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

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

@cmall the VOXL 2 IO connects via UART. You could use any breakout board, like an Arduino, to generate PWM

@VictorG have you looked at the instructions here? https://docs.modalai.com/flight-core-v2-usb-to-qgc/

@Daniel-Rincon 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

The easiest way to connect an IMX412, AR0144 and TOF would be to follow the Starling 2 architecture found here: https://docs.modalai.com/voxl2-d0014/

To just connect the TOF directly to VOXL 2, the M0172 is likely what you are looking for: https://www.modalai.com/products/mdk-m0172-1-00

We need to connect the following: Forward Facing MSU-M0149-1, MSU-M0107, and VOXL 2 Time of Flight (TOF) Depth Sensor
Sensor with Adapter PCB and M0177 Starling Flex (Molex 40-pin) and a second TOF Depth Sensor in the Rear of our platform as well facing downward. We seem to not be able to figure out which connector works from the TOF we have (MSU-M0178-1-01) with any of the connectors or adapter we have purchased. Do we need to instead be using the (MSU-M0169-1-01) TOF sensor and PCB? Or is there a way to buy the connector and PCB separately to use with the ones we have?

I’m setting up a delta-wing platform with the VOXL2 and using the VOXL2 IO board (M0065). I followed the instructions provided here to update the firmware.

However, I couldn’t locate the m0065_firmware.bin file mentioned in the instructions on the public downloads site. Instead, I used the voxl2_io_firmware_m0065_v1_35_58c82813.bin file. I later realized that this firmware is only compatible with VOXL2 SDK v1.1.1, while I’m currently using SDK v1.4.1. I don't see any other firmware file for the m0065.

Could you please advise how I should proceed to reflash the IO board with the correct firmware version compatible with SDK v1.4.1?
I appreciate any guidance you can provide.

@kerct the higher number cores are larger and more powerful, and they generate more heat. So, the kernel is intelligently biased towards keeping the chip from overheating

@cegeyer that does seem suspicious

Here's the code for cpu-monitor https://gitlab.com/voxl-public/voxl-sdk/services/voxl-cpu-monitor/-/blob/master/server/voxl-cpu-monitor.c?ref_type=heads