APRS Packet Errors for PY1SVL (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
20190425050048PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425051735PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425053430PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425055113PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425060756PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425064145PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425071532PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425073223PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425074924PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425080606PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425083937PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425085632PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425091316PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425092959PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425094643PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425100336PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425102022PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425103713PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190425105400PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz