This is a subtype of the Byte DataType with the OptionSetValues Property defined. The InFlagsType is formally defined in Table 14.
|
Value |
Bit No. |
Description |
|
CommunicationError |
0 |
0: No error 1: An error was detected in the previous ResponseSPDU. |
|
OperatorAckRequested |
1 |
Used to inform the SafetyProvider that operator acknowledgment is requested. |
|
FSV_Activated |
2 |
Is used for conformance test of SafetyConsumer.SAPI.FSV_Activated |
Bits 3..7 are reserved for future use shall be set to zero by the SafetyConsumer and shall not be evaluated by the SafetyProvider.
The InFlagsType representation in the AddressSpace is defined in Table 15.
Table 15 – InFlagsType Definition
|
Attribute |
Value |
|||||
|
BrowseName |
InFlagsType |
|||||
|
IsAbstract |
False |
|||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Other |
|
|
Subtype of the Byte DataType defined in OPC 10000-5 |
||||||
|
0:HasProperty |
Variable |
0:OptionSetValues |
0:LocalizedText [] |
0:PropertyType |
|
|
|
Conformance Units |
||||||
|
SafetySupport |
||||||
NOTE CommunicationError can be used as a trigger, e.g., for a communication analysis tool. It is not forwarded to the safety application by the SafetyProvider. If CommunicationError is needed in the safety application, bidirectional communication can be implemented and the value of CommunicationError can be put into the user data.