APRS Packet Errors for XE2CS (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
20240504231735XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240504234802XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505001829XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505004857XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505014951XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505022018XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505025045XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505032111XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505035137XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz
20240505042204XE2CS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CS-DP!2906.00N/110-0.00WrRNG0034 IPSC2-Mexico MMDVM 438.5000@-5.0 MHz