Search
15 result(s) for Severity
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.12.2.2 Parametersinformation 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: Servicesusability 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 Model6.4.2 BaseEventTypeHasProperty 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 Accessdata 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 & ConditionsSeverity, 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 & Conditions5.5.2 ConditionTypeWhen 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 & ConditionsHasProperty 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 Accesspresent 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: PubSub7.2.4.5.4 DataSetMessage headerhigh 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 ModelLogOverflowEventType 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 Modelless 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 Modeldefined 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 ModelMessage - 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 BasicsSourceNode 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 Basicsinformation 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