• TTTGW

The Tine naming schema uses as Tango device names with three fields as:
CONTEXT/SERVER_NAME/DEVICE_NAME
The names can be mapped one to one from Tine to Tango. A Tine device has a set of properties to read and write data. These Tine properties can be mapped, in most cases, to Tango attributes.

The basic idea of the Tine to Tango Gateway is based on the one to one name mapping. Every Tango device created for the gateway class MUST use a valid Tine device name. During the init_device() the connection to the Tine device will be established with the given device name. The properties of the Tine device are queried and mapped to Tango attributes. For every Tine property a dynamic attribute will be created under the same name. This is possible for all standard data types, but not for special Tine structure types. Tine properties with no input and no ouput data are mapped into Tango commands.

Tine alarms are mapped into an ALARM state of the Tango device. The alarm description is available with the Tango status command.

LIMITATION: Tine properties with different input and output data types are not yet handled.
They must be mapped into Tango commands. Tango commands can be created dynamically, but they are seen always by all devices of the class. This makes sense only when all devices instanciated by the gateway class have the same interface. To insure the same interface, the Tine devices mapped must have the same SERVER_NAME.