APRS Packet Errors for AB3LI (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
20190419182116AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419183843AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419185615AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419191336AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419193100AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419194807AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419200514AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419202217AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419203941AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419205649AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34WrRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419211346AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419213048AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419214809AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419220529AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419222227AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419224031AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419225806AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419231516AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419233230AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190419234947AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190420000651AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz