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
20190420121448XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420123124XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420124757XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420130427XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420132101XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420133752XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420135435XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420141120XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420142808XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420144501XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420150151XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420151838XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420153515XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420155153XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420160829XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420162524XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420164252XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420170007XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420171716XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420173408XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420175054XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz
20190420180743XE2CVR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CVR-DP!3218.02N/-117-4.25rRNG0034 IPSC2-Mexico MMDVM 440.0000 MHz