Version 1.1

Version 1.1 -- December 2014

New Features

• Logging of received packets and utility to convert log file
  into GPX format.
• AGW network port formerly allowed only one connection at a
  time. It can now accept 3 client applications at the same time.
  (Same has not yet been done for network KISS port.)
• Frequency / offset / tone standard formats are now recognized.
  Non-standard attempts, in the comment, are often detected and
  a message suggests the correct format.
• Telemetry is now recognized. Messages are printed for
  usage that does not adhere to the published standard.
• Tracker function transmits location from GPS position.
  New configuration file options: TBEACON and SMARTBEACONING.
  (For Linux only. Warning - has not been well tested.)
• Experimental packet regeneration feature for HF use.
  Will be documented later if proves to be useful...
• Several enhancements for trying to fix incorrect CRC:
  Additional types of attempts to fix a bad CRC.
  Optimized code to reduce execution time.
  Improved detection of duplicate packets from different fixup attempts.
  Set limit on number of packets in fix up later queue.
• Beacon positions can be specified in either latitude / longitude
  or UTM coordinates.
• It is still highly recommended, but no longer mandatory, that
  beaconing be enabled for digipeating to work.
• Bugs fixed:
• For Windows version, maximum serial port was COM9.
  It is now possible to use COM10 and higher.
• Fixed issue with KISS protocol decoder state that showed up
  only with "binary" data in packets (e.g. RMS Express).
• An extra 00 byte was being appended to packets from AGW
  network protocol 'K' messages.
• Invalid data from an AGW client application could cause an
  application crash.
• OSS (audio interface for non-Linux versions of Unix) should
  be better now.

Known problems

• Sometimes kissattach fails to connect with "direwolf -p".
  The User Guide and Raspberry Pi APRS document have a couple work-arounds.