This method reads safe data from the SafetyProvider. It is in the responsibility of the safety application, that this method is not concurrently called by multiple SafetyConsumers. Otherwise, the SafetyConsumer may receive invalid responses resulting in a safe reaction which may lead to spurious trips and/or system unavailability.

Signature

ReadSafetyData(

[in]UInt32InSafetyConsumerID

[in]UInt32InMonitoringNumber

[in]ByteInFlags

[out] StructureOutSafetyData

[out]ByteOutFlags

[out]UInt32OutSPDU_ID_1

[out]UInt32OutSPDU_ID_2

[out]UInt32OutSPDU_ID_3

[out]UInt32OutSafetyConsumerID

[out]UInt32OutMonitoringNumber

[out]UInt32OutCRC

[out] StructureOutNonSafetyData)

;

Table 9–ReadSafetyData Method Arguments

Argument

Description

InSafetyConsumerID

“Safety Consumer Identifier”, see SafetyConsumerID in Table 13.

InMonitoringNumber

“Monitoring Number of the RequestSPDU”, see Clause 8.1.1.2and MonitoringNumber in Table 13.

InFlags

“Byte with Non safety Flags from SafetyConsumer“, see Flags in Table 18.

OutSafetyData

“Safety Data”, see Clause 8.1.1.4.

OutFlags

“Byte with Safety Flags from SafetyProviderSafetyProvider“, see Flags in Table 19.

OutSPDU_ID_1

“Safety PDU Identifier Part1”, see Clause  8.1.3.2.

OutSPDU_ID_2

“Safety PDU Identifier Part2”, see Clause  8.1.3.2.

OutSPDU_ID_3

“Safety PDU Identifier Part3”, see Clause  8.1.3.2.

OutSafetyConsumerID

“Safety Consumer Identifier”, see SafetyConsumerID in Table 13and Table 17Table 13.

OutMonitoringNumber

Monitoring Number of the ResponseSPDU, see Clause 8.1.1.8, Clause  8.1.3.1, and Figure 13.

OutCRC

CRC-checksum over the ResponseSPDU, see Clause 8.1.3.5.

OutNonSafetyData

“Non-safe data” see Clause 8.1.1.10.

Table 10– ReadSafetyData Method AddressSpace definition

Attribute

Value

BrowseName

ReadSafetyData

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

HasProperty

Variable

InputArguments

Argument[]

PropertyType

Mandatory

HasProperty

Variable

OutputArguments

Argument[]

PropertyType

Mandatory