APRS Packet Errors for K6CLX (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
20251104102127K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104112239K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104115315K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104122351K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104125428K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104132505K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104135541K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104142620K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104145656K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz
20251104152733K6CLX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K6CLX-DP!0000.00N/00000.00ErRNG0034 IPSC2-USA MMDVM 449.7000@-5.0 MHz