Issues shutting down and restarting connection to PoE S-2 Camera

jakaskerl

Sorry for taking a while to get back to you.

I have tried waiting for 60 seconds after stopping the program but that still does not work.

I am on depthai version 2.22.0.0, os is Windows.

The Error I get is

[2023-07-21 14:30:00.791] [depthai] [warning] Monitor thread (device: 19443010B1937F1300 [169.254.1.222]) - ping was missed, closing the device connection

Traceback (most recent call last):

File "C:\code\cadds-visual-tyre-handler\source\recorder\main.py", line 153, in <module>

with dai.Device(pipeline, device_info) as device:

depthai.XLinkWriteError: Couldn't write data to stream: '__bootloader' (X_LINK_ERROR)

Also if I don't set usbSpeed I get a warning

C:\code\cadds-visual-tyre-handler\source\recorder\main.py:153: DeprecationWarning: Use constructor taking 'UsbSpeed' instead

with dai.Device(pipeline, device_info) as device:

I have done this It upgraded from version 0.0.21 to version 0.0.26 but that appears to have made things worse. I can no longer get it to work at all (ie power cycling doesn't fix anything).

The error I get now is
[19443010B1937F1300] [169.254.1.222] [1690352930.317] [host] [warning] Using a custom watchdog value of 60000ms

[2023-07-26 14:29:02.667] [depthai] [warning] Monitor thread (device: 19443010B1937F1300 [169.254.1.222]) - ping was missed, closing the device connection

Traceback (most recent call last):

File "C:\code\cadds-visual-tyre-handler\source\recorder\main.py", line 118, in <module>

with dai.Device(pipeline, device_info, maxUsbSpeed=dai.UsbSpeed.HIGH) as device:

depthai.XLinkWriteError: Couldn't write data to stream: '__bootloader' (X_LINK_ERROR)

It took less than 60 seconds for this error to come up so it isn't the watchdog tripping.Any ideas? I can still connect the device manager to it (and ping it). One of my colleague suggested I should do a factory reset. To do this I ran this from the depthai-python source code repo. Latest main branch as of commit 236e7ec1b8ac2c7573d980f45efe90e9b3df812f

erik
So today I have worked through quite a few hardware combinations as per this request.
For our production device we are planning to deliver to our client is a
+ Microsoft Surface Go 3 Tablet running Windows 11
+ USB - C to Ethernet adaptor
+ Tp-Link POE desktop switch (TL-SF1005P)
+ OAK S-2 POE Camera

All of this will be vehicle mounted, so we want as little gear as possible. Also we are focused on the PoE Camera instead of the USB Camera because Ethernet cables can be longer and clip in and unlike USB cables won't slip out.

I didn't test on that tablet, instead I have two laptop I use for development. One is Windows only the other dual boots Linux Ubuntu and Windows. Both laptops are Dell Vostro 7590's

I have three USB Network devices, a Comsol USB-A to ethernet adapter (it's a cheap one), a Bonelk USB-C to Ethernet adapter. A standard Dell Dock.

I replaced the network cable between the PC/ USB to ethernet and the switch at the start of today's test. That did not appear to make a difference.

No matter what combination of hardware I tried on Windows it did not work and always gave the same message as above.

At one I tried to reset to the Factory Defaults in the device_mamanger.py program (under Windows). This did not work, it gave a message to the effect that it had tried to reboot the device but couldn't. The device then disappeared from the network. Eventually after power cycling it, it came back but the firmware had not been downgraded.

I will frequently use 'ping 169.252.1.222' to check if it is on the network. I find that I frequently have to power cycle the switch and then the PoE camera by unplugging it to get it responding to pings.

The good news is that under Linux I was able to get it to work particular the Dell Dock seemed to work better than the Comsol USB adapter. But they were both able to work.

In the case of the Dell Dock I could confirm that I can start the program up. Then received images from the Camera. Then start it up again and receive more images from the Camera. However after this second successful run when I quit the program the Camera appeared to crash and I could no longer ping it. I was eventually able to get to to respond to pings by power cycling it.

We are considering buying a second PoE Camera incase we simply have a defective unit. (We have a USB Camera as well that we can develop the software with).

Sorry for taking a while to get back, client wanted to borrow the Camera to work on the housing design.

Got it back this morning and have managed to get a firm diagnosis.

Currently at version 0.0.26 of the bootloader firmware.

Everything works fine (with a few glitches) if I run it under Linux but the same program fails under Windows with the given message. (The program is this case being the code listed at the start of the original post in this thread).

This behaviour indicates a bug which is specific to running your software under Windows. The specific error message indicates a ping is being timed out too aggressively when running under Windows.

I have worked from home today and have been running the Camera off my home Ethernet. I can connect to the home Ethernet via Wifi or a USB Ethernet device which I can plug into either the PoE Switch which powers the Camera or my normal home Ethernet Switch. Which option I use doesn't matter Linux works 100%, Windows fails every time.

Just to be clear it's the same computer which I can boot into either Windows or Linux. The version of the depthai library being used is 2.22.0.0 installed from pypi

I have noticed some other issues.
- If I isolate the Camera from the DHCP Server and try to get it to use the link local address (169.254.1.222) under Linux this is unreliable. This may have worked better when using the Dell Dock, but I don't have that with me today.
- I use ping to test if the Camera is available. When trying under Windows and getting that error message, it is like the Camera would crash and not respond to pings. I had to power cycle it to get it back, sometimes multiple times.

Hope that is clear, I am glad I now have a clearly reproducible failure. If there is anything I can do on our end to help fix this, eg getting more logs from the library I am happy to do that. We also have a client we are building a hardware and software package for who are pushing us for this to be delivered now and this problem is the only thing holding us back from doing that.

mark_squarecode

Acting on a hunch that it will have worked in older versions I tried that. Version 2.17.4.0 appears to connect to the camera occasionally under Windows and doesn't given the same missing ping error message.

Notable using 2.17.4.0 under Windows it is taking much longer to connect to the camera 50 to 60 seconds, vs 16 to 24 seconds using 2.22.0.0 under Linux

I made a repo to help you guys reproduce this issue
https://github.com/mlockett42/depthai-windows-issue-demo