Classes | Functions
Device Interfaces

Abstraction APIs for hardware devices ('cards') such as IO, counters, but also logical devices like Encoders and generic Sensors. More...

Classes

class  RTT::dev::AnalogInInterface
class  RTT::dev::AnalogInput
class  RTT::dev::AnalogOutInterface
class  RTT::dev::AnalogOutput
class  RTT::dev::AxisInterface
class  RTT::dev::CalibrationInterface
 A class which will calibrate a sensor. It is useful for making 'calibration' objects. More...
class  RTT::dev::DigitalInInterface
class  RTT::dev::DigitalInput
class  RTT::dev::DigitalOutInterface
class  RTT::dev::DigitalOutput
class  RTT::dev::DriveInterface
 A Drive Object controls a single axis. It is responsible for keeping track of its status (enabled, disabled). More...
class  RTT::dev::EncoderInterface
 The most generic interface to a position/turn counter, for encoding positions. More...
class  RTT::dev::SensorInterface< SensorData >
 An interface that describes a general sensor You can read a value/structure. More...

Functions

 RTT::dev::HomingInterface::HomingInterface ()

Detailed Description

Abstraction APIs for hardware devices ('cards') such as IO, counters, but also logical devices like Encoders and generic Sensors.

The Orocos Device Interface classes are DigitalInInterface, DigitalOutInterface, AnalogInInterface, AnalogOutInterface, SensorInterface, EncoderInterface,...

Only header files are found in this package. In order to decouple device creation and device location, some classes have been extended with a (process-local) nameserver. See the NameServer class.


Function Documentation

A HomingInterface provides all necessary data to perform axis homing.



rtt
Author(s): RTT Developers
autogenerated on Fri Sep 9 2016 04:02:18