Conversation
…fake mir100 controllers
This branch has not been deployed
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.
Adds what RI needs to drive a MiR100 from RoboticsAcademy, simulated or
physical.
(mir_driver plus rosbridge_server) and republishes it as the same /mir100
topics the simulated robot uses. It runs inside the docker, the ROS1
drivers stay outside.
and robot_state_publisher instead of spawning the robot in Gazebo.
fake MiR100, to test without the robot.
Warehouse 1.
lasers do not publish.
Needs the RAM PR (JdeRobot/RoboticsApplicationManager#302) to launch physical worlds, and the RA PR of the mir100 for the exercise side and the roslibpy dependency.