Search

Scope: Core (OPC-10000-*) All specs

31 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
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

4.2.3.4 Introduction to OPC UA Devices

Device Object type hierarchy. Objects of the type FunctionalGroupType are used to group the Parameters and Methods of the Device into logical groups. The FunctionalGroupType and the grouping concept
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

7.1.1 Overview

user specific configurations. A concrete Ctrl Configuration type or instance may have ParameterSet , Parameters and FunctionalGroup s as defined for the TopologyElementType in OPC 10000-100 . The MethodSet Object
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

7.2.1 Overview

user specific resources. A concrete Ctrl Resource type or instance may have ParameterSet , Parameters and FunctionalGroup s as defined for the TopologyElementType in OPC 10000-100 . The MethodSet Object
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.3.4 PackMLAdminObjectType

Parameter - The parameter tags associated with the local interface are typically used as parameters that are displayed or used on the unit locally, for example from an HMI. These parameters ... used to display any quality, alarm, or machine downtime parameter. The Parameters are typically limited to parameters related the unit. The length of the array is the maximum number
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.7.2 SetUnitMode Method

This Method allows an OPC UA Client to change the mode of the unit. Parameters are defined in Table 23 Signature SetUnitMode( [in] Int32 RequestedMode ); Table 23 - SetUnitMode Method Parameters
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.7.3 SetMachSpeed Method

allows an OPC UA Client to change the speed of the machine or unit. Parameters are defined in Table 26 Signature SetMachSpeed( [in] Float RequestedMachineSpeed ); Table 26 - SetMachSpeed Method Parameters
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.7.4 SetProduct Method

Method allows an OPC UA Client to change product associated with this PackML system. Parameters are defined in Table 29 . Signature SetProduct( [in] PackMLProductDataType[] Product ); Table 29 - SetProduct Method Parameters
OPC-30100 – OPC UA for SERCOS Devices

4.2 OPC UA

expose individual elements of arrays and structures. This specification uses DataVariables to represent the Parameters of both Blocks and Devices
OPC-30100 – OPC UA for SERCOS Devices

5.1 General

model. TopologyElementType is the base ObjectType for elements in a device topology. It introduces Parameters (ParameterSet) and Methods (not shown). This specification also defines a functional grouping concept to provide
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

6.2.1 General

Object MethodSet ). As defined by the concepts of OPC 10000-100 the Parameters ( Variables ) of the ParameterSet and Methods of the MethodSet are organised in FunctionalGroups where they are referenced ... Organize-References . This concept allows splitting the Parameters into different categories, and at the same time, all Parameters are accessible under ParameterSet . Figure 16 - PowerlinkConnectionPointType
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.1 General Station Description (GSD)

Devices which are of interest for engineering tools, such as IO Data , IO Channels , Parameters and Alarms . The format defined for the GSD is the GSDML
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.9 Base Mode Parameter (BMP) Access

Base Mode Parameter (BMP) Access Access to Parameters via the "Base Mode" as described in [ PDP ], sec. 6.2.3. Requests and replies are transmitted
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.2 Application Object

Data mapping derived from the GSDML "(Virtual)SubmoduleItem/IOData" element. The "Parameters" sub-aspect contains the generic Parameter record mapping from the GSDML "(Virtual)SubmoduleItem/RecordDataList ... defined in the GSDML file. There may also exist a mapping of Parameters obtained using BMP Access . The "Alarms" sub-aspect contains the generic Alarm data mapping from
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.6 Parameters

Parameters Figure 14 shows the "Parameters" sub-aspect in the Functional Aspect of the Information Model. Figure 14 - Parameters Organization The GsdGenParameterVariableType Variable represents one Parameter as part ... values in the Parameter records referenced by the associated Submodule . The modelling of the Parameters as Variables allows Clients to obtain the Parameters without dissecting the Parameter record structure. Figure
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

7.1 GsdGenSubmoduleApplicationType

root container for the Objects and Variables representing a Submodule's IO Data, Parameters , Data Objects and Alarms . Moreover, information regarding the communication status of the Submodule is provided. Table
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

7.1.1 SetApplicationTag Method

details. The Configuration Object is an optional folder containing GsdGenParameterVariableType Variables representing the configuration Parameters of the Submodule . See section 6.6 for details. The <ValueVariable> Variable represents
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management

8.3.7.1 StartSingleJob method

MeasIdDataType measId,[in] PartIdDataType partId,[in] RecipeIdExternalDataType recipeId[in] ProductIdDataType productId[in] BaseDataType[] parameters[out] JobIdDataType jobId[out] Int32 error); Table 100 - StartSingleJob Method Arguments Argument Description measId Identifies ... which a recipe has been prepared which is to be used by this job. parameters List of parameters for this particular execution of the recipe; number and type
OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base

7.3.2 IJoiningSystemAssetType InterfaceType Definition

MachineryItemIdentificationType which can be specialized using MachineIdentificationType or MachineryComponentIdentificationType. The 2:Identification Object includes parameters from MachineryItemIdentificationType (which can be specialized to MachineIdentificationType or MachineryComponentIdentificationType ) defined ... MachineryLifetimeCounterType O 0:HasComponent Object 2:Maintenance 2:FunctionalGroupType O 0:HasComponent Object Parameters 0:FolderType O 0:HasComponent Object 4:MachineryBuildingBlocks 0:FolderType O 0:HasAddIn Object 4:Monitoring