Last Remote; Auto Tests; Low Power Tests; Retries - Ametek UPLC-II System Manual

Universal power-line carrier
Table of Contents

Advertisement

ly giving a checkback major or minor alarm. So
there would normally be at least 4 attempts to have
a successful test, when the number of retries is set
to 2, before getting any alarms. These tests would
be run at both low level and high level if "Low
Power Tests" are enabled with low power tests
being run first. All this gives security against noise
on the line or some temporary condition causing a
false alarm. Major alarms occur for high power test
failures and minor alarms occur for low power test
failures.

6.2.4 Last Remote

Your network may contain more than two check-
back terminals (i.e., one master and one remote).
Among other things, this setting lets the unit know
the final address to which it needs to send a check-
back test request. If the primary communication
mode is set to "timed", you can have up to four (4)
remotes. If it is set to "coded", you can have up to
10 remotes.

6.2.5 Auto tests

Automatic checkback tests can be enabled or dis-
abled. Normally, you would probably want them to
be enabled. But if, for example, you are installing a
new checkback system, you might 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 com-
manded by you, the user. In addition, 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 specifically command it.

6.2.6 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, except
when in recovery mode during which time only low
power tests are run.

6.2.7 Retries

During noisy line conditions, remote messages may
contain errors that cannot be fixed at the destination
January 2016
Chapter 6. Testing Facilities
module. With this setting, you can specify the max-
imum number of times you want the module to
automatically resend a message (retries). The valid
range is zero (0) to 5 (times).
6.2.8 Automatic Tests – Time Settings
The time setting specifies how you want automatic
checkback tests to be performed. You have two
options:
1. Checkback Hours of the Day
2. Checkback Period
Option 1 – Automatic checkback tests are per-
formed at your four user-specified times. These
might be, say, 6:00, 12:00, 17:00, and 23:00.
Option 2 – Automatic tests are performed every so
many hours, for example, every eight (8) hours.
When you set the time setting to "Hours of the Day"
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 test five minutes after the hour (e.g.
4:05). This delay provides some "wiggle" room to
compensate for unsynchronized checkback clocks.
Remotes that have their Interval Types set to
"Hours of the Day" 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 one test per day, you can simply
set all of the times equal to one another. For exam-
ple, you could set time #1 – #4 to 08 to perform a
test at 8am every day.
When the Time Setting is set to "Checkback Period"
and three tests per day are desired without caring
about the time of day when they occurred, you
could set this time to 8 hours. The Master attempts
periodic checkback tests at exactly this time, in this
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 minutes, if it did not receive a
checkback test from another unit.
6
Page 6–3

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents