[BUG] Occasional X_LINK_ERROR on POE devices

[justin-larking-pk]

We are repeatedly getting occasional disconnects from our oakd-w-poe devices that reads with the following error. The disconnects seems to happen randomly or just after some time.

The error:
"terminate called after throwing an instance of 'std::runtime_error'
what(): Communication exception - possible device error/misconfiguration. Original message 'Couldn't read data from stream: 'depth' (X_LINK_ERROR)'
[oakd-11] process has died [pid 1499128, exit code -6, cmd /home/grover/catkin_ws/devel/lib/grover_vision/oakd_node __name:=oakd __log:=/home/grover/.ros/log/659fb568-d1e9-11ed-b878-23da073fdadf/oakd-11.log].
log file: /home/grover/.ros/log/659fb568-d1e9-11ed-b878-23da073fdadf/oakd-11*.log"

We noticed the same error on our usb devices occasionally, we put that down to vibration/usb-cable issues.

What could be causing this? Could vibration be causing Ethernet disconnect? It is using the Luxonis cable and we've confirmed the POE switch the camera is connected to isn't losing power. Could it be an issue with the pipeline?

[themarpe]

@justin-larking-pk

Run the examples/CrashReport/crash_report.py example after that happens and post it here.

WRT vibration - yes that might be the case if connection temporarily drops. Both issues can show themselves in similar light

[justin-larking-pk]

We're having trouble getting crash dumps out of the camera. We're running the latest release however often after our x_link_error there appears to be no crash dump available.

Are the crash dumps stored in flash or ram? If so do they stick around after a power cycle and when do they get overwritten?

[diablodale]

The unhandled throw leading to terminate could be luxonis/XLink#59, the bugs I fix in #809, or the bug I'm waiting on Luxonis to answer #809 (comment)