Add feature publish empty error-id topic in no error#298
Open
Add feature publish empty error-id topic in no error#298
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
I will implement a function that allows you to confirm that the MG400 has recovered from an error state simply by subscribing to the “error_id” topic. To do this, we will publish an empty “error_id” topic when the system recovers from an error state.
Solution
Test
Start up the MG400 main unit.
Launch MG400_ROS2.
ros2 topic echo /mg400/error_idPress the emergency stop button.
Call "clear_error" service.
ros2 service call /mg400/clear_error mg400_msgs/srv/ClearError {}\