APRS Packet Errors for PY1JHG (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
20190523013034PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523014752PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523020501PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523022213PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523023921PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523025613PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523031326PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523033045PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523034750PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523040458PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523042212PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523043940PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523045650PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523051353PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523053059PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523054820PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523060712PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523062409PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523064114PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190523065830PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz