PacComm TINY-2 - Page 54

PACKET
CONTROLLER
COMMANDS
Parameters
the
packet
controller
shows
some
of
these
numeric
parameters
(those
which
set
special
characters),
they
will
be
given
in
hex.
The
fon
K
through
15
are
denoted
by
the
hexadecimal
digits
A
ough
F.
A
parameter
designated
as
text,
such
as
the
argument
to
CText,
may
be
entered
in
upper
or
lower
case,
and
may
include
numbers,
spaces,
and
punctuation.
The
text
is
accepted
exactly
as
typed
by
e
user.
Several
commands
require
callsigns
as
parameters.
They
may
be
any
collection
of
numbers
and
at
least
one
letter
up
to
six
charac-
ters;
they
are
used
to
identify
stations
sending
and
receivin
ackets.
A
callsign
may
additionally
include
sub-station
ESsID),
which
is
a
decimal
number
from
0
to
15
used
to
distin-
guish
two
or
more
stations
on
the
air
with
the
same
call
(such
as
a
base
station
and
a
repeater).
The
call
sign
and
SSID
are
entered
and
displayed
as
call-n,
e.g.,
OPFX-3.
If
the
SSID
is
not
entered,
it
is
set
to
0,
and
SSIDs
of
0
are
not
displayed.
Some
commands
have
parameters
which
are
actually
lists
of
items.
For
example,
you
may
specify
as
many
as
eight
callsigns
to
be
selectively
monitored
with
The
command
LCAIls.
The
second
and
later
items
in
the
list
are
optional,
and
you
may
separate
the
list
items
with
blank
spaces
or
with
commas.
For
example:
means
that
the
command
Beacon
requires
an
argument
which
must
be
either
Every
or
After
(abbreviated
to
E
or
A),
and
an
argument
n
which
the
user
may
choose
froma
range
ofvalues.
An
acceptable
command
might
be
B
E
2.
means
that
the
command
Connect
requires
a
callsign
argument
call#1.
You
may
optionally
include
the
keyword
Via,
followed
by
a
list
of
one
to
eight
callsigns,
call2
through
call#9.
The
callsigns
in
the
list,
if
included,
must
be
separated
by
commas
(as
shown),
or
b
Blank
spaces.
An
acceptable
command
might
be
C
N2
Vv
71
9FLW.
You
can
see
the
current
value
of
the
command’s
arguments
by
typing
the
command
name
by
itself,
without
any
arguments.
SU
Te
Operating
Manual,
4th
Ed..
©
PacComm,
1990
47