APRS Packet Errors for EA1GHG (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
20190918143037EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918145718EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918151227EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918152735EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918154243EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918155754EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918161303EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918170047EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918171556EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918173105EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918174613EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918180126EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918181635EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918183145EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918184655EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918190207EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918191717EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918193226EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918194734EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918200246EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz
20190918201756EA1GHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GHG-DP!4225.95N/-08-4.74ErRNG0034 IPSC2-EA1Master MMDVM 430.4000 MHz