USER'S GUIDE
COMMAND SUMMARY
PK232UG Rev. B 9/86
6-7
109
6.4.2.
Command Mode Error Messages
An error message is displayed if you make a mistake typing a command to the PK-232.
?bad
You typed a command correctly, but the remainder of the command line couldn't be inter-
preted.
?call sign
You typed a call sign that does not meet the PK-232's requirements for call signs. A call
sign may be any string of numbers and letters. Punctuation and spaces are not allowed.
The SSID, if given, must be a (decimal) number from 0 to 15, separated from the call by
a hyphen.
?clock not set
You typed the command
DAYTIME
to display the date and time, but you haven't yet set
the clock! DAYTIME sets the clock if it is given with the daytime parameter and displays
the date and time if it is given without parameters.
?What?
Your first entry is not a command or a command abbreviation – your PK-232 did not
understand your instructions!
?not enough
You didn't type enough arguments for a command that expects several parameters. For
example,
CONNECT W2JUP VIA
.
?not while connected
You attempted to change
MYCALL
or
AX25L2V2
while in a connected or connecting state.
?range
You typed a numeric argument too large or too small for the specific command.
?too long
You typed a command line that is too long, so the line is ignored. For example, if you try
to type too long a BTEXT or CTEXT message, you'll receive this message. When you get
this specific error message, the previous text entry is not changed.
?too many
You typed too many arguments for a command that expects several parameters. For ex-
ample, MFILTER can have up to 4 arguments.
cmd:
MFILTER $1B,$0C,$1A,$03,$07
?too many
