-
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
Hardware Notification:Depth stream start failure,1.60683e+12,Error,Hardware Error #1533
Comments
Hi @Steven-ZY As a starting point in this case, could you try adding a reset command to the end of your roslaunch instruction to reset the camera at launch, please? initial_reset:=true |
@MartyG-RealSense Thanks. But even I follow your instructions, the same problem wasn't solved. And I update the issue, which is more detailed. |
@MartyG-RealSense |
Is the camera able to stream depth correctly in the RealSense Viewer program? |
@MartyG-RealSense Yes, it's OK in realsense viewer program. |
That is a positive sign as it shows that there is not a hardware problem with the camera. I'm not convinced that the Motion Module Force Pause warning would make a difference to the launch. Asic temperature is not valid could suggest a lengthy timeout (lack of arriving data) from the camera if the Asic temperature is checked every 10 seconds and the warning has occurred three times in the log. Can you check if the depth topic is publishing data despite the depth stream start error please: rostopic echo /camera/depth/image_rect_raw |
Hi @Steven-ZY Do you require further assistance with this case, please? Thanks! |
No, thanks. I figured it out.
|
Okay, great to hear - thanks very much for the update! |
@Steven-ZY would be helpful if you mention how you solved the above mentioned issue as we face a similar one from time to time on some of our robots |
@Tal-seven Hey, bro. You may use the keyboard combination Super+O to toggle the rotation lock ON/OFF. |
I'm running into the exact same problem and I'm not sure how work around it. The issue seems to come up when I add enable the gyro and accel outputs. If I run But with I can kind of work around it if I remove the My full output when I see the error:
|
Hi @brentalanmiller Do you see any improvement in reliability if you add the command below to the end of your roslaunch instruction when enabling gyro and accel? unite_imu_method:=linear_interpolation |
Hi @MartyG-RealSense No, same error:
|
Your librealsense and ROS wrapper versions are matched correctly (2.40.0 SDK and 2.2.20 ROS wrapper). As you do not have problems when the IMU topics are not enabled, that would suggest that the librealsense and ROS wrapper installations are okay. The warning control_transfer returned suggests a serious communication problem with the device if the warning is generating continuously instead of just several times during launch, or once or twice per minute after launch. I note that your log is reporting that the IMU is not calibrated. 08/01 14:32:12,699 WARNING [139948410152704] (ds5-motion.cpp:473) IMU Calibration is not available, default intrinsic and extrinsic will be used. Have you performed a calibration of your D455's IMU yet please? https://dev.intelrealsense.com/docs/imu-calibration-tool-for-intel-realsense-depth-camera https://github.com/IntelRealSense/librealsense/tree/master/tools/rs-imu-calibration And does the IMU perform okay when accessed through the Motion Module of the RealSense Viewer program? |
@brentalanmiller Please do try what @MartyG-RealSense has suggested. Also have you updated the firmware of your realsense recently. Try downgrading a version and see if the error goes away, it helped me. |
Thanks for the help @Tal-seven!, I downgraded to 05.12.09.00 and that seems to have fixed the problem. I still get the warning But to @MartyG-RealSense's points, I also tried the following before downgrading:
Thanks to both of you for your help. |
Thanks so much @Tal-seven for your help! Hi @brentalanmiller Great news that you had successful results. Yes, the Motion Module Failure warning does not prevent the IMU from working normally in the Viewer after the message has occurred. |
I had the same error with the depth module failure. I believe it is because of the resolution with the depth sensor + its fps. I have tried different resolution and fps combinations. no failure for depth sensor if: |
note the previous trial is on D435. |
@MartyG-RealSense I get the same error: What could be the reason for this warning? EDIT: I just saw the other comment mentioning the fps. The warning doesn't appear on 60 fps |
@rakshith95 Similarly, the RealSense ROS case #2068 (comment) discusses how a Depth Stream Start Failure crash would occur at 90 FPS but there was not a problem at 60 FPS. In that case, a RealSense team member provided advice at #2068 (comment) that solved the problem. The discussion below the linked-to comment at that case is also worth reading. |
Hi @brentalanmiller @Tal-seven @rakshith95 @MartyG-RealSense @wx1909 Can you help me check my problem? I have similar issue. And I am using Ubuntu 18.04.6 in VMware. The D415 camera works fine with real-sense viewer but it fails to open in terminal with ros and rviz:
|
Hi @ozilxu The case at #2423 is a useful reference to start with in investigating your problem. Based on the information in that case, may I ask:
roslaunch realsense2_camera rs_camera.launch initial_reset:=true |
thanks!That's very good for me |
roslaunch realsense2_camera rs_camera.launch
There is an error:
"Hardware Notification:Depth stream start failure,1.60683e+12,Error,Hardware Error"
How to solve it? Thanks in advance.
The text was updated successfully, but these errors were encountered: