Unstable connection / connectivity issues

jt512

Oop, here we go again. This time I made it to the line cout << "Device name: " << device.getDeviceName() << endl; where it threw on device.getDeviceName().

🫠☠️🫠☠️🫠☠️

jt512

I updated to latest repo, v2.21.2, and don't really see much of a difference. This is it?

erik

Hi jt512 ,

Please also try the latest develop version of depthai library - relevant github issue here.

Thanks, Erik

jt512

The branches main, v2.21.2, and develop are all at the same commit…

erik

I see, it was just released 2 hours ago. The main changes are in the firmware, see commit here.

jt512

erik You're saying there is a firmware update paired with this? This is new to me so I need some explanation to understand what this means. Where are the side binaries kept?

jt512

I am also experiencing deadlocks on dai::Device::close() quite frequently. Referring to the code above, after getting a single frame, I call device.close(), break out of the loop and return the single frame. Deadlock on device.close();

erik

Hi jt512 ,

Best to report the deadlock issue on depthai-core with minimal repro example. For firmware - for C++ I believe it gets downloaded at build time from our servers, while for python it's bundled together into a wheel. Firmware is closed source (our core IP).

Thanks, Erik

jt512

I'm gonna send an email.

jt512

FYI, I can confirm the 2.21.2 update does nothing. Same exact sporadic connectivity issues.

erik

Hi jt512 ,

Please open an issue on depthai-core with specifications of the sporadic connectivity issues so firmware engineers can repro/debug easily.

Thanks, Erik

« Previous Page