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
20190618192639EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618194329EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618195835EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.47N/-06-22.65rRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
20190618200034EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618201540EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.47N/-06-22.65rRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
20190618201724EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618203234EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.47N/-06-22.65rRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
20190618203413EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618204950EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.47N/-06-22.65rRNG0034 IPSC2-EA4Master MMDVM 435.0000 MHz
20190618205101EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618210746EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618212431EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618214119EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618215809EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618221501EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618223145EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618224836EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618230519EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618232207EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618233857EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190618235544EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190619001226EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190619002910EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190619004557EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190619010244EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz