Possibly bricked camera after connecting with a faulty USB-C cable

fkmjec

Hello!

I have been working on a Luxonis Oak-D Wide camera for some time now. Lately, I wanted to change the cable to a one that can be screwed onto the camera, so as to not overwork the USB-C port. The cable was however probably faulty; upon connecting to the camera, I received data, even though it contained more speckles than normally (which I did notice, but did not give it much weight) and the camera had higher latency.

I then disconnected the cable and replaced it with the old one which worked fine until then. And now I cannot see the camera at all; it does not show up in dmesg -w or in lsusb. Is it possible that the camera was somehow fried? I am not using an external power source, I just have the camera on a short USB3 cable. What would be a way to debug this?

Thank you,
František

jakaskerl

Hi @fkmjec
You can try and open up the camera and see if the LEDs light up. I think it could also possible be that the port-cable connection is loose, preventing communication.

Thanks,
Jaka

fkmjec

Thanks a lot, Jaka. I tried that, but saw no LED light up. It also does not seem like the port-cable connection is loose.

Best,
František

erik

Hi @fkmjec, then the device is likely fried. You can ask support@luxonis.com, but since it's likely user-related error I'm not sure if our refund policy covers that.

fkmjec

Okay, so we found the issue. It was due to me screwing in the guard screws of the USB-C too deep and breaking off a component on the board. A colleague of mine soldered the component back on and now it works. But I was pretty unpleasantly surprised by the fact that the board is not guarded against this.