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
20190422070341PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422072021PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422073705PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422075351PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422081046PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422082727PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422084406PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422090045PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422091735PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422093414PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422095053PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422100733PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422102435PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422104116PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422105800PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422111447PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422113145PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422114832PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422120705PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190422122356PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz