- Edited
Hello,
I am trying to use an OAK-D Lite after a while I left the camera unused.
Since my purchase, the tooling has improved and there are more recent SW versions that I promptly downloaded to make sure I was up to date.
Unfortunately, that broke my previously working setup with OAK-D Lite.
I am running the camera on:
OS Name Microsoft Windows 10 Pro for Workstations
Version 10.0.19045 Build 19045
The camera is connected via USB2 cable. Indeed, I tried to pull the repository and run with the -usbs usb2
option. I used this cable before and never had this issue.
I obtain the following error log with this cable:
Available devices:
[0] 1844301041AA7D1200 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.HIGH
Enabling low-bandwidth mode due to low USB speed... (speed: UsbSpeed.HIGH)
Creating MJPEG link for MonoCamera node and left xlink stream...
Creating MJPEG link for MonoCamera node and right xlink stream...
Creating MJPEG link for ColorCamera node and color xlink stream...
[2022-12-19 23:51:59.468] [warning] Insufficient permissions to communicate with X_LINK_BOOTED device having name "3.2". Make sure udev rules are set
<MY_HOME>\AppData\Local\Programs\DepthAI\venv\lib\site-packages\depthai_sdk\previews.py:186: RuntimeWarning: invalid value encountered in cast
dispFrame = (dispFrame * 255. / dispIntegerLevels).astype(np.uint8)
I can stream from the camera, I can see all the streams, visualize the stereo depth... but I cannot apply any of the UI settings and restart the streaming.
I then switched cable to USB3, yielding
Depthai version installed: 2.19.0.0
Setting up demo...
Available devices:
[0] 1844301041AA7D1200 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.SUPER
[2022-12-20 08:03:12.105] [warning] Insufficient permissions to communicate with X_LINK_BOOTED device having name "3.17". Make sure udev rules are set
and no other message. The udev rules
error message persists even when changing connection or port. I still cannot apply and reset and therefore load any model from the DepthAI app.
I also tried running as Administrator (hoping it would work around any user permissions), without any luck.
Is this a known issue (I have seen some in the forum, but not quite identical), and is there a known solution? Could it be due to specific USB port rules applied by the OS?