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
20191115103232SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115104744SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115110255SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115111808SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115113326SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115114837SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115120348SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115121901SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115123417SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115124928SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115130441SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115131951SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115133507SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115135018SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115140531SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115142043SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115143558SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115145109SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115150620SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115152135SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115153651SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115155203SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz
20191115160715SV1OBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1OBT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.8000 MHz