Search
10 result(s) for IDeviceHealthType
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.2 FxAssetType definitionFolderType O 0:HasComponent Object 5:Diagnostics 5:FunctionalGroupType O 0:HasInterface ObjectType 5:IDeviceHealthType Applied from IDeviceHealthType (defined in OPC 10000-100) 0:HasComponent Variable 5:DeviceHealth 5:DeviceHealthEnumeration ... integrator or user of the component." The following two definitions are from the IDeviceHealthType interface. They are enclosed in quotes and included here for clarity. Their formal definition
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesshould treat the installation as successful. It can inform the incompatibility using e.g., the IDeviceHealthType Interface (see 4.5.4 ) of the device / component. This issue can be resolved later
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basicsenumeration can reasonably be applied. OPC 10000-100 defines the interface 2: IDeviceHealthType containing optionally the Variable 2: DeviceHealth. In older versions of OPC 10000-100 the Variable was only ... shall provide the 2: DeviceHealth Variable. This should be achieved by implementing the 2: IDeviceHealthType interface providing optionally the 2: DeviceHealth Variable . This can be done either directly
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basicsfailure or maintenance conditions the alarming mechanism of OPC UA is used. The 2: IDeviceHealthType already defines the optional 2: DeviceHealthAlarms folder, where such alarm Objects can be provided. However
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics12.1 Overviewprovided, it is recommended to use the 2: DeviceHealthAlarms folder defined in 2: IDeviceHealthType as container for those Objects. This specification does not define a specific 0: ConditionType for maintenance
-
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™6.1 Overviewprocess variables (see 7.1.2 ). The PADIMType includes these Interfaces , and additionally it includes the IDeviceHealthType , provided by OPC 10000-100 OPC 10000-100 . Furthermore PADIMType provides a reference
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>IFdtDeviceHealthType Interface IFdtDeviceHealthType defines additional requirements for the IDeviceHealthType interface, which is formally defined in Table 14 . Table 14 - IFdtDeviceHealthType Definition Attribute Value BrowseName IFdtDeviceHealthType IsAbstract True References Node Class ... BrowseName DataType TypeDefinition Other Subtype of the 2:IDeviceHealthType interface defined in OPC UA for Devices 5.5.4. 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType M The definition
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks16.1 OverviewMachineryItem . The Health of the MachineryItem may be represented by the 2: IDeviceHealthType Interface defined in OPC 10000-100 . Figure 24 - MonitoringType The building block can be used in parallel
-
OPC-40001-2 – OPC UA for Machinery - Part 2: Process Valuesoverall health status of the device as well as specific errors, the 2: IDeviceHealthType is implemented, defined in OPC 10000-100 . Note that it is not required to provide
-
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Managementrelated specifications and type definitions. Figure 14 - PtAssetType The PtAssetType references directly the IDeviceHealthType and the ISupportInfoType from OPC 10000-100. By that it gets the property DeviceHealth as well