-
Notifications
You must be signed in to change notification settings - Fork 155
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
Add documentation about MIR and mir_bridge functionalities #59
Labels
Comments
Yes, any updates to the documentation would be more than welcome! |
Do you prefer a set of markdown files or to start a wiki? |
I have a slight preference for a set of markdown files. |
Hi @matthias-mayr, @mintar I can help on this as well. @matthias-mayr can you provide the above documentation even if is just a draft? |
This issue is still in the back of my head, but I am totally busy until the first week of November. |
mintar
added
enhancement
New feature or request
help wanted
Extra attention is needed
labels
Jun 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently got a new MIR200 and since it comes with a new software version, it was not directly compatible with this ROS driver.
We spent quite some time to figure out, how the MIR would work, how it connects with rosbridge and why it was not working right away. With the insight we obtained up to now, we could have saved quite some of it, if there would have been some more documentation, e.g.
ROS - mir_driver - rosbridge - rosbridge - MIR
All the manuals I got with the MIR leave out, that it runs ROS and a lot of other tips and tricks that appear in various issues here. It seems to me that it would be a lot of help for people if this implicit knowledge would be expressed somewhere.
What do you think?
The text was updated successfully, but these errors were encountered: