APRS Packet Errors for SV9OFV (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
20190619200637SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619202320SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619204005SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619205651SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619211334SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619213017SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619214708SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619220348SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619222029SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619223707SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619225401SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619231051SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619232746SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190619234436SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190620000118SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190620001758SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190620003451SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190620005147SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190620010845SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz