APRS Packet Errors for SV1OBT (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
20190616083239SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616084917SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616090611SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616092255SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616093941SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616095624SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616102856SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616104533SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616110103SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616111736SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616113421SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616115104SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616120748SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616122432SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616125758SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616131445SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616133124SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616134808SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616140451SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190616142131SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz