Difference between revisions of "The Robotic Development Subsystem"

From The BABEL Development Site
 
(2 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
* [[ Architecture:Specification of BABEL Interfaces | Interfaces ]]
 
* [[ Architecture:Specification of BABEL Interfaces | Interfaces ]]
 
* [[ Architecture:Specification of BABEL Modules | Modules ]]
 
* [[ Architecture:Specification of BABEL Modules | Modules ]]
* [[ Architecture:Robotic Platform Descriptors | RPDs ]]
+
* [[ Architecture:The RPD and APP databases | The RPD and APP databases]]
 
* [[ Architecture:Data Types | Data Types ]]
 
* [[ Architecture:Data Types | Data Types ]]
 
* [[ Architecture:Unique Event Codes | Event Codes ]]
 
* [[ Architecture:Unique Event Codes | Event Codes ]]
 
* [[ Architecture:RPD_Server | RPD_Server ]]
 
* [[ Architecture:RPD_Server | RPD_Server ]]
 +
* [[ Architecture:APP_Server | APP_Server ]]
 +
* [[ Architecture:Visual_RPD_Editor | Visual RPD Editor ]]
 
* [[ Architecture:High Level ACHRIN layer | ACHRIN ]]
 
* [[ Architecture:High Level ACHRIN layer | ACHRIN ]]
 +
 +
 +
* '''Tutorials''':
 +
**  [[Architecture Tutorial: Retrieve laser scans ]]

Latest revision as of 20:58, 22 July 2009

The BABEL ROBOTIC DEVELOPMENT SUBSYSTEM (BRDS) addresses the problem of designing low-level modules for robotics control architectures under the BABEL development environment. These modules are typically developed by different researchers or students and their integration into any high-level architecture represents a big challenge due to the heterogeneity and the variety of involved tasks.

This specification aims to normalize the structure of the low-level part of robotics control architectures, related with sensory and motor issues. Their interfaces are normalized in an effort to give a long-term stabilized repertory of modules, as well as leading to architectures largely independent of the particular robotic platform they are executed on. Architecture designers are free to specify the high-level modules (world modeling, task planning or motion planning) as desired and exploiting the robot-independent services offered by this low-level architecture.


You can navigate through the BRDS documentation by following these links: