|
|
Topics | |
| DebugDrawerConfigWidget | |
| A description of the library DebugDrawerConfigWidget. | |
| Intelligent Coordinates | |
| ArmarX contains a concept for Intelligent Coordinates that eases transformation into different coordinate frames. | |
| RobotAPI Components | |
| | |
| RobotAPIComponentPlugins | |
| A description of the library RobotAPIComponentPlugins. | |
| RobotStatechartHelpers | |
| A description of the library RobotStatechartHelpers. | |
| RobotUnit | |
| A description of the library RobotUnit. | |
| RobotUnitDataStreamingReceiver | |
| A description of the library RobotUnitDataStreamingReceiver. | |
| Statecharts | |
| armem_grasping | |
| A library redirecting to GraspingUtility to make the ArMem-related classes there easier to find. | |
| diffik | |
| A description of the library diffik. | |
| natik | |
| A description of the library natik. | |
The RobotAPI package provides a robot-intependent API that other ArmarX packages can use for accessing central functionality of a robot. The central elements of RobotAPI are Sensor-Actor Units, i.e. components responsible for the propagation of sensor values and actor targets. Sensor-Actor Units work as a link between higher level ArmarX components and the actual robot hardware or a robot simulation environment, respectively. The RobotAPI package contains base classes for Sensor-Actor Units for different purposes, e.g. KinematicUnit for sensors and actors related to robotic joints. Concrete Sensor-Actor Units inherit from these base classes in order to provide a common interface. Each type of hardware and each type of simulation environment requires a distinct set of Sensor-Actor Units that handle the hardware/simulator access, e.g. KinematicUnitArmar3 and KinematicUnitArmar4 for accessing the kinematic elements of ARMAR-III and ARMAR-4, respectively:
There are three ways to access Sensor-Actor Units:
Further documentation on the various contents of the RobotAPI package: