The World of Computer Software

home *** CD-ROM | disk | FTP | other *** search

/ The World of Computer Software / World_Of_Computer_Software-02-387-Vol-3of3.iso / t / tpk-v181.exe / TPK181-5.ZIP / TNC2117.HLP < prev next >

Wrap

Text File | 1993-02-09 | 101KB | 2,664 lines

═[ TNC Commands v1.1.7a Compiled by: Andy Witts G1DIL (Dec-92) ]═ @8BITCONV ON|OFF Default : OFF Display group : A Parameters : ON - The high-order bit is not stripped in converse mode. OFF - The high-order bit is stripped in converse mode. This command enables transmission of 8-bit data in Converse Mode. If 8BITCONV is OFF, the high-order bit (bit 7) of characters received from the terminal is removed before the characters are transmitted in a packet. The standard character set requires only 7 bits, and the final bit is used as a parity bit, or is ignored. Setting bit 7 in text characters transmitted over the air may cause confusion at the other end. If you need to transmit 8-bit data, but don't want all the features of Transparent Mode, you should set 8BITCONV ON and AWLEN 8. This may be desirable, for example, if you are using a special non-ASCII character set. Bit 7 is always removed in Command Mode, since commands require only the standard 7-bit ASCII character set. @ACkprior ON|OFF Default : ON Display Group : L Parameters: ON - Enables Prioritized acknowledgments. OFF - Acknowledgments have the same priority as any other frames on the channel. When ACKPRIOR is ON, acknowledgments have priority. This means that if your TNC receives a frame that it must acknowledge (ACK), it will immediately send the ACK if the channel is clear. If other stations are running with ACKPRIOR ON, they will not access the channel until you have had a chance to send the ACK, even if they cannot hear your transmissions. When OFF, acknowledgments are queued up for transmission the same as any other frame. @ACKTime n Default : 14 Display Group : T Parameters: n 0-250 in 10 mSec increments. ACKTIME specifies the time required to send an RR or RNR response frame (an acknowledgment) to an I frame at the radio port data rate. This corresponds to about 510mSec at 1200bps with 8 digipeaters and about 140mSec at 1200bps with no digipeaters. The default of 140mSec (ACKT 14) allows for no digipeaters. @AUtolf ON|OFF Default : OFF Display Group : A Parameters: ON - A linefeed character (<LF>) is sent to the terminal after each carriage return character (<CR>). OFF - A <LF> is not sent to the terminal after each <CR>. AUTOLF controls the display of carriage return characters received in packets as well as echoing those which are typed in. If the TNC's sign-on message lines appear to be typed over each other, you should set AUTOLF ON. If the TNC's sign on message appears to be double-spaced, you should set AUTOLF OFF. If the TNC's sign-on message appears to be single-spaced you have AUTOLF set correctly. This command only affects what is displayed, not the data sent in packets. If you want to add linefeed characters to outgoing packets, use the command LFADD. @AWlen n Default : 7 Display Group : A Parameters: n = 7 - 8, specifying the number of data bits per word. This value defines the word length used by the serial I/O port. For most packet operations, including conversation, bulletin board operation and transmission of ASCII files, you should set AWLEN 7. If 8 bit words are transmitted to the TNC in Command Mode or Converse Mode, the eighth bit is normally removed, leaving a standard ASCII character, regardless of the setting of AWLEN. To transmit and receive packets retaining all the 8 data bits of each character, as you do if you need to send executable files or other special data, you should use Transparent Mode and set AWLEN 8. Alternatively, you can use Converse Mode and set AWLEN 8 and 8BITCONV ON (however, the data you then pass must handle the Converse Mode special characters with the PASS prefix). @Ax25l2v2 ON|OFF Default : ON Display Group : L Parameters: ON The TNC will use AX25 Level 2 Version 2.0 protocol OFF The TNC will use AX25 Level 2 Version 1.0 protocol Some implementations of the earlier version of AX25 protocol (e.g., TAPR's TNC 1) won't properly digipeat version 2.0 AX25 packets. This command exists to provide compatibility with these TNC's until their software has been updated. During the protocol transition period, you should set AX25L2V2 OFF. After your local area TNC's are updated to the newer protocol version you should set AX25L2V2 ON. @AXDelay n Default : 0 Display Group : T Parameters: n = 0 - 180, specifying the voice repeater keyup delay in 10ms intervals. AXDELAY specifies a period of time the TNC is to wait, in addition to the normal delay set by TXDELAY, after keying the transmitter and before data is sent. This feature will be used by groups using a standard "voice" repeater to extend the range of the local area network. Repeaters with slow mechanical relays, split sites, or other circuits which delay transmission for some time after the RF carrier is present require some amount of time to get RF on the air. If you are using a repeater that hasn't been used for packet operations before, you will have to experiment to find the best value for 'n'. If other packet stations have been using this repeater, check with them for the proper setting. Note that this command acts in conjunction with AXHANG. Note that TAPR TNC 1 and other TNCs using the same version 3.x firmware interpret 'n' in 120ms intervals. The value set by AXDELAY on TNC2 will thus be 12 times the value used by a TNC 1 user to give the same time delay. @AXHang n Default : 0 Display Group : T Parameters: n = 0 - 20. Specifying the voice repeater hang time in 100ms intervals. This value can be used to increase channel efficiency when an audio repeater with a hang time of greater than 100ms is used. For a repeater with a long hang time, it is not necessary to wait for the repeater key-up delay after keying the transmitter if the repeater is still transmitting. If the TNC has heard a packet sent within the hang period, it will not add the repeater key-up delay (AXDELAY) to the key-up time. If you are using a repeater that hasn't been used for packet operations before, you will have to experiment to find the best value for 'n'. If other packet stations have been using this repeater, check with them for the proper setting. Note that TAPR TNC 1 and other TNCs using the same version 3.x firmware interpret 'n' in 120ms intervals. The value set by AXDELAY on TNC2 will thus be 6/5 the value used by a TNC 1 user to give the same hang time (when converting, round DOWN to the nearest integer). @BBSmsgs ON|OFF Default : OFF Display Group : A This command controls how the packet controller displays certain messages in Command and Converse modes. The affected messages are described below: MESSAGE EFFECT OF BBSMSGS ON ------- -------------------- *** CONNECTED TO xxxx Message appears on new line *** DISCONNECTED Message appears on new line *** retry limit exceeded Message appears on new line *** xxxx Busy Message appears on new line *** FRMR Sent Message appears on new line *** FRMR Received Message appears on new line *** Connect request: xxxx This message is omitted The BBSMSGS command is primarily useful for host operation with 'W0RLI' type bulletin board software that require link state messages to begin in the first display column. @Beacon Every|After n Display Group : I Parameters: EVERY - Send beacon at regular intervals AFTER - Send beacon once after the specified time interval with no packet activity n = 0 - 250. Specifying beacon timing in 10ms intervals. A value of 0 disables the beacon. The command enables beacon sending and causes the first beacon frame to be transmitted. A beacon frame consists of the text specified by BTEXT in a packet addressed to "BEACON" and sent via the digipeat address specified by the UNPROTO command, if any. If the keyword EVERY is specified, a beacon packet is sent every n*10 seconds. This mode might be useful to transmit packets for testing purposes. If AFTER is specified, a beacon is sent only after n*10 seconds have passed with no packet activity. In this case, the beacon is sent only once until further activity is detected. This mode can be used to send announcements or test messages only when packet stations are on the air. If you choose 'n' properly you can avoid cluttering a busy channel with unnecessary transmissions. Beacon frames from other TNC's can be monitored by setting MONITOR ON. @BKondel ON|OFF Default : ON Display Group : C Parameters: ON - The sequence <BACKSPACE> <SPACE> <BACKSPACE> is echoed when a character is deleted from the input line. OFF - The <BACKSLASH> (\) is echoed when a character is deleted. This command determines the way the display is updated to reflect a character deletion in Command Mode or Converse Mode. The <BACKSPACE> <SPACE> <BACKSPACE> sequence will properly update the screen of a video display. If you have a video display terminal or computer you should set BKONDEL ON. The <BACKSPACE> <SPACE> <BACKSPACE> sequence on a printing terminal would result in overtyped text. If you have a paper-output display, or if your terminal does not respond to the <BACKSPACE> character (<CTRL-H>), you should set BKONDEL OFF. The TNC will type a <BACKSLASH> for each character you delete. You can display the corrected input line by typing the redisplay-line character, which is set by the command REDISPLA. @BText TEXT "" Display Group : I Parameters: Text - Any combination of characters and spaces, up to a maximum length of 120 characters. BTEXT specified the content of the data portion of a beacon packet. The default 'text' is an empty string, i.e., no message. Beacon packets are discussed in more detail under the BEACON command. You can send multiple-line messages in your beacon by including carriage return (<CR>) characters in the text. The <CR> character can be included by preceding it with the pass character. The pass character is set by the PASS command. If you enter a text string longer than 120 characters, an error message will appear and the command will be ignored. For example, a Bulletin Board program might set the beacon TEXT to a message like this, updating the TEXT after each connection: Mailbox on line. Messages for WB9FLW, AD7I, K9NG. To clear the BTEXT TEXT without issuing a RESET command, use a % or & character as the first character in the text. @BUdlist ON|OFF Default : OFF Display Group : M Parameters: ON - Ignore frames from stations which are NOT in the LCALLS list. OFF - Ignore frames from stations which ARE in the LCALLS list. BUDLIST works in conjunction with the command LCALLS, which sets up a callsign list. These commands determine which packets will be displayed when you have set MONITOR ON. BUDLIST specifies whether the callsigns in the list are the ones you want to ignore, alternatively, are the ones you want to listen to. If you want to listen only for packets from a limited list, you should enter this list with LCALLS and set BUDLIST ON. You can use this feature, for example, to have your TNC "keep an ear out" for a particular station while you converse with someone else. If you want to ignore packets from a limited list, you should list the callsigns to ignore in LCALLS and set BUDLIST OFF. For example, if there is a bulletin board on frequency, you can ignore it while monitoring other conversations. @CALibra CALIBRA is an immediate command, and is used to transfer control to the modem calibration routine. Calibration may be performed at any time without altering the current link state. Briefly, the commands available in the calibration routine are: <SPACE> Switch the transmit audio to the other tone D Alternate between the two transmit tones at a rate determined by the radio baud rate K Toggle PTT line ON/OFF Q Quit calibration routine Refer to your TNC manual for details of the calibration method. See also the command RXCALL. @CALSet n Default : None Display Group : T Parameters: n = 0 - 65535 specifying the count setting for use by the calibration routine The number to be specified by CALSET is determined by the frequency 'f' to be calibrated as follows:- n = (525.000 / f) + 1 ( modulator tones ) n = (262.500 / f) + 1 ( demodulator tones ) Round 'n' to the nearest integer. To calibrate the modem tones, you will set 'n' for the desired frequency using CALSET, enter the calibration routine with CALIBRA, and adjust the tone following the instructions in the TNC manual. To calibrate the next tone, exit the calibration routine and set 'n' for the next frequency. @CANline n Default : $18 Display Group : C <CTRL-X> Parameters: n = 0 - $7F specifying an ASCII character code. This command is used to change the cancel-line input editing command character. The parameter 'n' is the ASCII code for the character you want to type in order to cancel an input line. You can enter the code in either hex or decimal. For example, to change the cancel-line character to <CTRL-U), you would sent CANLINE $15 or CANLINE 21. If you cancel an input line in Command Mode, the line will be terminated with a <BACKSLASH> character, and you will see a new CMD: prompt. If you cancel a line in Converse Mode, you will see only the <BACKSLASH> and a new line. You can cancel only the line you are currently typing. Once a <CR> has been entered, you can not cancel an input line using the cancel-line character. Note that if your send-packet character is not <CR> the cancel-line character will cancel only the last line of a multi-line packet. To cancel the entire packet, use the CANPAC character. Line cancellation, like all other input editing features, is disabled in transparent mode. @CANPac n Default : $19 Display Group : C <CTRL-Y> Parameters: n = 0 - $7F specifying an ASCII character code. CANPAC is used to change the cancel-packet input editing command character. The parameter 'n' is the ASCII code for the character you want to type in order to cancel an input packet. You can alter the code in either hex or decimal. If you cancel a packet in Converse Mode, the line will be terminated with a <BACKSLASH> character and a new line. You can only cancel the packet which is currently being entered. Once you have typed the send-packet character, or waited PACTIME (of CPACTIME is enabled), the packet cannot be cancelled even if it has not been transmitted. Packet cancellation, like all other input editing features, is disabled in transparent mode. Cancel display-output The cancel-packet character also functions to cancel display output in Command Mode. If you are in Command Mode and type the cancel-packet character, any characters that would be type don the screen (except echoed characters) are "thrown away" by the TNC. Typing the cancel-output character a second-time restores normal output. To see how this works try typing DISPLAY, then type <CTRL-Y>. The command list will stop. You won't see any response from the TNC to commands. Now type another <CTRL-Y>, and type DISPLAY again to see that the display is back to normal. You can use the cancel-display feature if you inadvertently so something that causes the TNC to generate large amounts of output to the terminal, such as giving the DISPLAY command or setting TRACE ON. If you are in Converse Mode or Transparent Mode and want to cancel display output, you must exit to Command Mode and then type the cancel-packet character. @CBELL ON|OFF Default : OFF Display Group : I Parameters: ON - A bell character will be sent to the terminal as part of the connect message. OFF - No bell character is included in the connect message. The CBELL command is used to control whether an ASCII $07 (bell) character is sent as part of the connected message. When set ON, the bell character immediately precedes the asterisk portion of the connect indication. This command is not related to the MFILTER command. CBELL will produce a 'CONNECT BELL' even if MFILTER is set to delete incoming $07 (bell) characters. @CHeck n Default : 12 Display Group : I Parameters: n = 0 - 250 specifying the check time in 10 second intervals. A value of 0 disables this feature. This command sets a connection timeout. If a link connection exists between your TNC and another station, and the other station "disappears", your TNC could remain in the connected state indefinitely, refusing connections from other stations. this might happen if propagation changes unexpectedly or an intermediate digipeater station is turned off. In order to prevent this sort of lockup, the TNC will try to clean-up the link if the specified time elapses without any packets being heard from the other TNC. The operation of this feature depends upon the setting of AX25L2V2. If AX25L2V2 is ON, the TNC will send a "check-packet" to verify the presence of the other station if no packets have been heard for n*10 seconds. This frame contains no information, but is interpreted by the receiving station's TNC as an enquiry as to whether it is still connected. If the receiving TNC is still connected, it send an appropriate response packet. If the TNC initiating the enquiry does not hear a response after RETRY+1 attempts, it commences a disconnect sequence, as if the DISCONNE command had been given. If AX25L2V2 is OFF and the other station has not been heard for n*10 seconds, the TNC will not attempt an enquiry, but will send a disconnect packet, just as if you had typed the command DISCONNE. See also the command CHECKV1. @CHECKV1 ON|OFF Default : OFF Display Group : T Parameters: ON Enables CHECKtime (T3) when running AX.25 Level 2 Version 1.0 protocol. This will result in an automatic disconnect when packets haven't flowed between this TNC and the remote TNC for CHECKtime. See CHECK, above. OFF Disables the CHECKtime timer (T3) and requires the operator to initiate a disconnect sequence. This is in accordance with AX.25 Level 2 Version 1.0 procedures. When ON, the CHECK (T3) timer is used to automatically disconnect an AX.25 Level 2 Version 1.0 link when data hasn't flowed for CHECK time. Note that T3 is not defined for Version 1.0 operation. See CHECK, above. When OFF, T3 is ignored and normal Version 1.0 procedures apply. NOTE: Many operators prefer using Version 1.0 protocol, especially on marginal or noisy links in order to eliminate some of the overhead of AX.25 Level 2 Version 2.0 protocol. @CLKADJ n Default : 0 Display Group : T Parameters: n = 0 - 65535, specifying the correction factor to be applied to the real-time clock routine. A value of '0' is a special case and means no correction factor will be applied. If the value of CLKADJ is non-zero, then the correction factor is calculated as: relative clock speed in % = 100 - (9.16667 * 1/n) @CMdtime n Default : 1 Display Group : T Parameters: n = 0 - 250 specifying Transparent Mode timeout value in 1 second intervals. If 'n' is zero, the only exit from Transparent Mode is to send a BREAK signal or interrupt power to the TNC. This command sets the Transparent Mode timeout value. In order to allow escape to Command Mode from Transparent Mode while permitting any character to be sent as data, a guard time of 'n' seconds is set up. The same Command Mode entry character used for exit from Converse Mode is used to exit Transparent Mode, but the procedure is different. (The Command Mode entry character is set by COMMAND.) Three Command Mode entry characters must be entered less than 'n' seconds apart with no intervening characters, after a delay of 'n' seconds since the last characters were typed. After a final delay of 'n' seconds the TNC will exit Transparent Mode and enter Command Mode. You should then see the prompt cmd: the diagram below illustrates this timing. last first second third TNC terminal command command command now in input mode mode mode Command | entry entry entry Mode | character character character | | | | | | | | | | | |«longer than n»|«shorter than n»|«shorter than n»|«----n----»| @CMSg ON|OFF Default : OFF Display Group : I Parameters: ON - A text message is sent as the first packet after a connection is established. OFF - The message is not sent. CMSG enables automatic sending of the message set by CTEXT whenever your TNC accepts a connect request from another TNC. For example, if you have left your station running even though you don't want to operate just now, you might want to set CMSG ON to let people know that you can't talk when they connect to your TNC. When you are ready to operate your would set CMSG OFF. @CMSGDisc ON|OFF Default : OFF Display Group : I Parameters: ON - The packet controller will initiate a disconnect immediately after acknowledgement of the CTEXT sent by the CMSG feature. OFF - The packet controller will not initiate a disconnect associated with CMSG. This command controls whether the packet controller will initiate a disconnect after the packet containing connect text (CTEXT) is acknowledged. Use this command with care - If you receive connects, yet never get data, it is possible CMSGDisc has been left on. @COMmand n Default : $03 Display Group : C <CTRL-C> Parameters: n = 0 - $7F specifying an ASCII character code. This command is used to change the Command Mode entry character. You can enter the code in either hex or decimal. Command Mode is entered from Converse Mode when this character is typed. If you type the Command Mode entry character while you are already in Command Mode, nothing will happen. To see how this works, enter Converse Mode by typing CONVERS. Anything you type will become packet data. Now type a <CTRL-C>. You will see the Command Mode prompt indicating successful exit to Command Mode. the display might look like this: cmd: CONVERS Hello World! I'm on the air on packet radio [enter <CTRL-C>] cmd: See the command CMDTIME or the discussion of Transparent Mode for further information on how the Command Mode entry character is used to escape from Transparent Mode. @CONMode CONVERS|TRANS Display Group : L Parameters: CONVERS - Sets automatic entry to Converse Mode when a connection is established. TRANS - Sets automatic entry to Transparent Mode when a connection is established. CONMODE controls which mode the TNC will be placed in after a connection. The connection may result either from a connect request received over the air or a connect initiated by a CONNECT command that you issue. For most operations you would set CONMODE to CONVERS. However, if you are using Transparent Mode for a bulletin Board program, for example, you would set CONMODE to TRANS so that the correct mode will be entered when your bulletin board receives a connect request. If you initiate a connection with the CONNECT command, the timing of the entry into Converse or Transparent Mode is determined by NEWMODE. If the TNC is already in Converse or Transparent Mode when the connection is completed, the mode will not be changed. If you have typed part of a command line when the connection is completed, the mode change will not take place until you complete the command or cancel the line. This prevents the last part of your command from inadvertently being sent as a packet. @Connect call#1 [Via call#2[call#3...call#9]] Parameters: call#1 - Callsign of the TNC to be connected to. call#2 - Optional callsign of TNC to be digipeated through. As many as eight digipeat addresses can be specified. The part of the command line in brackets, VIA call2[,call3...,call9] is optional. The double-bracketed text, ,call3...,call9, is also optional, but would only be used if 'VIA call2' is present. The brackets should not be typed. Each callsign may include an optional sub-station ID specified as '-n' immediately following the callsign. The digipeat fields are specified in the order in which you want them to relay the packets to the destination, 'call1'. CONNECT is an immediate command. It initiates a connect request to TNC 'call1', optionally through digipeaters. If NEWMODE is on, the TNC will immediately enter Converse Mode or Transparent Mode, as specified by the command CONMODE. If NEWMODE is OFF, the TNC will enter Converse Mode or Transparent Mode when connection is successfully completed. An error message is returned if the TNC is in a connected state, or is already attempting to connect or disconnect. If no response to the connect request occurs after the number of attempts specified by RETRY, the command is aborted and a message typed. The TNC returns to Command Mode if NEWMODE is ON. If NEWMODE is OFF, the mode does not change, i.e. the TNC remains in Command Mode. For example, to connect to WA7GXD using N0ADI-1 (who is near your QTH) and WD0ETZ (who is near GXD's QTH) as digipeaters, you would type: CONNECT WA7GXD VIA N0ADI-1,WD0ETZ Packets coming back from WA7GXD access the digipeaters in the opposite order. Thus, packets from WA7GXD will first be repeated by WD0ETZ, then by N0ADI-1. @CONOk ON|OFF Default : ON Display Group : L Parameters: ON - Connect requests from other TNCs will be accepted OFF - Connect requests from other TNCs will be rejected This command determines the action taken by the TNC when a connect request for it is received through the radio. If CONOK is ON, the request will be acknowledged, the standard connect message will be typed and either Converse or Transparent mode will be entered, depending on the setting of CONMODE. If CONOK is OFF and the TNC is not in Transparent Mode, the TNC will notify you of the connect attempt with the following message: connect request: <call> The callsign of the station trying to connect will replace <call>. The TNC will also issue a DM packet, or "busy signal" to the requesting station. The user may then issue his own connect command. If your TNC receives a DM packet in response to a connect request, it will type the message: *** <call> station busy with the callsign of the station that sent the DM packet in place of <call>. For example, if you want to leave your station running as a digipeater you might set CONOK OFF until you are ready for a conversation. If you get a connect request in the meantime you can change your mind. Stations attempting to connect to your TNC will be able to see that the station is up but not available for connection (it might still be useful as a digipeater). @CONPerm ON|OFF Default : OFF Display Group : L Parameters: ON - The current connection on the current stream will not be allowed to enter the disconnected state. OFF - The current stream may be connected to and disconnected from other stations. This command when switched ON, forces the packet controller to always maintain the current connection, even when frames to the other stations exceed retry attempts to get an acknowledgement. RESTART will not affect this connected state. This command only takes effect when a connection is established. It functions on a stream-by-stream basis when multiple connections are allowed. @CONStamp ON|OFF Default : OFF Display Group : M Parameters: ON - Connect status messages are time stamped OFF - Connect status messages are not time stamped This command enables time stamping of *** CONNECTED status messages. The date and time information is then available for use by Bulletin Board programs or other computer applications. The date and time must be set initially by the DAYTIME command before time stamping will occur. The date format is determined by the DAYUSA command. For example, if CONSTAMP is ON, DAYUSA is ON and the date and time have been set, a connect message might appear as follows: *** CONNECTED to N2WX [05/28/85 16:28:31] @CONVers CONVERS is an immediate command, and will cause the TNC to exit from Command Mode into Converse Mode. Any link connections are not affected. Once in Converse Mode, everything you type is packetized and transmitted over the radio. Typing the Command Mode entry character returns the TNC to Command Mode. Note: You can replace the command CONVERS with the single letter 'K' @CPactime ON|OFF Default : OFF Display Group : T Parameters: ON - Packet timeout is used in Converse Mode. OFF -Packet timeout is not used in Converse Mode. This command enables the periodic automatic sending of packets in Converse Mode. This command may be used for computer communications, such as Bulletin Board operation, when the full transparent mode features are not desired. If CPACTIME is ON, characters are packetized and transmitted periodically as they are in Transparent Mode, but local editing and display features of Converse Mode are enabled, and software flow control may be used. For a discussion of how periodic packetizing works, see the command PACTIME, which controls the rate and mode of packet assembly. You should set CR OFF in this mode, since otherwise the send-packet character will be inserted in the data being packetized even though it was not typed. In order to include <CR> characters in transmitted packets, set SENDPAC to a normally unused character (e.g. <CTRL-P>), at which point the TNC will treat <CR> as an ordinary character. You can set CPACTIME ON for a mode of operation similar to full break-in CW, in which your text is transmitted soon after you type it, but in short bursts of a few characters, and the other station may break in at will. Some operators find it easier to carry on a conversation in this mode, since it eliminates the delays while long packets are being typed. @CR ON|OFF Default : ON Display Group : L Parameters: ON - The send-packet character, normally <CR>, is appended to all packets sent in Converse Mode. OFF - The send-packet character is not appended to packets. When CR is ON, all packets sent in Converse Mode will include, as the last character of the packet, the send-packet character which forces the packet to be sent. If CR os OFF, the send-packet character is interpreted solely as a command to the TNC, not as data to be included in the packet, and furthermore, it will not be echoed to the terminal. Setting CR ON and SENDPAC $0D resulted in a natural conversation mode. Each line is sent when a <CR> is entered, and arrives at its destination with a <CR> at the end of the line. If the station at the other end reports overprinting of lines on his display, you can set LFADD ON, or the other station can set AUTOLF ON. @CStatus CSTATUS is an immediate command which shows the stream identifier and link state of all ten streams (links), the current input and output streams, and whether or not each stream is "permanent" (See CONPERM). An example of a display resulting from issuing a CSTATUS command is: cmd:CS A stream - IO Link state is: CONNECTED to 305MLB B stream - Link state is: CONNECTED to AD7I P C stream - Link state is: DISCONNECTED D stream - Link state is: CONNECTED to N0ADI via K9NG-2 The example above shows the A stream is the currently selected or active stream for both input an output, which is indicated by the I and O symbols. The B stream is connected to AD7I "permanently". All other streams' states are shown as they might normally appear with multiple connections. cmd:CS A stream - IO Link state is: CONNECTED to 305MLB B stream - Link state is: CONNECTED to AD7I P C stream - Link state is: DISCONNECTED D stream - Link state is: CONNECTED to N0ADI via K9NG-2 -------- I stream - Link state is: CONNECT in progress J stream - Link state is: CONNECTED to KV7B via NK6K-1 @CText TEXT Default : "" Display Group : I Parameters: TEXT - Any combination of characters and spaces, up to a maximum of 120 characters. CTEXT specifies the text of the packet to be sent after a connection is made, if CMSG is ON. The default TEXT is an empty string, i.e., no message. You can send multiple-line messages by including carriage return (<CR>) characters in the text. The <CR> character can be included by using the PASS character immediately preceding it (see the PASS command). If you enter a TEXT string longer than 120 characters, an error message will appear and the command will be ignored. For example, you might set your CTEXT message to: I'm not here tight now, but you may leave a message To clear the CTEXT text without issuing a RESET command, use a % or & as the first character in the message. @DAytime date & time Parameters: date & time - Current date and time to set This command allows you to set the current date and time for the TNC. The format for entering the date and time is: yymmddhhmm where 'yy' is the last two digits of the year. 'mm' is the two-digit month code (01-12), 'dd' is date (01-31), 'hh' is the hour (00-23), and 'mm' is the minutes after the hour (00-59). All these codes must be exactly two digits, so that numbers from 0 to 9 must be entered with leading zeros. The TNC does not check thoroughly for the correct number of days in a month, so you should use some judgement when you set the date. The date&time parameter is used by the commands CONSTAMP and MSTAMP to "time stamp" received and monitored messages. Entries in the "heard" (displayed by MHEARD) are also time stamped continuously as long as it is powered up. You must reset the date and time each time you turn off the TNC. If you don't so this, the commands CONSTAMP and MSTAMP will not enable time stamping. If you type DAYTIME without a parameter, the TNC will display the current date&time. The format of the display is dd-mm-yy hh:mm if DAYUSA is OFF, and mm/dd/yy hh:mm if DAYUSA is ON. The format for entering date&time is not affected. For example, cmd:DAYTIME 8402291530 sets the date and time to February 29, 1984 at 3:30pm. The display of the date and time, with DAYUSA ON would be: cmd:DAYTIME 02/29/84 15:30:26 @DAYUsa ON|OFF Default : ON Display Group : M Parameters: ON - Date is displayed in the format mm/dd/yy OFF - Date is displayed in the format dd-mm-yy This command determines the format for the TNC's display of the date. If DAYUSA is ON, the standard U.S. format is used; if DAYUSA is OFF, the standard European format is used. This command affects the date display used in "time stamps" as well as the display when DAYTIME is entered without parameters. The format for entering the time using DAYTIME is not affected. For example, if DAYUSA is ON, the July 2, 1984 at 9:28:44 AM would be displayed as cmd:DAYTIME 07/02/84 9:28:44 If DAYUSA is OFF the same date and time would appear as cmd: DAYTIME 02-07-84 9:28:44 @DEAdtime n Default : 33 Display group : T n = 0 - 250 in 10ms increments DEAdtime specifies the time it takes a station's receiver to detect that a remote transmitter has been keyed. It should be set to the time of the SLOWEST acceptable radio on the channel. It must also allow for any squelch delays and DCD lock time. DWAIT and TXDELAY should also be set to this same value for everyone on the LAN. A fairly fast VHF FM radio and TNC might take 210ms (DEA 21), while an HF radio and TNCwill usually respond in 80ms (DEA 8). Some multi-mode radios and TNCs operating at 1200 bps may respond in only 40ms (DEA 4). The default value (DEA 33) will safely cover the majority of FM radios in common packet use. @DELETE ON|OFF Default : OFF Display Group : C Parameters: ON - The delete character input editing character is <DELETE> ($7F) OFF - The delete character input editing character is <BACKSPACE> ($08) This command is used to change the input editing command for character deletion. When this character is typed, the last character from the input line is deleted. How the TNC indicates the deletion is controlled by the BKONDEL command. You can not use this character to delete past the beginning of a line, although you can delete <CR> characters that have been entered in the test with the pass character. To see a corrected display of the current line after you have deleted characters, type the redisplay-line character, which is set by the REDISPLA command. @DIGipeat ON|OFF Default : ON Display Group : C Parameters: ON - The TNC will digipeat packets if requested OFF - The TNC will not digipeat packets When this parameter is ON, any packet received that has your callsign (including SSID) in the digipeat list of its address field will be retransmitted. Each station included in the digipeat list relays the packet in its turn, marking the packet so that it will not accidentally relay it twice (unless requested), and so that the stations will relay the packet in the correct order. In the spirit of cooperation typical of Amateur operation you will probably want to set DIGIPEAT ON most of the time. However, you might want to disable digipeating if you're not home, or if your transmit relay makes enough noise to wake you up at night. The command HID enables automatic transmission of identification packets if your station is acting as a digipeater. @DISCONNE DISONNE is an immediate command. It will initiate a disconnect request with the currently connected station. A successful disconnect results in the display of: *** DISCONNECTED Other commands may be entered while the disconnect is taking place, although connects are disallowed until the disconnect is completed. If the retry count is exceeded while waiting for the other side to acknowledge, the TNC moves to the disconnected state. If a disconnect command is entered while the TNC is disconnecting , the retry count is immediately set to the maximum number. In either case, the disconnect message is: *** retry count exceeded *** DISCONNECTED Disconnect messages are not displayed when the TNC is in Transparent Mode. @DISPLAY [class] Parameters: class - Optional parameter-class identifier, one of the following: ASYNC display asynchronous port parameters CHARACTE display special characters HEALTH display LED and TNC status ID display ID parameters LINK display link parameters MONITOR display monitor parameters TIMING display timing parameters DISPLAY is an immediate command, and with no CLASS parameter will cause all control parameters and their current values to be displayed. Sub-Groups of related parameters can be displayed by specifying the optional parameter-class. Individual parameters can be displayed by entering the parameter name with no options. @DWait n Default : 3 Display Group : I Parameters : n = 0 - 250 specifying default wait time in 10 ms intervals. This value is used to avoid collisions with digipeated packets. The TNC will wait the default wait time after last hearing data on the channel before it begins its own keyup sequence, unless the TNC is waiting to transmit digipeated packets. This value should be agreed on by all members of a local area when digipeaters are used in the area. the best value will be determined by experimentation, but will be a function of the keyup time (TXDELAY) of the digipeater stations. This feature is intended to help alleviate the drastic reduction in throughput that occurs on a channel when digipeated packets suffer collisions. It is necessary because digipeated packets are not retried by the digipeater, but must be restarted by the originating station. If all stations specify a default wait time, and the right value of 'n' is chosen, the digipeater will capture the frequency every time it has data to send, since digipeated packets are sent without delay. Do not set DWAIT to 0. @Echo ON|OFF Default : ON Display Group : A Parameters: ON - Characters received from the computer or terminal are echoed by the TNC. OFF - Characters are not echoed. This command controls local echoing from the TNC when it is in Command or Converse Mode. Local echoing is disabled in Transparent Mode. If you don't see your input on the display, you should set ECHO ON. If you see two copies of every character you type, you should set ECHO OFF. If you see the characters you type displayed correctly, you have ECHO set correctly. @EScape ON|OFF Default : OFF Display Group : A Parameters: ON - The <ESCAPE> character ($1B) is output as "$" ($24) OFF - The <ESCAPE> character is output as <ESCAPE> ($1B) This command specifies the character which will be output when an <ESCAPE> character is to be sent to the terminal. The <ESCAPE> translation is disabled in Transparent Mode. This command is provided because some terminals, and computer programs that emulate such terminals, interpret the <ESCAPE> character as a special command prefix. Such terminals may alter their displays depending on the characters that follow the <ESCAPE>. If you have such a terminal, you can protect yourself from unexpected text sequences and from other packeteers by setting ESCAPE ON. See also the MFILTER command, which allows general character stripping (rather than character translation) in monitored packets. @FIRMRnr ON|OFF Default : ON Display Group : L Parameters: ON - When this TNC's buffers fill, an RNR is sent. When the buffers are no longer full, an RR command frame is sent. When this TNC receives an RNR, it will not poll the sending TNC until [T0*10 seconds]. T0=CHECKtime*8 unless CHECKtime*8 is <30 or >253 in which case T0=12. OFF - When this TNC's buffers fill, an RNR is sent in response to an I frame. When this TNC receives an RNR, it will resend the data every FRACKtime (T1) until an RR is received. When OFF, standard AX.25 Level 2 Version 2.0 protocol procedures are used. If a TNC sending data receives an RNR, meaning the remote TNC cannot accept more data, the sending TNC will continuously re-send the data every T1 (FRACK) time until an RR is received, meaning the remote TNC accepted the data. This often results in a lot of unnecessary channel congestion. When FIRMRNR is ON, this TNC will stop sending data upon receipt of an RNR. If the remote TNC does not send an RR before [T0] (see above), this TNC will poll the remote TNC to be sure it is still active. If this TNC sent the RNR, then it will send an RR when its buffers have cleared to allow more data to be received. NOTE: The remote TNC should be capable of FIRMRNR operation. This mode is operable with all TNCs having a FIRMRNR settable to ON, and with most network nodes. If the remote TNC is not capable of FIRMRNR operation, and if the channel is poor, there will be additional delays in getting data passed between the TNCs. @FLOW ON|OFF Default : ON Display Group : A Parameters: ON - Type-in flow control is active. OFF - type-in flow control is disabled. When type-in flow control is enabled, any character entered from the terminal will halt output to the terminal until: (1) a packet is forced (in Converse Mode); (2) a line is completed (in Command Mode); (3) the packet length is exceed; or (3) the terminal output buffer fills up. Cancelling the current command or packet or typing the redisplay character will also cause output to resume. type-in flow control is not used in Transparent Mode. setting FLOW ON will keep received data from interfering with data entry. If you ( and the person you are talking to) wait for a packet from the other end before starting to respond, you can set FLOW OFF. Some Bulletin Board programs may work best with FLOW OFF. Some computers with "software UARTs" may be unable to send and receive data at the same time; users of such computers should set FLOW ON. @FRack n Default : 8 Display Group : T Parameters: n = 1-15, specifying frame acknowledgment timeout in 1 second intervals. After transmitting a packet requiring acknowledgment, the TNC will wait for the frame acknowledgment timeout before incrementing the retry counter and sending the frame again. If the packet address includes relay requests, the time between retries will be adjusted to: Retry interval = n * (2*m + 1) where 'm' is the number of relay stations. When a retried packet is sent, a random time is added to any other wait times in use. This is to avoid lockups in which two TNCs repeatedly send packets which collide with each other. @FULLDUP ON|OFF Default : OFF Display Group : L Parameters: ON - Full duplex mode is enabled OFF - Full duplex mode is disabled When full duplex mode is disabled, the TNC makes use of the Data Carrier Detect signal from the modem to avoid collisions, and acknowledges multiple packets in a single transmission with a single acknowledgment. When full duplex mode in enabled, the TNC ignores the DCD signal and acknowledges packets individually, such as through OSCAR 10. It should not be used unless both your station and the station you are communicating with are full-duplex stations. You may find full-duplex mode useful for some testing operations, such as analog or digital loopback tests. @HEaderln ON|OFF Default : OFF Display Group : M Parameters: ON - The header for a monitored packet is printed on a separate line from the packet text. OFF - The header and packet text of monitored packets are printed on the same line. This command affects the display format for monitored packets. If HEADERLN is OFF, the address information is displayed with the packet: KV7D>N2WX: Go ahead and transfer the file. If HEADERLN is ON, the address information is displayed, followed by the packet text on a separate line: N2WX>KV7D: Sorry, I'm not quite ready yet. If you have set MRPT ON or enabled MSTAMP, you may wish to set HEADERLN ON, as the packet header quickly becomes long enough to fill a screen when these functions are active. @HEAlled ON|OFF Default : OFF Display Group : H Parameters: ON - The packet controller will "dither" the CON and STA LEDs. OFF - The packet controller will control the CON and STA LEDs in normal fashion. This command allows the user to redifine the functions of the two CPU controllable LEDs (i.e. the STAtus and the CONnect LEDs). When HEALLED is set ON, the two LEDs flash in an alternate fashion. The LEDs will probably not flash if the software is not operating correctly. With HEALLED set OFF, the LEDs function in their normal fashion, indicating the presence of a connection and whether unacknowledged frames exist. @HId ON|OFF Default : OFF Display Group : I Parameters: ON - Enables HDLC identification by a digipeater OFF - Disables HDLC identification This command is issued to enable or disable the sending of identification packets by the TNC. If HID is OFF, the TNC will never send an identification packet. If HID is ON, the TNC will send an identification packet every 9.5 minutes IF THE STATION IS DIGIPEATING PACKETS. the ID command allows the operator to send a final identification packet if the station is being taken off the air. An identification consists of an unsequenced I frame whose data field is your station identification. the identification packet is addressed to the "CQ" address set by the UNPROTO command. Your station identification is your callsign as set by MYCALL, with /R appended. @ID ID is an immediate command. It will send a special identification packet. ID can be used to force a final identification packet to be sent as a digipeater station is being taken off the air. The identification packet will be sent only if the digipeater has transmitted since the last automatic identification. An identification consists of an unsequenced I frame whose data field is your station identification. The identification packet is addressed to the "CQ" address set by the UNPROTO command. Your station identification is your callsign as set by MYCALL, with "/R" appended. @KISS ON/OFF Default : OFF Display Group : L Parameters: ON - Serial Line Interface Protocol (SLIP) is used between the TNC and the attached computer. The TNC executes a very limited instruction set arbitrating channel access only and, depending on the computer, to handle all Level 2 and higher protocol issues. OFF - The TNC operates using the commands and messages contained in this version of firmware. This command is used to enter the KISS mode for operation with various experimental protocols. KISS is used with intelligent computers. The most popular use has been with the KA9Q TCP/IP networking software. To operate KISS with this version, enter the command KISS ON, then the command RESTART (*NOT* RESET). The CON and STA LEDs will flash three times when initially activated. The command will then have effect for subsequent power on/off cycles. To return to normal operation, enter the command PARAM <device> 255 at the NET> prompt if you are running the KA9Q TCP/IP software. If you are not using this software, send the three bytes $C0, $FF, $C0 to the TNC to restore normal operation. If you cannot send these characters with the software you are using, you must power the TNC off, disconnect the bbRAM battery for several minutes, then reconnect the battery and power up again to restore normal operation. The commands available in KISS mode are: Command Function Comments 0 Data frame The rest of the frame is data to be sent. 1 TXDELAY The next byte is the transmitter keyup time in 10ms units. Default is 50 (500ms). 2 P The next byte is the persistence parameter, P, scaled to the range 0 - 255. The probability of transmitting at the next opportunity is P/255. Default is 64 (probability of 0.25). 3 Slot time The next byte is the slot interval in 10ms units. Default is 10 (100ms). 4 Tx Tail The next byte is the time to hold the transmitter after the FCS has been sent, in 10ms units. The command is obsolete but is included for completeness with earlier versions. 5 Full Duplex The next byte is 0 for half duplex (normal) or any other number for full duplex (e.g. for MicroSat operation). FF Return Exit KISS mode and resume normal TNC operation. NOTE The TNC will only return type 0 frames (received information). Thus the computer cannot interrogate the TNC to find the values of other command types. @LCAlls call#1[,call#2...,call#8] Parameters: call - Callsign list. Up to 8 calls, separated by commas. Each callsign may include an optional Sub-Station ID specified as '-n' immediately following the call. This command works in conjunction with BUDLIST and allows selective monitoring of other stations packets. These two commands determine which packets will be displayed when you have MONITOR ON. BUDLIST specifies whether the callsigns in the list are the ones you want to ignore or, alternatively, are the ones you want to listen to. If you want to listen only for packets from a limited list, you should enter your selected list with LCALLS and set BUDLIST ON. If you want to ignore packets from a limited list, you should list the callsigns to ignore in LCALLS and set BUDLIST OFF. @LCok ON|OFF Default : ON Display Group : A Parameters: ON - The TNC will send lower case characters to the computer or terminal. OFF - The TNC will translate lower case characters to upper case. If LCOK is OFF, lower case characters will be translated to upper case before being output to the terminal. This case translation is disables in Transparent Mode. Input characters and echoes are not translated. If your terminal or computer does not accept lower case characters it may react badly if the TNC sends such characters to it. This command allows you to translate all lower case characters received in packets, as well as messages from the TNC, to upper case. Since echoes of the characters are NOT translated to upper case, you can use this command to make your display easier to read when you are conversing in connected mode. If you and the other stations operator set LCOK OFF, you can each type your messages in lower case an see incoming packets displayed in upper case. It will then be easy to distinguish incoming and outgoing packets. @LCStream ON|OFF Default : ON Display Group : C Parameters: When LCSTREAM is ON, the character immediately following the STREAMSWITCH character is converted to upper case before being acted upon. When off, the case is insignificant. @LFADD ON|OFF Default : OFF Display Group : L Parameters: ON - A <LF> character is added to outgoing packets following each <CR> transmitted in the packet. OFF - No <LF> is added to outgoing packets This function is similar to AUTOLF, except that the <LF> characters are added to outgoing packets rather than to text displayed locally. This feature is included in order to maintain compatibility with other packet Radio Controllers. If the person you are talking to reports overprinting of packets from your station you should set LFADD ON. This character insertion is disabled in Transparent Mode. @LFIgnore ON|OFF Default : OFF Display Group : L Parameters: ON - Line feed characters are ignored in COMMAND and CONVERSE modes. OFF - Line feed characters are acted upon in COMMAND and CONVERSE modes. This command controls whether the packet controller responds to ASCII line feed ($0A) characters or ignores them in COMMAND and CONVERSE modes. When turned ON, line feeds are totally ignored except in Transparent Mode. When turned OFF, line feeds are processed normally. The LFIGNORE command is useful when incoming data has imbedded line feed characters that cause double spacing of the data on your screen or printer. NOTE: See the LFADD command description. The transmitting station may have the LFADD command set ON inadvertently. @MAll ON|OFF Default : ON Display Group : M Parameters: ON - Monitored packets include both "connected" and "unconnected" packets OFF - Monitored packets include only "unconnected" packets This command determines the class of packets which are monitored. If MALL is OFF, only otherwise eligible packets (as determined by the BUDLIST and LCALLS commands) sent by other TNCs in the unconnected mode are displayed. This is the normal manner of operation when this TNC is being used to talk to a group of TNCs all of which are unconnected. If MALL is ON, all otherwise eligible frames are displayed, including those sent between two other connected TNCs. This mode may be enabled for diagnostic purposes or for "reading the mail". @MAXframe n Default : 4 Display Group : L Parameters: n = 1 - 7, signifying a number of packets MAXFRAME sets an upper limit on the number of unacknowledged packets which the TNC can have outstanding at any one time. This is also the maximum number of contiguous packets which can be sent during any given transmission. If some but not all of the outstanding packets are acknowledged, a smaller number may be transmitted next time, or new frames may be included in the retransmission, so that the total unacknowledged does not exceed 'n'. If you perform file transfers, you should experiment with MAXFRAME and PACLEN. If the link is good, there is an optimum relationship between parameters set by these commands so that the maximum numbers of characters outstanding does not exceed the packet receive buffer space of the TNC receiving the data. @MCOM ON|OFF Default : OFF Display Group : M Parameters: ON - Connect, disconnect, UA and DM frames are monitored. OFF - Only information frames are monitored. This command enables monitoring of connect and disconnect frames when MONITOR is ON. When MCOM is OFF, only I frames (packets containing user information) will be displayed. When MCOM is ON four protocol packets will also be displayed. Connect, disconnect, UA and DM packets that are monitored are indicated by <C>, <D>, <UA> and <DM> respectively. As with other monitor commands, the stations monitored are determined by BUDLIST and LCALLS. @MCon ON|OFF Default : ON Display Group : M Parameters: ON - Monitor mode remains active when TNC is connected. OFF - Monitor mode is off while the TNC is connected. If MCON is ON, the MONITOR command will enable monitoring while your TNC is connected to another TNC. If MCON is OFF, the display of monitored packets is suspended when a connect occurs, and is resumed when the TNC is disconnected. @MFilter n1[,n2[,n3[,n4]]] Parameters: n = 0 - $7F, specifying an ASCII character code . Up to 4 characters may be specified. This command allows you to specify characters to be "filtered", or eliminated from monitored packets. The parameters 'n1,' 'n2,' etc., are the ASCII codes for the characters you want to filter. You can enter the code in either hex or decimal. For example, if a <CTRL-L> character causes your screen to be cleared, and you don't want this to happen, you can set MFILTER 12. If you also want to eliminate <CTRL-Z> characters, which some computers interpret as end-of-file markers, you can set MFILTER 12, 26. @MHClear MHCLEAR is an immediate command. It causes the list of stations heard to be cleared. You can use this command in conjunction with MHEARD to keep track of the stations on the air over a given period of time, such as an evening or a week. Clear the list of stations heard when you first begin to monitor the packet activity. @MHeard MHEARD is an immediate command. It causes the TNC to display the list of stations that have been heard since the last time the command MHCLEAR was given. Stations that are heard digipeating are marked with an * in the heard log. If you clear the list of stations heard at the beginning of a session, you can use this command to easily keep track of the stations that are active during that period. The maximum number of heard stations that can be logged is 18. If more stations are heard, earlier entries are discarded. Logging of stations heard is disabled when PASSALL is ON. If the DAYTIME command has been used to set the date and time, entries in the heard log will be time stamped. For example, cmd:MHEARD K4NTA* O6/09/86 21:08:19 KC2FF-7* 06/09/86 21:08:17 W1BEL-2* 06/09/86 21:06:18 WD4AOQ 06/09/86 20:59:38 N2WX cmd: Note that no daytime string is displayed next to N2WX. This indicates that when N2WX was last heard the clock had not been set. @MNonax25 ON|OFF Default : OFF Display Group : M Parameters: ON - Monitors all frames with valid CRC. OFF - Monitors AX.25 Level 2 Protocol frames with no higher-level protocols (PID = F0). When OFF, only AX.25 Level 2 protocol frames will be displayed. Any packets with level 3 or level 4 protocols will be inhibited. Thus, NET/ROM, TCP/IP, ROSE, etc., networking frames will not be displayed. These frames often have binary values buried in them which cause undesirable responses on a normal screen display. When ON, any packet or frame with a valid CRC will be displayed regardless of protocol. @Monitor Default : ON Display Group : M Parameters: ON - Monitoring of packet activity is enabled. OFF - Monitoring of packet activity is disabled. If MONITOR is ON and the TNC is not in Transparent Mode, packets not addressed to your TNC may be displayed. The addresses in the packet are displayed along with the data portion of the packet, e.g.: N2WX>W5FD-3: I'm ready to transfer the file now. The calls are separated by a ">" and the sub-station ID field (SSID) is displayed if it is other than 0. The MALL, BUDLIST, and LCALLS commands determine which packets are to be monitored. The MCON command controls the action of monitor mode when the TNC is connected. All monitor functions are disabled in Transparent Mode. The format of the monitor display is controlled by HEADERLN. If you want to see the station addresses on a separate line from the text, you can set HEADERLN ON. MRPT enables monitoring of the digipeater route as well as source and destination addresses for each packet. MSTAMP includes a time stamp with the addresses if DAYTIME has been set. @MRpt ON|OFF Default : ON Display Group : M Parameters: ON - Displays the stations in the digipeat path for monitored packets. OFF - Display only the source and destination stations for monitored packets. This command affects the way monitored packets are displayed. If MRPT is OFF, only the originating station and the destination are displayed for monitored packets. If MRPT is ON, the entire digipeat list is displayed for monitored packets, and stations that have already relayed the packet are indicated with an asterisk. For example, WB9FLW>AD7I,K9NG*, N2WX-7:Hi Paul. This packets, sent from WB9FLW to AD7I, has been relayed by K9NG but not N2WX-7. With MRPT OFF, the same packet would be displayed as, WB9FLW>AD7I:Hi Paul. Setting MRPT ON increases the length of the address display, and you may wish to set HEADERLN ON as well to display this information on a separate line. @MStamp ON|OFF Default : OFF Display Group : M Parameters: ON - Monitored frames are time stamped. OFF - Monitored frames are not time stamped. This command enables time stamping of monitored packets. The date and time information is then available for use for automatic logging of packet activity or other computer applications. The date and time are initially set by the DAYTIME command, and the date format is determined by the DAYUSA command. Setting MSTAMP ON increases the length of the address display, and you may want to set HEADERLN ON as well to display this information on a separate line. @MYAlias call[-n] Display Group : I Parameters: call - Alternate identity of your TNC. 'n' = 0 -15, an optionally specified sub-station ID (SSID). This command specifies an alternate callsign (in addition to the callsign specified in MYCALL) for use a digipeater ONLY. Use of this command permits HID to identify normally with the MYCALL-specified callsign, yet permits an alternate (alias) repeat-only "callsign". @MYcall call[-n] Default : NOCALL Display Group : I Parameters: call - Callsign of your TNC. n = 0-15 - An optionally specified sub-station ID (SSID) This command tells the TNC what its callsign is. This callsign will be placed in the FROM address field for all packets originated by your TNC. It will accept frames with this callsign in the TO field and relay frames with this callsign in the digipeat field. MYCALL will also be used for identification purposes (see HID and ID). The default callsign MUST be changed for proper operation of the protocols. There should never be more tan one station with the same callsign (including SSID) on the air at once. The SSID can be used to distinguish two stations with the same Amateur call. The SSID will be 0 unless explicitly set to another value. @NEwmode ON|OFF Default : OFF Display Group : L Parameters: ON - Switching to data transfer mode occurs at the time of the CONNECT command and return to Command Mode is automatic at the time of disconnection. OFF - Switching to data transfer mode occurs at time of connection and no return to Command Mode occurs at disconnection. The NEWMODE command may be used to select the way the TNC behaves when connections are made and broken. If NEWMODE is OFF, the TNC will remain in Command Mode after you issue a CONNECT command until a connection is actually established. When the connection is established, the TNC will enter Converse Mode or Transparent Mode, depending on the setting of CONMODE. When the connection is terminated, the TNC remains in Converse or Transparent mode unless you have forced it to return to Command Mode. This is the same as the behaviour of TNC1 (running 3.x software) under these conditions. If NEWMODE is ON, the TNC will enter Converse Mode or Transparent Mode as soon as you issue a CONNECT command, without waiting for the connection to be established. Anything you type will be packetized to be transmitted once the connection is complete. When the connection is broken, or if the connect attempt fails, the TNC will return to Command Mode. If you have a Bulletin Board program designed to work with a TNC1 you should set NEWMODE OFF if the program relies on the sequence of actions used by TNC1. Otherwise, you should choose the setting for NEWMODE that seems most convenient to you. @NOmode ON|OFF Default : OFF Display Group : L Parameters: ON - The controller will switch modes (Command, Converse or Transparent) upon explicit command. OFF - The packet controller will switch modes in accordance with the setting of NEWMODE> When NEWMODE is ON, the TNC will -NEVER- jump on its own between CMD: and CONVERSE or TRANSPARENT mode or vise versa. Only user commands <CONV, TRANS, or ^C) will change the type-in mode. If the NEWMODE parameter is OFF then mode jumping is handled according to NEWMODE and the Rev 1 or Rev 2 TNC2 System manual. @NUcr ON|OFF Default : OFF Display Group : A Parameters: ON - <NULL> characters are sent to the terminal following <CR> characters. OFF - <NULL> characters are not sent to the terminal following <CR> characters. This command causes transmission of <NULL> characters (ASCII code $00), producing an effective delay following any <CR> sent to the terminal. The number of <NULL> characters is determine by the command NULLS. This delay is required by some hardcopy terminals. You need to set NUCR ON if your terminal misses one or more characters after responding to a <CR>. See also, NULLS. @NULf ON|OFF Default : OFF Display Group : A Parameters: ON - <NULL> characters are sent to the terminal following <LF> characters. OFF - <NULL> characters are not sent to the terminal after <LF> characters. This command causes transmission of <NULL> characters (ASCII code $00), producing an effective delay following any <LF> sent to the terminal. The number of <NULL> characters is determined by the command NULLS. This delay is required by some display terminals. You need to set NULF ON if your terminal sometimes misses characters at the beginning of the line. See also, NULLS. @NULLs n Default : 0 Display Group : A Parameters: n = 0 - 30, the number of <NULL>s to be added after <CR> or <LF> This command specifies the number of <NULL> characters (ASCII code $00) to send to the terminal after a <CR> or <LF> is sent. In addition to setting this parameter value, NUCR and/or NULF must be set to indicate whether nulls are to be sent after <CR>, <LF>, or both. Devices requiring nulls after <CR> are typically hardcopy devices requiring time for carriage movement. Devices requiring nulls after <LF> are typically CRTs which scroll slowly. Extra null characters are sent only in Command and Converse Modes. @PACLEN n Default : 128 Display Group : L Parameters: n = 0 - 255, specifying the maximum length of the data portion of a packet. The value 0 is equivalent to 256. The TNC will automatically transmit a packet when the number of input bytes for a packet reaches 'n'. This value is used both in Converse and Transparent Modes. @PACTime EVERY|AFTER n Display Group : T Parameters: EVERY - Packet timeout occurs EVERY n*100 milliseconds AFTER - Packet timeout occurs when n*100 milliseconds elapse with no input from the computer or terminal. n = 0 - 250, specifying 100 ms intervals. This parameter is always used in Transparent Mode, and will be used in Converse Mode if CPACTIME is ON. When EVERY is specified, input bytes are packetted and queued for transmission every n*100ms. When AFTER is specified, bytes are packaged when input from the terminal stops for n*100ms. In no case will a zero length packet be produced, and the timer is not started until the first byte is entered. If n=0, packets are generated with no wait time. @PARity n Default : 3 Display Group : A Parameters: n = 0 - 3, selecting a parity option according to the following code: 0=none, 1=odd, 2=none, 3=even. This command sets the parity mode for terminal or computer data transfer. The parity bit, if present, is automatically stripped on input and not checked in Command Mode and |Converse Mode. In Transparent Mode, all eight bits, including parity if any, are transmitted in packets. If "no parity" is set and AWLEN is 7, the eighth bit will be set to 0 in Transparent Mode. @PASs n Default : $16 Display Group : C <CTRL-V> Parameters: n = 0 - $7F, specifying an ASCII character code. This command selects the ASCII character used for the "pass" input editing command. The parameter 'n' is the ASCII code (hex or decimal) for the character typed in order to include the following character in a packet or text string. You can use the character in a packet to send ANY character in packets, even though that character may have some special function for the TNC. A common use for the PASS character is to allow <CR> to be included in the BTEXT and <CTEXT> messages. Similarly, you can include <CR> in text when you are in Converse MOde, to send multi-line packets. (The default send-packet character is <CR>) @PASSAll ON|OFF Default : OFF Display Group : L Parameters: ON - The TNC will accept packets with invalid CRCs. OFF - The TNC will only accept packets with valid CRCs. This command causes the TNC to display packets received with invalid CRC fields if they consist of an even multiple of 8 bits and up to 339 bytes. The TNC will attempt to decode the address field and display the callsign(s) in the standard monitor format, followed by the text of the packet. If you set PASSALL ON and monitor a moderately noisy channel you will periodically see "packets" received with errors from random noise. Logging of stations heard (for display of MHEARD) is disabled whenever PASSALL is ON, since the callsigns detected may be incorrect. @RECOnnect call#1 [VIA call#2[,call#3...,call#9]] Parameters: call#1 - Callsign to be reconnected to. call#2 - Optional callsign(s) to be digipeated through. RECONNECT is an immediate command. It may be used to change the path through which you are currently connected to a station. It may only be used when your TNC is connected on the current stream to a station to which you wish to RECONNECT. The integrity of the outstanding frames at the time of RECONNECT is not assured. For details regarding the parameter list see the CONNECT command. @REDispl n Default : $12 Display Group : C <CTRL-L> Parameters: n = 0 - $7F, specifying an ASCII character code. This command is used to change the redisplay-line editing character. The parameter 'n' (hex or decimal) is the ASCII code for the character you type in order to redisplay the current input line. When you type the redisplay-line character type-in flow control is temporaily released (if it was enabled), displaying any incoming packets that are pending. Then a <BACKSLASH> character is typed and the line you have begun is retyped on the next line. If you have deleted and retyped characters, only the final form of the line will be shown. You are now ready to continue typing. Use the redisplay-line character to see a "clean" copy of your input with a printing terminal after deleting characters. If you have BKONDEL OFF, deletions are designated with <BACKSLASH> characters, rather than by trying to correct the input line display. You can also use this character if you are typing in a message in Converse Mode and a packet comes in. You can see the incoming message before you send your packet, without cancelling your input. @RESET This is an immediate command. It resets all the parameters to default settings and re-initalizes the TNC. WARNING! - All parameter and monitor lists are lost. If you want to re-initalize the TNC using the parameter values in battery backed-up RAM, use the RESTART command or turn the TNC off then on. @RESPTIME n Default : 0 Display Group : T Parameters: n = 0 - 250, specifying 100ms increments. This command sets a minimum delay that is imposed on acknowledgement packets. This delay may run concurrently with default wait set by DWAIT and any random wait in effect. This delay may be used to increase throughput during operations such as file transfer when the sending TNC usually sends the maximum number of full length packets. Occasionally, the sending TNC may not have a packet ready in time to prevent transmission from being stopped temporarily, with the result that the acknowledgement of earlier packets collides with the final packet of the series. If the receiving TNC sets RESPTIME to 10, these collisions will be avoided. @RESTART RESTART is an immediate command. It re-initializes the TNC using the defaults stored in bbRAM. The effect of this command is the same as turning the TNC OFF then ON again. RESTART does not cause a reset of the parameters in bbRAM. See also RESET. @REtry n Default : 10 Display Group : L Parameters: n = 0 - 15, specifying the maximum number of retransmissions. The protocol allows for retries, i.e., retransmissions of frames that are not acknowledged. Frames are re-transmitted 'n' times before the operation is aborted. A value of 0 for 'n' specifies an infinite number of retries. If the number of retries is exceeded, the TNC goes to the disconnected state (with an informative message if not in Transparent Mode). See also the FRACK command. @RXblock ON|OFF Default : OFF Display Group : A Parameters: ON - The TNC will send data to the terminal in RXBLOCK format. OFF - The TNC will send data to the terminal in standard format RXBLOCK is designed for automated operations such as Bulletin Board stations. It is intended to help such systems discriminate between data received from the connected station and TNC generated messages. Correct operation of RXBLOCK is dependant upon the AWLEN parameter getting set to 8 (bits) since the character FF hex marks the beginning of a received data unit header. When RXBLOCK is ON, data from other stations will be sent from the TNC in the following format: +------------------------------------------------+ | $FF | L0 | L1 | PID | DATA | +------------------------------------------------+ (Prefix) (Length) (Pid) (Data) The fields above are defined as follows: Prefix $FF ::= A character with all 8 bits set Length L0 ::= The high order data length, length and pid fields logically ORed with $F0 L1 ::= The low order data length, length and pid fields Pid PID ::= The Protocol IDentifier byte received for the following data field Data DATA ::= [optional], variable length data For best operation it is suggested that parameters like AUTOLF, MFILTER etc. be set OFF in order to prevent uncertainties in the size of the data field. @RXCAL Display Group : NONE RXCAL is an immediate command. It is used for precise alignment of the demodulator. Briefly, after the modulator tones are set using the normal CALIBRATE routines, analog loopback is entered and RXCAL issued. You then tune the demodulator until the CON and STA LEDs are both lit, or slowly alternate. See the section New Calibration Procedures for details on using this command with a TAPR TNC 2. @Screenln n Default : 0 Display Group : A Parameters: n = 0 - 255, specifying the screen or platen width of the terminal in characters. This command i used to properly format terminal output. A <CR><LF> sequence is sent to the terminal in Command and Converse Modes after 'n' characters have been sent. A value of zero inhibits this action. If your computer automatically formats output lines, you should set SCREENLN 0 to avoid conflict. @SEndpac n Default : $0D Display Group : C <CR> Parameters: n = 0 - $7F, specifying an ASCII character. This command selects the ASCII code (parameter 'n') for the character that will force input to be packetized and queued for transmission in Converse Mode. You can enter the code in either hex or decimal. For ordinary conversation, you willprobably set SENDPAC $0D and CR ON. This causes the <CR> to be included in the packet. If you have set CPACTIME ON, you will probaly set SENDPAC to some value not normally used (say <CTRL-A), and set CR OFF. This will allow you to force packets to be sent, but will not result in extra <CR> characters being transmitted in the text. @SLots n Default : 3 Display Group : L Parameters: n = 0-127 SLOTS specifies the number of "slots" from which to choose when deciding to access the channel. For example, SLOTS 3 means there are three slots, each having a probability of 1/3 to be selected. Each slot is DEADTIME long. If SLOTS 0 is chosen, the TNC will act as if SLOTS 1 had been selected. Other implementations of this idea of channel access use "PERSISTENCE" to decide the probability of channel access when the channel is clear and "PPERSISTENCE" to enable or disable this feature. A low value means a greater chance of attempting to send data when the channel is clear, and a higher value means less chance. Normal AX.25 practice is to have every station jump on the channel when it goes clear, virtually assuring collisions and retries. SLOTS and its relation to the more common PPERSISTENCE and PERSISTENCE commands are given below: SLOTS PPERSISTENCE PERSISTENCE Probability to XMIT 1 OFF 255 Jump on = 100% 2 ON 127 50% 3 ON 85 33% 4 ON 63 25% 5 ON 51 20% and so forth. A typical value would be 2 or 3 for a channel with a few other users and 5 to 7 for a fairly busy channel. Higher values than about 10 imply the channel is too busy and other frequencies should be used if available. NOTE: SLOTS is independent of ACKPRIOR. @STArt n Default : $11 Display Group : C <CTRL-Q> Parameters: n = 0 - $7F, specifying an ASCII character code. This command selects the User restart character which is used to restart output from the TNC to the terminal after it has been halted by typing the stop character. You can enter the code in either hex or decimal. The user stop character is set by the STOP command. If the User Restart and User Stop characters are set to $00, software flow control to the TNC is disabled, and the TNC will only respond to hardware flow control (CTS). If the same character is used for both User Restart and User Stop characters the TNC will alternately start and stop transmission upon receipt of the characters. @STATUS STATUS is an immediate command. It returns the acknowledged status of the current outgoing packet link buffer. If all outgoing packets are acknowledged, STATUS returns 'No Outstanding packets', otherwise it returns the 'Outstanding packets' message. Note that this command works independently of the RS-232 flow-control state of the TNC. This command may be useful for special applications, like if you can't see the STATUS LED on the TNC, or you want your computer to watch the status. @STOp n Default : $13 Display Group : C <CTRL-S> Parameters: n = 0 - $7F, specifying an ASCII character. This command selects the User Stop character, which is used to stop output from the TNC to the terminal. This is the character used to halt the TNCs output and stop scrolling. Output is restarted with the User Restart character, which may be set using the START command. If the User Restart and User Stop characters are set to $00, software flow control to the TNC is disabled, and the TNC will only respond to hardware flow control (CTS). If the same character is used for both User Restart and User Stop characters the TNC will alternately start and stop transmission upon receipt of the characters. @STREAMCa ON|OFF Default : OFF Display Group : C Parameters: ON - Callsign of other station is displayed. OFF - Callsign of other station is not displayed. This command is used to enable the display of the connected-to station after the stream identifier. This is particularly useful when operating with multiple connections allowed. It is somewhat analogous to the use of MRPT to show digipeat paths when monitoring. In the example below, the characters inserted by STREAMCALL are clearly seen: STREAMCAll ON STREAMCAll OFF |A:K4NTA:Hi Howie |A Hi Howie Hello Ted how goes it? Hello Ted how goes it? |B:N7CL:*** CONNECTED to N7CL |B *** CONNECTED to N7CL |B:Ted, AZ on other stream |B Ted, AZ on other stream Thus, what looked like "|B" now appears as "|B<Callsign>:". This option is very useful for human operators trying to operate multiple simultaneous connections. It is probably less useful for "host" operations. Note that, in the first example the STREAMSWitch characters "|A" and "|B" with no ":" after them were entered by the operator of the TNC to switch streams for his multiple-connect QSO(s). If you intend to operate multiple connections (as opposed to having your "host" computer operate multiple connections), use of this option is recommended. @STREAMDbl ON|OFF Default : OFF Display Group : C Parameters: ON - Double all received STREAMSWITCH characters. OFF - Do not "double" received STREAMSWITCH characters. This command is used to display received STREAMSWitch characters by "doubling" them. The example below illustrates this action. With STREAMDbl ON, and STREAMSWitch set to"|", the following might be displayed from your TNC: ||this is a test In this case the sending station actually transmitted |this is a test The same frame received with STREAMBbl OFF would be displayed as: |this is a test When operating with multiple connections, this is useful for differentiating between STREAMSWitch characters received from other stations and STREAMSWitch characters internally generated by your TNC. NOTE: The STREAMSWitch character must NOT be one of the letters A-J for this command to function properly. @STREAMSWitch n Default : $7C Display Group : C <|> Parameters: n = 0 - $FF specifying the ASCII character. This command selects the character used by both the TNC and the user that a new "stream" (connection channel) is being addressed. The character can be PASSed in CONVERS mode. It is always ignored as a user-initiated stream switch in TRANSPARENT mode, and flows through as data. This means that the outgoing stream can not be changed while "on-line" in TRANSPARENT Mode (you must escape to COMMAND mode to switch streams). For further usage of the character, see the STREAMDbl and STREAMCAll commands. @TRACE ON|OFF Default : OFF Display Group : L Parameters: ON - Trace mode is enabled. OFF - Trace mode is disabled. This command is used to enable the protocol debugging function. When TRACE is ON, all received frames will be displayed in their entirety, including all header information. In normal operation you would probably never need this function; however,, if you need to report an apparent software bug, we may ask you to provide trace information if possible. A trace display will appear in four columns on an 80 column display. Following is an example trace display. For comparison, the frame shown in the trace example would be monitored as follows: KV7B>CQ,KF7B*:this is a test message The trace display would look something like this: byte ------------hex display------------ -shifted ASCII-- ------ASCII----- 000: 86A24040 40406096 AC6E8440 4060968C CQ OKV7B OKF ..@@@@'..n.@@'.. 010: 6E844040 E103F074 68697320 69732061 7B P.x:449.49.0 n.@@...this is a 020: 20746573 74206D65 73736167 650D :29:.6299032. test message. The 'byte' column shows the offset into the packet of the line. The 'hex display' column shows the next 16 bytes of the packet, exactly as received, in standard hex format. The 'shifted ASCII' column attempts to decode the higher order seven bits of each byte as an ASCII character code. The ASCII column attempts to decode the low order 7 bits of each byte as an ASCII character code. In a standard AX.25 packet the callsign address will be displayed correctly in the shifted ASCII column. A text message will be displayed correctly in the ASCII column. Non-printing characters and control characters are displayed in both ASCII fields as ".". You can examine the hex display field to see the contents of the sub-station ID byte and the control bytes used by the protocol. @Trans This is an immediate command. It causes the TNC to exit from Command Mode into Transparent Mode. The current link state is not affected. Transparent Mode is primarily useful for computer communications. In this mode the "human interface" features such as input editing capability, echoing of input characters, and type-in flow control are disabled. @TRFlow ON|OFF Default : OFF Display Group : A Parameters: ON - Software flow control can be enabled for the computer or terminal in Transparent Mode. OFF - Software flow control is disabled for the computer or terminal in Transparent Mode. If TRFLOW is ON, the settings of START and STOP are used to determine the type of flow control used in Transparent Mode. If TRFLOW is OFF, only hardware flow control os available to the computer and all characters received by the TNC are transmitted as data. If START and STOP are set to $00, disabling the User Stop and User Restart characters, hardware flow control must always be used by the computer. If TRFLOW is ON, and START and STOP are non-zero, software flow control is enabled for the users computer or terminal. The TNC will respond to the User's Restart and Users Stop characters (set by START and STOP) while remaining transparent to all other characters from the terminal. Unless TXFLOW is also ON, only hardware flow control is available to the TNC to control output from the terminal. @TRIES n Default : NONE Display Group : L Parameters: n = 0-15, specifying the current RETRY level on the currently selected input stream. This command is used to retrieve (or force) the count of "tries" on the currently selected input stream. When used with no argument: if the TNC has an outstanding unacknowledged frame, it will return the current number of tries; if the TNC has no unacknowledged frames, it will return the number of tries required to obtain an acknowledgement for the previous frame. If RETRY is set to 0, the value returned by issuing a TRIES command will always be 0. This command is useful for obtaining statistics on the performance of a given path or channel. It should be especially useful for automatic optimizing of such parameters as PACLEN and MAXFRAME by computer-oriented stations, such as automatic message forwarding stations using less-than-optimum paths (noisy HF or satellite channels, for example). If followed by an argument, TRIES will force the "tries" counter to that entered value. This usage is NOT recommended. @TXDelay n Default : 33 Display Group : T Parameters: n = 0 - 120, specifying 10 ms intervals This value tell the TNC how long to wait after keying up the transmitter before sending data. Some startup time is required by all transmitters to put a signal on the air; some need more, some need less. In general crystal controlled rigs with diode antenna switching don't need much time, synthesized rigs need time for PLL lockup, and rigs with mechanical T/R relays will need time for physical relay movement. The correct value for a particular rig should be determined by experimentation. The proper setting of this value may also be affected by the requirements of the station you are communicating with. @TXDELAYC n Default : 2 Display Group : T Parameters: n = 0-120 specifying additional transmit delay time added to TXdelay in terms of CHARACTER TIME at the current radio port data rate. Flags will be sent during this time, so a value of 1 is required as a minimum. TXDELAYC is used to fine-tune transmit delay after a transmit command is issued and before data is sent. Used in conjunction with TXDELAY, it allows a link to be set for maximum performance. TXDELAY should be used to account for the time it takes the radio (the slower of this TNC's radio and the remote TNC's radio) to switch between receive and transmit and allow the receiving unit's data carrier detect (DCD) circuit to respond. "0" bytes are sent to allow the remote TNC to synchronize to the data stream sent during TXDELAY. TXDELAYC then sends flags to start the frame. If TXDELAYC 0 is selected, the TNC will act as if TXDELAYC 1 had been chosen. With this method of keying up, a user may operate at various HDLC data rates without having to reset TXDELAY if the same radios are used. The summation of TXDELAY and TXDELAYC will automatically adjust the keyup time for the varying rates. @TXFlow ON|OFF Default : OFF Display Group : A Parameters: ON - Software flow control is enabled for the TNC in Transparent Mode. OFF - Software flow control is disabled for the TNC in Transparent Mode. If TXFLOW is ON, the setting of XFLOW is used to determine the type of flow control used in Transparent Mode. If TXFLOW is OFF, the TNC will use only hardware flow control and all data sent to the terminal remains fully transparent. If TXFLOW and XFLOW are ON, the TNC will use the TNC Restart and TNC Stop characters (set by XON and XOFF) to control the input from the terminal. Unless TRFLOW is also ON, only hardware flow control is available to the computer or terminal to control output from the TNC. Note that if the TNC Restart and TNC Stop characters are set to $00, hardware flow control will always be selected regardless of the setting of TXFLOW. @TXUIframe ON/OFF Default : OFF Display group : L ON The TNC will "flush its buffers" to the radio port on loss of connection. OFF The TNC will only send BEACON and ID frames as unconnected (UI) frames. It will discard information in its buffers on loss of connection. Setting TXUIframe OFF will prevent all but BEACON and ID unconnected (UI) frames from being originated and transmitted. This is useful for BBS and other stations which tend to leave UNACKed data in the TNC transmit buffer when a connection is lost. With TXUIframe OFF channel congestion is reduced because now useless data is never sent. NOTE: TXUIframe has NO effect on the digipeating of UI frames. It only affects frames from the originating station. @UNPROTO call#1 [VIA call#2[,call#3...,call#9]] Display Group : I Parameters: call#1 - Callsign to be placed in the TO address field. call#2 to 9 - Optional digipeater list, up to eight calls. This command sets the digipeat and destination address fields of packets sent in unconnected (unprotocol) mode. Unconnected packets are sent as unsequenced 'I' frames with the destination and digipeat fields taken from 'call#1' through 'call#9' options. The default destination for unconnected packets is CQ. Unconnected packets from other TNCs may be monitored by setting MONITOR ON and BUDLIST and LCALLS appropriately. The digipeater list is also used for BEACON packets (which are sent to destination address BEACON). @USers n Default : 1 Display Group : L Parameters: n = 0 - 10, indicating the number of simultaneous connections allowed. USERS affects only the manner in which incoming connect requests are handled, and has no effect on the number or handling of connections you may initiate from the TNC. For example: USERS 0 allows incoming connections on any free stream USERS 1 allows incoming connections on stream A only USERS 2 allows incoming connections on streams A & B, and so on through to USERS 10. @Xflow ON|OFF Default : ON Display Group : A Parameters: ON - XON/XOFF flow control is enabled. OFF - XON/XOFF flow control is disabled and hardware flow control is enabled. If XFLOW is ON, the computer or terminal is assumed to respond to the TNC Restart and TNC Stop characters set by XON and XOFF. If XFLOW is OFF, the TNC will communicate flow control commands via RTS. @XMitok ON|OFF Default : ON Display Group : L Parameters: ON - Transmit functions are enabled. OFF - Transmit functions are disabled. When XMITOK is OFF, transmitting is inhibited. All other functions of the board remain the same, in other words, the TNC generates and sends packets but does not key the radio PTT line. You might use this command to ensure that your TNC does not transmit in your absence if you leave it to monitor packet activity. This command can also be used for testing using loopback or direct wire connections when PTT operation is not relevant. @XOff n Default : $13 Display Group : C <CTRL-S> Parameters: n = 0 to $7F, specifying an ASCII character code. This command selects the TNC Stop character (hex or decimal), which is sent to by the TNC TO the computer or terminal to stop input from that device. This character would normally be set to <CTRL-S> for computer data transfers. If you want notification in Converse Mode when the buffers are filled, set this character to <CTRL-G> ($07), which rings the terminal bell. @XON n Default : $11 <CTRL-Q> Parameters: n = 0 to $7F, specifying an ASCII Character code. This command selects the TNC Restart character (hex or decimal), which is sent to by the TNC TO the computer or terminal to restart input from that device. This character would normally be set to <CTRL-Q> for computer data transfers. If you want notification in Converse Mode when the buffers are filled, set this character to <CTRL-G> ($07), which rings the terminal bell.