|
2 | 2 | # Revision History #
|
3 | 3 |
|
4 | 4 |
|
| 5 | +## Version 1.5 -- September 2018 ## |
| 6 | + |
| 7 | + |
| 8 | +### New Features: ### |
| 9 | + |
| 10 | +- PTT using GPIO pin of CM108/CM119 (e.g. DMK URI, RB-USB RIM), Linux only. |
| 11 | + |
| 12 | +- More efficient error recovery for AX.25 connected mode. Better generation and processing of REJ and SREJ to reduce unnecessary duplicate "**I**" frames. |
| 13 | + |
| 14 | +- New configuration option, "**V20**", for listing stations known to not understand AX.25 v2.2. This will speed up connection by going right to SABM and not trying SABME first and failing. |
| 15 | + |
| 16 | +- New "**NOXID**" configuration file option to avoid sending XID command to listed station(s). If other end is a partial v2.2 implementation, which recognizes SABME, but not XID, we would waste a lot of time resending XID many times before giving up. This is less drastic than the "**V20**" option which doesn't even attempt to use v2.2 with listed station(s). |
| 17 | + |
| 18 | +- New application "**kissutil**" for troubleshooting a KISS TNC or interfacing to an application via files. |
| 19 | + |
| 20 | +- KISS "Set Hardware" command to report transmit queue length. |
| 21 | + |
| 22 | +- TCP KISS can now handle multiple concurrent applications. |
| 23 | + |
| 24 | +- Linux can use serial port for KISS in addition to a pseudo terminal. |
| 25 | + |
| 26 | +- decode_aprs utility can now accept KISS frames and AX.25 frames as series of two digit hexadecimal numbers. |
| 27 | + |
| 28 | +- Full Duplex operation. (Put "FULLDUP ON" in channel section of configuration file.) |
| 29 | + |
| 30 | +- Time slots for beaconing. |
| 31 | + |
| 32 | +- Allow single log file with fixed name rather than starting a new one each day. |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +### Bugs Fixed: ### |
| 37 | + |
| 38 | +- Possible crash when CDIGIPEAT did not include the optional alias. |
| 39 | + |
| 40 | +- PACLEN configuration item no longer restricts length of received frames. |
| 41 | + |
| 42 | +- Strange failures when trying to use multiple KISS client applications over TCP. Only Linux was affected. |
| 43 | + |
| 44 | +- Under certain conditions, outgoing connected mode data would get stuck in a queue and not be transmitted. This could happen if client application sends a burst of data larger than the "window" size (MAXFRAME or EMAXFRAME option). |
| 45 | + |
| 46 | + |
| 47 | +- Little typographical / spelling errors in messages. |
| 48 | + |
| 49 | + |
| 50 | +### Documentation: ### |
| 51 | + |
| 52 | + |
| 53 | +- New document ***Bluetooth-KISS-TNC.pdf*** explaining how to use KISS over Bluetooth. |
| 54 | + |
| 55 | +- Updates describing cheap SDR frequency inaccuracy and how to compensate for it. |
| 56 | + |
| 57 | +### Notes: ### |
| 58 | + |
| 59 | +Windows binary distribution now uses gcc (MinGW) version 6.3.0. |
| 60 | + |
| 61 | +---------- |
| 62 | + |
5 | 63 | ## Version 1.4 -- April 2017 ##
|
6 | 64 |
|
7 | 65 |
|
|
0 commit comments