A & C Exclusive RateofChange

Supports Exclusive RateofChange Alarm type.


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

000

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

1

The type definition matches the UA Specifications (Part 9, Tables 50, 43, 40, 30, 23, and 7)

2

Walk through the address space looking for Instances of ExclusiveRateOfChangeAlarmType 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()  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.

002

Lab Determine the acceptable rate of change. Using the available triggers, apply a value at a rate that is within the acceptable rate of change. A rate of change must not exceed 1-minute, for the purpose of this test. No event is received during this "safe" interval.

003

Lab Determine the acceptable rate of change. Using the available triggers, apply a value at a rate that is outside of the acceptable rate of change, i.e. faster. An event is received of type ExclusiveRateOfChangeAlarmType.

004

Lab Call()  Determine the acceptable rate of change. Using the available triggers, apply a value at a rate that will exceed one of the limit types, e.g. HighLimit. Determine if the event has multiple Limit properties (e.g. hi, hihi etc.)
Step #
Action
Expected Result(s)

1

An event is received of type ExclusiveRateOfChangeAlarmType.

2

Acknowledge the event, and Confirm, if supported.

3

Repeat step #1 now using another limit, e.g. HighHighLimit.

The event is received with the new state.