APRS Packet Errors for XE2CGR (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
20191023011855XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023013420XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023014936XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023020458XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023022017XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023023542XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023025100XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023030621XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023032137XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023033842XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023035220XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023040819XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023042336XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023043900XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023045413XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023050932XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023052449XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023054012XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023055533XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023061050XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023062606XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023064129XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023065640XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz
20191023071154XE2CGR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2CGR-DP!3334.84N/-112-14.2rRNG0034 IPSC2-Mexico MMDVM 438.1500@-5.0 MHz