APRS Packet Errors for XE2LOD (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
20190217020452XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217022059XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217023706XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217025327XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217030950XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217032612XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217034232XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217035859XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz
20190217041532XE2LOD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2LOD-DP!2401.94N/-104-39.7rRNG0034 IPSC2-Mexico MMDVM 433.3750 MHz