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
20191121054156SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121055708SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121061219SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121062731SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121064246SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121065759SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121071310SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121072822SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121074337SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121075849SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121081403SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121082914SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121084430SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121085942SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121091453SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121093004SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121094518SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121100030SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121101541SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121103056SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121104618SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121110135SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121111650SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz
20191121113204SV1FMT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1FMT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.0000 MHz