Timewave DSP-232, Operating Manual

Page: 248 / 271

Chapter 13 Troubleshooting 13-16
Unable to monitor packets With obvious activity on the
channel, you don’t see any activity
on your screen.
WHYNOT
reports -
MONITOR
WHYNOT
reports -
MCON
WHYNOT reports -
MPROTO.
WHYNOT
reports -
MBX
WHYNOT reports -
PASSALL
WHYNOT
reports -
frame too
short
WHYNOT
reports - frame too
long
HBAUD incorrectly set.
VHF command incorrectly set.
Wrong Modem loaded
MONITOR
turned off
You’re currently connected, or in the
process of connecting, to another
station and
MCON
is set such that
received packets aren’t being
displayed.
You’re receiving packets which
contain special network addressing
You have entered a one or two calls
into the special monitoring setting
called
MBX .
The packet you received has an error
and wasn’t displayed for this reason.
This was probably due to receiving a
squelch burst or noise at the end of a
valid transmission.
This packet may have been sent by a
station using a higher level
networking protocol that allows
packets larger than the AX.25
standard.
Set HBAUD to 1200 for VHF FM
operations. Set
HBAUD
to
300
for
HF narrow shift applications.
Turn
VHF ON for 1200 baud VHF
FM operation; Turn it off for HF 300
baud operation.
Use
WHYNOT to assist in isolating
the cause or the command incorrectly
set.
Load proper modem
Set
MONITOR
to a non-zero level.
(The default is MONITOR 4 .)
Usually, you won’t want to monitor
while you’re connected, especially
on busy channels. If you do, set
MCON to a value greater than zero.
Either accept that you probably don't
really want to see those packets, or
turn
MPROTO ON
.
Enter MBX % to clear this setting.
Turn
PASSALL ON to see the
damaged packets if you want
No corrective action possible.
No corrective action possible.