-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
usbids conflicts with Movidius Neural Compute Stick #2924
Comments
[Realsense Customer Engineering Team Comment] I don't see this issue. If you re-connect NCS1, can it be recognized and show in lsusb? |
Test 1 - if not run realsense-viewer in backend. when re-connect NCS1, it could be recognized and show in lsusb.
Test 2 - if run realsense-viewer in backend, when re-connect NCS1, it could not see from lsusb. but from dmesg, it show first detected then disconnected..
Test 3 - try to connect NCS1 to another USB port, not near D435 device - the result is the same, USB disconnect while realsense-viewer (or rs-callback others) running. OS: Ubuntu 18.04.1 LTS |
[Realsense Customer Engineering Team Comment] Did you run the prebuilt realsense-viewer tool? Or, build from the source? I suspect the NCS1 is reset by realsense-viewer since our TM2 device has the same VID/PID with NCS1. |
NCS1 is reset by realsense-viewer since TM2 device has the same VID/PID with NCS1. Workaround is to build realsense-viewer tool without "BUILD_WITH_TM2". Fix issue: IntelRealSense#2924
Just verified, NCS1 could work without BUILD_WITH_TM2. The issue was reported from ros2debian, the debian package was prebuilt by ROS2 buildfarm based default CMakeList.txt. Don't know why the value of BUILD_WITH_TM2 is true by default? As there nowhere set it from CMakelist.txt. I have submitted a PR(#2970) to fix this issue. Disable BUILD_WITH_TM2 seems to be a workaround solution, is there any better way to fix the same VID/PID issue? Anyway, it can solve our currently problem as we do not use TM2, thanks. |
NCS1 is reset by realsense-viewer since TM2 device has the same VID/PID with NCS1. Workaround is to build realsense-viewer tool without "BUILD_WITH_TM2". Fix issue: IntelRealSense#2924
NCS1 is reset by realsense-viewer since TM2 device has the same VID/PID with NCS1. Workaround is to build realsense-viewer tool without "BUILD_WITH_TM2". Fix issue: IntelRealSense#2924
NCS1 is reset by realsense-viewer since TM2 device has the same VID/PID with NCS1. Workaround is to build realsense-viewer tool without "BUILD_WITH_TM2". Fix issue: IntelRealSense#2924
NCS1 is reset by realsense-viewer since TM2 device has the same VID/PID with NCS1. Workaround is to build realsense-viewer tool without "BUILD_WITH_TM2". Fix issue: IntelRealSense#2924
Issue: The usb ids of idProduct and idProduct conflict with Movidius NCS.
Reproduce:
1.plugin NCS
2.plugin Realsense
3.run realsense-viewer
4.the NCS device missed (lsusb)
Realsense rules:
librealsense/config/99-realsense-libusb.rules
Line 27 in c5b9aa0
NCSSDK rules:
https://github.com/movidius/ncsdk/blob/949131b4402c4ae4b7d1c7d11bb4ac9e70d703da/api/src/97-usbboot.rules#L1
Official defined here:
http://www.linux-usb.org/usb.ids
03e7 Intel
2150 Myriad VPU [Movidius Neural Compute Stick]
The text was updated successfully, but these errors were encountered: