Satec PM175 Manual User Manual Page 80

  • Download
  • Add to my manuals
  • Print
  • Page
    / 168
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 79
Chapter 4 PAS Application Software
80
Series PM175 Powermeters
Using Event Flags
The PM175 provides 8 common binary flags, called event
flags, which can be individually set, cleared and tested through
setpoints and via communications.
Event flags can be used in different applications, for example,
to transfer events between setpoints in order to expand a
logical expression or a list of actions that have to be done for a
specific event, or to externally trigger setpoint actions from the
SCADA system or from a PLC through communications.
Using Interval Timers
The PM175 provides four interval timers that are commonly
used for periodic recording of interval data at the time of the
fault or in the presence of other events detected by a setpoint.
The timers can be programmed to generate periodic events at
user-defined intervals (see Using Periodic Timers).
Interval timers are not synchronized with the clock. When you
run a timer, it generates a pulsed event that can trigger a
setpoint if you have put the timer into a list of the setpoint
triggers. When the setpoint event is asserted, the timer is
restarted, and then generates the next event when the timer
interval expires.
If you want to record interval data at predefined intervals
without linking to other events, just select a timer as a setpoint
trigger and specify a data log file you want to use for
recording, in the setpoint actions list. If you want the periodic
data to be recorded in presence of a specific event, select
triggers that will 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
device 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 will change the
setpoint status only if all conditions are asserted for a period at
least as long as the delay time.
Note that you cannot use delays with pulsed events since they
are cleared immediately and will no 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 through communications
from the SCADA system or from a programmable
Page view 79
1 2 ... 75 76 77 78 79 80 81 82 83 84 85 ... 167 168

Comments to this Manuals

No comments