APRS Packet Errors for SV1HAN (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
20190217153741SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217155404SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217161021SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217162642SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217164259SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217165924SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217171541SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217173214SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217174832SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217180455SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217182112SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217183729SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217185349SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217191010SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217192631SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217194252SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217195909SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217201532SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217203150SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217204809SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217210428SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz
20190217212053SV1HAN>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HAN-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 436.2000 MHz