APRS Packet Errors for XE2JC (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
20190616091209XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616092908XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616094600XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616100239XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616101919XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616103614XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616105312XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616111008XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616112703XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616114351XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616120041XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616121720XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616123401XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616125041XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616130729XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616132411XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616134101XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616135741XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616141429XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616143123XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190616144822XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz