Search
14 result(s) for Parameter
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.1.9 ParameterParameter variable of the Device that can be used for configuration, monitoring or control purposes Note 1 to entry: In the information model it is synonymous
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Accessflag, returnBounds, indicating that BoundingValues are requested. For a complete description of the Extensible Parameter HistoryReadDetails that include StartTime , EndTime and NumValuesPerNode, see 6.5 . The concept of Bounding Values
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access6.5.1 OverviewHistoryRead Service defined in OPC 10000-4 can perform several different functions. The HistoryReadDetails parameter is an Extensible Parameter that specifies which function to perform and the details that ... specific to that function. See OPC 10000-4 for the definition of Extensible Parameter . Table 27 lists the symbolic names of the valid Extensible Parameter structures. Some structures will perform
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access6.9.1 OverviewHistoryUpdate Service defined in OPC 10000-4 can perform several different functions. The historyUpdateDetails parameter is an Extensible Parameter that specifies which function to perform and the details that ... specific to that function. See OPC 10000-4 for the definition of Extensible Parameter . Table 61 lists the symbolic names of the valid Extensible Parameter structures. Some structures will perform
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.2 EstablishConnections signatureCreateConnectionEndpointCmd is set, at least one of the ConnectionEndpointConfigurations elements shall expose ConnectionEndpointDefinitionDataType with Parameter (see 10.16 ) as ConnectionEndpoint . If CommandMask CreateConnectionEndpointCmd is not set, all ConnectionEndpointConfigurations elements shall expose ... ConnectionEndpoint was not found. This error code may also be used for any other parameter error in an EstablishConnections Call. Bad_BrowseNameDuplicated The name for the ConnectionEndpoint was not unique
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.5 Command CreateConnectionEndpointCmdupdate a preconfigured ConnectionEndpoint for each element in ConnectionEndpointConfigurations (see 10.14 ) with the Parameter defined in ConnectionEndpoint (see 10.16 ). The EstablishConnections implementation shall set ConnectionEndpointConfigurationResults ConnectionEndpointResult on errors as specified ... BrowseName shall be set to Name, and all Variables shall be set according to Parameter . The appropriate entries in InputVariables and OutputVariables shall be populated. If IsPreconfigured
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.3.2 Establishing Connectionsargument ConnectionEndpointConfigurations ConnectionEndpoint that is passed for this command is constructed out of the Parameter Object in the ConnectionEndpoint Object in Endpoint1 or Endpoint2 Object in the instances of ConnectionConfigurationType
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelType Description Allow Subtypes ConnectionEndpointDefinitionDataType Union Subtype of Union defined in OPC 10000-5 Parameter 2:ConnectionEndpointParameterDataType Parameter holds the parameters to be used for the creation of the ConnectionEndpoint
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.1.1 BlockBlock functional Parameter grouping entity Note 1 to entry: It could map to a function block (see IEC 62769 ) or to the resource parameters of the Device itself
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.4.1 Modelcomponents of the TopologyElement either directly or via a subcomponent. The same Property , Parameter or Method can be useful in different application scenarios and therefore referenced from more than
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices6.3.1 GeneralReference . It is always of the same ObjectType as the offline instance. The online Parameter Nodes reflect values in a physical element (typically a Device ), i.e., reading or writing ... Parameter value will then result in a communication request to this element. When elements are not connected, reading or writing to the online Parameter will return a proper status code
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesreturned if the transfer was performed. Status information is returned for each transferred Parameter . Table 59 - FetchTransferResultData Method AddressSpace definition Attribute Value BrowseName 1:FetchTransferResultData References NodeClass BrowseName DataType TypeDefinition ... contain Device - or Protocol -specific error information. diagnostics 0:DiagnosticInfo Diagnostic information. This parameter is empty if diagnostics information was not requested in the request header or if no diagnostic
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.1.7 Parameterscontext of software update. The GenerateFileForRead and GenerateFileForWrite Methods accept an unspecified generateOptions Parameter . This argument is not used, and Clients shall always pass null. Future versions of this specification
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.3.3.1 Generalformat. In the TemporaryFileTransferType type the GenerateFileForRead and GenerateFileForWrite Methods take an unspecified generateOptions Parameter . For the FileTransfer Object an Enumeration of type SoftwareVersionFileType is used for this Parameter