Search
49 result(s) for TypeDefinition
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.2 Creating an Instancehierarchical Reference that has the same BrowsePath as an InstanceDeclaration of its TypeDefinition which has an optional or mandatory ModellingRule except for the one based on the InstanceDeclaration . Figure
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.4 OptionalPlaceholderintention of the ModellingRule OptionalPlaceholder is to expose the information that a complex TypeDefinition expects from instances of the TypeDefinition to add instances with specific References without defining BrowseNames ... Folder. The ModellingRule OptionalPlaceholder adds no additional constraints on instances of the TypeDefinition . It just provides useful information when exposing a TypeDefinition . When the InstanceDeclaration is complex, i.e. it references
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.5 MandatoryPlaceholdersimilar intention as the ModellingRule OptionalPlaceholder . It exposes the information that a TypeDefinition expects of instances of the TypeDefinition to add instances defined by the InstanceDeclaration . However, MandatoryPlaceholder requires that ... ModellingRule MandatoryPlaceholder requires that each instance provides at least one instance with the TypeDefinition of the InstanceDeclaration or a subtype, and is referenced with the same ReferenceType or a subtype
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelC.2.3 Extended notationfrom an Object or Variable to its ObjectType or VariableType the name of the TypeDefinition can be added to the text used in the Node . The TypeDefinition shall either ... additionally is the SourceNode of a HasTypeDefinition . Figure C.2 - Example of using a TypeDefinition inside a Node To display Attributes of a Node additional text can be put inside
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.4.1 Descriptiondelete additional Nodes and References like child Nodes that exist based on a TypeDefinition . The behaviour is Server specific. When any of the Nodes deleted by an invocation of this
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.7.4.1 OverviewBrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition and a relative path constructed from BrowseNames
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.7.4.5 SimpleAttributeOperandVariable . If this list is empty the Node is the instance of the TypeDefinition . attributeId IntegerId Id of the Attribute . The IntegerId is defined in 7.19 . The Value Attribute shall
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.9 UAMethodNodeId of the UAMethod with the same BrowseName contained in the TypeDefinition associated with the Object Node . If the TypeDefinition overrides a Method inherited from a base ObjectType then this
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.15 Example/Definition> </UADataType> This Node is an instance of an Object TypeDefinition Node defined in another InformationModel (ns=2;i=341). It has a single Property which ... /References> </UAObject> This Node is an instance of a Variable TypeDefinition Node defined in base OPC UA InformationModel (i=68). The DataType is the base type
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data AccessDataItem is represented by a DataVariable with a specific set of Attribute s. The TypeDefinition reference indicates the type of the DataItem (in this case the AnalogItemType ). Additional characteristics
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data AccessA.3.1.4 Propertyserver is represented in the COM UA Wrapper as a Variable with TypeDefinition as PropertyType . The properties for an item are retrieved using the QueryAvailableProperties call in the DA server
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.2.1 Event areasrepresented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . The EventNotifier Attribute for these Objects always has the SubscribeToEvents flag set to True
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.2.2 Event sourcesrepresented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . If the A&E COM Server supports source filtering then the SubscribeToEvents flag
-
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs5.1 GeneralFiniteStateMachineType and basic ObjectType models presented in OPC 10000-16 . Each Program has a Type Definition that is the subtype of the FiniteStateMachineType. The ProgramStateMachineType describes the Finite State Machine
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.9.2 CertificateDirectoryTypeCertificateDirectoryType This ObjectType is the TypeDefinition for the root of the CertificateManager AddressSpace . It provides additional Methods for Certificate management which are shown in Table 74 . Table 74 - CertificateDirectoryType ObjectType ... Definition Attribute Value BrowseName 2:CertificateDirectoryType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 2: DirectoryType defined in 6.5.3 . 0:Organizes Object 2:CertificateGroups 0:CertificateGroup
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.5.4 KeyCredentialServiceTypeKeyCredentialServiceType This ObjectType is the TypeDefinition for an Object that allows the management of KeyCredentials . It is defined in Table 125 . Table 125 - KeyCredentialServiceType Definition Attribute Value BrowseName 2:KeyCredentialServiceType ... IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 2:ResourceUri 0:String 0:PropertyType Mandatory 0:HasProperty
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global ServicesKeyCredentialConfigurationFolderType This ObjectType is the TypeDefinition for an Folder Object that contains the KeyCredentialConfiguration Objects which may be accessed via the Server . Table 133 - KeyCredentialConfigurationFolderType Definition Attribute Value BrowseName ... KeyCredentialConfigurationFolderType IsAbstract False References NodeClass BrowseName TypeDefinition Modelling Rule Subtype of the 0: FolderType defined in OPC 10000-5 . 0:HasComponent Object 0:<ServiceName> 0:KeyCredentialConfigurationType Optional Placeholder
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global ServicesKeyCredentialConfigurationType This ObjectType is the TypeDefinition for an Object that allows the configuration of KeyCredentials used by the Server . It also includes basic status information which report problems accessing ... KeyCredentialConfigurationType Definition Attribute Value BrowseName 0:KeyCredentialConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 0:ResourceUri
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services9.6.4 AuthorizationServiceTypeAuthorizationServiceType This ObjectType is the TypeDefinition for an Object that allows access to an AuthorizationService . It is defined in Table 147 . Table 147 - AuthorizationServiceType Definition Attribute Value BrowseName 2:AuthorizationServiceType ... IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 2:ServiceUri 0:String 0:PropertyType Mandatory 0:HasProperty
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global ServicesAuthorizationServiceConfigurationType This ObjectType is the TypeDefinition for an Object that allows the configuration of an AuthorizationService used by a Server . It is defined in Table 158 . Table 158 - AuthorizationServiceConfigurationType Definition ... Attribute Value BrowseName 0:AuthorizationServiceConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 0:BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 0:ServiceUri
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.1.1 Node definitionsInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns can be omitted and only a Comment column is introduced to point
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.1.2 Additional ReferencesAdditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.1.3 Additional sub-componentsused. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Other BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.4.1 ModelFunctionalGroupType definition Attribute Value BrowseName 1:FunctionalGroupType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:FolderType defined in OPC 10000-5 0:HasComponent Object ... part of) their References . If a FunctionalGroup can be hidden on an instance the TypeDefinition shall use an appropriate ModellingRule like "Optional". If desirable, Nodes can be also
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.1 Node definitionsInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.2 Additional ReferencesAdditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.3 Additional sub-componentsused. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.4 Additional Attribute valueschild Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management BasicsComponentType or 2: DeviceType . An Object representing an asset can have the TypeDefinition 2: ComponentType , 2: DeviceType , or a subtype of one of those ObjectTypes and thus containing the identification ... Object representing an asset can either directly implement those interfaces, or has a TypeDefinition directly or indirectly implementing the interfaces. Usage of 2: Identification Object . An Object representing an asset
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management BasicsThis can be done either directly on the instance (X:Asset1) or via the TypeDefinition (X:Asset2), as shown in Figure 3 . However, it is also allowed to just provide
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.1 Node definitionsInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.2 Additional ReferencesAdditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.3 Additional sub-componentsused. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.4 Additional Attribute valueschild Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial AutomationInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.1.1 Additional ReferencesAdditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.1.2 Additional sub-componentsused. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.1.3 Additional Attribute valueschild Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.1 Node definitionsInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.2 Additional ReferencesAdditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.3 Additional sub-componentsused. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.4 Additional Attribute valueschild Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial LocationValue BrowseName SpatialLocationType IsAbstract True ValueRank -2 (Any) DataType BaseDataType References NodeClass BrowseName DataType TypeDefinition Other Subtype of the RelativeValueType defined in 7.1 0:HasComponent Variable Position 0:BaseDataType ... NodeId 0:BaseDataVariableType M The Variable Position informs about a position. Note that the TypeDefinition is not defined in detail, so it is assumed to define, while subtyping from SpatialLocationType
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.1 Node definitionsInt32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.2 Additional Referencesadditional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.3 Additional sub-componentsused. Table 5 - <some>Type additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.4 Additional Attribute valueschild Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning4.2.3.1 ConceptsAddress Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure