APRS Packet Errors for XE2CE (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
20190216082129XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216083749XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216085409XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216091029XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216092657XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216094319XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216095942XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216101602XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216103228XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216104849XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216110511XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216112132XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216113800XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216115421XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216121044XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216122708XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216124337XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216130000XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216131622XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216133247XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216134914XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190216140538XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz