APRS Packet Errors for SY1CVL (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
20190616083239SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616084917SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616090611SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616092255SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616093941SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616095624SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616102856SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616104533SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616110103SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616111736SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616113421SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616115104SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616120748SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616122432SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616124116SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616125758SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616131445SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616133124SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616134808SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616140451SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190616142131SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz