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
20190720191434PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720193137PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720194834PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720200532PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720202311PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720204020PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720205726PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720211424PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720213120PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720214826PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720220519PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720222215PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720223921PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720225631PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720231328PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720233029PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190720234723PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190721000434PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190721002136PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190721003827PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz
20190721005520PY4DY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4DY-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 432.3000 MHz