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
20190418104201EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418104201EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418105925EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418105925EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418111637EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418111637EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418113355EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418113355EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418115113EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418115113EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418120822EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418120822EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418122552EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418122552EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418124317EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418124317EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418130029EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418130029EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418131758EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418131758EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418133506EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418133506EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418135221EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418135222EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418140943EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418140943EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418142650EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418142650EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418144352EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418144352EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418150054EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418150054EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418151800EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418151800EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418153458EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418153458EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418155201EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418155201EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418160908EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418160908EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190418162603EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3647.26N/-06-19.15rRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
20190418162603EA7DYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7DYY-DP!3650.18N/-05-57.20rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz