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
20190922075702SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922081216SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922082733SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922084245SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922085757SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922091307SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922092817SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922094328SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922095841SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922101353SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922102903SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922104413SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922105927SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922111439SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922112950SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922114500SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922120015SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922121526SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922123037SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922124549SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922130104SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922131613SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922133124SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190922134635SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz