Search

Scope: Core (OPC-10000-*) All specs

16 result(s) for iVendorNameplateType

OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

VendorNameplate Interface IVendorNameplateType includes Properties that are commonly used to describe a TopologyElement from a manufacturer point of view. They can be used as part of the identification. The Values ... Figure 5 and formally defined in Table 17 . Figure 5 - VendorNameplate Interface Table 17 - IVendorNameplateType definition Attribute Value BrowseName 1:IVendorNameplateType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

only instances of FxAssetType or a subtype of it or instances that implement the IVendorNameplateType , ITagNameplateType , and IAssetRevisionType Interfaces . The Folder may be empty; however, typically, there is at least ... that was tested. Furthermore, at least one Asset listed in this AutomationComponent shall include IVendorNameplateType information on the related OPC Foundation product page. Descriptors is a Folder that can contain
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

Subtype of the 0:BaseObjectType defined in OPC 10000-5 0:HasInterface ObjectType 5:IVendorNameplateType Applied from IVendorNameplateType (defined in OPC 10000-100 ) 0:HasProperty Variable 5:Manufacturer 0:LocalizedText ... FxAssetType models, see Annex D . The following are the definitions associated with the IVendorNameplateType interface; they are enclosed in quotes and included here for clarity. Their formal definition
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.2 Creating a new model based on OPC UA FX

might define a fixed set of optional items like in MyAssetType, which fixed optional IVendorNameplateType variables (i.e., making them mandatory). It could define a fixed structure of Connectors
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.3.1 General

model is similar to the base model for Interface but it has removed the IVendorNameplateType . Figure B.5 - Base Information Model for examples AddIns are used to attach
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.3.2 Extending an existing OPC UA model using AddIns

functionality defined in UA FX [for example, any of the FxAssetType interfaces - IVendorNameplateType , ITagNameplateType ]. An AddIn also allows the function to be placed as a separate object, which might
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.2 Example single board computer model

example The MyRaspberryPiType is a subtype of FxAssetType . It mandates some of the Optional iVendorNameplateType Properties (all items listed), and it omits other Optional Properties from the interfaces that
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.4 UAFX FxAsset

FxAssetType , or a subtype of it, or an Object that implements the following interfaces: IVendorNameplateType , ITagNameplateType, IDeviceHealthType and IAssetRevisionType . This includes supporting all required types. Server UAFX SoftwareUpdate Supports
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.6 ComponentType

DeviceType Defined in 4.7 . HasSubtype ObjectType 1:SoftwareType Defined in 4.8 . HasInterface ObjectType 1:IVendorNameplateType Defined in 4.5.2 . HasInterface ObjectType 1:ITagNameplateType Defined in 4.5.3 . Applied from IVendorNameplateType 0:HasProperty ... ComponentType . There will be no instances of a ComponentType itself, only of concrete subtypes. IVendorNameplateType and its members are described in 4.5.2 . ITagNameplateType and its members are described
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.11 AddIn model

instance of SoftwareUpdateType shall be attached to either Objects that implement the Interface IVendorNameplateType (see 4.5.2 ) or Objects that support an Identification FunctionalGroup (see B.2 ) that implements IVendorNameplateType ... identify the device / component that is the target for the software update, the IVendorNameplateType Interface is used. In this Interface at least the Variables Manufacturer, ManufacturerUri, ProductCode and SoftwareRevision shall
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.6.1 UpdateParent ReferenceType

SourceNode and TargetNode of References of this type shall be objects that implement IVendorNameplateType . A server shall support browsing of this ReferenceType in both directions. Table 118 - UpdateParent ReferenceType definition
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.6.2 CanUpdate ReferenceType

updated. SourceNode and TargetNode of References of this type shall be objects that implement IVendorNameplateType . Table 119 - CanUpdate ReferenceType definition Attributes Value BrowseName 1:CanUpdate InverseName CanBeUpdatedBy Symmetric False IsAbstract
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.5 Solution packages

ProductInstanceUri is specified, only the target with the specified ProductInstanceUri in its IVendorNameplateType shall be updated. If AssetId is specified, only the target with the specified AssetId in its ITagNameplate ... ManufacturerUri and ProductCode are specified, all targets identified with these properties in its IVendorNameplateType shall be updated. If ManufacturerUri, ProductCode and SerialNumber are specified, only the target identified with these
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

B.3.2 Factory Automation example

devices. Determine currently installed software and how the devices can perform the update (using IVendorNameplateType Interface and Loading Object ). Determine technical preconditions for the update. E.g., if the device uses
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

thus containing the identification Properties defined in OPC 10000-100 . Usage of 2: IVendorNameplateType and 2: ITagNameplateType . An Object representing an asset can either directly implement those interfaces ... Object , and the 2: Identification Object provides the Properties , either by implementing the 2: IVendorNameplateType and 2: ITagNameplateType or by just providing the Properties . Figure 1 - Different Options for Identification
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.4.1 CalibrationTargetType ObjectType

provides identification information about the calibration target. It implements the 2: IVendorNameplateType and 2: ITagNameplateType , see Table 51 . The Properties defined by those interfaces are listed in Table ... HasComponent Variable <CapacityRange> 0:Range CapacityRangeType OP Properties of the 2:IVendorNameplateType defined in OPC 10000-100 2:Identification 0:HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType