Search

Scope: Core (OPC-10000-*) All specs

9 result(s) for SPDUs

OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.5 Requirements for CRC calculation

value, shall use the value "1" instead. [RQ5.6] SPDUs with all values (incl. CRC signature) being zero shall be ignored by the receiver ( SafetyConsumer and SafetyProvider ). For Client/Server ... answered with all fields making up the ResponseSPDU being zero. Neither of these SPDUs shall be presented to the respective state machines
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.1 General

this document. This implementation serves three purposes: support of the safe exchange of SPDUs at runtime online browsing, to identify SafetyConsumers and SafetyProviders , and to check their parameters for diagnostic
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

repeatedly publishing and subscribing Messages , see Figure 14 . [RQ6.4] For diagnostic purposes, the SPDUs received and sent shall be accessible by calling the Method ReadSafetyDiagnostics . Figure 3 - Server Objects
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.5 Object SafetyPDUs

value to the other three SafetyAutomationComponents using three SafetyProviders , each comprising a pair of SPDUs . For each recipient, there is an individual pair of SPDUs . Figure 5 - Safety multicast with
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

SafetyProviderLevel is used to distinguish devices of a different SIL . As a result, SPDUs coming from a device with a low SIL will never be accepted when a SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.3 RequestSPDU: MonitoringNumber

RequestSPDU: MonitoringNumber The SafetyConsumer uses the MNR to detect SPDUs with timeliness errors, e.g. such SPDUs which are continuously repeated by an erroneous network element which stores data. A different
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.9 ResponseSPDU: MonitoringNumber

corresponding RequestSPDU . See 7.2.3.1 . NOTE The SafetyConsumer uses the ResponseSPDU.MonitoringNumber to detect SPDUs received with timeliness error, e.g. SPDUs which are continuously repeated by an erroneous network element which stores
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

used as guard condition of "Changed ResponseSPDU received" as well. 2 SPDUs with all values (incl. CRC signature) being zero shall be ignored, see requirement RQ5.6
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

instead of "0" 5.5 Requirements for CRC calculation RQ5.6 Ignore all-zero SPDUs 5.5 Requirements for CRC calculation RQ6.1 Singleton SafetyACSet Folder 6.2.2.1 SafetyACSet Object RQ6.2 Objects ... SafetyACSet Object RQ6.3b Usage of SafetyPDUs for PubSub 6.2.2.1 SafetyACSet Object RQ6.4 Provide SPDUs for diagnostics in Method ReadSafetyDiagnostics 6.2.2.1 SafetyACSet Object RQ6.5 Restrictions on DataTypes 6.2.2.2 Safety ObjectType definitions