APRS Packet Errors for XE1ENL (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
20190825021411XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825023105XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825024754XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825030444XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825032151XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825033850XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825035601XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825041310XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825043021XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825044716XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825050405XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825052051XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825053748XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825055454XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825061213XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825062920XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825064624XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825070315XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825071959XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825073649XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz