Pixhawk not responding with solid red led on B/E IO light up

What is the probable problem? I have pixhawk 4 that randomly not responding. Here is my log output from mavros:

MAVROS UAS via /uas1 started. MY ID 1.240, TARGET ID 1.1
[starter-2] [INFO] [1773031437.488168571] [starter]: Starter Node started
[mavros_node-1] [WARN] [1773031438.964811103] [mavros.sys]: VER: broadcast request timeout, retries left 4
[mavros_node-1] [WARN] [1773031439.965010277] [mavros.sys]: VER: broadcast request timeout, retries left 3
[mavros_node-1] [WARN] [1773031440.966867710] [mavros.sys]: VER: unicast request timeout, retries left 2
[mavros_node-1] [INFO] [1773031441.720605108] [mavros_router]: link[1000] opened successfully
[mavros_node-1] [INFO] [1773031441.720765180] [mavros_router]: Requested to add endpoint: type: 1, url: udp://@192.168.1.2:14550
[mavros_node-1] [INFO] [1773031441.720842336] [mavros_router]: Endpoint link[1001] created
[mavros_node-1] [INFO] [1773031441.721426652] [mavros_router]: link[1001] opened successfully
[mavros_node-1] [INFO] [1773031441.721479903] [mavros_router]: Requested to add endpoint: type: 2, url: /uas1
[mavros_node-1] [INFO] [1773031441.721526625] [mavros_router]: Endpoint link[1002] created
[mavros_node-1] [INFO] [1773031441.725171763] [mavros_router]: link[1002] opened successfully
[mavros_node-1] [INFO] [1773031441.943420071] [mavros_router]: link[1002] detected remote address 1.240
[mavros_node-1] [WARN] [1773031441.965247919] [mavros.sys]: VER: unicast request timeout, retries left 1
[mavros_node-1] [INFO] [1773031442.381910800] [mavros_router]: link[1001] detected remote address 255.190
[mavros_node-1] [WARN] [1773031442.964829660] [mavros.sys]: VER: unicast request timeout, retries left 0
[mavros_node-1] [WARN] [1773031443.966942407] [mavros.sys]: VER: your FCU don’t support AUTOPILOT_VERSION, switched to default capabilities

Hi @Lexciese,

I’m not particularly familiar with the Pixhawk 4 or MAVROS, but if I’m remembering correctly the “Bootloader / Error” LED on Pixhawks goes solid red when there’s an error with the firmware startup process. Did you recently try to flash a firmware onto your Pixhawk? That process may have failed to complete successfully, in which case you may need to try flashing again. If a few attempts of that don’t resolve the issue then there may be something wrong with the firmware you’re trying to use, or with the board itself.

After many reflash and testing, for now, i can assume that it is related to the pixhawk board overheating while inside the AUV tube. Because when we put the pixhawk outside the tube in 1 hour, the issue did not arise.

1 Like