Pulsar TC-10B, User Manual

Page: 156 / 190

Page 16–22 October 2003
TC–10B System Manual
Technologies, Inc.
To enable this option:
1. Turn on the automatic test feature:
set auto on
This changes the "Auto Tests" setting to "On".
2. Set the interval type to "periodic":
set int period
This changes the "Interval Type" setting to
"Periodic".
3. Set the interval for the checkback tests:
set period[#]
Where "#" is the number of hours between tests.
This changes the "Checkback Period" setting to
the time you specified.
You can only make these settings changes if the
module's DIP switch is set to "CUSTOM".
16.5.3.5 Automatic Carrier Recovery
Using the set recovery command, you can set a
module to begin more frequent tests after failing
any of the above checkback tests. With the carrier
recovery mode enabled, the master module, after
failing a test, switches to carrier recovery mode. In
carrier recovery mode, checkback tests are
performed periodically, but much more frequently
than otherwise, for example, every 20 minutes.
You can set this time from five minutes to one
hour. After three consecutive successful tests, the
carrier recovery output is set, and the master
reverts to the normal automatic tests.
You can accelerate recovery by performing
manual tests at the master module. After you
execute three successful manual checkback tests,
the master module counts these as carrier recovery
tests and reverts to normal mode. Note that while
in recovery mode, the master only sends low-
power checkback tests. This ensures that the line
conditions are good before resuming normal
operation.
The module's local carrier recovery LED flashes
while in carrier recovery mode. After passing the
three tests, this LED changes to solidly on, and
any user defined outputs set to carrier recovery are
set for five seconds.
To enable the automatic carrier recovery mode,
use the set recovery command:
set recovery on
This changes the "Carr Recovery" setting to
"On".
16.5.3.6 Remote-Initiated Periodic Tests
In some cases, a remote module initiates its own
checkback test. Obviously, you can always
manually request a test by pressing the remote's
test switch (TST), closing the external switch
connected to the rear panel's TB6-1/TB6-2, or
entering the do checkback command. But the
remote automatically does a checkback test if it
detects the master is late. When a remote is set to
do automatic periodic tests, it determines the
master is late if it does not receive a checkback
request within the user period plus some delay, or
grace period. For remote #1, this grace period is
five minutes.
For example, let's say your remote is set for
automatic periodic testing, with a period of eight
hours. If it does not receive a checkback test
within eight hours and five minutes, it executes a
checkback test. If this test is successful, both the
master and the remote's periodic timers are
restarted at roughly the same time, and the master
takes over for subsequent checkback tests, if both
modules are set for the same periodic interval.
Note that this situation can occur when you are
first installing the checkback modules. The
periodic timer starts as soon as the module is
powered, so that one module will have a head start
on the others. After the first successful checkback
test, all the periodic timers in the network are
synchronized, and the master initiates any future
tests.
If you have more than one remote in your system,
each has its own unique grace period. Remote #1
waits five (5) minutes, remote #2 waits 10
minutes, remote #3 waits 15 minutes, and so on.
For example, if neither remote #1 nor the master
has initiated a checkback test for the interval plus
10 minutes, remote #2 executes a test.