.NET Based OPC UA Client/Server SDK
3.3.1.531
|
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | FiniteStateMachineType | ||||
HasComponent | Method | OneShotShelve | Mandatory | |||
HasComponent | Object | OneShotShelved | StateType | None | ||
HasComponent | Object | OneShotShelvedToTimedShelved | TransitionType | None | ||
HasComponent | Object | OneShotShelvedToUnshelved | TransitionType | None | ||
HasComponent | Method | TimedShelve | Mandatory | |||
HasComponent | Object | TimedShelved | StateType | None | ||
HasComponent | Object | TimedShelvedToOneShotShelved | TransitionType | None | ||
HasComponent | Object | TimedShelvedToUnshelved | TransitionType | None | ||
HasComponent | Method | Unshelve | Mandatory | |||
HasComponent | Object | Unshelved | StateType | None | ||
HasComponent | Object | UnshelvedToOneShotShelved | TransitionType | None | ||
HasComponent | Object | UnshelvedToTimedShelved | TransitionType | None | ||
HasProperty | Variable | UnshelveTime | Duration | Scalar | PropertyType | Mandatory |
Defines a substate machine that represents an advanced Alarm filtering model.
The state model supports two types of Shelving: OneShotShelving and TimedShelving.The illustration includes the allowed transitions between the various substates. Shelving is an Operator initiated activity.
In OneShotShelving, a user requests that an Alarm be Shelved for its current Active state. This type of Shelving is typically used when an Alarm is continually occurring on a boundary (i.e. a Condition is jumping between High Alarm and HighHigh Alarm, always in the Active state). The One Shot Shelving will automatically clear when an Alarm returns to an inactive state. Another use for this type of Shelving is for a plant area that is shut down i.e. a long running Alarm such as a low level Alarm for a tank that is not in use. When the tank starts operation again the Shelving state will automatically clear.
In TimedShelving, a user specifies that an Alarm be shelved for a fixed time period. This type of Shelving is quite often used to block nuisance Alarms. For example, an Alarm that occurs more than ten times in a minute may get shelved for a few minutes.
In all states, the Unshelve can be called to cause a transition to the Unshelve state; this includes Un-shelving an Alarm that is in the TimedShelve state before the time has expired and the OneShotShelve state without a transition to an inactive state.
The “Time Expired” transition is simply a system generated transition that occurs when the time value defined as part of the “Timed Shelved Call” has expired. The “Any Transition Occurs” transition is also a system generated transition; this transition is generated when the Condition goes to an inactive state.
The ShelvedStateMachine includes a hierarchy of substates. It supports all transitions between Unshelved, OneShotShelved and TimedShelved.
This FiniteStateMachine supports three Active states; Unshelved, TimedShelved and OneShotShelved. It also supports six transitions.This FiniteStateMachine also supports three methods: TimedShelve , OneShotShelve and Unshelve.
Unshelve sets the AlarmCondition to the Unshelved state.
Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed to the Call Service. However, some Servers do not expose Condition instances in the AddressSpace. Therefore all Servers shall also allow Clients to call the Unshelve method by specifying ConditionId as the ObjectId. The method cannot be called with an ObjectId of the ShelvedStateMachineType Node.
Method Result Codes:
ResultCode | Description |
---|---|
Bad_ConditionNotShelved | The Alarm is not in the requested shelved state. |
Sets the AlarmCondition to the OneShotShelved state.
Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed to the Call Service. However, some Servers do not expose Condition instances in the AddressSpace. Therefore all Servers shall also allow Clients to call the OneShotShelve method by specifying ConditionId as the ObjectId. The method cannot be called with an ObjectId of the ShelvedStateMachineType Node.
Method Result Codes
ResultCode | Description |
---|---|
Bad_ConditionAlreadyShelved | The Alarm is already in a shelved state. The Alarm is already in OneShotShelved state. |
Sets the AlarmCondition to the TimedShelved state.
Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed to the Call Service. However, some Servers do not expose Condition instances in the AddressSpace. Therefore all Servers shall also allow Clients to call the TimedShelve method by specifying ConditionId as the ObjectId. The method cannot be called with an ObjectId of the ShelvedStateMachineType Node.
Method Result Codes
ResultCode | Description |
---|---|
Bad_ConditionAlreadyShelved | The Alarm is already in a shelved state. The Alarm is already in TimedShelved state and the system does not allow a reset of the shelved timer. |
Bad_ShelvingTimeOutOfRange | The provided Shelving time is outside the range allowed by the Server for Shelving. |
Input Arguments
Argument | DataType | ValueRank | Description |
---|---|---|---|
ShelvingTime | Duration | Scalar | Specifies a fixed time for which the Alarm is to be shelved. The Server may refuse the provided duration. If a MaxTimeShelved Property exist on the Alarm than the Shelving time shall be less than or equal to the value of this Property. |
Specifies the remaining time in milliseconds until the Alarm automatically transitions into the Unshelved state.
For the TimedShelved state this time is initialised with the ShelvingTime argument of the TimedShelve method call. For the OneShotShelved state the UnshelveTime will be a constant set to the maximum Duration except if a MaxTimeShelved Property is provided.
Reference | NodeClass | BrowseName | DataType | ValueRank | TypeDefinition | ModellingRule |
---|---|---|---|---|---|---|
HasSupertype | ObjectType | FiniteStateMachineType | ||||
HasComponent | Object | High | StateType | None | ||
HasComponent | Object | HighHigh | StateType | None | ||
HasComponent | Object | HighHighToHigh | TransitionType | None | ||
HasComponent | Object | HighToHighHigh | TransitionType | None | ||
HasComponent | Object | Low | StateType | None | ||
HasComponent | Object | LowLow | StateType | None | ||
HasComponent | Object | LowLowToLow | TransitionType | None | ||
HasComponent | Object | LowToLowLow | TransitionType | None |
Defines the state machine used by AlarmTypes that handle multiple mutually exclusive limits.
It is created by extending the FiniteStateMachineType.
The ExclusiveLimitStateMachine defines the sub state machine that represents the actual level of a multilevel Alarm when it is in the Active state. The sub state machine defined here includes High, Low, HighHigh and LowLow states. This model also includes in its transition state a series of transitions to and from a parent state, the inactive state. This state machine as it is defined shall be used as a sub state machine for a state machine which has an Active state. This Active state could be part of a “level” Alarm or “deviation” Alarm or any other Alarm state machine.
The LowLow, Low, High, HighHigh are typical for many industries. Vendors can introduce substate models that include additional limits; they may also omit limits in an instance.