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
20190421170345EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421172112EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421173821EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421175514EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421181219EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421182917EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421184638EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421190401EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421193756EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421195503EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421201153EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421202842EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421204546EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421210253EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421212013EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421213707EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421215355EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421221058EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421222753EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190421224450EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz