Topics created by Aaron Porter

@Aaron-Porter , thank you for clarifying. We resolved your issue offline, as this was a pre-release development effort.

Moving forward, all customers have two options:

if you already purchased M0065 without ModalAI bootloader (the board was using old px4io bootloader and firmware), you can request a free replacement that will be sent with our latest bootloader and firmware installed (please request via support email) all the new M0065 shipments will come with ModalAI bootloader and firmware

With the new bootloader / firmware combination, there is no need for STLink at all. The firmware will be updated via UART directly from VOXL2 or optionally via a USB adapter. The firmware update protocol is very similar to our ESC firmware update protocol, so we will be able to use voxl-esc tools to perform the firmware update.

We will be updating the docs shortly (https://docs.modalai.com/voxl2-io-firmware/) and will post an update here once it's ready.

Alex

@Aaron-Porter The tracking sensor does not need to be straight, but the extrinsics need to reflect the accurate position of the sensor relative to the IMU

if you monitor the qvio-overlay in voxl-portal, it's usually obvious what is going on. If you need help interpreting, please post a screen video capture of the qvio-overlay here

@Aaron-Porter So I made a mistake that the IMU-server was not running during my screen shots. But I figured out the issue. Yo can use the starling file you have to run the command,

voxl-configure-qvio factory_enable_imu_apps

This will tell qvio-server to look for imu_apps instead of imu0.

@Moderator
Thank you

So this is the correct functionality, and that the Data is updated relative to the IMU and not to the Body of the Drone.

@Aaron-Porter I am facing the same issue, is it solved?