Search
37 result(s) for AliasName
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names3.1.1 AliasNameAliasName alternate well-defined name for any Node in the system
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names1 ScopeServer that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related Node on a Server . An aggregating Server can collect these AliasNames
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Namesoften needs to be configured, where the configuration can include the addition of an AliasName . An interface for adding AliasNames and AliasNameCategories would allow a standard configuration to setup
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Namesfixed instances. The key functionality of AliasNames is to reference the information that an AliasName is assigned to. These can be any Node. The AliasNames can be grouped according
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names6.1 Overviewthis object model is provided in Clause 5 . Figure 1 illustrates the overall AliasName Object Model
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesDataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 ConformanceUnits AliasName Base This ObjectType has no Properties or Variables . The BrowseName of the Object is used ... Reference (or subtype of). A Client shall always ignore the namespace associated with an AliasName for comparison with other AliasNames . AliasName can be defined in Namespace 1 (the local Server
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names6.3.1 DefinitionAliasNames . It includes a mandatory Method for finding instances of AliasNameType in the AliasName hierarchy, starting at this instance of AliasNameCategoryType . For example, if the Method call is made ... static NodeId allowing it to be aggregated. For details on aggregation of AliasName and AliasNameCategories see Annex B . The AliasNameCategoryType is a subtype of FolderType and is formally defined
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names6.3.2 FindAlias MethodMethod allows a Client to obtain the list of Nodes that match the provided AliasName search string. The signature of this Method is specified below, the arguments are defined ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits AliasName Base It is important to note that there could be more than one entry
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesAddAliasesToCategory Method The AddAliasesToCategory Method allows a Client to add an AliasName to the AliasNameCategory . The signature of this Method is specified below, the arguments are defined in Table ... AddAliasesToCategory Method Arguments Argument Description AliasNames An array of the string part of the AliasName . It is Server specific as to what namespace the AliasName is added to. TargetNodes
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Namesspecified below; the arguments are defined in Table 13 . This Method shall only delete AliasName instances that are defined on the Server exposing this Method . I.e. an aggregating Server that ... pulled AliasName instances from an aggregated Server cannot delete AliasName instances that are from the aggregated Server . Signature DeleteAliasesFromCategory ( [in] String[] AliasNames, [in] ExpandedNodeId [] TargetNodes, [out] StatusCode[] ErrorCodes ); Table
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesDataType defines a structure that can contain an array of ExpandedNodeId for a single AliasName . Its elements are defined in Table 17 . It will always have at least one entry ... ReferencedNodes array. Table 17 - AliasNameDataType DataType structure Name Type Description AliasNameDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . Its representation
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesDataType defines a structure that can contain an array of ExpandedNodeId for a single AliasName . Its elements are defined in Table 19 . It will always have at least one entry ... ReferencedNodes array. Table 19 - AliasNameVerboseDataType DataType structure Name Type Description AliasNameVerboseDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . ServerUris String
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesA.1 Overviewprovided to help illustrate how AliasNames function. This includes a Client using an AliasName Server , inside of a Server , in an aggregating Server
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesDataSet (see OPC 10000-14 ) that provides the Variables defined in the well. The AliasName model includes the standard organization items that are required in this document. In addition
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesClient use of an AliasName Server AliasNames allow a Client to find TagVariables or Topics easily. Many industrial systems assign tags to specific measurement or sensors. These tags follow established ... depending on how a system is configured. A Client could select which AliasName source to call via a configuration setting. The FindAlias Method call returns a list of all ExpandedNodeIds
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesObjects , which then also shall be merged. An aggregating Server could expose the same AliasName referencing multiple NodeIds . For example as shown in Figure B.1 , if a temperature sensor were ... connected to two Servers for redundancy, the same AliasName TI101 could exist in both Servers . The aggregating Server simply reports two ExpandedNodeIds to any Client that requested TI101. Figure
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesC.1 OverviewAliasNames, provides AliasNames functionality, but the target Nodes referenced are in other Servers. The AliasName s are aggregated from the Servers that have registered with the GDS that expose
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Namesavailable in any Server that has registered with the GDS. If the same AliasName is registered from different Servers , the GDS shall combine the AliasName within its Alias structure ... large list of AliasNames and it is important that an efficient storage of AliasName is provided to allow for fast AliasName resolution ( FindAlias
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Namesinstances of AliasNameType and AliasNameCategoryType that are associated with an unregistered Server . However, the AliasName instance or AliasNameCategory instance could be from multiple Servers and should only be removed
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesDisconnect between a Client and an AliasName Server When a Client that uses aliased Nodes detects a communication problem with the Server , the Client can return ... request a new AliasNodeList for the AliasName . The original Server could recover and again be listed in the GDS, but the Client is not required to switch back. Figure
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesD.1.1 Overviewable to detect if a Server that contains AliasNames has had updates to the AliasName definitions. An aggregating Server or GDS could Subscribe for the LastChange Variable on AliasNameCategoryType instances ... section describes an extension for determining that a Server has had updates to the AliasName definitions. This extension to a Server that supports AliasNames , provides a Publisher capability
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Nameslist it has from the Server . There could be new AliasNameCategories , new AliasName Nodes , there could also be deleted AliasName Nodes or AliasNameCategories. For new AliasName Nodes , a Browse ... AliasName node would be required. Any updates would be stored. For a data delta frame message the following process could be followed: The Subscriber would add all of the AliasNameCategories
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesD.1.3 PubSub AliasName Notification Configuration The setting for a PubSub AliasName Publisher are fixed as defined in D.2 . Only the following items can be changed as part of configuring ... PubSubConnection for the published messages . This flag can be used to enable the Servers AliasName PubSub Notifications feature. A Server that supports this feature would typically have this feature
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesD.2.1 AliasCategoryUpdateDataType This structure is used to indicate that an AliasName category has an updated AliasName (s). Its elements are defined in Table D.1 . Table D.1 - AliasCategoryUpdateDataType DataType structure Name ... TypeDefinition Modelling Rule Subtype of the Structure defined in OPC 10000-5 Conformance Units AliasName PubSub Notification
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesD.2.2 AliasUpdateDataTypeindicate a Server has had changes to one or more AliasNameCategories , where an AliasName was added or deleted. Its fields are defined in Table D.3 . Table D.3 - AliasUpdateDataType DataType structure ... HasProperty Variable DataSetClassId Guid PropertyType HasProperty Variable DataSetMetaData DataSetMetaDataType PropertyType Conformance Units AliasName PubSub Notification
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesD.3.1 OverviewD.3.1 Overview This layout is specially configured for AliasName update messages. For additional detail on PubSub and header layouts
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelalso be used for DataSet /topic discovery and many other uses. Figure 15 - AliasName model overview In OPC UA FX, AliasNames can be used to define a configuration for information ... this configuration information into the actual Server / NodeId of the Node identified by the AliasName happens at runtime. The aggregation of AliasNames into a Global Discovery Server (GDS) happens automatically
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.36 PortableNodeIdentifierNode 0:PortableNodeId The NodeId of the item Alias 0:String The AliasName of the Item IdentifierBrowsePath 4:PortableRelativePath The IdentifierBrowsePath to the item. The starting node of the IdentifierBrowsePath
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.1 Overviewconfiguration might contain Nodes in any of the following formats: PortableNodeId , PortableRelativePath or AliasName , each of which has components that might have changed since they were generated by the engineering
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.1 GeneralConnectionConfigurationSets and their components. That information may be represented as PortableNodeId , PortableRelativePath or AliasName . These all need to be resolved to NodeIds (illustrated in Figure 67 and described in Clause
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.4 AliasName providedAliasName provided If the ConnectionConfigurationSet contains AliasNames ( Figure 72 provides an overview of the configuration), then the Client should perform the following steps: Connect to the well-known ... provides other functionality, such as certificate management or discovery. Call FindAlias with the provided AliasName(s) , which will return the target Server and the NodeId . A single Call
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis clause, such as finding or connecting to a Server , resolving Node Information by AliasName lookup, TranslateBrowsePathToNodeId , or even for Namespace lookup issues. The ConnectionManager also report errors from interactions
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.1.2.2 Namespacesreduce the overall size of the DataTypes defined in this Clause (i.e. ConnectionConfigurationSetConfDataType ), NodeId , AliasName and RelativePath are used instead of their portable version. The scope of those identifiers
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.1.15 NodeIdentifierNamespaces in the ServerAddressConfDataType (see F.1.11 ) of the related Server . Alias 0:String The AliasName of the Node. IdentifierBrowsePath 0:RelativePath The IdentifierBrowsePath to the Node . The starting Node
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics8.1 Overviewused to categorize AliasNames and provide filter functionality on the AliasNames . The same AliasName can be represented by several Nodes , for example, if managed in different Servers . Using AliasNames simplifies ... specification defines two standardized categories for AliasNames , one using the mandatory 2: ProductInstanceUri as AliasName , and another one using the writable 2: AssetId , which can be set by the user
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basicsassets having a 2: ProductInstanceUri (see section 7 ). The string part of the AliasName shall be identical to the value of the 2: ProductInstanceUri, the namespace of the AliasName shall
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics8.2.3 AssetsByAssetIdassets having a 2: AssetId (see section 7 ). The string part of the AliasName shall be identical to the value of the 2: AssetId, if the value of 2: AssetId ... empty or null String. The namespace of the AliasName shall be the one defined by this specification in section 16 . As the default value of the 2: AssetId