APRS Packet Errors for DO1GKI (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
20190823114440DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823120157DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823121926DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823123712DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823125432DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823131303DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823133125DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823134943DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823140849DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823142723DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823144459DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823150332DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823152135DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823153915DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823155633DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823161437DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823163251DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823165121DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823170900DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz
20190823172736DO1GKI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO1GKI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.8375@-9.4 MHz