.NET Based OPC UA Client/Server SDK
3.3.1.531
|
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | AlarmConditionType | ||||
HasProperty | Variable | HighHighLimit | Double | Scalar | PropertyType | Optional |
HasProperty | Variable | HighLimit | Double | Scalar | PropertyType | Optional |
HasProperty | Variable | LowLimit | Double | Scalar | PropertyType | Optional |
HasProperty | Variable | LowLowLimit | Double | Scalar | PropertyType | Optional |
An abstract type used to provide a base Type for AlarmConditions with multiple limits
Alarms can be modelled with multiple exclusive substates and assigned limits or they may be modelled with non exclusive limits that can be used to group multiple states together.
Four optional limits are defined that configure the states of the derived limit Alarm Types: HighHighLimit, HighLimit, LowLimit, and LowLowLimit. These Properties shall be set for any Alarm limits that are exposed by the derived limit Alarm Types. These Properties are listed as optional but at least one is required. For cases where an underlying system cannot provide the actual value of a limit, the limit Property shall still be provided, but will have its AccessLevel set to not readable. It is assumed that the limits are described using the same Engineering Unit that is assigned to the variable that is the source of the alarm. For Rate of change limit alarms, it is assumed this rate is units per second unless otherwise specified.
The Alarm limits listed may cause an Alarm to be generated when a value equals the limit or it may generate the Alarm when the limit is exceeded, (i.e. the Value is above the limit for HighLimit and below the limit for LowLimit). The exact behaviour when the value is equal to the limit is Server specific.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | LimitAlarmType | ||||
HasComponent | Variable | ActiveState | LocalizedText | Scalar | TwoStateVariableType | Mandatory |
HasComponent | Object | LimitState | ExclusiveLimitStateMachineType | Mandatory |
Used to specify the common behaviour for Alarm Types with multiple mutually exclusive limits.
The LimitState is a Substate of the ActiveState and has a IsTrueSubstate reference to the ActiveState.
Represents the actual limit that is violated in an ExclusiveLimitAlarm.
When the ActiveState of the AlarmConditionType is inactive the LimitState shall not be available and shall return NULL on read. Any Events that subscribe for fields from the LimitState when the ActiveState is inactive shall return a NULL for these unavailable fields.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | ExclusiveLimitAlarmType |
The ExclusiveLevelAlarmType is a special level Alarm utilized with multiple mutually exclusive limits.
A level Alarm is commonly used to report when a limit is exceeded. It typically relates to an instrument – e.g. a temperature meter. The level Alarm becomes active when the observed value is above a high limit or below a low limit.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | ExclusiveLimitAlarmType |
A Rate of Change Alarm utilized with multiple mutually exclusive limits.
A Rate of Change Alarm is commonly used to report an unusual change or lack of change in a measured value related to the speed at which the value has changed. The Rate of Change Alarm becomes active when the rate at which the value changes exceeds or drops below a defined limit.
A Rate of Change is measured in some time unit, such as seconds or minutes and some unit of measure such as percent or meter. For example, a tank may have a High limit for the Rate of Change of its level (measured in meters) which would be 4 meters per minute. If the tank level changes at a rate that is greater than 4 meters per minute then the High sub state is entered.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | ExclusiveLimitAlarmType | ||||
HasProperty | Variable | SetpointNode | NodeId | Scalar | PropertyType | Mandatory |
A special deviation alarm utilized with multiple mutually exclusive limits.
A deviation Alarm is commonly used to report an excess deviation between a desired set point level of a process value and an actual measurement of that value. The deviation Alarm becomes active when the deviation exceeds or drops below a defined limit.
For example if a set point had a value of 10 and the high deviation Alarm limit were set for 2 and the low deviation Alarm limit had a value of -1 then the low sub state is entered if the process value dropped to below 9; the high sub state is entered if the process value became larger than 12. If the set point were changed to 11 then the new deviation values would be 10 and 13 respectively.
Provides the NodeId of the set point used in the deviation calculation.
If this Variable is not in the AddressSpace, a Null NodeId shall be provided.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | LimitAlarmType | ||||
HasComponent | Variable | ActiveState | LocalizedText | Scalar | TwoStateVariableType | Mandatory |
HasComponent | Variable | HighHighState | LocalizedText | Scalar | TwoStateVariableType | Optional |
HasComponent | Variable | HighState | LocalizedText | Scalar | TwoStateVariableType | Optional |
HasComponent | Variable | LowLowState | LocalizedText | Scalar | TwoStateVariableType | Optional |
HasComponent | Variable | LowState | LocalizedText | Scalar | TwoStateVariableType | Optional |
Used to specify the common behaviour for Alarm Types with multiple non-exclusive limits
HighHighState, HighState, LowState, and LowLowState represent the non-exclusive states. As an example, it is possible that both HighState and HighHighState are in their TRUE state. Vendors may choose to support any subset of these states.
Four optional limits are defined that configure these states. At least the HighState or the LowState shall be provided even though all states are optional. It is implied by the definition of a HighState and a LowState, that these groupings are mutually exclusive. A value cannot exceed both a HighState value and a LowState value simultaneously.
Represents one of the four non-exclusive states.
Recommended state names for LocaleIds are listed in the following table.
LocaleId | FALSE State Name | TRUE State Name |
---|---|---|
en | HighHigh inactive | HighHigh active |
de | HighHigh inaktiv | HighHigh aktiv |
fr | Très Haute Inactive | Très Haute active |
Represents one of the four non-exclusive states.
Recommended state names for LocaleIds are listed in the following table.
LocaleId | FALSE State Name | TRUE State Name |
---|---|---|
en | High inactive | High active |
de | High inaktiv | High aktiv |
fr | Haute inactive | Haute active |
Represents one of the four non-exclusive states.
Recommended state names for LocaleIds are listed in the following table.
LocaleId | FALSE State Name | TRUE State Name |
---|---|---|
en | Low inactive | Low active |
de | Low inaktiv | Low aktiv |
fr | Basse inactive | Basse active |
Represents one of the four non-exclusive states.
Recommended state names for LocaleIds are listed in the following table.
LocaleId | FALSE State Name | TRUE State Name |
---|---|---|
en | LowLow inactive | LowLow active |
de | LowLow inaktiv | LowLow aktiv |
fr | Très basse inactive | Très basse active |
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | NonExclusiveLimitAlarmType |
A special level Alarm utilized with one or more non-exclusive states.
If for example both the High and HighHigh states need to be maintained as active at the same time this AlarmType should be used.
A level Alarm is commonly used to report when a limit is exceeded. It typically relates to an instrument – e.g. a temperature meter. The level Alarm becomes active when the observed value is above a high limit or below a low limit.
The NonExclusiveLevelAlarmType is based on the NonExclusiveLimitAlarmType.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | NonExclusiveLimitAlarmType |
A special level Alarm utilized with one or more non-exclusive states.
If for example both the High and HighHigh states need to be maintained as active at the same time this AlarmType should be used.
A Rate of Change Alarm is commonly used to report an unusual change or lack of change in a measured value related to the speed at which the value has changed. The Rate of Change Alarm becomes active when the rate at which the value changes exceeds or drops below a defined limit.
A Rate of Change is measured in some time unit, such as seconds or minutes and some unit of measure such as percent or meter. For example a tank may have a High limit for the Rate of Change of its level (measured in meters) which would be 4 meters per minute. If the tank level changes at a rate that is greater than 4 meters per minute then the High sub state is entered.
The NonExclusiveRateOfChangeAlarmType is based on the NonExclusiveLimitAlarmType.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | NonExclusiveLimitAlarmType | ||||
HasProperty | Variable | SetpointNode | NodeId | Scalar | PropertyType | Mandatory |
A special level Alarm utilized with one or more non-exclusive states.
For example if a set point had a value of 10 and the high deviation Alarm limit were set for 2 and the low deviation Alarm limit had a value of -1 then the low sub state is entered if the process value dropped to below 9; the high sub state is entered if the process value became larger than 12. If the set point were changed to 11 then the new deviation values would be 10 and 13 respectively.
If for example both the High and HighHigh states need to be maintained as active at the same time this AlarmType should be used. The NonExclusiveDeviationAlarmType is based on the NonExclusiveLimitAlarmType.
A deviation Alarm is commonly used to report an excess deviation between a desired set point level of a process value and an actual measurement of that value. The deviation Alarm becomes active when the deviation exceeds or drops below a defined limit.
Provides the NodeId of the set point used in the deviation calculation.
If this Variable is not in the AddressSpace, a Null NodeId shall be provided.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | AlarmConditionType |
Used to classify Types into Alarm Conditions where the input for the Alarm may take on only a certain number of possible values (e.g. true/false, running/stopped/terminating).
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | DiscreteAlarmType | ||||
HasProperty | Variable | NormalState | NodeId | Scalar | PropertyType | Mandatory |
A specialization of the DiscreteAlarmType intended to represent a discrete Condition that is considered to be not normal.
This subtype is usually used to indicate that a discrete value is in an Alarm state, it is active as long as a non-normal value is present.
The NormalState Property is a Property that points to a Variable which has a value that corresponds to one of the possible values of the Variable pointed to by the InputNode Property where the NormalState Property Variable value is the value that is considered to be the normal state of the Variable pointed to by the InputNode Property. When the value of the Variable referenced by the InputNode Property is not equal to the value of the NormalState Property the Alarm is Active. If this Variable is not in the AddressSpace, a Null NodeId shall be provided.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | OffNormalAlarmType |
A specialization of the OffNormalAlarmType intended to represent an equipment trip Condition
The Alarm becomes active when the monitored piece of equipment experiences some abnormal fault such as a motor shutting down due to an overload Condition. This Type is mainly used for categorization.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | OffNormalAlarmType |
Used by a Server to indicate that an underlying system that is providing Alarm information is having a communication problem and that the Server may have invalid or incomplete Condition state in the Subscription.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | SystemOffNormalAlarmType | ||||
HasProperty | Variable | Certificate | ByteString | Scalar | PropertyType | Mandatory |
HasProperty | Variable | CertificateType | NodeId | Scalar | PropertyType | Mandatory |
HasProperty | Variable | ExpirationDate | DateTime | Scalar | PropertyType | Mandatory |
A SystemOffNormalAlarmType raised by the Server when the Server’s certificate is within the ExpirationLimit of expiration.
This alarm automatically returns to normal when the certificate is updated.
The date and time this certificate will expire.
Describes the purpose of a certificate.
The certificate that is about to expire.