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
20190319110834SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319112501SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319114131SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319115801SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319121431SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319123103SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319124736SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319130409SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319132042SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319133717SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319135348SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319141014SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319142641SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319144308SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319145936SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319151602SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319153227SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319154853SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319160523SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319162149SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319163814SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190319165442SY1CVL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SY1CVL-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz