APRS Packet Errors for EA7DYY (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
20181022210532EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022212101EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022213632EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022215205EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022220735EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022222305EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022223834EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022225406EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022230933EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022232509EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022234038EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181022235609EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023001137EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023002705EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023004232EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023005803EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023011331EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023012900EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023014429EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023015959EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023021527EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023023055EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181023024622EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz