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
20190217223926PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190217225600PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190217231256PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190217232942PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190217234626PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218000316PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218002000PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218003650PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218005339PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218011019PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218012657PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218014342PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218020012PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218021640PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218023324PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218025003PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218030636PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218032308PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218033949PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218041305PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz
20190218042937PY1SVL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1SVL-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 146.8300@-0.6 MHz