APRS Packet Errors for EA7UH (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
20190420230200EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190420231833EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190420233509EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190420235144EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421000822EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421002455EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421004135EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421005809EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421011441EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421013116EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421014753EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421020425EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421022057EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421023728EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421025404EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421031038EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421032709EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421034342EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421040018EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421041650EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421043324EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190421044955EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz