Using time triggers, Delaying setpoint operations, Using setpoint events and actions – SATEC EM720 Operation Manual User Manual

Page 91

Advertising
background image

Chapter 5 Configuring the EM720

General Meter Setup

EM720 Power Quality and Revenue Meter

91

setpoint triggers. When the setpoint event is asserted, the
timer is restarted, and then generates the next timer event
when the timer interval expires.

If you wish to record interval data at predefined intervals
without linking to other events, just select a timer as a
setpoint trigger and specify in the setpoint actions list a data
log file you want to use for recording. If you want the
periodic data to be recorded in presence of a specific event,
select triggers that identify your event, and then add the
timer at the end of the trigger list using the AND operator.

Using Time Triggers

If you want the setpoint actions to be synchronized with the
clock, for example, to provide synchronous recording interval
data each 15 minutes or each hour, or to output time pulses
through relay contacts, use the time triggers that generate
static events synchronized to the device clock.

You can exercise the default setting for Setpoint #1 in your
meter as an example of using time triggers. The setpoint is
pre-programmed for data profiling at 15-minute intervals
using Data logs #1 and #2.

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.

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:

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.

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.

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

Advertising