APRS Packet Errors for W6SLO-2 (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
20260208130323W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208133324W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208140324W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208143324W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208150324W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208153325W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208160324W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208163324W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208170324W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208171326W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208174325W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208181325W6SLO-2>APDW17,WIDE1-1,qAR,K7AZ-11:!3540.48NS12103.21W#PHG3140Direwolf Linux
20260208184324W6SLO-2>APDW17,WIDE1-1,qAR,W3IVH-10:!3540.48NS12103.21W#PHG3140Direwolf Linux