Riccardo Zuppetti

**Update:** Rerunning the following command with the default parameters: ``` ros2 launch realsense_camera2 rs_launch.py ``` leads to the same issue encountered with the updated parameters: ``` [realsense2_camera_node-1] 06/03 09:59:05,679 WARNING...

Referring to this error: ``` [realsense2_camera_node-1] [ERROR] [1709723913.783679926] [camera.camera]: Given value, 63 is invalid. Set ROS param back to: 100 ``` what values can be used?

Hi @MartyG-RealSense, updating the camera firmware and connecting the camera to an USB3 port seems to overcome the encountered issue. By the way there is always the error about the...

> I note that in your log, **accel_fps** is set to 63. Around April 2022, the IMU component in RealSense cameras was changed to a similar component that supports **100**...

Instead, the gyro values supported are still 200 and 400?

Hi @MartyG-RealSense, no thanks. I'll close the issue right now. Thank you again.

Probably in the clone on this repo there is not specified the branch to which refer. On top, regarding the Ros2 Sdk that can be used with this digital twin...

Quick update: the clone command in the README should be updated by putting the `-b added_copter` arg. On top, from the `omniverse_sim.py` I've removed everything that concerns `copter`. Starting the...

> Do you have screenshots? Can you send it here please? Like I've said above, the IP to which the Ros2 SDK refers is the one of the machine, and...

Hi @xl232lx, I've tried to run the reconstruction on my own RGB data and the result seems quite good. Btw, trying to show the final pcd using open3d, I'm only...