A & C Exclusive Limit

Supports Exclusive Limit Alarms. A Server that supports this must support one of the sub-types Level, Deviation or RateOfChange.


Questions? Contact us
Generated: 21/11/2021 at 17:21:20 p.m.
A & C Exclusive Limit - 5 Test Cases
Test Case Id Test Type Keywords Test Case Description Test Requirements Expected Result

000

CTT Unavailable  Call()  Walk through the address space checking the type definition of ExclusiveLimitType.
Step #
Action
Expected Result(s)

1

The type definition matches the UA Specifications (Part 9, Table 43 and all references).

2

Walk through the address space looking for Instances of ExclusiveLimitAlarmType types and verify they comply to the type definition. Note: CTT Settings to specify where these instances are.

Instances are typed correctly.

001

CTT Unavailable  Call()  Invoke an event of each instance of ExclusiveLimitAlarmType alarm by setting the level value beyond predefined limits. Browse the address space to find the definition of each instance and how many states are supported. One is state required; Four is the max.
Step #
Action
Expected Result(s)

1

Each event type is received as expected.

2

Acknowledge the event.

Event acknowledged successfully.

3

Confirm the event by calling the method on the Type.

Event confirmed.

4

Clear the event state.

Cleared - no alarm active.

5

Repeat all previous steps but for the next state (loop through all possible states).

003

CTT Unavailable  Call()  Invoke an event of each instance of ExclusiveLimitAlarmType alarm by setting the level value beyond predefined limits. Browse the address space to find the definition of each instance and how many states are supported. One is state required; Four is the max.
Step #
Action
Expected Result(s)

1

Each event type is received as expected.

2

Clear the event state.

3

Acknowledge the event.

Event acknowledged successfully.

4

Confirm the event by calling the method on the Type.

Event confirmed.

5

Repeat all previous steps but for the next state (loop through all possible states).

005

CTT Unavailable  Call()  Invoke an event of each instance of ExclusiveLimitAlarmType alarm by setting the level value beyond predefined limits. Browse the address space to find the definition of each instance and how many states are supported. For this test, two states are required; Four is the max.
Step #
Action
Expected Result(s)

1

Success.

2

In a loop, cause the transition to the next state without confirming/acknowleding the last state.

A state-change event notification is received. The LimitState represents the currently active state ONLY (does not contain any past states).

006

CTT Unavailable  Call()  Prepare a list of ALL fields (including inherited) that can be filtered (in a SELECT clause). In a loop, add the ""next"" field to a SELECT clause in a MonitoredItem.Filter.
Note: A single WHERE clause to receive this type of Alarm only.
The fields list array (to be tested) should start with the EventId. Note: the loop should jump 3 or 4 at a time (not 1 at a time).
Step #
Action
Expected Result(s)

1

Server accepts the subscription/monitoring request.

2

Invoke the event by writing to the trigger node and then call Publish.

The event is received in the Publish response and contains the list of fields requested only.

3

Repeat the loop by adding the "next" field until the last iteration where all fields are selected.