APRS Packet Errors for KB2LUV-2 (last 24 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
20180624182610KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,KB2FAF-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180624184828KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,KB2FAF-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180624185433KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,KB2FAF-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180624202016KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180624205401KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180624224700KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,AC2VK-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180625124536KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000/kb2luv@arrl.net
20180625124735KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000
20180625124934KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000
20180625125134KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000
20180625125333KB2LUV-2>APT311,WIDE1-1,WIDE2-2,qAR,K2MST-1:!0000.000/00000.000k000/000/kb2luv@arrl.net