Subject: USB 3.0 Connection Issue with OAK-D Lite Dear Luxonis Support Team, I am currently integrating the OAK-D Lite into a robotics system and have encountered an issue where the device consistently connects via USB 2.0, despite being directly connected to a USB 3.0 port using a certified USB 3.0 cable. Here are the details of my setup: \- Device: OAK-D Lite \- Host: Raspberry Pi 4 Model B (ARM64) \- OS: Ubuntu 22.04.3 LTS (64-bit) \- SDK: depthai-python v2.21.2.0 \- Cable: Certified USB 3.0 cable (verified with other devices) \- Port: Raspberry Pi USB 3.0 port (blue) \- Power: 5V/3A regulated supply Observed behavior: \- \`device.getUsbSpeed()\` returns \`HIGH\`, indicating USB 2.0 \- \`dmesg | grep -i usb\` shows enumeration as USB 2.0 device \- No other devices are connected to the same bus \- Tested with multiple cables and ports, same result I have reviewed the documentation and verified that the cable and port support SuperSpeed. I also tested the same cable with other USB 3.0 peripherals, which connect correctly. Could you please advise on the following: 1\. Is there any firmware or hardware-level constraint that could force USB 2.0 mode? 2\. Are there known compatibility issues with Raspberry Pi 4 USB 3.0 ports? 3\. Is there a recommended method to confirm SuperSpeed negotiation from the device side? 4\. Would a powered USB 3.0 hub improve negotiation reliability? I would appreciate any guidance or troubleshooting steps you can provide. If needed, I can share full \`dmesg\` logs and SDK initialization traces. Thank you for your support. Best regards, Akihiko

Hey @"shimizuakihiko"#3617 - quick clarification first: the OAK devices shows up as USB2 only in bootloader. After DepthAI sends firmware it disconnects and re-enumerates as USB3. You can check speed like this: ``` import depthai as dai d=dai.Device() print(d.getUsbSpeed()) ``` If it still reports HIGH on the Pi 4, this points to the host side. The device always tries SuperSpeed if the host negotiates it. I know some Pi 4 running ubuntu had problems with VL805 controller. I think `rpi-eeprom-update` should fix this, but check online... Two more things you can try: -Try the camera on a desktop/laptop USB3 port. Does it come up as SUPER there? -Power it through a powered USB3 hub or a USB-C Y-splitter (data to the Pi, power from a separate 5 V source) to rule out Pi power/negotiation quirks. Thanks, Oskar

USB 3.0 Connection Issue with OAK-D Lite

shimizuakihiko

Hi Oskar,

Thanks for the helpful information. Unfortunately, the microSD card on my Raspberry Pi got corrupted, so I'm currently recovering it. I got a USB Y-cable so I'll try it out. I will report back with results.

OskarSonc

Happy to help, let me know 🙂

shimizuakihiko

In conclusion, I was able to connect using UsbSpeed.SUPER. I tried three different USB 3.0 cables, and one of them was effective. Also, the auxiliary power supply using the Y-Cable required a separate power supply rather than using the Raspberry Pi's USB socket. Thank you.

OskarSonc

Yes, power is very limited on Raspi, so outside power is recommended.

shimizuakihiko

I found that the orientation of the Type-C plug affects the USB connection speed. I tested this with two different cables from different manufacturers and found it reproducible. When I connected the side with the manufacturer's logo facing the back of the camera, the connection speed became "SUPER" without auxiliary power.

OskarSonc

@shimizuakihiko - thanks for sharing this. Hmmm this is interesting, the USB-C is nominally reversible. Which cables did you use?

shimizuakihiko

The two types of cables used are:

BUFFALO USB 3.1 Gen1 Cable (AtoC) 0.5m BSUAC31105BK

AmazonBasics USB-C to USB-A 3.1 Gen 2

OskarSonc

shimizuakihiko - thanks for this info... If I understand correctly, if using the auxiliary power, you always get SUPER?

shimizuakihiko

I checked and found that even when using auxiliary power, the USB connection becomes HIGH depending on the orientation of the Type-C.

Last time, I thought that using auxiliary power would always make it SUPER, but that was not the case. Even when running some of the depthai-core/examples and applying load, it is currently working without auxiliary power. However, I cannot explain this.

OskarSonc

shimizuakihiko - neither can I... I am guessing a bad cable, but even that is weird since you tried two. I guess just have it plugged in the right way and see if it works normally... Maybe you could try usb c - usb c cable, if you have that c port on your PC....

g199

Extremely annoying, hours wasted because of this, thank you @OskarSonc

OskarSonc

Hey g199 - sorry to hear that you wasted hours because of this...
Is this connected to this tread that you opened? Did you fix it just by turning usb-c in other direction?:
https://discuss.luxonis.com/d/6584-dissapointed-and-frustrated

g199

OskarSonc It was yeah, just turning the USB fixes the issue

OskarSonc

g199 - glad that worked!