APRS Packet Errors for PI1SNK-7 (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
20170721170458PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721173314PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721180128PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721182942PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721185756PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721192610PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721195425PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721202238PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721205053PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721211906PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721214721PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721221534PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170721224348PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB