APRS Packet Errors for ED2ZAC (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20191023082604ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023084111ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023085619ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023091134ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023092651ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023094218ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023095727ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023101245ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023102758ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023104311ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023105821ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023111336ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023112846ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023114357ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023115906ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023121420ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023122932ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023124446ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023125954ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023131506ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023133016ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023134528ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023140041ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz
20191023141551ED2ZAC>APZDMR,QTH,TCPIP*,qAU,T2BIO:)ED2ZAC-DP!4316.78N/-02-56.76rRNG0034 IPSC2-EA2Master MMDVM 438.2000@-7.6 MHz