Search

13 result(s) for SAPI

• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.6 Objects SafetyProviderParameters and SafetyConsumerParameters
  system is still offline; the values which have been set during runtime via the SAPI parameters ( SafetyProviderID , SafetyBaseID ); the corresponding "[...]Configured" values if the active values have been ... zero via the SAPI parameters ( SafetyProviderID , SafetyBaseID ). The Property SafetyBaseIDConfigured is shared for all SafetyProviders with the same SafetyBaseIDConfigured value. If multiple instances of SafetyObjectsType are running on the same
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.3.2 OutFlagsType
  Operator acknowledgment at the provider, hereby forwarded to the SafetyConsumer , see OperatorAckProvider in the SAPI of the SafetyProvider , 6.3.3.2 . ActivateFSV 1 Activation of fail-safe values by the safety application ... SafetyProvider , hereby forwarded to the SafetyConsumer , see ActivateFSV in the SAPI of the SafetyProvider , 6.3.3.2 . TestModeActivated 2 Enabling and disabling of test mode in the SafetyProvider, hereby forwarded
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.1 Overview
  protocol. The state machines interact with the following interfaces: The Safety Application Program Interface ( SAPI ) is accessed by the safety application for exchanging SafetyData during runtime. The Safety Parameter Interface ... safe OPC UA stack and is used during runtime. The interfaces ( SAPI , SPI , DI and OPC UA PI ) described in 6.3 are abstract and informative. They represent logical data inputs
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.1 General
  General Figure 8 shows an overview of the SafetyProvider interfaces. The SAPI is specified in 6.3.3.2 , the SPI is specified in 6.3.3.3 . Figure 8 - SafetyProvider interfaces
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.2 SAPI of SafetyProvider
  SAPI of SafetyProvider [RQ6.12] The SAPI of the SafetyProvider represents the safety communication layer services of the SafetyProvider . Table 23 lists all inputs and outputs of the SAPI ... SafetyProvider . Each SafetyProvider shall implement the SAPI as shown in Table 23 , however, the details are vendor-specific. Table 23 - SAPI of the SafetyProvider SAPI Term Type I/O Definition SafetyData
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.3 SPI of SafetyProvider
  providing a non-zero value at the input SafetyProviderID of the SafetyProvider 's SAPI . This runtime value can be queried using the SafetyProviderIDActive parameter. See 6.2.2.6 for details on configured ... active values. NOTE If both the values provided at the SPI and the SAPI are 0x0, this means that the SafetyProvider is not properly configured. SafetyConsumers will never
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.4.1 General
  Figure 10 shows an overview of the SafetyConsumer interfaces. The Safety Application Program Interface ( SAPI ) is specified in 6.3.4.2 , the Safety Parameter Interface ( SPI ) is specified in 6.3.4.4 . Figure
• 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 ... RQ6.14] Each SafetyConsumer shall implement the SAPI as shown in Table 25 , however, the details are vendor-specific. Table 25 - SAPI of the SafetyConsumer SAPI Term Type I/O Definition SafetyData
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.4.4 SPI of the SafetyConsumer
  providing a non-zero value at the input SafetyProviderID of the SafetyConsumer 's SAPI . This runtime value can be queried using the SafetyProviderIDActive parameter. See 6.2.2.6 for details on configured ... providing a non-zero value at the input SafetyBaseID of the SafetyConsumer 's SAPI . This runtime value can be queried using the SafetyBaseIDActive parameter. See 6.2.2.6 for details on configured
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.3 Duration of demand
  SafetyProvider 's safety application shall provide the respective SafetyData at the SafetyProvider 's SAPI until at least one change of the MNR is detected. In case B, repeated identical RequestSPDUs ... SafetyProvider 's safety application shall provide the respective SafetyData at the SafetyProvider 's SAPI until at least two changes of the MNR have been detected. Figure 15 and Figure
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.4 SafetyProvider state diagram
  BaseID_i Guid Local variable containing the BaseID (taken either from the SPI or SAPI ). ProviderID_i UInt32 Local variable containing the ProviderID (taken either from the SPI or SAPI
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  Values for Boolean DataType 6.2.5 DataTypes and length of SafetyData RQ6.12 Implementation of SafetyProvider SAPI 6.3.3.2 SAPI of SafetyProvider RQ6.13a Implementation of SafetyProvider SPI 6.3.3.3 SPI of SafetyProvider RQ6.13b Parameters ... SafetyProvider SPI 6.3.3.3 SPI of SafetyProvider RQ6.14 Implementation of SafetyConsumer SAPI 6.3.4.2 SAPI of SafetyConsumer RQ6.15a Implementation of SafetyConsumer SPI 6.3.4.4 SPI of the SafetyConsumer RQ6.15b Parameters of SafetyConsumer
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  B.3.1 Explanation
  consumer side via the Boolean outputs OperatorAckRequested and OperatorAckProvider on the SafetyConsumer 's SAPI (see 6.3.4.2 ). Subclauses B.3.2 to B.3.5 show some examples on how to use these inputs