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
20190822225321XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190822231015XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190822232719XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190822234426XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823000129XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823001828XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823003523XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823005218XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823010917XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823012613XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823014320XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823020025XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823021740XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823023434XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823025137XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823030830XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823032528XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823034225XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823035929XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823041637XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz
20190823043329XE1ENL>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1ENL-DP!2019.80N/-102-18.0rRNG0034 IPSC2-Mexico MMDVM 433.3000 MHz