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
20190618014754EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618020446EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618022132EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618023817EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618025506EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618031150EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618032836EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618034523EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618040207EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618041852EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618043540EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618045230EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618050917EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618052603EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618054250EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618055946EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618061631EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618063319EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618065008EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618070659EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618072353EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz