D435 "No device detected". Raspberry Pi 3B+ #8874
Labels
Comments
|
@williamx97 So I understood you followed https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md#install-realsense-sdklibrealsense to build librealsense, right? LibUVC and WinUSB are deprecated from the build in SDK 2.30+, replaced by RSUSB. So could you please try to re-build with the following? Thanks! |
|
Thanks! I've recompiled it with the cmake flags listed above and now I have rebooted the raspberry pi and changed the usb ports. The T265 camera still detects correctly though. Would there be a way to detect whether a linux process is using the D435 or were there some other realsense debugging tools I could employ? librealsense was compiled using the 'source code' |
|
Update to the above: Reversing the USBC connection to the D435 seemed to fix the issue temporarily. I unplugged and replugged the USBC sides to confirm that only one side of the USBC connection was causing the However after running some tests within the Realsense ROS wrapper seemed to cause the Output of Roslaunch commands (click to expand)
|
|
@williamx97 Did you use the original USB cable when get the issue? |
|
@RealSenseSupport Yes I am using the original USB cable that came with D435. There are occasional moments where reversing the USB C side seems to work, however most times the |
|
@williamx97 Did you get such issue if you connect this D435 to other PC like x86 PC with the original cable? Thanks! |
|
@RealSenseCustomerSupport I'm not getting the |
|
@williamx97 Did you install ROS wrapper by sudo apt-get install ros-$ROS_DISTRO-realsense2-camera ? According to IntelRealSense/realsense-ros#1187 (comment) , please try the following:
|
|
@williamx97 Any update from your side? Looking forward to your reply. Please note that the ticket will be closed if we don't hear from your for another 7 days. Thanks! |
|
@williamx97 Any update from your side? Thanks! |
|
@williamx97 Sorry that we don't hear from you for weeks. This issue will be closed. Please create new issue if you still have other questions or issues. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Hi there,
Our team is having issues getting our D435 to show on
rs-enumerate-devices. We are getting theNo device found. Is it plugged in?error message.We are using a custom version of raspbian provided by our robot manufacturer called TurtleOS: https://github.com/TurtleRover/turtleos
It is based on Linux Kernel
4.14.79Here are the troubleshooting steps applied:
~/catkin_ws/srcand using ROS commandcatkin build. The UDEV rules were also updated.sudo apt-get update && sudo apt-get upgrade. Kernel patched to 3.19sudo rpi-update. Kernel patched to 5.10 ,still did not worksudo rpi-update 453e49bdd87325369b462b40e809d5f3187df21dthe specific commit this command used was here Hexxeh/rpi-firmware@453e49b we could not connect to our raspberry pi after this command howeverNote both methods 1 and 2 seem to detect our other T265 camera that we have with us:
The outputs of
lsusbanddmesgseem to also detect the D435 camera:dmesg output (click to expand)
Furthermore was there an alternate way to upgrade the Linux Kernel, considering method 5 caused a disconnect from the raspberry pi?
The text was updated successfully, but these errors were encountered: