APRS Packet Errors for SV1HBS (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
20190723173343SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723175036SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723180722SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723182414SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723185528SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723191214SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723192904SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723194549SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723200244SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723201931SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723203624SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723205311SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723211001SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723212646SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723220218SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723221904SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723223549SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723225235SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190723230926SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz