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
	An interface for reading analog input, like for addressing a whole subdevice in comedi. More...
class	RTT::dev::AnalogInput
	A class representing an analog input channel. More...
class	RTT::dev::AnalogOutInterface
	An interface for writing analog output, like for addressing a whole subdevice in comedi. More...
class	RTT::dev::AnalogOutput
	A class representing an analog output channel. More...
class	RTT::dev::AxisInterface
	The AxisInterface represents an axis from a control point of view. More...
class	RTT::dev::CalibrationInterface
	A class which will calibrate a sensor. More...
class	RTT::dev::DigitalInInterface
	A class representing a Digital Input device from which a maximum of 32 bits can be read at once. More...
class	RTT::dev::DigitalInput
	A class representing a switch which can be on or off. More...
class	RTT::dev::DigitalOutInterface
	A class representing a Digital Output device which can read or write a maximum of 32 bits at once. More...
class	RTT::dev::DigitalOutput
	A DigitalOut represents any on/off output. More...
class	RTT::dev::DriveInterface
	A Drive Object controls a single axis. 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 ()
	A HomingInterface provides all necessary data to perform axis homing.

---

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.