APRS Packet Errors for PY4KD (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
20190918133827PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918135342PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918140902PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918142417PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918143936PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918145454PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918151019PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918152542PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918154056PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918155610PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918161135PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918162649PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918164206PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918165728PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918171259PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918172814PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918174328PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918175844PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918181410PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918182924PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918184440PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918185954PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918191522PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20190918193034PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz