The DisplayToOperatorType ObjectType is used to display messages to the operator of a machine. It is based on the BaseObjectType and is intended to be used as AddIn. Its formal definition is given in Table 31.
Table 31 – DisplayToOperatorType ObjectType Definition
Attribute |
Value |
||||
BrowseName |
DisplayToOperatorType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of BaseObjectType as defined in OPC 10000-3 |
|||||
0:HasProperty |
Variable |
0:DefaultInstanceBrowseName |
0:QualifiedName |
0:PropertyType |
|
0:HasComponent |
Variable |
DispFlag |
DispFlag |
0:BaseDataVariableType |
O,RW |
0:HasComponent |
Variable |
AckFlag |
String |
0:BaseDataVariableType |
O,RW |
0:HasComponent |
Variable |
DispText |
String |
0:BaseDataVariableType |
O,RW |
|
|
|
|
|
|
Conformance Units |
|||||
IREDES DisplayToOperatorType |
The component Variables of the DisplayToOperatorType have additional Attributes defined in Table 32.
Table 32 – DisplayToOperatorType Attribute values for child Nodes
BrowsePath |
Value Attribute |
Description Attribute |
0:DefaultInstanceBrowseName |
DisplayToOperator |
The default BrowseName for instances of this type. |
The description can be found in Table 33.
Table 33 – DisplayToOperatorType Attribute Values for Child Nodes
BrowsePath |
Description Attribute |
DispFlag |
States under which circumstances the line (message) has to be displayed to the operator. |
AckFlag |
Acknowledgement by the operator that he has read the message. (Will be transferred back as soon as the SiteHead is returned to the mine’s computer system with the next protocol exchange. Contains the name of the operator (user name in the Automation system) or simply ACK if automation system does not work with user logins. |
DispText |
Text to be displayed. |