UA Part 15: Safety - 6.2.3 Datatype Definition

This is a subtype of the Byte DataType with the OptionSetValues Property defined. The InFlagsType is formally defined in Table 14.

Table 14 – InFlagsType Values

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.

6.2.3.2 OutFlagsType

This is a subtype of the Byte DataType with the OptionSetValues Property defined. The OutFlagsType is formally defined in Table 16.

Table 16 – OutFlagsType Values

Value	Bit No.	Description
OperatorAckProvider	0	Operator acknowledgment at the provider, hereby forwarded to the SafetyConsumer, see OperatorAckProvider in the SAPI of the SafetyProvider, Subclause 6.3.3.2.
ActivateFSV	1	Activation of fail-safe values by the safety application at the SafetyProvider, hereby forwarded to the SafetyConsumer, see ActivateFSV in the SAPI of the SafetyProvider, Subclause 6.3.3.2
TestModeActivated	2	Enabling and disabling of test mode in the SafetyProvider, hereby forwarded to the SafetyConsumer, see EnableTestMode in the SAPI of the SafetyProvider, Subclause 6.3.3.2

Bits 3..7 are reserved for future use shall be set to zero by the SafetyProvider and shall not be evaluated by the SafetyConsumer.

The OutFlagsType representation in the AddressSpace is defined in Table 17.

Table 17 – OutFlagsType Definition

Attribute		Value
BrowseName		OutFlagsType
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

6.2.3.3 RequestSPDUDataType

Table 18 – RequestSPDUDataType Structure

Name	Type	Description
RequestSPDUDataType	structure
InSafetyConsumerID	UInt32	See corresponding method argument in Table 7.
InMonitoringNumber	UInt32	See corresponding method argument in Table 7.
InFlags	InFlagsType	See corresponding method argument in Table 7.

NOTE The Prefix “In” should be interpreted from the SafetyProvider’s point of view and is used in a consistent manner to the parameters of the method ReadSafetyData (see 6.2.2.3).

The representation in the AddressSpace of the RequestSPDUDataType DataType is defined in Table 19.

Table 19 – RequestSPDUDataType definition

Attributes	Value
BrowseName	RequestSPDUDataType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	ModellingRule
Subtype of Structure defined in OPC 10000-5.
Conformance Units
SafetyPDUs

6.2.3.4 ResponseSPDUDataType

Table 20 – ResponseSPDUDataType Structure

Name	Type	Description
ResponseSPDUDataType	structure
OutFlags	OutFlagsType	See corresponding method argument in Table 7.
OutSPDU_ID_1	UInt32	See corresponding method argument in Table 7.
OutSPDU_ID_2	UInt32	See corresponding method argument in Table 7.
OutSPDU_ID_3	UInt32	See corresponding method argument in Table 7.
OutSafetyConsumerID	UInt32	See corresponding method argument in Table 7.
OutMonitoringNumber	UInt32	See corresponding method argument in Table 7.
OutCRC	UInt32	See corresponding method argument in Table 7.

NOTE The Prefix “Out” is interpreted from the SafetyProvider’s point of view and is used in a consistent manner to the parameters of the method ReadSafetyData (see 6.2.2.3).

[RQ6.7] To define the concrete data type for the ResponseSPDU (which specifies the concrete data types for SafetyData and NonSafetyData, respectively), proceed as follows: (1) Derive a concrete data type from the abstract ResponseSPDUDataType. (2) In doing so, add the following fields to the structure in the given order: (a) First, field OutSafetyData with the concrete structure data type for the SafetyData (which has to be a concrete structure data type, see 7.2.1.5). (b) Second, field NonSafetyData with the concrete structure data type for the NonSafetyData (or a placeholder data type, see requirement RQ6.8).

[RQ6.8] To avoid possible problems with empty structures, the dummy structure NonSafetyDataPlaceholder shall be used as DataType for OutNonSafetyData when no non-safety data is used. The datatype-node defining this structure has a fixed node-ID and contains a single Boolean.

The representation in the AddressSpace of the ResponseSPDUDataType DataType is defined in Table 21.

Table 21 – ResponseSPDUDataType definition

Attributes	Value
BrowseName	ResponseSPDUDataType
IsAbstract	True
References	NodeClass	BrowseName	DataType	TypeDefinition	ModellingRule
Subtype of Structure defined in OPC 10000-5
Conformance Units
SafetyPDUs

6.2.3.5 NonSafetyDataPlaceholderDataType

Table 22 – NonSafetyDataPlaceholderDataType Structure

Name	Type	Description
NonSafetyDataPlaceholderDataType	structure
Dummy	Boolean	Dummy variable to avoid empty structures.

NOTE The receiver should not evaluate the value of ‘Dummy’.