Hi @austin-c
Sorry I missed this message somehow.
I will email you to kick this off with your team.

Hi @irw
Can you please post High Res and clear photos of both sides of the VOXL 2?

Hi there, just to confirm: does flying manually in position mode work and follows the XYZ position in voxl-portal's VIO page. as well as follows figure 8 mode too? This will confirm the vio pose estimate is correct and more of a issue on mapper.

@Aniruddha Did you follow this guide: https://docs.px4.io/main/en/config/level_horizon_calibration

Hi @Daehan-Won
To help us, what camera and how is it connected (cable details, with photo will help)
We want to first understand how much power it needs.

However, if it appears upon boot up, that is usually the worst power draw (in-rush), so I'm not inclined to think this is the case. It may be loose wiring, which is why a photo of your cable setup will also help. Even the slighest intermittent glitch on USB will create USB reconect events.
You can monitor that in a VOXL console (over ADB) with this command :

dmesg -w | grep -Ei 'usb|xhci'

Thanks!

@Aniruddha Can you use level calibration in QGC instead? Are you saying that you are crashing after running voxl-calibrate-px4-horizon or in your attempt to run it? What flight mode are you using in your flight? If you fly in manual mode is everything okay?

@DronAlan With 1.6.3 SDK upgrade, did you test against the figure 8/offboard mode? Also flying in position mode after drawing the trajectory, if you manually fly the path you created, does the drone follow correctly? If position mode manual flying is working fine and figure 8/offboard mode is working fine (a clockwise figure then we have a trajectory calculation problem on the voxl-mapper side (I'll check our code, but our QA currently show that was working properly).

Since you're using OpenVINS vio module now, there's an unlikely chance of a reset causing a 180 orientation change by design. Also make sure qvio is disabled. You can check if it's running via voxl-inspect-services and run systemctl disable voxl-qvio-server (+reboot).

@Daehan-Won The mb12xx px4 driver is not in our build so you would need to add it to the voxl2-slpi build. Which pins are you attaching it to on J19?

@DronAlan Hi there, when the camera was rotated 180, you'll have stable take off behavior, but any XY movement would cause the drone to 'fly away' quickly.

Taking a step back with your concerns on physical mounts:

1. checking camera orientation:
   a. bring up the front camera in portal: it should be upright orientation, e.g. top of the camera image should be from the top of the drone itself ("tops are aligned").

2. Since you are using qvio, only 1 camera is supported. Ensure in /etc/modalai/vio_cams.conf has tracking_down disabled, It's a safeguard if qvio is accidentally using that camera (would would lead to a orientation problem).

As for IMU, the voxl2 unit should have the USB-C port facing the bottom/ground side (and WiFi dongle on the top side). Let's force reset the imu calibration. If you run on the drone voxl-calibrate-imu and follow the directions, will reset the imu.

Let's check these items. If they all pass and still presents the orientation problem, then it's worth moving to the SDK1.6.3 to take advantage of the advanced config installer.

@Dan-Jennings I'm also guessing that the driver may not be detecting the hardware so is not able to get the data for the battery_status. Have you tried swapping some other hardware to see if the problem is associated with a particular unit?