Search

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

35 result(s) for Severity

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.12.2.2 Parameters

information like an application specific error code, the Method should return a StatusCode with Severity Uncertain . inputArgumentResults [] StatusCode List of StatusCodes corresponding to the inputArguments . This list is empty unless ... element of the methods OutputArguments Property . The list shall be empty if the statusCode Severity is Bad. diagnosticInfos [] DiagnosticInfo List of diagnostic information for the statusCode of the results . This
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.11.5 StatusCode assigned to a value

usability of the value. The StatusCode is defined in 7.38 . Overall condition (severity) A StatusCode with severity Good means that the value is of good quality. A StatusCode with severity ... value is uncertain for reasons indicated by the SubCode . A StatusCode with severity Bad means that the value is not usable for reasons indicated by the SubCode . Rules The StatusCode
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.2 BaseEventType

HasProperty Variable LocalTime TimeZoneDataType PropertyType Optional HasProperty Variable Message LocalizedText PropertyType Mandatory HasProperty Variable Severity UInt16 PropertyType Mandatory HasProperty Variable ConditionClassId NodeId PropertyType Optional HasProperty Variable ConditionClassName LocalizedText PropertyType Optional ... return the string part of the BrowseName of the Node associated with the Event . Severity is an indication of the urgency of the Event . This is also commonly called
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

7.3.2 Operation level result codes

data quality in the various fieldbus specifications. Table 61 contains codes with BAD severity which indicates a failure. Table 62 contains codes with UNCERTAIN severity which indicates that the value ... LastKnown OPC UA requires that the Server shall return a Null value when the Severity is Bad. Therefore, the Fieldbus code "Bad_LastKnown" shall be mapped to Uncertain
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.6 Severity, quality, and comment

Severity, quality, and comment Comment , Severity and Quality are important elements of Conditions and any change to them will cause Event Notification s. The severity of a Condition is inherited ... commonly called alarm priority or 'priority', especially in relation to Alarms in the ProcessConditionClassType . Severity is defined to have a range of 1-1000, but this range includes Alarms
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

When enabled, changes to the following Variables shall cause a ConditionType Event Notification : Quality Severity (inherited from BaseEventType ) Comment Subtypes of ConditionType may define additional Variables that trigger Event Notifications ... initial transition of the Retain field from True to False. LastSeverity provides the previous severity of the ConditionBranch . Initially this Variable contains a zero value; it will return a value
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

8.2 AlarmState Variable

HasProperty Variable Filter ContentFilter PropertyType Mandatory ConformanceUnits A & C Summary HighestActiveSeverity - the highest Severity of any active Alarm . HighestUnackSeverity - the highest Severity of any Unacknowledged Alarm ActiveCount - a count
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.3 HistoricalEventConfigurationType

present it shall include at least the event fields Time , SourceName and Severity of the BaseEventType Type defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

high order 16 bits of the StatusCode DataType representing the numeric value of the Severity and SubCode of the StatusCode DataType . The field shall be omitted
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.2 LogObjectType definition

LogOverflowEventType Event indicating an overflow of LogRecords (see 6.4 ). The MinimumSeverity describes the minimum Severity of LogRecords associated with this LogObject . LogRecords with a Severity that is less than this ... available from this LogObject . If omitted, there is no restriction on the Severity associated with LogRecords associated with this LogObject . This number shall be between 1 and 1000, any other
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.3 GetRecords Method

less than this limit and can return a continuation point. MinimumSeverity The minimum Severity (all LogRecords with a Severity equal to this number or greater are returned). RequestMask The RecordMask ... Table 3 - GetRecords Result Codes Result Code Description Bad_OutOfRange The provided Severity is outside the range 1-1000 Bad_InvalidArgument One or more arguments are invalid, or StartTime
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.5 LogRecord structure

defined in OPC 10000-5 Time 0:DateTime Time associated with this record. False Severity 0:UInt16 Is a number between 1 and 1000 inclusive and corresponds to the range ... BaseEventType (see OPC 10000-3 ). Additional details for mapping of the severity defined for OPC BaseEvents to LogRecords is described in Table 9 . False EventType 0:NodeId Describes the specific
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.2 LogRecord EventType Mapping

Message - shall describe the issue that is being represented in the LogRecord . Severity - in the Event system is defined as a number between 1 and 1000 inclusive. Typically, the full
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

9.3 Asset specific information on health status

SourceNode and 0: SourceName shall identify the asset. The 0: Severity should be used as defined in Table 15 . Applications may refine those categories to a more detailed categorisation. Table ... Usage of Severity for Alarms containing asset specific information Severity Classification Description 801-1000 Critical Fault The asset has permanently failed. 601-800 Major Recoverable Fault The asset
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

12.2 IMaintenanceEventType

information to identify the overall duration the maintenance took place. Servers might change the Severity or other Event Fields as well as the state of the conditions when a maintenance
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

9.2 IOLinkEventType

defined by its subtypes. The optional Property LocalTime shall not be provided. The Property Severity reflects the mode of IO-Link events. The IOLinkEventType or subtypes shall only be used ... Notification" and the severity shall be "200". The Property IOLinkEventCode is defined by the subtypes of the EventType
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

9.7 IOLinkAlarmType

defined by its subtypes. The optional Property LocalTime shall not be provided. The Property Severity reflects the mode of IO-Link events. In case of "Warning" it shall
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)

6.4.7.2 Preset label CSPP element

item value and mapped to the Attribute value. 2. P_NA Severity field (bit 30 and bit 31) of the statusCode element of a value as DataValue DataType *1 from ... return values When the value acquired from the machine is 0 (not missing), the Severity should be "00" (Good Success). When the value acquired is 1 (missing
OPC-30140 – OPC UA for PROFINET

6.3.4.1 PnDiagnosisAlarmType

dynamic format string, this is replaced by the ExtChannelAddValue . For an active alarm the Severity variable of the Event must be dependent on the Maintenance and the QualifiedChannelQualifier variables ... Severity is divided into the 4 categories shown in the following table: Category Severity Range Fault 750 - 1000 Maintenance demanded 500 - 749 Maintenance required 250 - 499 Advise
OPC-30140 – OPC UA for PROFINET

6.3.4.3 PnTopologyChangedEventType

PnPortType object. This means that the physical network topology has changed. The Severity variable (inherited from BaseEventType) shall be set to 1. Table 104 - PnTopologyChangedEventType Definition Attribute Value BrowseName PnTopologyChangedEventType
OPC-30142 – OPC UA for PROFINET Remote IO

6.8.3 StatusCode of Arrays of Process Values

Process Values When returning arrays of Process Values , the Server shall set the Severity of the StatusCode to "Bad" if one or more Process Values in the returned ... Process Value in the array is "Bad", the Severity returned shall be "Uncertain" if one or more Process Values in the returned array are "Uncertain
OPC-30142 – OPC UA for PROFINET Remote IO

8 OPC UA EventTypes

Information Model (see OPC PN ). Both EventTypes defined in the following sections inherit the Severity Property from 0:BaseEventType. Servers shall provide a Value in the range ... Value which fits in the 4 categories shown in the following table: Category Severity Range Fault 750 - 1000 Maintenance demanded 500 - 749 Maintenance required 250 - 499 Advise
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

8.1 GsdGenAlarmEventType

dynamic format string, this is replaced by the ExtChannelAddValue . For an active alarm the Severity variable of the Event must be dependent on the Maintenance and the QualifiedChannelQualifier variables ... Severity is divided into the 4 categories shown in the following table: Category Severity Range Fault 750 - 1000 Maintenance demanded 500 - 749 Maintenance required 250 - 499 Advise
OPC-30200 – OPC UA for Commercial Kitchen Equipment

5.2.3.4 ErrorConditions Object

define various states such as EnabledState , AckedState or ActiveState and further properties such as Severity , Message , Time and SourceNode . The Retain Property indicates whether an error message is of interest
OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components

7.26.2 ObjectType definition

defined in OPC 10000-5 , containing a human-readable text of the Event . Severity as defined in OPC 10000-5 . For Events of VendingBaseAuditEventType the Severity shall
OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components

7.29.2 ObjectType definition

defined in OPC 10000-5 , containing a human-readable text of the Event Severity as defined in OPC 10000-5 . For Events of ConfigurationChangedEventType the Severity shall
OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices

18.1 General

HelpOffNormalAlarmType . Both are subtypes of OffNormalAlarmType, can be synchronized via ConditionRefresh and contain a Severity for error handling according to OPC 40083. Messages related to process parameters shall be represented
OPC-40082-3 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 3: LSR Dosing Systems

12 Alarmmanagement

HelpOffNormalAlarmType . All are subtypes of OffNormalAlarmType, can be synchronized via ConditionRefresh and contain a Severity for error handling according
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

6.4 Severity of events

Severity of events Wherever a Severity property is used (e.g. in MESMessage in 14.4 , all events based on BaseEventType ), the following classification shall be used: Table 9 - Severity Classes Range ... Severity Description 667 - 1000 Messages of high urgency (Error) 334 - 666 Messages of medium urgency (Warning) 1 - 333 Messages of low urgency (Information
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

14.6 ClearMESMessage

this method sets the Properties Id and Message in MESMessage to empty string and Severity to 0. Signature ClearMESMessage (); The method has no Input - or OutputArguments . Table 48 - ClearMESMessage Method
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

14.8 MessageConditionType

standstill. NOTE: The AlarmConditionType is a subtype of BaseEventType and therefore includes the Properties Severity and Message (= text
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

35.4.3 Inherited properties of BaseEventType

Inherited properties of BaseEventType Severity in accordance with clause 6.4 . SourceNode NodeId of the root Node of the specific interface. Message keeps the result of diagnostics as a vendor specific
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

35.5.2 Inherited properties from BaseEventType

Inherited properties from BaseEventType Severity in accordance with clause 6.4 . SourceNode contains the NodeId of the root Node of the specific interface. Message keeps the result of diagnostics
OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model

6.10.1 General

However, the following explanations give further instructions on how to specifically use the CncAlarmType . Severity is, as defined in OPC 10000-5 , an indication of the urgency of the Event ... ranges between a value of 1 and 1000. Regarding the severity levels, this OPC UA companion standard does not prescribe the severity levels in detail but expects the lowest alarm
OPC-40540 – OPC UA for Additive Manufacturing

8.4 ProcessValueAMType Definition

inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable Severity SensorSeverity 0:PropertyType O 0:HasProperty Variable Category SensorCategory 0:PropertyType M Conformance Units AdditiveManufacturing Monitoring - Process AdditiveManufacturing Monitoring - Health ... Severity indicates the criticality of the respective sensor data. Category indicates the area of application of the respective sensor. Warnings and errors created by these process values shall be indicated