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
20190825011044EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825012743EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825014443EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825020150EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825021843EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825023532EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825025224EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825030914EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825032604EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825034254EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825035947EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825041637EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825043328EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825045021EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825050714EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825052405EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825054057EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825055751EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825061447EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825063145EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825064839EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190825070535EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz