APRS Packet Errors for EB3DAU (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
20191118140340EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118141849EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118143358EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118144913EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118150422EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118151932EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118153442EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118154955EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118160505EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118162015EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118163524EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118165038EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118170547EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118172057EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118173607EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118175121EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118180631EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118182141EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118183651EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118185206EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118190716EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118192227EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118193737EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz
20191118195251EB3DAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DAU-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 431.6500 MHz