APRS Packet Errors for DO3DO (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
20190216203512DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216205252DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216211019DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216212723DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216214447DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216220217DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216221924DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216223621DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216225316DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216231032DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216232728DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190216234420DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217000114DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217001831DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217003604DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217005306DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217011027DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217012729DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217014435DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190217020152DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz