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
20190717164959SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717170657SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717172350SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717174040SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717175728SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717181432SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717183135SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717184830SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717190524SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717192213SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717193919SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717195622SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717201312SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717203003SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717204659SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717210349SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717212042SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717213732SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717221118SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20190717222808SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz