Skip to content
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

D435i not detected with built pyrealsense #6510

Closed
pwoolvett opened this issue Jun 3, 2020 · 4 comments
Closed

D435i not detected with built pyrealsense #6510

pwoolvett opened this issue Jun 3, 2020 · 4 comments

Comments

@pwoolvett
Copy link

pwoolvett commented Jun 3, 2020

Required Info
Camera Model D435i
Firmware Version 05.12.05.00
Operating System & Version Linux (Ubuntu 18.04)
Kernel Version (Linux Only) 4.9.140-tegra
Platform NVIDIA Jetson Xavier
Language python
Segment others

Issue Description

pyrealsense2.context.devices does not contain an entry for a D435i form a Jetson Xavier.

  1. install librealsense2: librealsense2-utils librealsense2-dev
  2. cloned librealsense repo
  3. built with build python binding flag only
  4. connect a D435 () and D435i (5.12.5.00)
  5. [*pyrealsense2.context().devices] contains a D435, but not the 435i

Additional info:

  • rs-enumerate-devices does not whow the camera
  • ls /dev/video* -> 6 devs: 3 only for the D435i and 3 for the D435
  • A Laptop with pip install pyrealsense2 does detect both cameras.
  • The laptop shows 6 devs for the D435i in /dev/video (besides the other 3 from the D435)
  • lsusb | grep 8086 -> Bus 002 Device 057: ID 8086:0b3a Intel Corp.
  • Same result when connecting with a hub or directly
  • realsense-viewer shows 03/06 14:23:08,173 WARNING [547583812032] (types.cpp:49) Accel Sensitivity:hwmon command 0x4f failed. Error type: No data to return (-21)., but runs OK and streams all three (rgb,depth, imu) data

Maybe related??

@pwoolvett pwoolvett changed the title D435i not detected built pyrealsense D435i not detected with built pyrealsense Jun 3, 2020
@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Jun 4, 2020

Hi @pwoolvett It sounds as though you are using multiple cameras attached to the computer at the same time. Is that correct, please?

If so, the RealSense developer team have created improvements to multicam that should appear in an upcoming SDK version. It should improve multicam problems that are related to rs2::pipeline but may not correct issues caused by specific USB hub hardware models.

#6467

There have been issues encountered by other Xavier users recently with using more than one camera at the same time. Until the multicam improvements are available, a RealSense user has offered a workaround for multi-camera detection problems in the link below in the meantime:

#5828 (comment)

@pwoolvett
Copy link
Author

I do not think this issue is related to multicamera setup.

It sounds as though you are using multiple cameras attached to the computer at the same time. Is that correct, please?

Indeed, but the problem also appeared when connecting only the D435i.

If so, the RealSense developer team have created improvements to multicam that should appear in an upcoming SDK version. It should improve multicam problems that are related to rs2::pipeline but may not correct issues caused by specific USB hub hardware models.

Good to know, but the problem showed up before pipeline creation earlier, as the D435i wouldn't show up using the library (although both realsense-viewer and gstreamer were able to launch videos - realsense-viewer could even stream depth and imu data)

There have been issues encountered by other Xavier users recently with using more than one camera at the same time. Until the multicam improvements are available, a RealSense user has offered a workaround for multi-camera detection problems in the link below in the meantime:
#5828 (comment)

Thanks, I'll keep it on my toolbox if such a problem appears.

I managed to solve the issue by re-building but now with these flags:
-DBUILD_PYTHON_BINDINGS:bool=true -DFORCE_RSUSB_BACKEND=ON -DPYTHON_EXECUTABLE=...

NOTE:

  • /dev/video still only shows three devs for D435i

@MartyG-RealSense
Copy link
Collaborator

Great news that you found a solution - thanks for the update!

@pwoolvett
Copy link
Author

Great news that you found a solution - thanks for the update!

Maybe its useful for someone checking compatibility with tegra devices to know the D435i reports different number of devices in /dev/video ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants