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
20190624160832SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624162520SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624164217SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624165903SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624171544SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624173231SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624174921SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624180601SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624182243SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624183925SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624185609SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624191253SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624192940SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624194626SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624200314SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624201957SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624203652SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624205356SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624211051SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624212732SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20190624214413SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz