Search
12 result(s) for ComponentType
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.6 ComponentTypeComponentType Compared to DeviceType the ComponentType is more universal. It includes the same components but does not mandate any Properties . This makes it usable for representation of a Device ... parts of a Device . Parts include both mechanical and software parts. The ComponentType applies the VendorNameplate and the TagNameplate Interface . Figure 9 Illustrates the ComponentType. It is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.2 FxAssetType definitionaddress)." " DeviceClass indicates in which domain or for what purpose a certain ComponentType is used. Examples are "ProgrammableController", "RemoteIO", and "TemperatureSensor". This
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.1 Generaldevice topology. Its most essential aspect is the functional grouping concept. The ComponentType ObjectType provides a generic definition for a Device or parts of a Device where parts include mechanics
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.7 DeviceTypeBrowseName 1:DeviceType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the ComponentType defined in 4.5.7 HasInterface ObjectType 1:ISupportInfoType Defined in 4.5.3 . HasInterface ObjectType 1:IDeviceHealthType Defined ... ImageSet 0:FolderType O Conformance Units DI DeviceType DeviceType is a subtype of ComponentType which means it inherits all InstanceDeclarations . The DeviceType ObjectType is abstract. There will be no instances
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.8 SoftwareTypeDevice or a part of a Device . SoftwareType is a concrete subtype of ComponentType and can be used directly. Figure 11 Illustrates the SoftwareType. It is formally defined in Table ... BrowseName 1:SoftwareType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the ComponentType defined in 4.5.7 . 0:HasProperty Variable 1:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesDevices . It shall either directly or indirectly reference all instances of a subtype of ComponentType with a Hierarchical Reference . For complex Devices that are composed of various components that ... root of the robotic system. The mechanics and controls are represented by ComponentType instances which are organized as sub-components of the root instance. Figure 12 shows the AddressSpace organisation
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices5.4 ConnectionPointUnits DI ConnectionPoint ConnectionPoints are components of a Device , represented by a subtype of ComponentType . To allow navigation from a Network to the connected Devices , the ConnectionPoints shall have
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices6.3.2 IsOnline ReferenceTypeReferences of this type shall be an instance of the same subtype of a ComponentType . Each Device shall be the source of at most one Reference of type IsOnline
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.11 AddIn modelsoftware. The SoftwareRevision Object shall be the same at both places. The ComponentType (see 4.5.7 ) already implements the Interface IVendorNameplateType . This makes it a good candidate for a SoftwareUpdate AddIn
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices9.4 Modular DevicesModular Devices A Modular Device is represented by a (subtype of) ComponentType that is composed of a top- Device and a set of subdevices (modules). The top- Device often
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesModel Additional transitions removed from the diagrams 10218 Editorial Missing SoftwareUpdate reference at ComponentType Added optional SoftwareUpdate reference to ComponentType . 10223 Feature Standardized folder to add / remove applications with software
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management BasicsThis leads to the following options, as shown in Figure 1 : Usage of 2: ComponentType or 2: DeviceType . An Object representing an asset can have the TypeDefinition 2: ComponentType ... DeviceType , with default values when the value cannot be provided. The 2: ComponentType and the Interfaces define the Properties as optional, i.e., they should be omitted when the information cannot