APRS Packet Errors for MW0LPU (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
20260208131242	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208133706	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208140344	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208143334	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208145849	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208152709	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208155339	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208161916	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208164629	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208171603	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208174355	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208180945	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208183634	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260208190402	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate