Search

13 result(s) for Parameters

• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.3 TopologyElementType
  essential aspect introduced by the TopologyElementType . FunctionalGroups are used to structure Nodes like Properties , Parameters and Methods according to their application such as configuration, diagnostics, asset management, condition monitoring ... MethodSet are defined as standard containers for systems that have a flat list of Parameters or Methods with unique names. In such cases, the Parameters are components
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.1 Model
  This subtype of the OPC UA FolderType is used to structure Nodes like Properties , Parameters and Methods according to their application (e.g. maintenance, diagnostics, condition monitoring). Organizes References should
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.2 Well-Known FunctionalGroup BrowseNames
  Namespace of this specification. Table 15 - Well-Known 1:FunctionalGroupType BrowseNames BrowseName Purpose Configuration Parameters representing the configuration items of the TopologyElement . If the CurrentWrite ... AccessLevel Attribute they can be modified by Clients . Tuning Parameters and Methods to optimize the behavior of the TopologyElement . Maintenance Parameters and Methods useful for maintenance operations. Diagnostics Parameters
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.11 BlockType
  Units DI Blocks BlockType is a subtype of TopologyElementType and inherits the elements for Parameters , Methods and FunctionalGroups . The BlockType is abstract. There will be no instances of a BlockType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  5.4 ConnectionPoint
  other components that they inherit from the TopologyElementType . The NetworkAddress FunctionalGroup includes all Parameters to specify the protocol-specific address information of the connected Device . These Parameters can be components
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.3.1 General
  offline information. Its HasTypeDefinition Reference points to the concrete configured or identified ObjectType . All Parameters of this instance represent offline data points and reading or writing them will typically result ... online Parameter will return a proper status code (Bad_NotConnected). The transfer of information ( Parameters ) between offline nodes and the physical device in correct order is supported through TransferToDevice , TransferFromDevice
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.1 Definition
  based on the AddIn model specified in OPC 10000-3 . The transfer of information ( Parameters ) between offline nodes and the physical device is supported through OPC UA Methods . These Methods ... functionality. The transfer is usually terminated if an error occurs for any of the Parameters . No automatic retry will be conducted by the Server . However, whenever possible after a failure
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.4 TransferToDevice Method
  TransferToDevice Method TransferToDevice initiates the transfer of offline configured data ( Parameters ) to the physical device. This Method has no input arguments. Which Parameters are transferred is based on Server -internal ... Server will reset any cached value for Nodes in the online instance representing Parameters affected by the transfer. That way the cache will be re-populated from the Device next
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.5 TransferFromDevice Method
  TransferFromDevice Method TransferFromDevice initiates the transfer of values from the physical device to corresponding Parameters in the offline representation of the Device . This Method has no input arguments. Which Parameters
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.6 FetchTransferResultData Method
  transfer and also if the previous call of FetchTransferResultData failed. MaxParameterResultsToReturn The number of Parameters in TransferResult.ParameterDefs that the Client wants the Server to return in the response. The Server ... Client is imposing no limitation. OmitGoodResults If TRUE, the Server will omit data for Parameters which have been correctly transferred. Note that this causes all good results to be released
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.2 Identification Functional Group
  TopologyElement , like Manufacturer, SerialNumber, will usually be sufficient as identification. If other Parameters or even Methods are required, all required elements shall be organized in a FunctionalGroup called Identification . Figure
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.3.3 Update sequence using Direct-Loading
  Figure B.6 . If the Server does not implement the properties PrepareForUpdate , PowerCycle or Parameters of the SoftwareUpdateType , the associated options are not supported by the component and Client - Server interaction
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.3.4 Update sequence using Cached-Loading
  Figure B.7 . If the Server does not implement the properties PrepareForUpdate , PowerCycle or Parameters of the SoftwareUpdateType , the associated options are not supported by the component and Client - Server interaction