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
20190818201735EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818203438EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818205143EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818210846EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818212546EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818214301EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818220007EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818221658EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818223402EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818225109EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818230815EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818232529EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190818234256EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819000005EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819001731EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819003430EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819005131EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819010835EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819012538EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819014240EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190819015952EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz