Search

9 result(s) for NonSafetyData

• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.3.4 ResponseSPDUDataType
  concrete DataType for the ResponseSPDU (which specifies the concrete DataTypes for SafetyData and NonSafetyData , respectively), proceed as follows: (1) Derive a concrete DataType from the abstract ResponseSPDUDataType . (2) In doing ... OutSafetyData with the concrete Structure DataType for the SafetyData (see 7.2.1.5 ). (b) Second, field NonSafetyData with the concrete Structure DataType for the NonSafetyData (or a placeholder DataType , see requirement RQ6.8
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.2 SAPI of SafetyProvider
  Safety Application, ActivateFSV can be set to "1" by the Safety Application. NonSafetyData Structure I Used to consistently transmit NonSafetyData values (e.g. diagnostic information) together with safe data
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.1.1 General
  octets), an additional 25 octet safety code ( STrailer ) and the NonSafetyData . See 7.2.1.5 to 7.2.1.11 for details. See 6.2.3.4 for details on the ResponseSPDUDataType definition. Figure 12 - ResponseSPDU NOTE
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.1.11 ResponseSPDU: NonSafetyData
  ResponseSPDU: NonSafetyData [RQ7.8] This structure shall be used to transmit NonSafetyData values (e.g. diagnostic information) together with SafetyData consistently. NonSafetyData is not CRC -protected and can stem from an unsafe ... possible problems with empty structures, the dummy structure NonSafetyDataPlaceholder shall be used when no NonSafetyData is used (see requirement RQ6.8
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.3 Duration of demand
  times the SafetyConsumerTimeout to ensure that the respective safety data reaches the SafetyConsumer . Since NonSafetyData is consistently transmitted with SafetyData , the same considerations apply for NonSafetyData . Figure 15 - Duration
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.4 SafetyProvider state diagram
  SPDU_ID_2_i, SPDU_ID_3_i, Flags, the SafetyData and the NonSafetyData , as well as the calculated CRC . See 7.2.3.1 Table 31 shows the states of a SafetyProvider
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.5 SafetyConsumer state diagram
  implemented in the safety application by querying SAPI.FSV_Activated. NOTE 2 The NonSafetyData is always updated if data is available. In case of a timeout, no data is available, which ... binary zero received", it can add a Boolean variable to the NonSafetyData . This value is set to "1" during normal operation
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.3.1 Build ResponseSPDU
  RequestSPDU.SafetyConsumerID into the ResponseSPDU . In addition, SPDU_ID , Flags , the SafetyData and the NonSafetyData shall be updated. Finally, ResponseSPDU.CRC shall be calculated and appended. Figure 20 gives an overview over
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  ResponseSPDU: MonitoringNumber RQ7.7 Usage of CRC signature 7.2.1.10 ResponseSPDU: CRC RQ7.8 Usage of NonSafetyData 7.2.1.11 ResponseSPDU: NonSafetyData RQ7.9 Indication of NonSafetyData 7.2.1.11 ResponseSPDU: NonSafetyData RQ7.10 Answer repeated RequestSPDUs in Client/Server