OpenDAF configuration consists of several configurable named entities. Entity name must conform to C-language symbol name requirements (can contain only letters, digits and the underscore, can't start with digit) and must be unique among entities of the same type.
Entity attributes fall into one of three categories:
- mandatory (mandatory user-configured attribute)
- optional (optional user-configured attribute)
- runtime (runtime-only attribute)
By definition, measurement is the assignment of a number to a characteristic of an object or event, which can be compared with other objects or events. In the context of OpenDAF, measurement is always obtained from one of connected downlink devices via assigned connector.
In OpenDAF context, emitting command is a way to execute some action in connected downlink device via assigned connector. It can be used to control downlink device outputs, set setpoints, or invoke any device-specific actions.
Alarm is a stateful object representing some alarm condition presence. It can be triggered and acknowledged automatically by script, or through public API.
Connector is an instance of a stack of software modules, designed to provide communication with some downlink device. The stack typically implements some standard (i.e. IEC-60870-5-101 controlling station, Modbus/RTU master...) or proprietary communication protocol.
Provider is an instance of a stack of software modules, designed to handle communication with some uplink device. The stack typically implements some standard (i.e. IEC-60870-5-104 controlled station, Modbus/TCP slave...) or proprietary communication protocol.