-
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
RGB Extrinsic recovery routine failed #6914
Comments
Hi @fiorano10 In a past ROS case where the Ignoring transform for child_frame_id error was reported, Doronhi the RealSense ROS wrapper developer said that camera extrinsics can go wrong during a firmware update. This may be what happened to you, given that the problem coincided with a firmware update. IntelRealSense/realsense-ros#595 (comment) Given that firmware 5.12.5 is no longer the most recent firmware (5.12.6 is the newest at the time of writing this), upgrading to 5.12.6 would seem to be the best option. If 5.12.5 is your preference, you would still have the option of downgrading back to 5.12.5 afterward and hopefully the update will complete successfully this time. If the problem is not resolved by a firmware update, performing a gold reset of the camera to its factory-default configuration may resolve the problem, and this method worked for RealSense users in the discussion linked to above. who still had issues after a firmware update A Gold Reset restores the camera's calibration to its factory-new configuration and corrects corruptions in the calibration table stored inside the camera. The details of how to perform a gold reset are:
You can use CustomRW to perform a gold reset on the camera by inputting the command below: Intel.Realsense.CustomRW -g See page 58 onward of the user guide for the full documentation about CustomRW. |
Case closed due to no further comments received. |
I updated the camera to 5.12.5 using
rs-fw-update
and since then I've been getting these errors when launching the ROS node:The text was updated successfully, but these errors were encountered: