Problem running D435i on Orin Nano 4gb
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, docker, yaml
- Domain
- devops, embedded-iot, robotics
Research direction
Start with the realsense2_camera::RealSenseNodeFactory entry point and the supplied YAML configuration, reproducing the launch in Docker on the Jetson Orin Nano 4GB with a D435i. Observe /dev/video devices during startup and after stopping the container, and verify whether the ROS node can restart without reconnecting the camera. Done means the cause and a reliable fix or documented limitation are established.
Written by the indexing model from the issue text.
Description
I'm having an issue when using a D435i in docker on an nvidia Jetson Orin nano 4GB.
The issue is that when I launch the camera using the following configuration, the /dev/video devices disappear from my system.
I use them to determine if the camera is connected within the container, so I want them to stay.
The other issue I experience is that after killing the docker container and trying again, I am unable to start the ros node unless I unplug and replug the device.
I have the udev rules set correctly on the host, and the only realsense lib installed is inside my container, and I have checked that I only have one installed. I have tried both the RSUSB and the UVC backends and both have the issue. I have also tried both the latest libraries and firmwares and the NVIDIA recommended ones and I still have the issue. I'm hoping someone has also seen this issue, and maybe has figured out how to fix this.
realsense_node = ComposableNode(
namespace=namespace,
package='realsense2_camera',
plugin='realsense2_camera::RealSenseNodeFactory',
name=f'{camera_name}_realsense_camera', # Give a unique name to the node
parameters=parameters)
Yaml config:
device_type: ''
serial_no: ''
usb_port_id: ''
rgb_camera:
profile: '640x480x15'
color_info_qos: "SENSOR_DATA"
color_qos: "SENSOR_DATA"
depth_module:
profile: '640x480x60'
emitter_enabled: 1
emitter_on_off: true
depth_qos: "SENSOR_DATA"
depth_info_qos: "SENSOR_DATA"
infra_qos: "SENSOR_DATA"
enable_accel: true
enable_color: true
enable_depth: true
enable_gyro: true
enable_infra1: true
enable_infra2: true
pointcloud:
enable: false
pointcloud_texture_index: 0
pointcloud_texture_stream: RS2_STREAM_ANY
enable_sync: true
align_depth: true
gyro_fps: 200
accel_fps: 63
unite_imu_method: 2
- Dominant language
- C++
- Stars
- 750
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA-ISAAC-ROS/isaac_ros_nvblox
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
NVIDIA-ISAAC-ROS/isaac_ros_nvblox#171 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
coming soon!
NVIDIA-ISAAC-ROS/isaac_ros_nvblox#159 · 5 comments · 2 assignees ·
All issues in NVIDIA-ISAAC-ROS/isaac_ros_nvblox
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·