APRS Packet Errors for XE1YJR (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
20190616083826XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616085517XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616091209XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616092908XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616094600XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616100239XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616101919XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616103614XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616105312XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616111008XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616112703XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616114351XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616120041XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616121720XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616123401XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616125041XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616130729XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616132411XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616134101XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616135741XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616141429XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz
20190616143123XE1YJR>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1YJR-DP!1927.16N/-99-8.49ErRNG0034 IPSC2-Mexico MMDVM 433.4000 MHz