realsense-ros: Incorrect Parsing of Physical IDs

I have two realsense d435 cameras connected to a powered USB 3.0 hub, but I can’t run them at the same time.

The reason seems to be related to incorrectly parsing the physical IDs of the devices to get the usb port. See the following warning: [ WARN] [1578695869.249368440]: Error extracting usb port from device with physical ID: 2-1.1.1.2-28 Please report on github issue at https://github.com/IntelRealSense/realsense-ros

I also noticed that there was a recent merge to attempt to remedy issues with parsing physical IDs of realsense cameras connected to USB hubs: #972

This merge makes the assumption that the physical ID has a format similar to the following: [ INFO] [/rear_right/realsense/realsense_camera_manager] [1572376422.393304228]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb4/4-6/4-6.3/4-6.3:1.0/video4linux/video6 was found.

However, my device physical IDs are not being read in that format: [ INFO] [1578696525.735386134]: Device with physical ID 2-1.1.1.2-28 was found.

Here’s some more information generated from rs-enumerate-devices:

Device info: 
    Name                          : 	Intel RealSense D435
    Serial Number                 : 	740112070338
    Firmware Version              : 	05.11.10.00
    Recommended Firmware Version  : 	05.10.03.00
    Physical Port                 : 	/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1.2/2-1.1.1.2:1.0/video4linux/video1
    Debug Op Code                 : 	15
    Advanced Mode                 : 	YES
    Product Id                    : 	0B07
    Usb Type Descriptor           : 	3.2

 Device info: 
    Name                          : 	Intel RealSense D435
    Serial Number                 : 	801312071134
    Firmware Version              : 	05.11.10.00
    Recommended Firmware Version  : 	05.10.03.00
    Physical Port                 : 	/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1.3/2-1.1.1.3:1.0/video4linux/video4
    Debug Op Code                 : 	15
    Advanced Mode                 : 	YES
    Product Id                    : 	0B07
    Usb Type Descriptor           : 	3.2

Finally, it seems like all of the following issues stem from this same problem: #1018 #1039 #1036

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 28 (2 by maintainers)

Most upvoted comments

@RealSenseCustomerSupport The issue is not there in the librealsense 2.28.1 and the associated realsense-ros. Using these versions, I could get it to work. However, the issue exists in the new ros realsense version 2.30 and 2.31. Therefore, I hope that this issue will be fixed in subsequent versions so that we can use any new features that will be released along with the newer librealsense versions. If realsense has a record of this, we can close the issue here. I initially presumed that the issue will be kept open until a fix is released with a newer librealsense version.

shreyas2311 on Feb 19, 2020

After you clone the realsense-ros repo, cd into it and do git checkout 2.2.8

shreyas2311 on Jan 15, 2020