Nova Carter PFC – 4 Failures (NVMe Threaded IRQ + Hesai 3D LiDAR) — Could This Be Why Host is Locked (Amber LED)?

[Lefkios]

Hi everyone,

I’m currently setting up my Nova Carter robot, but the host LED stays yellow/amber, indicating the host is locked. I’ve gone through all the documentation and ran the Nova Preflight Checker (nova_preflight_checker -v).

The results show 4 failed tests out of 97, as you can see below:

My questions:

1. Could these failed PFC tests (especially NVMe IRQ or Hesai LiDAR unreachable) be the reason the Nova Carter host remains locked (LED yellow/amber)?

2. Is it safe to proceed with teleop / bringup after fixing NVMe, or does the host stay locked until all 97 PFC tests pass?

3. Is there a way to manually unlock or reinitialize the host once these errors are corrected?

Any official guidance or steps to fully clear the PFC tests and turn the LED green would be really appreciated.

Thanks in advance!

[Ahung]

Hi @Lefkios

Thank you for your post.

I wouldn’t expect those PFC failures to be a reason for it to be locked. The PFC should have no impact on locking.

The NVME issue another way to check is to run cat /sys/module/nvme/parameters/poll_queues this will show if the NVME kernel driver was configured by Nova. If this test is failing it just means that the cameras may have lower performance.

For the Hesai, I’d check that ifconfig eno1 is configured to 192.168.1.100 (the same subnet as the Hesai). Then ping 192.168.1.201 -I eno1 . Also try pinging the RPLIDAR too ping 192.168.1.2 . If just the hesai is failing this could be a HW/loose connection issue on the Hesai. Either the ethernet or power is not getting through.

I would say its safe to proceed with teleop/bringup if those tests are failing. The locked signal is a result of responses from the motor wheelbase. PFC has no relation. When running the Nova Carter teleop app it should initialized and change the wheelbase state.

Best,
Ahung