Pulsar TC-10B, User Manual

Page: 167 / 190

Get Status
Minimum abbreviation: get sta
Displays the status of a module's front panel
LEDs.
Examples:
get status–Gets and displays the status of the
local module's LEDs.
get status > 1–Get and displays the status of
remote #1's LEDs
Get Counts
Minimum abbreviation: get cou
Displays a module's event counts. This shows the
number of major and minor alarms, communica-
tion errors, checkback retries, checkback tests
performed, successful checkback tests, and the
elapsed time since these counts were reset (see
"Clear Event Counts" and "Set Retries Before
Reporting a Failure").
Examples:
get count–Gets and displays the local
module's event counts.
get count > 2–Gets and displays remote #2's
event counts.
Get All
Minimum abbreviation: get all > n
Get all compliments set all and allows you to
replace all your local module's settings with those
of a distant module. Like Set All, this command
should always be redirected to some other
module, e.g., get all > 1. All settings except
address, password, time, and date are set identical
to the distant module.
Examples:
get all > 1–Sets the local module's settings to
match remote #1's.
get all > 0–Sets the local settings to match the
master's.
16.5.5.3 Clear Commands
Clear commands let you clear the stored events or
counts, or reset the alarm outputs
Clear alarms
Minimum abbreviation: clr a or clear a
Clears the alarm relays and display LEDs.
Examples:
clear alarms–Clears local alarms.
clr alarm > 1–Clears remote #1's alarms.
clr a>1–Clears remote #1's alarms.
Clear Events
Minimum abbreviation: clr e or clear e
Clears all stored events from the non-volatile
memory. Make sure you really want to do this
command before you actually do it, because you
may delete a considerable amount of data.
Examples:
clr events–Clears all locally stored target
events.
clear eve> 1–Clears remote #1's events.
clr e>1–Clears remote #1's events.
Clear Event Counts
Minimum abbreviation: clr c or clear c;
Clears the event counts which show the number of
major and minor alarms, communication errors,
communication retries, and the number of
checkback test attempts and successes.
Examples:
clr c–Clears local counts.
clr c> 2–Clears remote #2's counts.
16.5.5.4 Action Commands
You can command a Universal Checkback
Module to execute a loopback or checkback test
with an action command.
October 2003 Page 16–33
Chapter 16. Universal Checkback Module
16