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
20190825120622XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825122314XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825124000XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825125647XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825131332XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825133028XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825134717XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825140406XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825142057XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825143757XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825145452XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825151154XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825152854XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825154605XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825160306XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825161958XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825163712XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825165406XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825171113XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825172810XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190825174503XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz