Search
22 result(s) for DeviceHealth
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.2 FxAssetType definitionIDeviceHealthType Applied from IDeviceHealthType (defined in OPC 10000-100) 0:HasComponent Variable 5:DeviceHealth 5:DeviceHealthEnumeration 0:BaseDataVariableType O 0:HasComponent Object 5:DeviceHealthAlarms 0:FolderType O 0:HasAddIn Object ... defines the device condition." " DeviceHealthAlarms shall be used for instances of the DeviceHealth AlarmTypes specified in OPC 10000-100 ." AlarmType instances can also be defined in other
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelBaseDataVariableType M ConformanceUnits UAFX AutomationComponent Base AggregatedDeviceHealth shall be the aggregation of the DeviceHealth of the AutomationComponent's top-level Assets . The aggregation rules are defined as follows ... least one top-level Asset has DeviceHealth set to Failure , the AggregatedDeviceHealth DeviceFailure bit shall be set. If at least one top-level Asset has DeviceHealth set to Check_Function
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSubtype of Structure defined in OPC 10000-5 AggregatedDeviceHealth 3:DeviceHealthOptionSet Aggregation of the DeviceHealth of the AutomationComponent's top-level Assets AggregatedOperationalHealth 3:OperationalHealthOptionSet Aggregation of the OperationalHealth
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.21 DeviceHealthOptionSetDescription DeviceFailure 0 At least one of the top-level Assets has its DeviceHealth set to Failure . DeviceCheckFunction 1 At least one of the top-level Assets has its DeviceHealth ... Check_Function . DeviceMaintenanceRequired 2 At least one of the top-level Assets has its DeviceHealth set to Maintenance_Required . DeviceOffSpec 3 At least one of the top-level Assets
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices4.5.4 DeviceHealth InterfaceDeviceHealth Interface The DeviceHealth Interface includes Properties and Alarms that are commonly used to expose the health status of a Device . It is illustrated in Figure 7 and formally defined ... Table 21 . Figure 7 - DeviceHealth Interface Table 21 - IDeviceHealthType definition Attribute Value BrowseName 1:IDeviceHealthType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:BaseInterfaceType defined
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management BasicsOverall health status of an asset The Variable 2: DeviceHealth defined in OPC 10000-100 is used to provide the overall health status of an asset. It uses an enumeration ... 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 defined
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basicsoverall health status of an asset over time, the history of the 2: DeviceHealth Variable shall be used. For each 2: DeviceHealth Variable , where the history is currently tracked ... events for the same amount of time as the history of the 2: DeviceHealth
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation5.2.2 StacklightTypeHasInterface ObjectType 2:IDeviceHealthType Properties of the 2:IDeviceHealthType 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType O 0:HasComponent Object 2:DeviceHealthAlarms 0:FolderType O DeviceHealth , defined ... Table 15 - StacklightType Attribute values for child Nodes Source Path Value Description 2:DeviceHealth - Contains the health status information of the stacklight. 2:DeviceHealthAlarms - Contains alarms of the stacklights providing
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>7.2 FdtDeviceTypeDeviceTag 0:String 0:PropertyType M Applied from 2:IFdtDeviceHealthType 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType M, RO The FdtDeviceType is an abstract type and cannot ... used directly. The definition for DeviceHealth overrides the definition of OPC UA for Devices and makes this member mandatory for FdtDeviceType . The mapping of FDT information to FdtDeviceType is defined
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>IDeviceHealthType interface defined in OPC UA for Devices 5.5.4. 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType M The definition for DeviceHealth overrides the definition ... Devices and makes the DeviceHealth member mandatory for IFdtDeviceHealthType
-
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture7.1.2 OverviewHardwareRevision String PropertyType Optional HasProperty Variable 2:SoftwareRevision String PropertyType Optional HasComponent Variable 2:DeviceHealth DeviceHealthEnum BaseDataVariableType Optional HasProperty Variable MinCycleTime Duration PropertyType Mandatory HasProperty Variable RevisionID String PropertyType Mandatory ... does not support this ISDU Index, the Variable shall not be provided. The Variable DeviceHealth of DataType DeviceHealthEnum shall be mapped to ISDU Index 0x0024 (Device Status). If the device
-
OPC-30200 – OPC UA for Commercial Kitchen Equipment5.1.8 DeviceHealth propertyDeviceHealth property The status of the device is provided as DeviceHealth enumeration in the DeviceHealth property. The possible values are NORMAL_0, FAILURE_1, CHECK_FUNCTION_2, OFF_SPEC
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics4.1.3.1 OverviewMachineryItemState . The MachineryOperationMode provides additional context about the type of Tasks being performed. The DeviceHealth and DeviceHealthAlarms provide information about the device's condition and any Alarms that may have ... proposed mappings between the DeviceStateMachine , the FunctionalUnit state machines, the MachineryItemState and the DeviceHealth
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basicsproposed mappings between the DeviceStateMachine , the FunctionalUnit state machines, the MachineryItemState and the DeviceHealth . MachineryItemState indicates the current state of the device and is comparable with the LADS Device state
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: BasicsHasInterface ObjectType 2:IDeviceHealthType Applied from 2:IDeviceHealthType 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType O 0:HasComponent Object 2:DeviceHealthAlarms 0:FolderType O Conformance Units LADS LADSComponentType ... delineated in the OPC UA for AutoId Devices Release 1.01.1 (2021-07-13) specification. DeviceHealth indicates the health status of a Device as defined by NAMUR Recommendation
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: BasicsLADSDeviceStateMachineType ), the states of the FunctionalUnits (as represented by the FunctionalUnitStateMachineType ), and the DeviceHealth status. Table 148 illustrates this mapping. The first column represents the state of the MachineryItemState , while ... device management and operation. Table 148 - Recommendation for building the MachineryItemState MachineryItemState LADSDeviceStateMachineType FunctionalUnitStateMachineType DeviceHealth Executing "Operate" One or more in "Running" Not in "FAILURE
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basicsfunctional unit accurately reflects the operational status of the overall device. The DeviceHealth of the LADS Device should be determined by aggregating the DeviceHealth of its components. The specific rules
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocksconsider the MachineryItemState of subcomponent X:MyComponent as well. Same is true for the DeviceHealth . Depending on the functionality of the X:MyMachine, this may actually be required
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building BlocksB.4.3 Referencesused for the health of the subcomponent. Just referencing the Health folder or the DeviceHealth Variable would not provide the context of the subcomponent (assuming there would be several subcomponents
-
OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition MonitoringHasInterface ObjectType 2:IDeviceHealthType Applied from 2:IDeviceHealthType 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnumeration 0:BaseDataVariableType O 0:HasComponent Object 2:DeviceHealthAlarms 0:FolderType O The RemainingLifeTime property denotes ... State property denotes the SEMI E10 State of the item (see Section 11.1 ). The DeviceHealth variable indicates the status as defined by NAMUR Recommendation NE107. The DeviceHealthEnumeration DataType is formally
-
OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition MonitoringSection 0 for further details. The Health object contains Properties like Temperature , DeviceHealth and Notifications indicating the status of an item. All the objects mentioned above (namely 2:Identification
-
OPC-40450-1 – OPC UA for Joining Systems - Part 1: BaseLifetimeVariableType O, RO Health 0:HasInterface ObjectType 2:IDeviceHealthType Health 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnum 0:BaseDataVariableType O, RO Health 0:HasComponent Object 2:DeviceHealthAlarms 0:FolderType ... Health 0:HasInterface ObjectType 2:IDeviceHealthType 4:Monitoring 4:Health 0:HasComponent Variable 2:DeviceHealth 2:DeviceHealthEnum 0:BaseDataVariableType O, RO 4:Monitoring 4:Health 0:HasComponent Object 2:DeviceHealthAlarms