TNC 2 Software Release Notes for Release 1.1.4  February 17, 1987

                  TNC 2 Software Release 1.1.4 Notes
                  ----------------------------------

This  document  describes the differences between the latest  re-
lease 1.1.4 and the previous (1.1.3) release of TAPR software for 
the TNC 2 Terminal Node Controller.

The  new Checksum is $21,  and the object image  occupies  almost 
0x44FF bytes of EPROM.

NOTE:     THIS SOFTWARE UPGRADE REQUIRES MODIFICATIONS TO THE TNC 
          TO INSTALL IT!   REFER TO THE INSTALLATION INSTRUCTIONS 
          AT  THE  END  OF THIS  DOCUMENT  BEFORE  ATTEMPTING  TO 
          INSTALL THE EPROM OR USE THE SOFTWARE!

                              FIXES
                              -----

 o - Transmitted  I-frames  under Level 2 Version 2 did not  have 
     their P bits set at the appropriate times.   In  fact,  they 
     never had their P bits set.    This has now been fixed.  The 
     last  I-frame  of a multiple I-frame transmission has its  P 
     bit set.

 o - A mistake in the protocol state table was fixed.

 o - bbRAM  scanning now checks all ten possible connection  con-
     trol structures (instead of just the first one).

     Thanks to Steve Stuart in California for being the earliest, 
     and to others as well, for pointing out this bug.

                              CHANGES
                              -------

 o - AX25L2V2 defaults to the ON position.

 o - Major  change made to AX25L2V2 handling.   If retry limit is 
     exceeded, or the TNC receives a "disconnected" response to a 
     poll, the connection is ended.

     The  old  method (and the one proscribed)  is  fraught  with 
     problems   for  automated  stations  that  can  not  recover      
     without an indication of loss of the connection.

     The  PERMCON control will replace the functionality of  this 
     aspect of AX25L2V2 which was removed.

                          ENHANCEMENTS
                         --------------

 o - 32K of RAM is now expected.   Virtually all of the new space 
     is used to enlarge existing queues within the TNC,  yielding 
     greater performance especially at faster RF data rates,  and 
     making  the  on-board message buffer capability a  bit  more 
     useful.

 o - The  MCOM command decodes all control fields  (invalid  ones 
     are marked with ????).

For  I and S frames,  sequence number information is also presen-
ted.

Frames  compatible  with  the AX.25 Level 2.0 standard  are  also 
decoded  as to the state of the Command/Response (C/R) and  Poll/ 
Final (P/F) bits.

     Ex:   WA7GXD>KV7B <I C S0 R0>:
           Hi Dan,

           WA7GXD>KV7B <I C P S1 R0>:
           have you been on EIES lately?

           KV7B>WA7GXD <RR R F R2>
           KV7B>WA7GXD <I C P S1 R2>:
           I was just thinking about that.  I heard that @(username)
           made some real unbelievable comment on it!

           WA7GXD>KV7B <RR R F R2>
           WB2SPE>KV7B <C>
           KV7B>WB2SPE <DM>
           KV7B>WA7GXD <I C P S2 R2):
           Good conditions now...

           WA7GXD>KV7B <RR R F R3>
           WA7GXD>KV7B <I C P S2 R3>:
           Yes @(username) did.  It was quite remarkable.

And  so on.  See Chapter 9 Table 9-1 in your TNC 2 manual  for  a 
breakdown  of the control field codes.   For complete information 
on  the AX25 Level 2 Version 2.0 Protocol,  please refer  to  the 
ARRL  AX25 Protocol Specification document,  available from  ARRL 
for $10.

                            NEW COMMANDS
                            ------------

CBELL ON|OFF                                         Default: OFF


Parameters:

     ON        Connect bell enabled

     OFF       Connect bell disabled

This  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 connected message, e.g.:

     <BELL>*** Connected to: <callsign>



CMSGDISC ON|OFF                                      Default: OFF


Parameters:

     ON        Automatic disconnect enabled

     OFF       Automatic disconnect disabled

This command controls whether the TNC 2 will initiate a disconnect 
sequence after it is connected to.

If CMSG is OFF, or CTEXT has no connected text, the TNC initiates 
a  disconnect  immediately upon receiving information or  acknow-
ledgement frames from the other station.

If  CMSG is ON and CTEXT contains some text information,  the TNC 
intitiates a disconnect after the packet containing connect  text 
(CTEXT) is acknowledged.

This command may be useful to bulletin board operators or  others 
with  a need to send a short message,  confirm its  receipt,  and 
disconnect.

NOTE:     Use this command with care - If you find you're able to 
          receive  connects,  yet never get data,  it's  possible 
          CMSGDisc  has been left on.  It's also possible is that 
          RS-232 DCD is holding the terminal off -- see the TNC 2 
          System Manual for details on hardware flow control.


LFIGNORE ON|OFF                                      Default: OFF


Parameters:

     ON        TNC will ignore <LF> characters.

     OFF       TNC wil respond to <LF> characters.

This  command controls whether TNC 2 responds to ASCII Line  Feed 
(<LF>  $0A)  characters or ignores them in command  and  converse 
modes.

When turned on,  line feeds are totally ignored except in  trans-
parent mode.


New HEALTH Counters


BBfailed n :   Counts number of times bbRAM checksum was in error

TXQovflw n :   Counts  how  many times frames were discarded  be-
               cause the outgoing frame queue was too small.


                    THE REVOLUTION EVOLVES!


                     Howard Goldstein N2WX
                     TNC-2 Software Design
                             'n
                        Damage Control


INSTALLATION OF THE NEW SOFTWARE

TNC 2 Rev 1: (has four LEDs on the front panel)

( )  If you are still running 1.1.0 software, perform the modifi-
     cations  sent  to you free of charge in December,  1985  and 
     verify that all is working.   If you bought your TNC 2 Rev 1 
     used, and the mods weren't performed, contact the party from 
     whom you purchased it and get the mod kit.  If you can't, or 
     they  won't,  you may order one from TAPR for $25.   Do  not 
     proceed until your TNC is modified!

( )  Turn off the TNC and remove it from its case.

( )  Cut the trace from U12 pin 2 on the bottom (solder side)  of 
     the PC board.

( )  Add a jumper from U12 pin 2 to U12 pin 3.

( )  Carefully  remove the 8k RAMS at U25 and U24.   DO NOT USE A 
     METALLIC IC PULLER THAT COULD SHORT PINS 14 AND 28 TOGETHER!

( )  Cut  the  trace at U25 between pins 26 and 28 on the  bottom 
     (solder side) of the PC board.

( )  Add a jumper from U25 pin 26 to U23 pin 26.

( )  Add a jumper from U25 pin 1 to U23 pin 27.

( )  Install a new 32k RAM IC at U25.   DO NOT USE A METALLIC  IC 
     INSERTION TOOL THAT COULD SHORT PINS 14 AND 28 TOGETHER.

( )  Turn on the TNC and verify that it signs on as before.  This 
     verifies  the new RAM is working.   You should also get  the 
     bbRAM initialized message.

( )  Turn off the TNC.

( )  Remove the EPROM at U23.

( )  Install the new 1.1.4 software EPROM at U23.

( )  Now,  turn  on the TNC and verify that it signs on.   Again, 
     you should get the bbRAM initialized message.

( )  Remove power and reinstall the TNC in its case.

( )  Now,  turn on the TNC, set up your callsign and timing para-
     meters  that  you prefer and enjoy the new features and  in-
     creased buffers in your TNC 2!

INSTALLATION OF THE NEW SOFTWARE

TNC 2 Rev 2: (has five LEDs on the front panel)

( )  Turn off the TNC and remove it from its case.

( )  Remove  jumper  at  JMP5.    This  disconnects  the  Lithium 
     battery.

( )  Remove 8K RAM at U24.

( )  Remove 8k RAM at U25.

( )  Cut trace at JMP12 top and center pins.

( )  Add jumper at JMP12 bottom and center pins.

( )  Install 32k RAM chip at U25.

( )  Replace jumper at JMP5.

( )  Turn on the TNC and verify that it signs on as before.  This 
     verifes  the new RAM is working.   You should also  get  the 
     bbRAM initialized message.

( )  Turn off the TNC.

( )  Remove the EPROM at U23.

( )  Install the new 1.1.4 software EPROM at U23.

( )  Now, turn on the TNC and verify that it signs on. Again, you 
     should get the bbRAM initialized message.

( )  Remove power and reinstall the TNC in its case.

( )  Now,  turn  on the TNC and verify that it signs on.   Set up 
     your  callsign  and timing parameters that  you  prefer  and 
     enjoy the new features and increased buffers in your TNC 2!


