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

Encountered usbEnumerator create UnpackDevicePort failed! error #66

Open
bd-fauna opened this issue Oct 14, 2024 · 1 comment
Open

Encountered usbEnumerator create UnpackDevicePort failed! error #66

bd-fauna opened this issue Oct 14, 2024 · 1 comment

Comments

@bd-fauna
Copy link

bd-fauna commented Oct 14, 2024

When running this command:

ros2 run orbbec_camera list_devices_node

I get the following error:

[10/14 15:42:32.536321][info][593222][Context.cpp:68] Context created with config: default config!
[10/14 15:42:32.536331][info][593222][Context.cpp:73] Work directory=/workspaces/isaac_ros-dev, SDK version=v1.10.15-20241012-bb4e350
[10/14 15:42:32.536343][info][593222][LinuxPal.cpp:32] createObPal: create LinuxPal!
[10/14 15:42:32.548750][info][593222][LinuxPal.cpp:166] Create PollingDeviceWatcher!
[10/14 15:42:32.548765][info][593222][DeviceManager.cpp:15] Current found device(s): (1)
[10/14 15:42:32.548899][info][593222][DeviceManager.cpp:24] 	- Name: Femto Bolt, PID: 0x066b, SN/ID: , Connection: USB3.1
[ERROR] [1728934953.049575478] [list_device_node]: usbEnumerator create UnpackDevicePort failed!

Any idea what might be the issue?

I am running this command inside a docker, I am able to run it outside of the docker.

Thanks in advance!

@jian-dong
Copy link
Contributor

Hi @bd-fauna
The Femto Bolt depth engine seems to require access to GPU resources, which might not be configured correctly in your Docker environment. When you run the command outside of Docker, your system likely has access to the GPU, but this access may not be enabled inside the Docker container.

To fix this issue, please ensure your Docker container is set up to allow access to the GPU. When starting the container, you can check Docker's settings and documentation regarding GPU access, mainly using the --gpus option. If GPU access is not correctly configured, the depth engine will not function as expected, leading to errors like yours.

CC @zhonghong322 @xcy2011sky

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

No branches or pull requests

2 participants