-
Notifications
You must be signed in to change notification settings - Fork 4.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
WARNING : (d400-factory.cpp:1195) DS5 group_devices is empty. #12047
Comments
This case is related to IntelRealSense/realsense-ros#2816 Hi @jesusramondovale Yes, firmware 5.15.0.2 should be used with SDK 2.54.1. The firmware can be updated in the RealSense Viewer tool by going to the More option near the top of the Viewer's options side-panel and selecting **Update Firmware from its drop-down menu, then navigate a pop-up file selector from a firmware .bin file downloaded from the link below. https://dev.intelrealsense.com/docs/firmware-releases If you do not have access to the RealSense Viewer then you can also update using the text-based tool rs-fw-update and a firmware .bin file from the link above. https://github.com/IntelRealSense/librealsense/tree/master/tools/fw-update |
Hi! I succesfully updated the camera's firmware version to the last and recommended : 5.15.0.2 as you can see:
But the output when I run
Note that "Camera Locked" value says YES ... Does it mean something? EDIT: I noticed that I don't have librealsense-dkms package and I can't install it because it doesn't find the repository IP following the installation guide at https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md |
It is normal for the Camera Locked value to be Yes. It means that it is not one with special debug functions used by Intel engineers. The DKMS packages at the distribution_linux.md page will not work with an Arm computer such as your Debix. They are designed for computers with an x86 / x64 architecture such as desktop and laptop PCs. An exception to this is Nvidia Jetson Arm-based boards, which have their own dedicated Jetson packages for librealsense. DS5 group_devices is empty indicates that the librealsense and ROS wrapper software are being correctly detected but when the launch process then looks for the camera hardware, it cannot detect it. |
Don't ask me how, but now the realsense2_camera_node is working, publishing multiple topics: But the output of the camera node gives some warnings and errors, and I can't visualize the camera video on rqt nor rviz2 (no image):
|
The Did the advice that I suggested in your other case at IntelRealSense/realsense-ros#2816 (comment) to perform a reset make a difference? |
It's continously. It never stops ... I only copied two of them but there are lots of them messages. I'll try with that reset parameter.. EDIT: nope, doesn't make any difference :
|
It appears that a lot of streams are enabled at the same time. Let's try a launch where only depth is enabled and it is set to a low FPS speed and resolution to see if it reduces the number of warnings.
|
Same output:
|
It was confirmed in an earlier discussion that the camera works normally on another computer and the problems only occur on your Debix Model A. And unfortunately you are not able to change to another type of computing board. Do you have a different USB cable that you can try with the camera to confirm if the Debix is not working well with your current cable even though it works with the camera on your other computer. |
Yes, I'll try with another USB cable and come back to you. Thanks! EDIT: nothing changed. Topics are being published on ROS net (at least the names), but I can't visualize the video. |
Apologies for the delay in responding. A notification is not sent to me if an edit is made to a comment instead of a new comment being posted. Has there been no change since the previous week? |
Hi @jesusramondovale Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Hey. I've got the exact same problem again... debix@DEBIX25:~/librealsense$ ros2 launch realsense2_camera rs_launch.py I get this error ouput: [INFO] [launch]: All log files can be found below /home/debix/.ros/log/2023-09-27-06-45-57-373454-DEBIX25-14668 [INFO] [launch]: Default logging verbosity is set to INFO [INFO] [realsense2_camera_node-1]: process started with pid [14682] [realsense2_camera_node-1] [INFO] [1695797158.404652736] [camera.camera]: RealSense ROS v4.54.1 [realsense2_camera_node-1] [INFO] [1695797158.404968999] [camera.camera]: Built with LibRealSense v2.54.1 [realsense2_camera_node-1] [INFO] [1695797158.405047252] [camera.camera]: Running with LibRealSense v2.54.1 [realsense2_camera_node-1] 27/09 06:45:58,435 WARNING [281472476768480] (d400-factory.cpp:1195) DS5 group_devices is empty. [realsense2_camera_node-1] 27/09 06:45:58,830 ERROR [281472476768480] (librealsense-exception.h:52) xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument [realsense2_camera_node-1] 27/09 06:45:58,837 WARNING [281472476768480] (rs.cpp:312) null pointer passed for argument "device" [realsense2_camera_node-1] [WARN] [1695797158.837362369] [camera.camera]: Device 1/3 failed with exception: xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument [ERROR] [realsense2_camera_node-1]: process has died [pid 14682, exit code -11, cmd '/home/debix/ros2_ws/install/realsense2_camera/lib/realsense2_camera/realsense2_camera_node --ros-args --log-level info --ros-args -r __node:=camera -r __ns:=/camera --params-file /tmp/launch_params_j9ko_vrh --params-file /tmp/launch_params_w3fbxgpj']. I need help as soon as possible, please. |
Hi @jesusramondovale I have posted a reply at IntelRealSense/realsense-ros#2816 (comment) |
I get this output when trying to execute
ros2 run realsense2_camera realsense2_camera_node
on my DEBIX Model A (2GB RAM) with Ubuntu 22.04 (Debix Image) (Kernel 5.15) and ROS2 Humble installed:
Output:
The sudo rs-enumerate-devices command works fine (only doing it with sudo):
I've just seen that the camera's firmware version is lower than recommended. How do I update it?
The text was updated successfully, but these errors were encountered: