-
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
D435 camera won't publish infra2 topic #9158
Comments
Hi @Russ76 Infra2 would be unavailable if the camera was on a USB 2 connection, as that mode requires USB 3. If your camera is plugged into a USB 3 port, could you check please the USB type that your ROS launch process is detecting by checking the Device USB type line of the launch log, as described in the link below. If it is detecting the camera as being on USB 2 then the number reported should be 2.1 instead of 3.2 (a USB 3 connection). |
[ INFO] [1622814592.984338256]: Device with name Intel RealSense D435 was found. Yes, this indicates a problem. The port is type 3, I understand. At some times I have used a hub so that the keyboard and mouse may be also connected. That device says it is type 3. Somewhere the type number got changed, for it was working with both stereo streams on an earlier day. Is this a ROS problem or a Linux problem? |
If you launch the RealSense Viewer program at look at the number beside the camera name in the options side-panel (2.1 or 3.2), this should indicate whether the detection issue is only in the ROS wrapper or in both RealSense ROS and librealsense. |
Realsense viewer reports USB port is type 2.1 It also reports this error at startup: Timestamp: 1622821858845.864258 |
The Multiple realsense udev-rules were found warning typically occurs if librealsense has been built with both the source-code and Debian packages on the same computer. If this is the case, the warning should disappear if the version of the udev (device handling) rules in the etc/udev folder is removed. The rule in the lib/udev folder is the one that should not be deleted, as doing so may break linkages to Debian packages. |
OK, thanks. Is there any way to correct this USB misidentification? |
I would recommend first dealing with the multiple udev rule warning to see if that resolves the USB 2.1 issue. You could also try adding the command initial_reset:=true to the end of your ROS roslaunch instruction to reset the camera at launch if you are not doing so already. A camera reset can also be performed in the Viewer by going to the More option near the top of the side-panel and selecting Reset Hardware from the drop-down menu. |
I have done all you suggested. Even installed another USB 3.0 powered hub. ROS and Realsense-viewer still report port is USB 2.1. |
If the control_transfer returned warning generates continously then it can indicate that there is a serious communication problem with the device. We can test whether the USB system on that particular computer is being over-burdened by launching ROS with a custom camera configuration that only streams low-resolution depth. roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30.0 initial_reset:=true |
$ roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30.0 initial_reset:=true RLException: while processing /opt/ros/melodic/share/realsense2_camera/launch/includes/nodelet.launch.xml: Param xml is . Node xml is
|
$ roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30 initial_reset:=true started roslaunch server http://thomas-tx1:41437/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 1bb7ca52-c55d-11eb-8907-00044b79c483 [ INFO] [1622828928.557308887]: Device with physical ID 1-3.1.1-8 was found. [ INFO] [1622828934.816057911]: Device with physical ID 1-3.1.1-9 was found. |
Can you run it again with depth_fps:=30 instead of 30.0 please? Sorry about that! |
Yes, the second one listed above was with number corrected. |
It is unusual that a depth-only configuration was defined in the link below: roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30 initial_reset:=true But in the launch log, the color stream seems to be being published too at 640x480 and 15 FPS. Please add enable_color:=false to the above roslaunch instruction to see whether that provides a depth-only launch. |
thomas@thomas-tx1:~$ roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30 initial_reset:=true enable_color:=false started roslaunch server http://thomas-tx1:39687/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 79474998-c564-11eb-9d8a-00044b79c483 [ INFO] [1622832091.995735178]: Device with physical ID 1-3.1.1-9 was found. [ INFO] [1622832098.262045950]: Device with physical ID 1-3.1.1-10 was found. rostopic list |
Stop the presses! It was my cable. It was not 3.0 type. I'm sorry, I didn't know to watch for that. A number of my cables are type 2.0 even though they are new. It must have the blue plastic inside, then it has more pins for the connections. My bad |
Which firmware driver version is your D435 camera using please? If you do not know the firmware version, you can find it in the RealSense Viewer by left-clicking on the Info option near the top of the options side-panel Edit:. Never mind - thanks for the update! |
05.12.13.50 |
Okay, that firmware is correct for SDK 2.45.0. Thanks very much. Please do post an update when you are able to test with a USB 3 cable. Good luck! |
Yes, I had one 3.0 cable, and there is the topic infra2, as before! Sorry, I must have missed the memo about blue plugs on USB 3.0 cables. There are more wires inside! Of course the others can't work. I thought the difference was only in the jacks. Thanks for your patient help. I now have 5 new cables on order! |
You are very welcome - I'm pleased that you had a successful outcome. :) |
This issue can bite a fellow. In fact, in an article on the Intel website, there is a link to buy a cable for this very camera, and the cable is not type 3.0 |
An update or a wrong setting seems to have stopped infra2 ROS topic from being published. This is to work with rtabmap software. At first the camera worked perfectly with the mapping software, with infra1 and infra2 stereo image streams. Now I can't get camera to produce infra2 at any time. Using the parameters I can reliably turn on and off the infra1 steam, but infra2 is gone! Is this from a software or firmware update? I am using the Nvidia Jetson TX1 board, Ubuntu 18.04, and ROS Melodic.
The text was updated successfully, but these errors were encountered: