Enable dependency injection of the ethercat master #15
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
By allowing the EtherCat master to be injected into each class, it is possible to design a plugin-based architecture for binding the youbot driver to a robotic software framework such as ROS or OROCOS: One component or plugin in the framework instantiates the EtherCat master and can then pass it to further components or plugins which are in turn responsible for communicating with either the base, the manipulator or the gripper. The dependency injection is optional. Thus, the default behaviour remains unchanged.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
By allowing the EtherCat master to be injected into each class, it is possible to design a plugin-based architecture for binding the youbot driver to a robotic software framework such as ROS or OROCOS: One component or plugin in the framework instantiates the EtherCat master and can then pass it to further components or plugins which are in turn responsible for communicating with either the base, the manipulator or the gripper.
The dependency injection is optional. Thus, the default behaviour remains unchanged.