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.

@Ashish-Kumar What OS are you running on your host machine? If linux can you provide the output of lsusb with the board powered and plugged in?

@jmltt SDK testing for Sentinel ended at SDK 1.4.0

That doesn't mean that newer releases won't work, it just means we don't put it through the SW QA testing cycles that we do with our newer platforms.

You likely won't see any major performance improvements on Sentinel with newer SDK releases but there may be some nice quality of life additions such as helper scripts, voxl-portal updates and others.

If you have any questions about any specific packages feel free to ask.

@Ashish-Kumar Can you post a picture of your hardware setup so I can verify all looks normal?

@latif You can order replacement propellors here: https://www.modalai.com/products/starling-propellers-set-of-4?_pos=1&_sid=4b5f94f4e&_ss=r

If you have access to a 3d printer there are some STL files available from our downloads page here: https://developer.modalai.com/

When you plug your VOXL2 in to your machine does it enumerate at all?

Worst case you can submit an RMA here: https://www.modalai.com/pages/rma

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?

Hi @Seungjae-Baek,

It is hard to see the detail in the screenshot, it is very low resolution. Can you please clarify which cameras you are turning on / off?

Also, what streams are consumed from the camera server (by other processes) and what are the resolutions?

Also, keep in mind that your cpu may not run at a high frequency. Please check voxl-inspect-cpu for more details. If your cpu governor is in auto mode, it will reduce cpu core frequency, which will result in higher % usage of each core (at lower frequency).

If you sent your cpu to performance mode (voxl-set-cpu-mode perf), this will push the frequency of all cores to the maximum and will give you a better estimate of the cpu usage per process (out of the full core capacity). Please note that in performance mode, the cpu will consume more power (and heat up a bit more) to perform the same tasks (with lower latency).

Alex