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
20191017231000SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191017232517SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191017234031SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191017235544SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018001057SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018002614SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018004129SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018005646SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018011158SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018012714SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018014226SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018015739SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018021251SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018022806SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018024317SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018025830SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018031342SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018032856SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018034406SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018035916SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018041428SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018042942SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018044456SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191018050008SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz