COMMANDS
50
TXDFec
n
(n = 0 – 25)
v3.0
default 0
KAM
FEC
This command sets the number of extra seconds that the
KAM
will send phasing signals at the be-
ginning of a FEC transmission. This allows more time for a station to tune your FEC transmission
and obtain a LOCK condition before you actually begin transmitting data.
See also: fec
TXFlow
ON | OFF
default OFF
All Units
Packet
This command allows the TNC to send software flow control (XON and XOFF) to stop and restart
the flow of data from the computer while in the Transparent Mode. When TXFLOW is OFF, hard-
ware flow control must be used between the computer and TNC. RTS and CTS must be connected
between the TNC and computer for hardware flow control. When TXFLOW is ON, software flow
control between the TNC and the computer in Transparent Mode will depend on the setting of
XFLOW. XFLOW ON enables software flow control, XFLOW OFF disables it. When software flow
control is enabled, the TNC will send the XON an XOFF characters to the computer to control data
flow.
When set for software flow control, all characters can be sent in Transparent Mode (including the
XON and XOFF characters) by setting TXFLOW ON, XFLOW ON and TRFLOW OFF. You will not,
however, be able to receive the START and STOP characters, since your terminal program should
interpret them as flow control.
See also: trans, trflow, xflow
Unproto
call1 (VIA call2, call2, call3 ... call9) | [NONE]
default CQ
KPC-1
/
KPC-2
/
KPC-2400
Packet
default CQ/CQ
KAM
/
KPC-4
Packet
call1 = destination address (this is really just a "dummy" address, as no connection takes place,
people often put their name or CQ here).
call2 ... call9 = optional stations to be digipeated through a maximum of 8 digipeat addresses
(callsigns or aliases) can be specified. This is referred to as a path.
Each callsign may also have an optional supplemental station identifier (SSID) specified as -n,
where n = 1 – 15. The digipeat callsigns are specified in the order in which they are to relay trans-
mitted packets. This command is used to set the digipeat and destination address fields for
packets sent in the unconnected (unprotocol) mode. Unproto packets do not receive an acknowl-
edgment and are not retried. They are sent as Unsequenced I-frame <UI>. The digipeater list is
also used for BEACON and ID packets. If UNPROTO is "NONE", no unconnected packets will be
sent except for BEACON and ID. Unconnected packets sent from other units can be monitored by
setting MONITOR ON.
See also: alias, beacon, id, monitor, mrpt, xmitok