Search

9 result(s) for non-safety

• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  4.3 Features
  lower transport layers such as the OPC UA stack, underlying physical media, and non-safety network elements (e.g. routers and switches). "Dynamic" systems: Safety communication partners can change
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  5.2 Safety functional requirements
  following requirements apply for the development of this document: Safety communication suitable for safety integrity level up to SIL 4 (see the IEC 61508 series ... Combination of SIL 1 to 4 devices according to this document as well as non-safety devices on one communication network. Implementation of the safety transmission protocol is restricted
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  SafetyConsumers . SafetyACSet is intended for safety-related purposes only. It should not reference non-safety -related items. See Table 3 for the definition of the SafetyACSet. Table 3 - SafetyACSet definition
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.3 Method ReadSafetyData
  RequestSPDU ", see 7.2.1.3 and MonitoringNumber in Table 23 . InFlags "Octet with non-safety -related flags from SafetyConsumer ", see 6.2.3.1 . OutSafetyData " SafetyData ", see 7.2.1.5 . OutFlags
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.1 Overview
  setting safety parameters such as IDs or the timeout value in the SafetyConsumer . The non-safety related Diagnostic Interface ( DI ) can be accessed at runtime for troubleshooting the safety communication
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.4.2 SAPI of SafetyConsumer
  SAPI of SafetyConsumer The SAPI of the SafetyConsumer represents the safety communication layer services of the SafetyConsumer . Table 25 lists all inputs and outputs of the SAPI of the SafetyConsumer ... SPDU field SafetyData , or FSV . NonSafetyData Structure O This output delivers the non-safety process values (e.g. diagnostic information) which were sent together with safe data, see 7.2.1.11 Enable Boolean
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.4.1 General
  General Diagnostics according to this document may be implemented in a non-safety -related way. This allows for categorization and localization of safety communication errors. This document provides two types
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.1.1 General
  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. See 6.2.3.3 for details on the RequestSPDUDataType definition
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  requirements (informative) Table 41 gives an informative overview of all the requirements (safety and non-safety ) which are described in this document. A summary requirement description and the corresponding clause