-
Notifications
You must be signed in to change notification settings - Fork 313
/
Copy pathCHANGES.txt
246 lines (141 loc) · 5.41 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
----------------
Revision history
----------------
-----------
Version 1.1 -- December 2014
-----------
* Changes since beta test version.
It is still highly recommended, but no longer mandatory, that
beaconing be enabled for digipeating to work.
* Known problems.
Sometimes kissattach fails to connect with "direwolf -p".
The User Guide and Raspberry Pi APRS document have a couple work-arounds.
-----------
Version 1.1 -- Beta Test 1 -- November 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.
* 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.
-----------
Version 1.0a May 2014
-----------
* Bug fix:
Beacons sent directly to IGate server had incorrect source address.
-----------
Version 1.0 May 2014
-----------
* New Features:
Received audio can be obtained with a UDP socket or stdin.
This can be used to take audio from software defined radios
such as rtl_fm or gqrx.
9600 baud data rate.
New PBEACON and OBEACON configuration options. Previously
it was necessary to handcraft beacons.
Less CPU power required for 300 baud. This is important
if you want to run a bunch of decoders at the same time
to tolerate off-frequency HF SSB signals.
Improved support for UTF-8 character set.
Improved troubleshooting display for APRStt macros.
In earlier versions, the DTMF decoder was always active because it
took a negligible amount of CPU time. Unfortunately this sometimes
resulted in too many false positives from some other types of digital
transmissions heard on HF. Starting in version 1.0, the DTMF decoder
is enabled only when the APRStt gateway is configured.
-----------
Version 0.9 November 2013
-----------
* New Features:
Selection of non-default audio device for Linux ALSA.
Simplified audio device set up for Raspberry Pi.
GPIO lines can be used for PTT on suitable Linux systems.
Improved 1200 baud decoder.
Multiple decoders per channel to tolerate HF SSB signals off frequency.
Command line option "-t 0" to disable text colors.
APRStt macros which allow short numeric only touch tone
sequences to be processed as much longer predefined sequences.
* Bugs Fixed:
Now works on 64 bit target.
* New Restriction for Windows version:
Minimum processor is now Pentium 3 or equivalent or later.
It's possible to run on something older but you will need
to rebuild it from source.
-----------
Version 0.8 August 2013
-----------
* New Features:
Internet Gateway (IGate) including IPv6 support.
Compatibility with YAAC.
Preemptive digipeating option.
KISS TNC should now work with connected AX.25 protocols
(e.g. AX25 for Linux), not just APRS.
-----------
Version 0.7 March 2013
-----------
* New Features:
Added APRStt gateway capability. For details, see:
APRStt-Implementation-Notes.pdf
-----------
Version 0.6 February 2013
-----------
* New Features:
Improved performance of AFSK demodulator.
Now decodes 965 frames from Track 2 of WA8LMF’s TNC Test CD.
KISS protocol now available thru a TCP socket.
Default port is 8001.
Change it with KISSPORT option in configuration file.
Ability to salvage frames with bad FCS.
See section mentioning "bad apple" in the user guide.
Default of fixing 1 bit works well.
Fixing more bits not recommended because there is a high
probability of occasional corrupted data getting thru.
Added AGW "monitor" format messages.
Now compatible with APRS-TW for telemetry.
* Bugs Fixed:
None.
* Known Problem:
The Linux (but not Cygwin) version eventually hangs if nothing is
reading from the KISS pseudo terminal. Some operating system
queue fills up, the application write blocks, and decoding stops.
* Workaround:
If another application is not using the serial KISS interface,
run this in another window:
tail -f /tmp/kisstnc
-----------
Version 0.5 March 2012
-----------
More error checking and messages for invalid APRS data.
-----------
Version 0.4 September 2011
-----------
First general availability.