Only released in EOL distros:
Package Summary
RMS (Robot Management System) is a remote lab management tool designed for use with controlling ROS enabled robots from the web.
- Author: Russell Toris
- License: BSD
- Source: git https://github.com/WPI-RAIL/rms.git (branch: fuerte-devel)
Package Summary
RMS (Robot Management System) is a remote lab management tool designed for use with controlling ROS enabled robots from the web.
- Maintainer: Russell Toris <rctoris AT wpi DOT edu>
- Author: Russell Toris <rctoris AT wpi DOT edu>
- License: BSD
- Bug / feature tracker: https://github.com/WPI-RAIL/rms/issues
- Source: git https://github.com/WPI-RAIL/rms.git (branch: groovy-devel)
About
The RMS (Robot Management System) is a remote lab management tool designed to controll ROS enabled robots from the web. RMS itself refers to a web-management system written in PHP/HTML backed by a MySQL database. RMS is written in a robot-platform independent manner allowing for the control of a variety of robots. In addition to being cross-platform, RMS allows for basic user management, interface management, and content management. The RMS stack itself contains the web server code for the RMS. |
|
Who Should Use the RMS?
RMS was designed to be an easy to use, easy to mange remote lab system for use by robotic researchers and enthusiasts. Developed in PHP/HTML with a MySQL backend, the RMS itself is not considered a light-weight system; however, by using a heavier system, tools such as user management, content management, and interface management become possible.
Does the RMS Itself Require ROS to Install?
No. The RMS was designed as a standalone system that can be easily installed on UNIX based web servers. The decision was made so that it is possible to host the RMS site itself on campus or third-party web servers without the need of maintaining and installing ROS on that server. RMS will point to ROS servers which are running rosbridge v2.0 in order to control the robot.
How Does the RMS Communicate with ROS?
The RMS uses the lastest version of rosjs to communicate with ROS servers. For the ROS server to communicate back to the RMS, a server running rosbridge_suite should be running.
Cool Widgets! Do I Need RMS to Use Them?
No. Most of the widgets available in the system were developed as standalone widgets as part of the Robot Web Tools effort. The RMS admin panel simply wraps these widgets and provides an easy-to-use GUI to customize them to fit your needs.
Is There More to Come?
Yes! The current released version of RMS is a very early-stage release of the system. The following are just a few of the features we hope to add soon:
- 3D Interactive Widgets
- Additional, more complex, interface examples
- Additional tutorials
- More robust REST API
- Much more!
API Reference
There are two forms of the RMS API: the RMS PHP Developers API and the RMS REST API.
RMS PHP Developers API
The first is the RMS PHP Developers API. This API should be referenced if you want to modify, add to, or debug the RMS system itself. This portion of the API is under active developement and will become available once it is in a more stable state.
RMS REST API
Portions of the RMS REST API are avaiable in RMS since release 0.1.0. This API is under active developement, but many features are already avaible. To learn more about the API, please refer to the RMS REST API Documentation.
Tutorials
This section contains a set of useful tutorials for use with the RMS.
Installation and Basic Management
The follow is a list of tutorials that will help with installation and basic management tasks:
RMS Environment Servers
The follow is a list of tutorials that can help with setting up an RMS environment server:
Full List
The following is a complete set of useful tutorials for use with the RMS.
|
|
Support
Please feel free to contact me at any point with questions, comments, and bug reports.
