This method is mandatory for the profile SafetyProviderServerMapper (see 13.2.2.1). It is used to read SafetyData 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.
The method argument OutSafetyData has an application-specific type derived from Structure. This type (including the type identifier) is expected to be the same in both the SafetyProvider and the SafetyConsumer. Otherwise, the SafetyConsumer will not accept the transferred data and switch to fail-safe values instead (see state S16 in Table 33 – SafetyConsumer states as well as Clauses 8.2.3.2 and 8.2.3.4).
Signature
ReadSafetyData (
[in]UInt32InSafetyConsumerID,
[in]UInt32InMonitoringNumber,
[in]InFlagsTypeInFlags,
[out] StructureOutSafetyData,
[out]OutFlagsTypeOutFlags,
[out]UInt32OutSPDU_ID_1,
[out]UInt32OutSPDU_ID_2,
[out]UInt32OutSPDU_ID_3,
[out]UInt32OutSafetyConsumerID,
[out]UInt32OutMonitoringNumber,
[out]UInt32OutCRC,
[out] StructureOutNonSafetyData)
;
Table 8 – ReadSafetyData Method Arguments
|
Argument |
Description |
|
InSafetyConsumerID |
“Safety Consumer Identifier”, see SafetyConsumerID in Table 24. |
|
InMonitoringNumber |
“Monitoring Number of the RequestSPDU”, see Clause 8.2.1.2 and MonitoringNumber in Table 24. |
|
InFlags |
“Byte with non-safety-related flags from SafetyConsumer”, see Clause 6.2.1. |
|
OutSafetyData |
“Safety Data”, see Clause 8.2.1.4. |
|
OutFlags |
“Byte with safety-related flags from SafetyProvider”, see Clause 6.2.2. |
|
OutSPDU_ID_1 |
“Safety PDU Identifier Part1”, see Clause 8.2.3.2. |
|
OutSPDU_ID_2 |
“Safety PDU Identifier Part2”, see Clause 8.2.3.2. |
|
OutSPDU_ID_3 |
“Safety PDU Identifier Part3”, see Clause 8.2.3.2. |
|
OutSafetyConsumerID |
“Safety Consumer Identifier”, see SafetyConsumerID in Table 24 and Table 27. |
|
OutMonitoringNumber |
Monitoring Number of the ResponseSPDU, see Clause 8.2.1.8, Clause 8.2.3.1, and Figure 14. |
|
OutCRC |
CRC-checksum over the ResponseSPDU, see Clause 8.2.3.5. |
|
OutNonSafetyData |
“Non-safe data” see Clause 8.2.1.10. |
Table 9 – 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 |
|
Conformance Units |
|||||
|
ReadSafetyData |
|||||