SGN 71001-1017
29
The second way of accessing the log information is by issuing the
LOG 2 command. This
command will list the event type by numeric value. The numeric value is shown in Table 5
below, which lists all of the possible event types. If the
LOG 2 command is issued with a
second parameter, a specific event can be displayed. For example, issuing a
LOG 2,3 command
will display the fourth event in the log (the first is event 0).
The receiver’s signal strength can be placed into the log by issuing a
LOG 6 command. For
monitoring purposes the uplink may be programmed to issue
LOG 6 commands to take
“snapshots” of the network as a whole (each receiver would log their signal strength
simultaneously which would allow monitoring of the network’s performance).
The receiver’s signal strength can be dumped into the log periodically with the
LOG 7
command. The
LOG 7 command requires a parameter (the time interval, in seconds) for the
signal strength to be logged. For example, issuing a
LOG 7,60 command will place the signal
strength into the log every minute. Remember that only 256 events will be logged so the log
should be retrieved and reset often enough so the
LOG 7,0 command does not fill the log. The
LOG 7 command should be turned off when not in active use to prevent filling the log.
A user event can be inserted into the log by issuing a
LOG 4 command. This event has no
predefined meaning. For example, a
LOG 4 could be issued whenever the log was queried but
not restarted which would indicate the last time the log was viewed.
Table 5. LOG Event Types
Event Type
Event Value
Event Description
START
0
The log was started.
BER
1
An uncorrected bit error has occurred.
FADE
2
The receiver began a fade acquisition.
SYNC LOSS
3
The demultiplexer lost lock.
ACQUIRED
4
The receiver acquired the signal.
EBNO
5*
The signal strength was placed in the log.
USER
6
A user event was placed in the log.
RELAY
7
An audio card has all relays in the ON position (FFFF)
POWER
8
The receiver lost power or was reset.
CRC
9
A block of non-volatile memory had a bad CRC
AUTH
11
One of the current services changed authorization state.
NVCMP
12
The receiver’s automatic NV Correction detected an
error
Summary of Contents for StarGuide III
Page 4: ...iv StarGuide Digital Networks ...
Page 12: ...2 StarGuide Digital Networks ...
Page 32: ...22 StarGuide Digital Networks ...
Page 48: ...38 StarGuide Digital Networks ...
