Search

10 result(s) for MonitoringNumber

• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  3.1.2.5 MonitoringNumber
  MonitoringNumber means used to ensure the correct order among transmitted safety PDUs and to monitor the communication delay Note 1 to entry:  Instance of sequence number as described
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  4.1 General
  requirements of the IEC 61508 series and IEC 61784-3. This document uses a MonitoringNumber , a timeout, a set of IDs and a cyclic redundancy check ( CRC )code
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  5.3 Safety measures
  RQ5.2] For an implementation of this document, the following safety measures shall be implemented: MonitoringNumber ; timeout with receipt in the SafetyConsumer ; set of IDs for the SafetyProvider ; Data Integrity check ... Table 2 - Deployed safety measures to detect communication errors Communication error Safety measures MonitoringNumber a Timeout with receipt b Set of IDs for SafetyProvider c Data integrity check d Corruption
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.3 Method ReadSafetyData
  Description InSafetyConsumerID "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 ... Safety Consumer 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
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.2 SAPI of SafetyProvider
  implementation of this document, the safety application is not required to check this SafetyConsumerID . MonitoringNumber UInt32 O This output yields the MonitoringNumber ( MNR ). It is updated whenever a new request ... implementation of this document, the safety application is not required to check this MonitoringNumber . SafetyProviderID UInt32 I For dynamic systems, this input can be set to a non-zero value
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.4.2 Diagnostics messages of the SafetyConsumer
  0x16 B Yes MNRerrIgn The SafetyConsumer has discarded a message due to an incorrect MonitoringNumber . 0x07 A Yes MNRerrOA The SafetyConsumer has switched to fail-safe substitute values
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.1.1 General
  structure of a RequestSPDU which originates at the SafetyConsumer and contains a SafetyConsumerID , a MonitoringNumber ( MNR ), and one octet of ( non-safety -related) Flags . See 7.2.1.2 to 7.2.1.4 for details
• 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 ... which are continuously repeated by an erroneous network element which stores data. A different MonitoringNumber is used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.5 SafetyConsumer state diagram
  input SAPI.OperatorAckConsumer has been 'false' since FaultReqOA_i was set MNR_i UInt32 Local MonitoringNumber ( MNR ) prevMNR_i UInt32 Local memory for previous MNR ConsumerID_i UInt32 Local memory
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  flags 7.2.1.6 ResponseSPDU: Flags RQ7.5 Copy SafetyConsumerID into ResponseSPDU 7.2.1.8 ResponseSPDU: SafetyConsumerID RQ7.6 Copy MonitoringNumber into ResponseSPDU 7.2.1.9 ResponseSPDU: MonitoringNumber RQ7.7 Usage of CRC signature 7.2.1.10 ResponseSPDU: CRC RQ7.8 Usage