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
20190217221926XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217223552XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217225218XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217230840XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217232502XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217234128XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190217235752XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218001414XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218003033XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218004703XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218010327XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218011957XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218013624XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218015252XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218020912XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218022536XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218024159XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218025829XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218031451XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218033113XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218034739XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz
20190218040409XE2RZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2RZM-DP!0000.00N/00000.00ErRNG0034 IPSC2-Mexico MMDVM 438.1000@-5.0 MHz