-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Can't use rs_camera.py script with D457 using serial_no option in ROS2 #2912
Comments
Hi @maksimmasalski Is your D457 set up for use on a GMSL connection, with the required accompanying components such as a special software driver and a deserializer board? If you do not have either of these then the D457 can be used on a USB connection by moving a mode switch in a recess within the camera casing to the 'USB' position (the switch's default position is 'MIPI'). Instructions for doing so can be found at the link below. https://support.intelrealsense.com/hc/en-us/community/posts/14840675121043/comments/14843232242835 In USB mode the camera will be detected as D455, with the same feature-set and performance as a D455 but with the added protection against dust and water provided by the IP65-rated camera casing. In USB mode the camera is 'plug and play' like the other RealSense 400 Series models and does not require the special driver or the deserializer board. |
Yes, I have all the equipment like deserializer board and driver. |
Support for D457 in the ROS2 compatibility 'wrapper' for RealSense was added in version 4.54.1 of the wrapper, which is designed for use with version 2.54.1 of the RealSense SDK and ROS2 Humble or Iron. So this part of your system should be fine. Intel's MIPI reference driver is designed for use with an Jetson AGX Xavier computer and Intel's own brand of deserializer board, otherwise then the reference driver must be converted (ported) for use with the computer and deserializer component that you have chosen. Intel are unfortunately unable to assist with the porting process, so it must be done by the user's own development team. https://github.com/IntelRealSense/realsense_mipi_platform_driver The Intel deserializer is only supplied for very large volume orders, so most D457 users who are using GMSL will need to obtain a third-party deserializer and port the driver for their particular hardware. An exception to this is the D457-compatible Connect Tech system, which does not require a deserializer and has its own driver. More information about this can be found at IntelRealSense/librealsense#10984 (comment) |
Hi @maksimmasalski Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Hi,
I have D457 GMSL camera and I'm trying to make it work in ROS. Usually with USB 3.0 Realsense cameras like D435i, I can easily provide
serial_no
option to choose camera that I want to use in ROS2 (I use Humble), like thisros2 launch realsense2_camera rs_launch.py align_depth.enable:=true enable_sync:=true init_reset:=true pointcloud.enable:=true serial_no:="'947522071000'"
with D457 the same style causes an error "No RealSense devices were found!:"
ros2 launch realsense2_camera rs_launch.py align_depth.enable:=true enable_sync:=true init_reset:=true pointcloud.enable:=true serial_no:="'220422302342'"
Full Error log:
What I am doing wrong or is it a bug?
The text was updated successfully, but these errors were encountered: