@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.

@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?

@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

Actually, I see from the log that your FPV camera is IMX214 (please confirm).

So then my next questions are:

which Voxl2 SDK are you using? does the crash happen if you only view the Hadron EO stream (this is OV64B camera) can you please check the cpu temps when you view many cameras (using voxl-inspect-cpu)

The dmesg error suggests some sort of low level error during MIPI transmission, but it could be tied to the SoC overheating.

When voxl-portal is used to view images (especially in multi-view), the images on VOXL2 are converted from YUV to Jpeg using a software Jpeg encoder (which is very taxing on the cpu for large images). This can cause the cpu to overheat and start throttling operating frequencies to reduce the temperature). We are aware of this issue and it is on the list to fix the multi view to be more efficient and not overheat the CPU.

Alex

@Seungjae-Baek
image.png IMG_0429.jpg
One more question: Should we use 5G antenna, not LTE? As I know when we buy the 5g modem the default antenna is the one with LTE.

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

@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.

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