Realsense d435i is not detected on docker #10829
Comments
|
|
|
Hi @goyalvarun02 Is the camera detected if you add initial_reset:=true to your roslaunch instruction to reset the camera at launch, please? For example: roslaunch realsense2_camera rs_camera.launch initial_reset:=true in regard to the rs-enumate-devices command that you attempted, the command (which should be input into the Ubuntu terminal) is: rs-enumerate-devices |
|
Hi @MartyG-RealSense , PFA image of the output after running , device not found Pls advice |
|
Can you confirm please that you used initial_reset, as your log image shows initial-reest (with a - instead of the underline _ ) |
|
Hi @MartyG-RealSense I I am really sorry for typo error .
|
|
No problem at all :) Which method did you use to install the librealsense SDK and the RealSense ROS wrapper? Did you install them separately (the SDK first and the wrapper second) or install them both at the same time from packages with the Method 1 instructions in the ROS wrapper? |
|
I first installed ROS-Melodic and then use command thereafter created a catkin_ws with clone of repository of xarm_ros and realsense . Compiled the realsense in Catkin_src and install. |
|
Using sudo apt-get install ros-$ROS_DISTRO-realsense2-camera is fine. This will install both the librealsense SDK and the ROS wrapper from packages. You will not likely need to install realsense2-description unless you are performing ROS robot simulations such as Gazebo. Creating a catkin_ws with a clone of RealSense sounds as though it has the potential to cause a conflict with the package installation that you made before taking that step. If you have installed from packages then you should not then need to install from source with cloning. |
|
Okay So I can remove the realsense-ros repo , recompiled . I tried that too, still getting an error |
|
Does the error still occur if you delete the entire catkin_ws/src folder? |
|
I can not delete the entire SRC folder but have deleted the build and devel folder to clean recompiled. But still error occurred. |
|
My recollection is that it is advised that only RealSense files should be installed in the catkin_ws workspace and not non-RealSense files. Is the camera able to be detected if you run the realsense-viewer tool in the Ubuntu terminal? |
|
For other setup I have kept the non-Realsense files as well in catkin_ws it was working fine . I did not find the command realsense-viewer in ubuntu ? Do I need to install anything for it. |
|
I'm not certain whether the realsense-viewer tool is included in a librealsense build created with the ROS wrapper's apt-get installation instructions. What details are listed if you do rs-enumerate-devices |
|
rs-enumerate-devices command not found . I am trying to install in docker but still looking for it to install. |
|
Which VM tool are you using, please? Intel recommend VMWare Workstation Player (and not Oracle VrtualBox) because it provides proper emulation of the USB 3 controller. |
|
I am using oracle VM and also done the enabling of Virtualization and USB 3 in Bios setting . I have created a new catkin_ws as well , and still facing the same issue . |
|
My knowledge of Docker setups is admittedly limited. Also, Ubuntu 22.04 is not yet officially supported by librealsense - there is an unofficial test installation at #10439 (comment) - though my understanding is that the host machine's Ubuntu version should not affect the librealsense build on the VM's Ubuntu that us using 18.04. I am also not familiar with xarm_ros. What details are shown if you input lsusb in the Ubuntu terminal? lsusb is an Ubuntu tool rather than a RealSense one and so should work no matter what problems a RealSense installation has. |
|
Hi @MartyG-RealSense , When I do lsusb in host machine/ VM /Docker it shows intel real-sense is detected and USB 007 is used for it. I am struggling and could not find the root cause of this issue . |
|
I went through the case again carefully from the beginning but did not find a clear possibility for the cause of the problem, aside from perhaps the USB port supplying insufficient power to the camera for it to do more than be detected by lsusb; or the Oracle VM not being able to process the camera's USB 3 connection despite the enabling of virtualization and USB 3 in the BIOS. The typical diagnosis process for a Failed to set power state error in the RealSense ROS wrapper would involve first confirming whether the camera can work successfully with a librealsense program such as the RealSense Viewer or one of the librealsense example programs and tools (such as rs-enumerate-devices) |
|
I observed following things:
PFA image You can let me know how to check with realsense-viewer and rs-enumerate-devices as I did not find the direct command to use . |
|
Hi @MartyG-RealSense PFA full logs as well . root@ubuntu-22:/# roslaunch realsense2_camera rs_camera.launch started roslaunch server http://ubuntu-22:44361/ SUMMARYPARAMETERS
auto-starting new master setting /run_id to 8d092cf0-283a-11ed-a696-6cb3115d58d8 [ INFO] [1661846748.421541872]: Device with physical ID 2-1.4-107 was found. . |
|
Are pre-built executable versions of RealSense examples and tools such as rs-enumerate-devices and realsense-viewer present in the usr/local/bin folder of Ubuntu 18.04 after you installed the SDK and wrapper from packages with sudo apt-get install ros-$ROS_DISTRO-realsense2-camera please? Launch commands for these examples and tools should be input into the Ubuntu terminal and not the ROS terminal. As the roslaunch proceeds normally with the camera detected up until the RealSense Node is Up! message and then is no longer detected, it does again suggest a power related issue (the camera disconnecting as the power demands of the camera increase as the streams start publishing). Because you can output RGB from cheese, this suggests that the depth stream might be the cause of the Failed to set power state warnings. Does it still disconnect if you add enable_depth:=false to your launch instruction so that it only publishes color? |
Setup1 : Setup 2:
I have observed from cheese while RGB output If some movement happen it can seen in video , while using depth camera no movement can seen (or it stuck/hung ). |
|
Let's try installing from packages only the examples and tools, not the librealsrnse SDK (which is already installed)
|
|
Hi @MartyG-RealSense . Here is the output of commands:
Stream Profiles supported by Stereo Module Stream Profiles supported by RGB Camera
Output of roslaunch command is still same :-( |
|
It is good that realsense-viewer is working for you now. Your image of it highlights a couple of issues though.
The recommended firmware version for use with SDK 2.51.0 is 5.13.0.50 and so I would strongly recommend updating your camera's firmware.
You can correct this easily by going to the location below on your computer and deleting the udev rule there, and then the error should disappear. /etc/udev/rules.d/99-realsense-libusb.rules |
|
I have deleted the rules from /etc/udev/rules.d/99* and updated the firmware. After firmware update when I observed error , I reconnect the camera again it says need to update firmware , Why so ? May I know the reason If I have update firmware once it should be persistent. I have used the method check update and install. i was trying to update firmware using "More" -> update firnware as well but there I could not find any signed image in bin :-( . I dont know whether firmware update earlier has been completed or not . PFA images for your reference (output of lsusb, rs-enumerate device after firmware updates)
|
|
When using the Update Firmware option in the Viewer, a firmware bin file should first be downloaded to your computer from the list at the link below. The most recent firmware at the time of writing this, 5.13.0.50, is at the top of the list. Once the bin file is downloaded then when the Update Firmware option is selected, navigate the file selector pop-up window to the file at the computer location that it was downloaded to and select the file. The firmware update should then begin automatically. https://dev.intelrealsense.com/docs/firmware-releases#d400-series-firmware-downloads
It is recommendable that the firmware update is performed using the official 1 meter long USB cable supplied with the camera if possible. Your kindly provided images indicate to me that a firmware update commenced and reached the 30% point. At this point, the camera resets itself, disconnects for a moment and then is re-detected and continues the firmware installation process. In a small number of cases though, the camera may not be detected again after the reset at the 30% point and the firmware update fails. Are you performing the firmware update outside of Docker, please? Because the firmware is stored inside the camera hardware instead of on the computer, it is possible to perform the update on another computer if you have one available and then take the camera back to the original computer with the updated firmware inside it. |
|
Hi @goyalvarun02 Do you require further assistance with this case, please? Thanks! |
|
Hi @MartyG-RealSense , After upgrading to latest FW , it works and I did not observer " Power state failure error" . Thanks for help. |
|
That's great to hear, @goyalvarun02 - thanks very much for the update! |
|
Case closed due to solution achieved and no further comments received. |
I am using Ubuntu 22.04 host machine and created a VM of ubuntu 18.04 to use Melodic version of ROS with Realsense camera.
But I am using docker on VM (ubuntu 18.04) , and when I tried to run
roslaunch realsense2_camera rs_camera.launch
I got an error :
"Failed to set power state" as shown in pic
I am new to librealsense please advise
The text was updated successfully, but these errors were encountered: