ROSE-AP supporting the management of robot program definitions that can be instantiated for different robot vendors and a management system for working with them.
This project is part of DIH^2. For more information check the RAMP Catalogue entry for the components.
| 📚 Documentation | 🐳 Docker Hub |
|---|
This ROSE-AP is an IoT application for defining, building, and managing robot programs. The use case description exposed below better conveys an idea of the ROSE-AP main features.
- Using a cad designer a program_definition is generated. This program_definition is a JSON document that describes a robot program defining a series of trajectories that the robot is going to follow using a specific tool and velocity.
- The program_definition is sent to the Management System.
- Using the robot program manager front-end we select a program_defintion to generate a robot program executable for a particular robot model.
- The robot_program generated is downloaded to a particular robot on the factory floor.
- The robot engineer checks that the robot_program generated works correctly.
- If the robot engineer edits the program the program manager front-end is used to upload the edited program to the Management System.
- Once the robot_program has been verified the robot engineer changes the state of the robot_program to verified using the program manager front-end.
Information about how to install the IoT Robot Program Manager can be found at the corresponding section of the Installation Guide.
Please visit the step-by-step guide to setup a demonstration, or watch the step-by-step video.
A description of the architecture can be found in the Architecture documentation
Information about how to use the ROSE-APP can be found in User & Programmers Manual.
If you'd like to contribute, start by searching through the issues and pull requests to see whether someone else has raised a similar idea or question. Before contributing, please check out Contribution guidelines.
Apache2.0 © 2022