Search
62 result(s) for Name
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelserialize DataTypes . Some of these DataEncodings are text based and make use of Name portion the DataType BrowseName . For this reason, the BrowseName for all DataTypes should be Strings that ... BrowseName that does not meet these requirements it will be transformed using the Name encoding rules defined in OPC 10000-6 into a String that meets the requirements. This will
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.51 StructureFieldStructure DataType . The StructureField is formally defined in Table 36 . Table 36 - StructureField Structure Name Type Description StructureField Structure Name String A name for the field that is unique within ... StructureDefinition . The name is restricted to 512 characters and shall not contain Unicode control characters.Unicode control characters are defined by Unicode C0 and Unicode C1 . Description LocalizedText A localized description
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.52 EnumFieldfield. The EnumField is formally defined in Table 37 . Table 37 - EnumField Structure Name Type Description EnumField Structure Name String A name for the field that is unique within ... serialize Enumeration DataTypes . Some of these DataEncodings are text based and make use of Name field. For this reason, the Name should be a String that starts with a letter
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.3 QueryFirstThis is done by setting the namespaceIndex of the targetName to zero and the name part of the targetName to the XML representation of the NodeId. The XML representation ... Table B.4 the response parameters for the QueryFirst Service . Table B.3 - QueryFirst Request Parameters Name Type Description Request requestHeader RequestHeader Common request parameters (see 7.32 for RequestHeader definition). View ViewDescription
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.3.13 NamespaceMetadataTypenamespace in the NamespaceArray as NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . The NamespaceUri Property contains the namespace represented by an instance
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.3.14 NamespacesTypenamespace in the NamespaceArray as NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . Clients should not assume that all namespaces provided by a Server
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsQualifiedName is found in Table 7 . Table 7 - Description for a QualifiedName <qualified-name> = <name> <qualified-name> =/ <short-index ... name> <qualified-name> =/ <namespace-uri> ";" <name> <name> = 1*(UNICODE) <short-index> = 1*DIGIT QualifiedNames
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsStructure FieldPath Encoding Rules Values of Structure DataTypes are sequences of name-value pairs. In many cases the value will be an array or another Structure . There are situations where ... path-element> *("." <path-element>) <path-element> = <name> / <index> <name> = 1*<char
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.14 QualifiedNameNamespaceIndex . If this occurs the decoder shall set the NamespaceIndex to 0 and the Name to the raw JSON string that includes the NamespaceUri that cannot be decoded
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.9 UAMethodUAMethodArgument [] A list of Descriptions for the Method Node Arguments . Each entry has a Name which uniquely identifies the Argument that the Descriptions apply to. There shall only ... entry per Name . Each entry also has a 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.12 DataTypeDefinitionfields if the programming environment supports the concept. Table F.12 - DataTypeDefinition Element Type Description Name QualifiedName A unique name for the data type. This name should be the same ... BrowseName for the containing DataType. SymbolicName String A symbolic name for the data type that can be used as a class/structure name in autogenerated code. It should only be specified
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.13 DataTypeFieldDataTypeField type are defined in Table F.14 . Table F.14 - DataTypeField Element Type Description Name String A name for the field that is unique within the DataTypeDefinition . SymbolicName String A symbolic ... name for the field that can be used in autogenerated code. It should only be specified if the Name cannot be used for this purpose. Only letters, digits
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.3.8.2 Namespace tablequalified area names. One solution to this problem would be to use a qualified name syntax which includes the complete URIs for all referenced table indices. This however would result ... calls GetQualifiedAreaName, the A&E COM UA Proxy first validates that the area name provided is a valid area at the current level. Then looping through the stack
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.7.5 Create Endpoint Workflowindex in the list of CertificateGroups currently in the configuration. The Name of the new record can be any value which is unique within the configuration and the CertificateGroups Object ... IssuedTokenType may also require a new AuthorizationServices record to be created as well. The Name of the new record can be any value which is unique within the configuration
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.8.3.3 CertificateGroupFolderTypeshall leave CertificateTypes list empty. Any additional CertificateGroups shall have a BrowseName where the Name is unique within the CertificateGroupFolder
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.8.3.4 CertificateGroupDataTypewhich allows multiple of CertificateGroups in a Server to be updated at once. The Name of the record is the name portion of the BrowseName of the associated CertificateGroup Object ... Object (see 7.10.20 ). This type is defined in Table 44 . Table 44 - CertificateGroupDataType Structure Name Type Description CertificateGroupDataType Structure Subtype of BaseConfigurationRecordDataType . Purpose 0:NodeId This value specifies the purpose
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.8.5.5 BaseConfigurationRecordDataTypecontained within a configuration. It is defined in Table 67 . Table 67 - BaseConfigurationRecordDataType Structure Name Type Description BaseConfigurationRecordDataType Structure Name 0:String The name of the record used when updating ... record corresponds to an Object in the AddressSpace then this shall be the Name portion of the BrowseName . If the record does not have a matching Object, then Name
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Serviceswhich allows multiple of AuthorizationServices in a Server to be updated at once. The Name of the record is the name portion of the BrowseName of the associated AuthorizationServiceConfiguration Object ... Server that is needed for Certificate Management Methods . Table 159 - AuthorizationServiceConfigurationDataType Structure Name Type Description AuthorizationServiceConfigurationDataType Structure ServiceUri 0:UriString A URI uniquely identifies the AuthorizationService . ServiceCertificates 0:ServiceCertificateDataType
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubQualifiedName in the KeyValuePair for properties defined in this document shall be 0. The Name of the QualifiedName is the property key from Table 4 . The DataType of the Value
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.2.3.10.2 RequestDataSetMetaDataActionResponse messages is defined by the DataSetMetaData parameter of the PublishedDataSetDataType . The fields Name and ConfigurationVersion of the DataSetMetaData and the RequestDataSetMetaData in one PublishedDataSet shall be identical
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.2.7.4 ConnectionPropertiesconsists of a QualifiedName and a value of BaseDataType . The mapping of the namespace, name, and value to concrete functionality may be defined by transport protocol mappings or vendor-specific ... QualifiedName in the KeyValuePair for properties defined in this document shall be 0. The Name of the QualifiedName is the property name from Table 47 . The DataType of the Value
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.2.12.2 SecurityGroupDataTypeSecurityGroupDataType is formally defined in Table 89 . Table 89 - SecurityGroupDataType structure Name Type Description SecurityGroupDataType Structure Name String Name of the SecurityGroup. SecurityGroupFolder String[] Optional path of the SecurityGroupFolders used ... SecurityGroupId String The identifier for the SecurityGroup . The SecurityGroupId shall match the Name field. RolePermissions RolePermissionType[] The permissions that apply to the security key access through GetSecurityKeys for the SecurityGroup
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.2.4.6.11 ActionMetaData announcement messageprobe if the configuration of the Action changed. Table 177 - ActionMetaData announcement message structure Name Type Description DataSetWriterId UInt16 DataSetWriterId of the Actions described with the MetaData . ActionTargets ActionTargetDataType ... ActionMethodDataType . Request DataSetMetaDataType The structure and content of the ActionRequest message. The name of the Action is defined by the Name field in the DataSetMetaDataType. Response DataSetMetaDataType The structure
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.2.5.5.7 ActionMetaDataJSON Data Encoding defined in OPC 10000-6 . Table 193 - JSON ActionMetaData definition Name Type Description MessageId String A globally unique identifier for the message. This value is mandatory. MessageType ... mandatory. It is unique within the scope of a Publisher . DataSetWriterName String The name of the DataSetWriter. This value is optional. The presence of the value depends on the setting
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.3.2.4.3 Connection PropertiesQualifiedName in the KeyValuePair shall be 0 for DTLS standard properties. The Name of the QualifiedName is constructed from a prefix and the DTLS property name with the following syntax ... QualifiedName in the KeyValuePair for properties defined in this document shall be 0. The Name of the QualifiedName is the property key from Table 202 . The DataType of the Value
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.3.4.4 Connection propertiesdefined in 7.3.4.7.1 . The default value is "opcua" For MQTT properties, the Name of the QualifiedName is constructed from a prefix "connection" followed by a hyphen ... MQTT property name with the following syntax. Name = connection-<MQTT property name> Table 202 defines the MQTT standard connection properties. Table 202 - OPC UA MQTT standard connection property
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.3.4.8 Message headerMQTT User Property is intended to provide a means of transferring application layer name-value tags whose meaning and interpretation are known only by the application programs responsible for sending ... version 5.0 message is constructed. Table 207 - OPC UA MQTT message properties MQTT property name MQTT property type MQTT property value UAMessageType User Property Valid values
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubPubSub functionality when invoking this Method on the Server . Signature AddSecurityGroupFolder ( [in] String Name, [out] NodeId SecurityGroupFolderNodeId ); Argument Description Name Name of the Object to create. SecurityGroupFolderNodeId NodeId ... SecurityGroupFolderType Object . Method Result Codes ResultCode Description Bad_BrowseNameDuplicated A folder Object with the name already exists. Bad_InvalidArgument The Server is not able to apply the Name . The Name
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubPubSub functionality when invoking this Method on the Server . Signature AddPushTargetFolder ( [in] String Name, [out] NodeId PushTargetFolderNodeId ); Argument Description Name Name of the Object to create. PushTargetFolderNodeId NodeId ... PubSubKeyPushTargetFolderType Object . Method Result Codes ResultCode Description Bad_BrowseNameDuplicated A folder Object with the name already exists. Bad_InvalidArgument The Server is not able to apply the Name . The Name
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.3.2 PublishSubscribeTypeconsists of a QualifiedName and a value of BaseDataType . The mapping of the namespace, name, and value to concrete functionality may be defined by transport protocol mappings, future versions ... Variables where the Value of a Variable represents a DataSetClass . For each Variable , the Name field of the BrowseName equals the Name in the DataSetMetaData . The Object is formally defined
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.2.1 PublishedDataSetTypechanged based on DataSet configuration change. The DataSetMetaDataType is defined in 6.2.3.2.3 . The Name field in the DataSetMetaDataType shall match the name of the PublishedDataSetType Object if the DataSetMetaData
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.2.2 ExtensionFieldsTypequalifying namespace is the OPC UA namespace. Table 249 - Well-Known Extension Field Names Name Type Description PublisherId BaseDataType The PublisherId from the Connection Object . DataSetName String The Name from ... DataSetWriterTransport Object . MessageSequenceNumber UInt16 The sequence number from the DataSetMessage . If a well-known name is used, the value placed in the message body is dynamically generated from the current
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.2.3 AddExtensionField MethodSignature AddExtensionField ( [in] QualifiedName FieldName, [in] BaseDataType FieldValue, [out] NodeId FieldId ); Argument Description FieldName Name of the field to add. FieldValue The value of the field to add. FieldId ... added field Property . Method Result Codes ResultCode Description Bad_NodeIdExists A field with the name already exists. Bad_InvalidArgument The Server is not able to apply the Name . The Name
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.5.2 AddPublishedDataItems MethodPubSub functionality when invoking this Method on the Server . Signature AddPublishedDataItems ( [in] String Name, [in] String[] FieldNameAliases, [in] DataSetFieldFlags[] FieldFlags, [in] PublishedVariableDataType[] VariablesToAdd, [out] NodeId DataSetNodeId, [out] ConfigurationVersionDataType ConfigurationVersion ... StatusCode[] AddResults ); Argument Description Name Name of the Object to create. FieldNameAliases The names assigned to the selected Variables for the fields in the DataSetMetaData and in the DataSetMessages
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.5.3 AddPublishedEvents MethodPubSub functionality when invoking this Method on the Server . Signature AddPublishedEvents ( [in] String Name, [in] NodeId EventNotifier, [in] String[] FieldNameAliases, [in] DataSetFieldFlags[] FieldFlags, [in] SimpleAttributeOperand[] SelectedFields, [in] ContentFilter Filter ... ConfigurationVersionDataType ConfigurationVersion, [out] NodeId DataSetNodeId ); Argument Description Name Name of the DataSet Object to create. EventNotifier The NodeId of the Object in the event notifier tree
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.5.5 AddPublishedEventsTemplate MethodPubSub functionality when invoking this Method on the Server . Signature AddPublishedEventsTemplate ( [in] String Name, [in] DataSetMetaDataType DataSetMetaData, [in] NodeId EventNotifier, [in] SimpleAttributeOperand[] SelectedFields, [in] ContentFilter Filter, [out] NodeId DataSetNodeId ); Argument ... Description Name Name of the Object to create. DataSetMetaData The DataSetMetaData predefined by the caller. The initial setting shall not be changed by the Publisher . If the dataSetClassId
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.5.7 AddDataSetFolder MethodPubSub functionality when invoking this Method on the Server . Signature AddDataSetFolder ( [in] String Name, [out] NodeId DataSetFolderNodeId ); Argument Description Name Name of the Object to create. DataSetFolderNodeId NodeId ... DataSetFolderType Object . Method Result Codes ResultCode Description Bad_BrowseNameDuplicated A folder Object with the name already exists. Bad_InvalidArgument The Server is not able to apply the Name . The Name
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.9.4.4 AddDataSetFolder MethodPubSub functionality when invoking this Method on the Server . Signature AddDataSetFolder ( [in] String Name, [out] NodeId DataSetFolderNodeId ); Argument Description Name Name of the Object to create. DataSetFolderNodeId NodeId ... SubscribedDataSetFolderType Object . Method Result Codes ResultCode Description Bad_BrowseNameDuplicated A folder Object with the name already exists. Bad_InvalidArgument The Server is not able to apply the Name . The Name
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubB.3.4 Connection propertiesNamespaceIndex of the QualifiedName in the KeyValuePair is 0 for AMQP standard properties. The Name of the QualifiedName is constructed from a prefix and the AMQP property name with ... following syntax. Name = <target prefix>-<AMQP property name> The target prefix can have the following values: Connection; session; link. The Value of the KeyValuePair is converted
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubB.3.7 Message headerpopulated when an AMQP message is constructed. Table B.1 - AMQP standard header fields Field Name Source message-id A globally unique value per message. Subject Valid values are ua-data ... QualifiedName in the KeyValuePair is 0 for AMQP standard message properties. The Name of the QualifiedName is constructed from a message prefix and the AMQP property name with the following
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.3 StateVariableTypeVariables that store the current state of a StateMachine as a human readable name. The StateVariableType is formally defined in Table 2 . Table 2 - StateVariableType definition Attribute Value BrowseName StateVariableType ... HasSubtype VariableType FiniteStateVariableType Defined in 4.4.7 HasProperty Variable Id BaseDataType PropertyType Mandatory HasProperty Variable Name QualifiedName PropertyType Optional HasProperty Variable Number UInt32 PropertyType Optional HasProperty Variable EffectiveDisplayName LocalizedText PropertyType Optional
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.5 TransitionVariableTypeVariables that store a Transition that occurred within a StateMachine as a human readable name. The SourceTimestamp for the value specifies when the Transition occurred. This value may also ... HasSubtype VariableType FiniteTransitionVariableType Defined in 4.4.8 HasProperty Variable Id BaseDataType PropertyType Mandatory HasProperty Variable Name QualifiedName PropertyType Optional HasProperty Variable Number UInt32 PropertyType Optional HasProperty Variable TransitionTime UtcTime PropertyType Optional
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machinesused to store a Transition that occurred within a FiniteStateMachine as a human readable name. The FiniteTransitionVariableType is formally defined in Table 8 . Table 8 - FiniteTransitionVariableType definition Attribute Value BrowseName ... where the Transition is defined the first time in the type hierarchy. The Name Property is inherited from the TransitionVariableType. Its Value shall be the BrowseName
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesC.1 OverviewAliasNames list on the GDS. Pull all AliasNameCategory instances, merge any that have identical Name part of the BrowseNames . The GDS will provide the ExpandedNodeId of all of the referenced
-
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject ModelStructure The NameValuePair structure is formally defined in Table 15 . This structure has a Name field that is a name that is associated with the value that is reported ... that are to be included in the LogRecord as AdditionalData. Table 15 - NameValuePair structure Name Type Description NameValuePair Structure Subtype of Structure defined in OPC 10000-5 Name String
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.5 Command CreateConnectionEndpointCmdshall be of the subtype specified in ConnectionEndpointTypeId. The BrowseName shall be set to Name, and all Variables shall be set according to Parameter . The appropriate entries in InputVariables ... TRUE, a preconfigured ConnectionEndpoint (see 5.5.5 ) shall exist with a BrowseName that matches Name in the ConnectionEndpoints Folder of the FunctionalEntity identified by FunctionalEntityNode. Its ConnectionEndpointTypeId , InputVariables and OutputVariables shall
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasProperty Variable 3:Id 0:UInt16 0:PropertyType O 0:HasProperty Variable 3:Name 0:String 0:PropertyType O 0:HasSubtype ObjectType 3:SlotType Defined in 6.3.5 0:HasSubtype ObjectType ... Asset . The use of this ID can be further explained or defined in subtypes. Name provides the physical label that is associated with this connector. The use of Name
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.6 SocketType definitionHasComponent Variable 3:Kind 0:UInt16 0:MultiStateValueDiscreteType O 0:HasProperty Variable 3:Name 0:String 0:PropertyType M ConformanceUnits UAFX AssetConnector Socket Base Name is from AssetConnectorType
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.7 ClampType definitionClass BrowseName DataType TypeDefinition Other Subtype of the 3:AssetConnectorType 0:HasProperty Variable 3:Name 0:String 0:PropertyType M 0:HasComponent Variable 3:Kind 0:UInt16 0:MultiStateValueDiscreteType ... ConformanceUnits UAFX AssetConnector Clamp Base UAFX AssetConnector ClampBlock Base Name is from AssetConnectorType and is mandatory in ClampType . The optional Kind is a MultiStateValueDiscreteType that describes the type of clamp
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelClass BrowseName DataType TypeDefinition Other Subtype of the 3:AssetConnectorType 0:HasProperty Variable 3:Name 0:String 0:PropertyType M 0:HasProperty Variable 3:BlockSize 0:UInt16 0:PropertyType ... HasComponent Object 3:<Clamp> 3:ClampType OP ConformanceUnits UAFX AssetConnector ClampBlock Base Name is from AssetConnectorType and is mandatory in ClampBlockType . The optional BlockSize is the maximum number
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelcontroller algorithm. The optional ApplicationIdentifier - provides application information consisting of two properties: a localised Name that is intended to be human-readable and a unique identifier that is intended ... definition of the ApplicationIdentifierDataType , see 10.3 . The ApplicationIdentifier shall be used as follows: Name provides the name of the application in which this FunctionalEntity is used. The name is given
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.4.3 Verify methodverified that NodeId exists. If the NodeId references a FunctionalEntity ApplicationIdentifier , then its Name sub-element shall always be ignored; only its UniqueIdentifier shall be used. A Client may pass
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelelement in this array for each < Connection > instance in the ConnectionConfigurationSet . The Name field of the ConnectionDiagnosticsType provides a linkage between an array element and a specific
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSubtype of the 0:BaseObjectType defined in OPC 10000-5 0:HasComponent Variable 4:Name 0:String 0:SelectionListType M 0:HasComponent Variable 4:ConnectionEndpointTypeId 0:PortableNodeId 0:BaseDataVariableType ... HasComponent Variable 4:PreconfiguredSubscribedDataSet 0:String 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Base Name specifies the BrowseName of the ConnectionEndpoint to create. This name shall be unique within the FunctionalEntity
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasProperty Variable 4:ConnectionConfigurationSetNode 0:NodeId 0:PropertyType M 0:HasProperty Variable 4:Name 0:String 0:PropertyType M 0:HasProperty Variable 4:Action 4:FxProcessEnum 0:PropertyType ... NodeId of the ConnectionManager that is executing the state machine. ConnectionConfigurationSetNode and Name identify the ConnectionConfigurationSet , which was processed. Action identifies the action that was requested to process the ConnectionConfigurationSet
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionConfigurationSet . The ConnectionDiagnosticsDataType is formally defined in Table 162 . Table 162 - ConnectionDiagnosticsDataType structure Name Type Description ConnectionDiagnosticsDataType Structure Subtype of Structure defined in OPC 10000-5 Name 0:QualifiedName BrowseName ... LastActivityMask The last activity taken by the ConnectionManager on the Connection indicated by Name , including results of the activity. A zero indicates no activity has been taken on this Connection
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelD.3.6.1 Overviewwill indicate if the poor man's reference is using a NodeId or a Name
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionEndpointConfigurationConfDataType is formally defined in Table F.5 . Table F.5 - ConnectionEndpointConfigurationConfDataType structure Name Type Description Optional ConnectionEndpointConfigurationConfDataType Structure Subtype of Structure defined in OPC 10000-5 FunctionalEntityNode 4:NodeIdentifier FunctionalEntityNode specifies ... True FunctionalEntityNodeModify 0:Boolean Flag indicating if the FunctionalEntityNode options can be modified. True Name 0:String BrowseName of the ConnectionEndpoint to create in the AutomationComponent . False NameSelection 0:String
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelCommunicationFlowConfigurationConfDataType is formally defined in Table F.7 . Table F.7 - CommunicationFlowConfigurationConfDataType structure Name Type Description Optional CommunicationFlowConfigurationConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName ... this document shall be the namespace that has index 4 in this document. The Name of the QualifiedName is the property key from Table F.8 . The DataType of the Value
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.12.1 Add Methodused to add a new item to the folder. The parameters Subclass and Name are exposed at the attached SoftwareUpdate AddIn as SoftwareSubclass and SoftwareName Properties . The Name shall ... unique within the SoftwareFolderType . Signature Add( [in] 0:String Subclass, [in] 0:String Name); Table 108 - Add Method Arguments Argument Description Subclass Subclass of the new item. Name Name
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.3 Package metadataSoftware Package is uniquely defined with the ManufacturerUri , PackageType , TargetProductCodes , PackageRevision and Name . The PackageMetadata structure and all contained types are encoded using the JSON VerboseEncoding . Note: The following tables ... show up in the AddressSpace of an OPC UA Server . Table 120 - PackageMetadata structure Name Type Description Optional PackageMetadata 0:Structure Name 0:String Names the package (the package file
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.5 Solution packagesstructures for the Assignment are defined in Table 136 . Table 136 - Assignment structure Name Type Description Optional Assignment 0:Structure Subpackage 0:String Name of the subfolder within the SUBPACKAGES ... Other Subtype of 0:Structure defined in OPC 10000-3 Table 138 - PackageTarget structure Name Type Description Optional PackageTarget 0:Structure TargetType 0:NodeId Install to all instances of that