Search
18 result(s) for Argument
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model12.2.12.1 ArgumentArgument The representation in the AddressSpace of the Argument DataType is defined in Table 197 . Table 197 - Argument definition Attributes Value BrowseName Argument IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition ... Subtype of the Structure DataType defined in Table 196 . Conformance Units Base Info Method Argument DataType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.7.1 Method NodeClasswhenever the Method is called. HasArgumentDescription 0..* The HasArgumentDescription References are used to specify argument metadata. If the SourceNode of this Reference is defined on an InstanceDeclaration the TargetNode shall ... determine when the structure of a Node has changed. InputArguments O Argument[] The InputArguments Property is used to specify the arguments that shall be used by a client when calling
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelClient is able to interpret the data. An example of a Structured DataType is Argument (see 8.6 ). Enumeration DataTypes are DataTypes that represent discrete sets of named values. Enumerations
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.32 StructureStructure This abstract DataType is the base DataType for all Structured DataTypes like Argument defined in 8.6 . While abstract Structures may be defined with no fields a non-abstract Structure
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.12.2.2 ParametersHasComponent from the Node defined by objectId . inputArguments [] BaseDataType List of input argument values. An empty list indicates that there are no input arguments. The size and order of this ... Property of the Method . The name, a description and the data type of each argument are defined by the Argument structure in each element of the method's InputArguments Property
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.9 UAMethodMethod Node Arguments . Each entry has a Name which uniquely identifies the Argument that the Descriptions apply to. There shall only be one entry per Name . Each entry also ... list of Descriptions for the Argument in different locales. There shall be only one entry per locale per Argument
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.10 TranslationTypeTable F.10 . If multiple Arguments existed there would be a Translation element for each Argument . The type can have two forms depending on whether the Value is a LocalizedText ... Server/ApplicationName". The following example illustrates how translations for the Description field in the Argument Structure are represented in XML: <Value> <ListOfExtensionObject xmlns="http://opcfoundation.org/UA/2008/02/Types.xsd">
-
OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer4.4.3 GenerateFileForReadSignature GenerateFileForRead( [in] BaseDataType generateOptions [out] NodeId fileNodeId [out] UInt32 fileHandle [out] NodeId completionStateMachine ); Argument Description generateOptions The optional parameter can be used to specify server specific file generation options ... allow such options, the Server shall specify a concrete DataType in the Argument Structure for this argument in the instance of the Method . If the DataType is BaseDataType , the Client
-
OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer4.4.4 GenerateFileForWriteaccess the Object . Signature GenerateFileForWrite( [in] BaseDataType generateOptions [out] NodeId fileNodeId [out] UInt32 fileHandle ); Argument Description generateOptions The optional parameter can be used to specify server specific file generation options ... allow such options, the Server shall specify a concrete DataType in the Argument Structure for this argument in the instance of the Method . If the DataType is BaseDataType , the Client
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.3 Command VerifyFunctionalEntityCmdshall be called on the FunctionalEntity identified by FunctionalEntityNode , supplying the ExpectedVerificationVariables as Method Argument . The StatusCode returned by the Verify Method shall be stored in VerificationStatus, and the values
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.4.2 PubSubeach requested TransportProfileUri for the PublisherId , the reserved WriterGroupIds , and DataSetWriterIds in the output Argument ReserveCommunicationIdsResults . Additionally, if the RequestTransportSpecificInfo is set to TRUE in the request for the given
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.6 Command EstablishControlCmdpass the ApplicationUri of the Session associated with the EstablishConnections Method Call as LockContext Argument to EstablishControl (see 6.5.3 ). The EstablishConnections implementation shall stop processing this command on the first
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.5.3 EstablishControl methodConnectionAdmin as defined in Clause 5.9 . EstablishControl shall set Lock LockingClient to the LockContext Argument . The signature of this Method is specified below; the arguments are defined in Table ... EstablishControl ( [in] 0:String LockContext, [out] 0:Int32 LockStatus ); Table 64 - EstablishControl Method Arguments Argument Description LockContext A string used to provide context information about the lock owner
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.5.5 ReassignControl methodentity as defined by the LockContext . It shall set Lock LockingClient to the LockContext Argument . It is recommended that this Method be restricted to Client connections that have the well ... ReassignControl ( [in] 0:String LockContext, [out] 0:Int32 LockStatus ); Table 69 - ReassignControl Method Arguments Argument Description LockContext A string used to provide context information about the lock owner
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics7.1.7.3 StartProgramstart running a program based on a ProgramTemplate of a FunctionalUnit. The Properties Argument can be used to provide an optional list of property values when initiating a program ... String SupervisoryTaskId [in] SampleInfoType[] Samples [out] 0:String DeviceProgramRunId) Table 44 - StartProgram Method Arguments Argument Description ProgramTemplateId The unique identifier of the program template used for the program
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basicsspecific workflow consisting of one or multiple steps. It is provided as an Argument of the StartProgram () Method which initiates the program run. SupervisoryTaskId is the unique identifier ... supervisory system to which the result belongs. It is provided as an Argument of the StartProgram () Method which initiates the program run. ProgramTemplate is an immutable copy of the Program
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: BasicsSupportedPropertyType Definition The SupportedPropertyType provides argument names and links to variables within the information model, typically target values or parameters of Functions. This makes it possible to specify a list ... SupportedPropertyType is used in the SupportedPropertiesSet of the FunctionalUnit . The name of each Argument object is used as a key in the KeyValueType list input Argument of the Start()/StartFunctions
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basicsprovides a set of properties which are supported as members of a properties list Argument for Method calls, such as FunctionalUnit.StartFunctions() or ActiveProgram.Start() . It is formally defined in Table