-
Notifications
You must be signed in to change notification settings - Fork 172
Open
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed
Description
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.
- That MIR is actually running ROS internally (although that didn't really take long to figure out)
- A figure of the architecture like
ROS - mir_driver - rosbridge - rosbridge - MIR - That one can actually just connect to the roscore on MIR. I misread the network specifications and thought that all the ports would be closed, so I though our only access would be through rosbridge.
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?
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed