[aprssig] chewed-up APRS messages
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Mon Nov 28 12:31:02 CST 2011
Yep, there's a bunch of trashy packets out on the APRS-IS. My
suggestion: if it doesn't look good, ignore it. If it originated from a
good packet, it either was just processed in the correct form or it'll
come again, hopefully not corrupted.
When in doubt, check the originating station's raw packets at aprs.fi
and see if Hessu sees the same thing and what his parser complains about.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 11/28/2011 1:14 PM, Andrew P. wrote:
> Greetings, all.
> I've been looking at APRS messages I've been receiving, and noticing
> an alarming tendency towards mangled messages. It can't be just from
> my software not keeping up with the serial data stream, because I'm
> getting this on APRS-IS server connections (which, by their nature as
> TCP/IP connections, can't drop bytes in mid-stream). So, is there that
> great a frequency of garbled packets out there being forwarded by
> I-gates, or do we just have sloppy software (or sloppy manual data
> entry) putting garbaged messages out there? Here's some examples:
> KA1GJU-3>APN382,UNCAN,WIDE2*,qAR,W1CLA-1:!!06 0F02 at 000-,-----(--,--
> 02035 00000"7
> $GPRMC,11,A,4458.2127,N,08720.8152,W,0.000,0.0,120,2.2, W
> Chicago-Peet2100-All Sensors Nominal
> wx3in1 A=650?
> Largo Fill+in Digi
> *11115026.94N/00334.92Wr050.750MHz T077 1.5M GB3TQ PAIGTON G0AZX!w+G!
> Any suggestions for dealing with such packets would be appreciated.
> Andrew Pavlin, KA2DDO
> aprssig mailing list
> aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig