[BUG] Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND #560
Labels
bug
Something isn't working
Comments
|
Hi, could you please post more logs following the bug template? You can skip running stereo_inertial_node as this one won't support OAK-D-LR |
|
Bug Description: The camera OAK-D-LR presenting the issue during initialization with the camera launch from the depthai_ros_driver. Minimal Reproducible Example
Other Tests When I run the
dmesg output Expected behavior Pipeline Graph The pipeline Graph did not created an image graph. However the command was executed with verbose, and the output are: Attach system log
Which OS/OS version are you using? |
|
Hi, just to be sure, could you run echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="03e7", MODE="0666"' | sudo tee /etc/udev/rules.d/80-movidius.rules
sudo udevadm control --reload-rules && sudo udevadm triggerand replug the device after that? |
|
Hi, @Serafadam Thanks for your reply. Adittional information I tested with the docker image(luxonis/depthai:latest), and I was able to connect the camera. GUI Screenshot However, the issue with the ROS driver continues. |
|
Dear @Serafadam I tested the camera with the PoE and it t works with the deptai_ros_driver launch. Did you manage to reproduce the issue? Regards. |
|
Hi, unfortunately I haven't been able to replicate that issue, but could you test if you can connect via either MXID or USB port name directly? |
|
Hi @Serafadam I tested with your suggestion, related the mxid and the usb_port_id, and it make no difference. To help with the issue replication, I can generate an docker image with my base system environment, and share with you. Is it work for you? Regards. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear all,
I am facing an issue with running the ROS2 driver for the Humble version. The driver software was installed via ROS2 Humble repository, which has the deptai_ros_driver version 2.26.
The is the OAK-D-LR, with Bootloader version 0.028.
The OS is the Ubuntu 22.04.
After I ran the launch from the deptai_ros_driver, I got the following result:
I suspected the udev rules were not correct, however, I cloned the repository from the depthai-python, and tested the utility python scripts device_manager.py and the cam_test.py. From these scripts, I could access the camera information and acquire data. It proves the udev is correct.
Terminal Output from the cam_test.py
I dug the source code the line where the error rises, and I found this line
I played with the bootupTimeout (WAIT_FOR_BOOTUP_TIMEOUT) values, but increasing or decreasing the time did not affect the error.
I also monitored the lsusb to see the device boot and when the device is not running, the values are:
Bus 001 Device 043: ID 03e7:f63c Intel Luxonis BootloaderWhen I run the ROS driver, the devices change name to
Bus 002 Device 019: ID 03e7:f63b Intel Myriad VPU [Movidius Neural Compute Stick]and stay for a few seconds, until come back to the initial USB name.
Could you help me? Please!
In case you more information, please do not hesitate to ask.
The text was updated successfully, but these errors were encountered: