APRS Packet Errors for XE2CVR (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
20190216113800	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190216115421	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190216121044	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190216122708	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190216124337	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190216125959	XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz