@Moderator
Thanks, I will try it.

Although the temperature will reach 80°C, there has been no shutdown at this temperature.
The temperature wasn't high when the problem occurred.

So if the problem occurs and I want to view the system logs or use DBG_UART12 at J3 PIN-OUT of voxl2 to check.
What can I do?

Simon

@Moderator
I also suspected whether it was due to overheating, so I used voxl-inspect-cpu to check the CPU status.

When ADB and SSH were unresponsive, the temperature was about 50°C~55°C, and voxl-inspect-cpu also didn't respond.

But if VOXL2 operated normally, there was no problem if the temperature had reached about 80°C.

Simon

@tom
When ADB and SSH are unresponsive and I also repluged the USB, it also showed the same name.
The device name is "KONA-QRD_SN:886DD761" in Windows 11's Device Manager.

The situation doesn't always happen when VOXL2 booted.
And it happens approximately a few minutes after VOXL2 boots, not immediately after booting.

Simon

@tom
Although ADB and SSH are unresponsive, I can see the device in Windows 11's Device Manager.

Simon

@Moderator
The problem I encountered was that ADB and SSH did not respond after booting VOXL2 for a while, but it worked after rebooting.

Not ADB is unable to detect VOXL2.

So I want to see the system log or other way to find the problem.

Thanks,
Simon

Hi ModalAI team,

I'm having a voxl2 crash, I don't know why. I tried to connect voxl 2 using adb and ssh but no response.

Is there a way to see the system log or other way to find the problem?

And I find DBG_UART12 at J3 PIN-OUT of voxl2. Can I use it to check if voxl2 is completely crashed or just adb and ssh not working?
If possible, what is the DBG_UART12's reference voltage and baudrate.

thanks,
Simon