Low Power Tests; Checkback Time 1-4; Checkback Period; Loopback Duration - Ametek UPLC CU44-VER04 Applications Manual

Universal power-line carrier
Table of Contents

Advertisement

UPLC™ Application Manual
want to disable automatic checkback tests until all
units are in place. When auto tests are disabled at
a unit, it does not issue checkback tests unless
manually commanded by you, the user. In addi-
tion, the master unit does not issue the automatic
clock update at around 12:30 AM. In other words,
no unit sends any command, unless you specifical-
ly command it.

7.4.9 Low Power Tests

Here, you can enable or disable the low power set-
ting during checkback tests. When enabled, all
checkback tests initiated by this unit are first per-
formed on low power, then high power. When dis-
abled, only the high-power test is performed.

7.4.10 Checkback Time 1-4

These settings let you set the four times at which
you want to execute automatic checkback tests for
timed checkback tests. When you set the Interval
Type to "timed", the master initiates a checkback
test at each of these times. You can set these times
only to the nearest hour, using a 24-hour format.
The master actually executes a timed test five min-
utes after the hour (e.g. 4:05). This delay provides
some "wiggle" room to compensate for unsyn-
chronized checkback clocks. Remotes that have
their Interval Types set to Timed also use these
times to initiate their own checkback tests, if they
do not hear from the master within a grace period.
The grace period is ten minutes after the hour for
remote #1, fifteen minutes for remote #2, and so
on.
If you do not want to use all four times, say you
are only interested in three tests per day, you can
simply set one of the times equal to another. For
example, you could set time 1 to 12:00, time 2 to
6:00, time 3 to 18:00, and time 4 to 18:00 as well.
If the current Interval Type is Periodic, the word
"Inactive" is displayed next to the checkback
times. This means that these times are disabled
and checkback tests occur according to the period-
ic interval (e.g., in the above example, every 8
hours). When you set the Interval Type to "timed",
these times become active and the Periodic time is
inactive.
Page 7–6

7.4.11 Checkback Period

As mentioned earlier, the checkback period is
enabled when the Interval Type is set to "period-
ic". If you wanted three tests per day and really did
not care about the time of day when they occurred,
you could set this time to, say, 8 hours. Masters
attempt periodic checkback tests at exactly this
time, in our case eight hours since the last test.
Remotes have a grace period before they, too,
attempt a checkback test, if they have not heard
from the master. For example, remote #1 would do
a checkback test after eight hours and five min-
utes, if it did not receive a checkback test from
another unit.

7.4.12 Loopback Duration

The loopback duration specifies how long a mod-
ule holds the carrier on during a loopback test.
Loopback tests are performed at both high and low
power. If you are at remote #1 and request a loop-
back test at the master, it turns the carrier on high
power then on low power for the duration of the
time. You can use loopback tests to set the sensi-
tivity of your local receiver or other such tasks.
The range of times is four to 60 seconds.

7.4.13 Carrier Recovery Period

When the master is in carrier recovery mode after
failing a checkback test, it begins initiating check-
back tests according to the carrier recovery period.
For example, if the carrier recovery period is 15
minutes, the master tries another checkback test
every 15 minutes. It remains in carrier recovery
mode and continues to initiate tests every 15 min-
utes, until it has successfully completed three con-
secutive checkback tests. At that time, it shifts
back to the normal mode, either periodic or timed
checkback tests.

7.4.14 Carrier Recovery Window

The carrier recovery window is a time limit for the
delayed alarm. If a unit goes into carrier recovery
mode and does not recover before this time limit,
it sets the delayed alarm. If any user-programma-
ble output is set to delayed alarm, it becomes
active. The main reason for having a carrier recov-
ery window and delayed alarm is to cut down on

Advertisement

Table of Contents
loading

Table of Contents