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
20190419042745EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419044421EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419050059EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419051742EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419053424EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419055102EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419060739EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419062424EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419064102EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419065740EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419071420EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419073109EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419074750EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419080437EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419082127EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419083820EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419085505EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419091154EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419092847EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419094539EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190419100227EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz