SATEC SA300 ezPAC Operation Manual - Manual (Page 81)

Chapter 7 Programming the SA300 Using Control Setpoints
SA300 Substation Automation Unit 81
units from the Preferences tab in the Tools/Customize dialog (see Voltage
Disturbance Units in Chapter 14).
The trigger does not respond to slow voltage variations whenever the voltage rise
above or drop below the specified threshold takes longer than 1 cycle time.
Delaying Setpoint Operations
Two optional delays can be added to each setpoint to extend monitoring setpoint
triggers for a longer time before making a decision on whether the expected event
occurred or not. When a delay is specified, the logical controller changes the setpoint
status only if all conditions are asserted for a period at least as long as the delay time.
Although a delay can be specified with a 1-ms resolution, the actual value is aligned
at a lower 1/2-cycle time boundary.
Note that you cannot use delays with pulsed events since they are cleared
immediately and do not longer exist on the next setpoint scan.
Using Setpoint Events and Actions
When a setpoint status changes, i.e., a setpoint event is either asserted or de-
asserted, the following happens in your device:
1. The new setpoint status is logged to the setpoint status register
that can be monitored from the SCADA system or from a
programmable controller in order to give an indication on the
expected event.
2. The operated setpoint status is latched to the setpoint alarm latch
register, which is remotely accessible. The register holds the last
setpoint alarm status until it is explicitly cleared.
3. Up to four programmable actions can be performed in sequence
on setpoint status transition when a setpoint event is asserted.
Generally, setpoint actions are performed independently for each setpoint and can be
repeated a number of times for the same target. The exceptions are relay operations,
data logging and waveform logging that are shared between all setpoints using an
OR scheme for each separate target.
A relay output is operated when one of the setpoints linked to the relay is activated
and stays in the operated state until all of these setpoints are released (except for
latched relays that require a separate release command to be deactivated).
Data logging and waveform logging directed to the same file are done once for the
first setpoint among those that specify the same action, guaranteeing that there will
not be repeated records related to the same time.
Recording Setpoint Events
Time-tagged setpoint events can be recorded both to the Event log, and to the
Sequence-of-Events log files if you put corresponding actions into the setpoint action
list.
If you link a setpoint to the Sequence-of-Events recorder, all setpoint transition events
are recorded to the Sequence-of-Events log by default. If you select to record setpoint
operations into the Event log, define in the action target box which transition events
you want to be recorded: when the setpoint is operated, when it is released, or both
events. The Event recorder puts into a log file a separate record for each active
trigger caused a setpoint status transition, and a separate record for each action done
on the setpoint activation (except for logging actions that are not recorded to the
Event log).
If you run a number of recorders from the same setpoint action list, it is recommended
that you put the Event log action before others in order to allow other recorders to use
the event sequence number given to the event by the Event recorder.