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
20190618030023XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618031733XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618033445XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618035151XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618040844XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618042558XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618044319XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618050034XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618051758XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618053534XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618055254XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618061035XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618062807XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618064543XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618070240XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618071945XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618073656XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618075400XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618081052XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618082746XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz
20190618084452XE2JC>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2JC-DP!3230.30N/-116-59.0rRNG0034 IPSC2-Mexico MMDVM 438.8000 MHz