APRS Packet Errors for SV1FMT (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
20191019062953SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019064513SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019070025SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019071537SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019073050SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019074606SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019080122SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019081633SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019083144SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019084658SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019090215SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019091726SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019093238SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019094752SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019100305SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019101817SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019103329SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019104844SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019110354SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019111903SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019113415SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019114928SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191019120441SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz