APRS Packet Errors for XE2PMP (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
20190217161737XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217163407XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217165039XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217170709XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217172332XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217173957XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217175623XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217181252XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217182914XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217184539XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217190204XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217191835XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217193506XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217195137XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217200803XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217202430XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217204053XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217205720XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217211347XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217213016XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217214641XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz
20190217220304XE2PMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2PMP-DP!2838.16N/-106-5.58rRNG0034 IPSC2-Mexico MMDVM 433.9750 MHz