I am using an Oak-D Pro W PoE in a ROS2 environment. I am occasionally experiencing an issue where the driver crashes. See the error below:

[oak_device_manager_node-1] [ERROR] [1752187840.536591297] [oak_device_manager.forward_camera]: forward_camera state changed to OAK_STATE_ERROR: Device is not valid or running [oak_device_manager_node-1] terminate called after throwing an instance of 'dai::XLinkWriteError' [oak_device_manager_node-1] what(): Couldn't write data to stream: '__bootloader' (X_LINK_ERROR) [ERROR] [oak_device_manager_node-1]: process has died [pid 1259338, exit code -6, cmd '/workspace/install/sbai_oak_device_manager/lib/sbai_oak_device_manager/oak_device_manager_node --ros-args -r __node:=oak_device_manager -r __ns:=/ --params-file /tmp/tmpawzkp9jk'].

I believe this is due to the driver attempting to reconnect/reboot while the Oak camera is a corrupted state. So my questions is this: is there anything I can do (through software) to give the Oak driver more robustness to these failures? I’d rather the driver kept trying to reconnect, rather than crash.

Alternatively, are there ways to monitor whether or not the Oak camera is in a corrupted state? I’d like to know what actually triggers it.

Thank you.

    4 days later

    Hi @henry0987, there is a possibility of restarting on detected errors via a parameter, but depending on the type of crash it might not be available. Could you post some more information on your setup as in the bug report template?