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
20190124062510PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124064118PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124065718PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124071332PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124072931PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124074539PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124080143PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124081741PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124083343PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124084955PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124090612PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124092217PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124094737PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124100357PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124103615PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124105223PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124110834PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124112434PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124114055PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124115705PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190124121340PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz