APRS Packet Errors for XE2RZM (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
20191121051215XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121052734XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121054246XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121055757XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121061315XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121062834XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121064346XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121065858XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121071409XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121072928XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121074440XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121075951XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121081503XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121083019XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121084531XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121090044XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121091555XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121093116XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121094629XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121100142XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121101654XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121103216XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121104729XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20191121110241XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2RZM-DP!3152.00N/-116-35.7rRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz