Search

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

18 result(s) for RequestSPDU

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

5.4 Safety communication layer structure

provided by the SafetyProvider . PubSub : The SafetyProvider publishes the ResponseSPDU and subscribes to the RequestSPDU . The SafetyConsumer publishes the RequestSPDU and subscribes to the ResponseSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.5 Requirements for CRC calculation

Client/Server communication, this means that a Method Call with all fields making up the RequestSPDU being zero shall be answered with all fields making up the ResponseSPDU being zero. Neither
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

used. The Method ReadSafetyData has a set of input arguments that make up the RequestSPDU and a set of output arguments that make up the ResponseSPDU . The SafetyConsumer uses ... implementations supporting OPC UA PubSub , the OPC UA Object SafetyPDUs with its Properties RequestSPDU and ResponseSPDU shall be used. RequestSPDU is published by the SafetyConsumer and subscribed by the SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

Safety Consumer Identifier", see SafetyConsumerID in Table 23 . InMonitoringNumber " MonitoringNumber of the RequestSPDU ", see 7.2.1.3 and MonitoringNumber in Table 23 . InFlags "Octet with non-safety -related
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.5 Object SafetyPDUs

Facet SafetyConsumerPubSubMapper It is used by the SafetyProvider to subscribe to the RequestSPDU and to publish the ResponseSPDU . The DataType of RequestSPDU is structured in the same ... have a counterpart within the Information Model of the SafetyConsumer . The SafetyConsumer publishes the RequestSPDU and subscribes to the ResponseSPDU . Table 11 - SafetyPDUsType definition Attribute Value BrowseName SafetyPDUsType IsAbstract False
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.2 SAPI of SafetyProvider

operator acknowledge is requested by the SafetyConsumer . This flag is received within the RequestSPDU . ActivateFSV ( Fail-safe substitute values) Boolean I By setting this input
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

configuration as well. SafetyProviderDelay is the maximum time at the SafetyProvider from receiving the RequestSPDU to start the transmission of ResponseSPDU , see 8.1 . The parameter SafetyProviderDelay has no influence
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

General Figure 11 shows the structure of a RequestSPDU which originates at the SafetyConsumer and contains a SafetyConsumerID , a MonitoringNumber ( MNR ), and one octet of ( non-safety -related) Flags ... details. See 6.2.3.3 for details on the RequestSPDUDataType definition. NOTE 1 The RequestSPDU does not contain a CRC signature. Figure 11 - RequestSPDU Figure 12 shows the structure of a ResponseSPDU
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 ... used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only be accepted if its MNR matches the MNR of the corresponding RequestSPDU . The checking for correctness
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.8 ResponseSPDU: SafetyConsumerID

ResponseSPDU shall be a copy of the SafetyConsumerID received in the corresponding RequestSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.9 ResponseSPDU: MonitoringNumber

ResponseSPDU shall be a copy of the MonitoringNumber received in the corresponding RequestSPDU . See 7.2.3.1 . NOTE The SafetyConsumer uses the ResponseSPDU.MonitoringNumber to detect SPDUs received with timeliness error, e.g. SPDUs ... erroneous network element which stores data. A different MonitoringNumber is used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only be accepted if its MonitoringNumber matches
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram

state machine implementation itself or the SafetyProvider 's OPC UA Mapper ) with an identical RequestSPDU multiple times in a row. In that case, the SafetyProvider (state machine ... watchdog time checked in the SafetyConsumer . The watchdog is restarted immediately before a new RequestSPDU is generated (transitions T14 and T28 of the SafetyConsumer in Table 35 ). If an appropriate
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.3 Duration of demand

SafetyConsumer can evaluate any one of a given number of ResponseSPDUs for a given RequestSPDU . In the examples, the SafetyData is made up of two components: the "respective safety ... times the SafetyConsumerTimeout . This worst-case time occurs when the two transmissions of a RequestSPDU and its corresponding ResponseSPDU , which are necessary according to the descriptions above, each take
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

Method call in the case of Client/Server communication or the detection of a changed RequestSPDU by the OPC UA Mapper in the case of PubSub communication. In case of several ... SafetyProvider instance. Table 30 - SafetyProvider instance internal items Internal items Type Definition RequestSPDU_i Variable Local memory for RequestSPDU (required to react on changes). SPDU_ID_1_i UInt32 Local
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

ResponseSPDU.NonSafetyData SAPI.FSV_Activated:= 0 RequestSPDU.Flags.FSV_Activated:= 0 RequestSPDU.Flags.CommunicationError:= 0 <Set RequestSPDU> Macro Instruction to transfer the whole RequestSPDU to the OPC UA Mapper . <(Re)Start ConsumerTimer ... random MNR ) MNR_i:= max(MNR_i, MNR_min)1 S13_PrepareRequest // Build RequestSPDU and send (done in T16) S14_WaitForChangedSPDU // Safety Layer is waiting for next ResponseSPDU from SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

8.2 Safety function response time part of communication

SafetyConsumerTimeout: Watchdog timer running in the SafetyConsumer . It is started immediately before a new RequestSPDU is sent (T14 or T28). If the timer runs out a timeout error is triggered ... justified by Figure 25 and the following explanation: The SafetyConsumer sends a RequestSPDU . At about the same time, a dangerous event occurs at the SafetyProvider , demanding the safety function
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

qualifier" RQ6.17 SafetyConsumer diagnostic message texts 6.4.2 Diagnostics messages of the SafetyConsumer RQ7.1 RequestSPDU Flags 7.2.1.4 RequestSPDU: Flags RQ7.2 Contents and structure of SafetyData in ResponseSPDU 7.2.1.5 ResponseSPDU: SafetyData
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.3 Usage of OPC UA safety Variables in Connections

exchange is always bidirectional ( ResponseSPDU containing the safety application data in one direction and RequestSPDU in the other direction), even for a unidirectional safety data exchange. Figure C.3 - Example