@clange Yes, definitely. All the support to build a Debian package for installation is in https://github.com/ArduPilot/ardupilot/tree/master/libraries/AP_HAL_QURT/packaging

@Ashish-Kumar
Few things:

1. Please stop trying with only USB-C, that is invalid. Think of this as your smartphone... there is always a battery present (our power module) before you insert a USB-C cable.
2. Please remove USB-C, Plug in the power module when it is OFF, then turn the power module ON.., then insert the USB-C cable. Our Hardware is not hot-swappable. Only USB ports can tolerate an active host connection, but all power supplies must be OFF when plugged in, then turned ON.
3. Your power module was delivered with clear heatshrink. What happened to it? That would not be a covered RMA since the HW of the power module is now compromised.
4. Can you confirm if you have tried multiple USB cables and multiple ports on your PC? (or even another PC?). We often see that fix some folks issues, either a lose cable or bad port... happens more than you would think.

After those steps are confirmed, then I think @tom can guide you further.

Thanks!

@Hunter-Scott When you swapped in the power module board did you update the px4 configuration file in /etc/modalai/voxl-px4.conf? In that file, how is POWER_MODULE set? For the power module it should be POWER_MANAGER=VOXLPM. For standard Starling 2 Max configuration it should be NONE. Can you stop voxl-px4 running as a service systemctl stop voxl-px4, wait a few seconds, then run voxl-px4 from the command line in non-daemon mode with voxl-px4 -d and let the startup script run through. At the command prompt type ver all and qshell voxl_esc status and then include all of the output here? In the log that you sent that did have battery_status, where did that come from? A different drone?

Hi @Aaky
You just went one page in too far
https://docs.modalai.com/voxl-escs/
Hope this helps!

@Ashish-Kumar
With ONLY USB-C, the board will not boot, so that is normal behavior.
VBAT is always required.
D1 (Green LED) says the VBAT is present and our local 3.3V is ON.
With just that LED on, it tells me your board is likely stuck in QDL mode and needs reflashing, so the steps Tom provided will help confirm that.

option 2: upgrade to SDK 1.6 as we have a new version of VIO and numerous bug fixes

Directions are found here. where the SDK for starling 2 is found here.

Hi there, looking at the files and review our analytics here since you were flying fine in position mode that says VIO was likely ok (as per you config files).

We did have a some changes between vision-hub and px4 that make have been incompatible with the 1.4.5 version. Hence you have 2 options:

option 1: debug & confirm either probem lies in voxl-vision-hub or PX4.
(a) you need to ssh onto the vehicle, in the remote terminal, run:
voxl-vision-hub --debug_offboard

That will display streaming position data, which is the traj commands to PX4. Then you may restart/start voxl-mapper (e.g. systemctl restart voxl-mapper). In the vision-hub streaming output, you'll see a print out like Trajectory Monitor connected to voa pointcloud.

(b) you can now switch to position mode, fly around in that mode to map as normal, then stop to hover. Draw your simple trajectory in portal and execute. Ensure the draw trajectory is within the space using the mouse and rotating around the area--portal can sometimes make the 'plan point' appear close to the drone, but it is actually very far away so you need to check at different viewing angles. When you execute the plan, the streaming output in the vision-hub display above should reflect the drawn trajectory. In both your example and mine, the Z position output should stay relatively close to the current. If it rises, we have a trajectory calculation problem (drone is doing what it's told). If it rises while the position data is fairly minimal, then PX4 likely has failed (VIO or dropped out of offboard mode). Please try this and report back. We suspect VIO may have failed. Here's a example of the output:

@aspen The landing detector in PX4 isn't perfect (obviously) so in this case it didn't detect the landing. I would map one of the switches to toggle between arm and disarm so that when the drone lands you can disarm via switch. Did you try the v1.16 package?

@aspen Can you provide the log file? There is a version of px4 v1.16 available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.4-202509030932_arm64.deb

@Hunter-Scott If you delete all logs then fly you don't see any log files afterwards?