APRS Packet Errors for XE1TTS (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
20190918143644XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918145158XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918150720XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918152234XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918153748XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918155302XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918160822XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918162334XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918163850XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918165403XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918170922XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918172438XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918173953XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918175505XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918181025XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918182539XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918184052XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918185605XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918191122XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918192636XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918194148XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918195702XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190918201222XE1TTS>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1TTS-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz