APRS Packet Errors for PY4DY (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
20190720081325PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720083016PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720084706PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720090359PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720092058PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720093756PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720095448PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720101140PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720102843PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720104535PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720110227PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720111927PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720113631PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720115331PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720121029PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720122721PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720124425PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720130119PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720131812PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720133506PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720135211PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz