Search

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

26 result(s) for ResponseSPDU

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

5.4 Safety communication layer structure

Client calling the Method 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

RequestSPDU being zero shall be 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.2.1 SafetyACSet Object

make up the RequestSPDU and a set of output arguments that make up the ResponseSPDU . The SafetyConsumer uses the OPC UA Client with the OPC UA Service Call . [RQ6.3b ... 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 . ResponseSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

Identifier", see SafetyConsumerID in Table 23 and Table 26 . OutMonitoringNumber MonitoringNumber of the ResponseSPDU , see 7.2.1.9 , 7.2.3.1 , and Figure 11 . OutCRC CRC over the ResponseSPDU , see 7.2.3.6 . OutNonSafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.5 Object SafetyPDUs

used by the SafetyProvider to subscribe to the RequestSPDU and to publish the ResponseSPDU . The DataType of RequestSPDU is structured in the same way as the input arguments of ReadSafetyData ... DataType of ResponseSPDU is structured in the same way as the output arguments of ReadSafetyData . See Table 11 for the definition of the SafetyPDUsType. Both variables in the SafetyPDUsType have
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.1 InFlagsType

Description CommunicationError 0 0: No error 1: An error was detected in the previous ResponseSPDU . OperatorAckRequested 1 Used to inform the SafetyProvider that operator acknowledgment is requested. FSV_Activated
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.4 ResponseSPDUDataType

corresponding Method argument in Table 7 . [RQ6.7] To define the concrete DataType for the ResponseSPDU (which specifies the concrete DataTypes for SafetyData and NonSafetyData , respectively), proceed as follows: (1) Derive
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

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

6.3.4.2 SAPI of SafetyConsumer

output SafetyData FSV (all binary "0") are provided1. NOTE A ResponseSPDU which is checked with an error results in FSV_Activated being ... allowed, this output is connected to OperatorAckConsumer, see B.3.4 and B.3.5 . NOTE If the ResponseSPDU is checked with error, this output remains at its last value, see T24 in Table
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

contain a CRC signature. Figure 11 - RequestSPDU Figure 12 shows the structure of a ResponseSPDU which originates at the SafetyProvider and contains the SafetyData (1 to 1 500 octets ... details. See 6.2.3.4 for details on the ResponseSPDUDataType definition. Figure 12 - ResponseSPDU NOTE 2 To avoid spurious trips, the ResponseSPDU is transmitted in an atomic (consistent) way from
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.3 RequestSPDU: MonitoringNumber

different MNR is 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
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.7 ResponseSPDU: SPDU_ID

ResponseSPDU: SPDU_ID This field is used by the SafetyConsumer to check whether the ResponseSPDU is coming from the correct SafetyProvider . For details
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.8 ResponseSPDU: SafetyConsumerID

ResponseSPDU: SafetyConsumerID [RQ7.5] The SafetyConsumerID in the 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: MonitoringNumber [RQ7.6] The MonitoringNumber in the 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 ... different MonitoringNumber is used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only be accepted if its MonitoringNumber matches the MonitoringNumber in the corresponding RequestSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.10 ResponseSPDU: CRC

ResponseSPDU: CRC [RQ7.7] The ResponseSPDU CRC shall be used to detect data corruption. See 7.2.3.6 on how it is calculated in the SafetyProvider and how it is checked
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram

transition T17 in Table 35 ), and therefore will use only the first evaluated ResponseSPDU for a given MNR and all further ResponseSPDUs with the same MNR will be ignored. NOTE ... generated (transitions T14 and T28 of the SafetyConsumer in Table 35 ). If an appropriate ResponseSPDU is received in time, and the checks for data integrity, authenticity, and timeliness
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.3 Duration of demand

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 a time of just slightly
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

Macro Instruction to take the whole RequestSPDU from the OPC UA Mapper . <Set ResponseSPDU> Macro Instruction to transfer the whole ResponseSPDU to the OPC UA Mapper. <Calc ... BaseID_i (octets 12…15) XOR ProviderID_i // see 7.2.3.2 for clarification <build ResponseSPDU> Macro Take the MNR and the SafetyConsumerID of the received RequestSPDU . Add the SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

error Timers ConsumerTimer Timer This timer is used to check whether the next valid ResponseSPDU has arrived on time. It is initialized using the parameter SPI.SafetyConsumerTimeout . NOTE As opposed ... consecutive errors is smaller than the value SafetyErrorIntervalLimit , FSV will be activated. Otherwise, the ResponseSPDU is discarded and the SafetyConsumer waits for the next ResponseSPDU . This timer is initialized using
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.1 Build ResponseSPDU

Build ResponseSPDU [RQ7.15] The ResponseSPDU shall be built by the SafetyProvider by copying RequestSPDU.MonitoringNumber and RequestSPDU.SafetyConsumerID into the ResponseSPDU . In addition, SPDU_ID , Flags , the SafetyData and the NonSafetyData shall ... calculated and appended. Figure 20 gives an overview over the task of building the ResponseSPDU . Figure 20 - Overview of task for SafetyProvider For the ResponseSPDU.Flags , see 7.2.1.6 . For the calculation
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.6 Calculation of a CRC signature

signature ( ResponseSPDU.CRC ) and sends it to the SafetyConsumer as part of the ResponseSPDU . This enables the SafetyConsumer to check the correctness of the ResponseSPDU including the SafetyData , flags , MNR , SafetyConsumerID ... beginning with the highest memory address. Figure 23 shows the calculation sequence of a ResponseSPDU CRC on a little-endian machine, using an example SafetyData with the following fields: Int32
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

8.2 Safety function response time part of communication

processed at the SafetyProvider just before the dangerous event becomes known. Hence, the ResponseSPDU does not yet contain any information about the dangerous event. In the worst case, the ResponseSPDU ... error leads to a loss or unacceptable delay of either the RequestSPDU or the ResponseSPDU . Hence, the SafetyConsumerTimeout expires. In the worst case, the timer expires immediately after
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.1.1 SafetyBaseID and SafetyProviderID

SafetyProviderID and SafetyBaseID is used by the SafetyConsumer to check the authenticity of the ResponseSPDU . SafetyProviderID and SafetyBaseID are usually assigned during engineering or during commissioning
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.3.2 Safety related assumptions (informative)

restrictions; any number of message storing elements is permitted Size of SafetyData within one ResponseSPDU : ≤ 1 500 octets Even for safety functions that do not require manual operator acknowledgment
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

DataTypes for out data 6.2.2.2 Safety ObjectType definitions RQ6.7 Definition of concrete DataTypes for ResponseSPDU 6.2.3.4 ResponseSPDUDataType RQ6.8 Usage of NonSafetyDataPlaceHolder 6.2.3.4 ResponseSPDUDataType RQ6.9 Restriction to scalar types 6.2.5 DataTypes ... 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 RQ7.3 Usage of ResponseSPDU.Flags 7.2.1.6 ResponseSPDU: Flags RQ7.4 Zero out reserved flags
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.3 Usage of OPC UA safety Variables in Connections

safety application data. From a communication perspective, however, data exchange is always bidirectional ( ResponseSPDU containing the safety application data in one direction and RequestSPDU in the other direction), even