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
20190923121743SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923123253SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923124803SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923130311SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923131825SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923133333SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923134843SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923140351SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923141906SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923143415SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923144924SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923150434SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923151948SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923153458SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923155011SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923160523SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923162040SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923163553SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923165102SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923170612SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923172126SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923173638SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923175149SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz
20190923180659SV9OFV>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9OFV-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.5000 MHz