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
20181118092555EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181118094114EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181118095649EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181118101212EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181118102740EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20181118105055EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118110623EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118112148EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118115225EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118120804EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118122316EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118123834EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118125352EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118130907EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118132421EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118133935EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118135456EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118141010EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118142523EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118144040EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118145552EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20181118151104EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz