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