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
20190618194135EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618195835EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618201540EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618203234EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618204950EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618210646EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618212338EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618214026EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618215723EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618221420EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618223109EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618224800EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618230452EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618232138EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618233825EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190618235513EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619001208EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619002858EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619004547EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619010234EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619011923EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190619013613EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz