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
20170624201530PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624203833PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624210136PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624212423PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624214727PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624221409PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624224235PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624231120PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170624233935PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170625000754PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170625003607PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170625010428PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20170625013257PI1SNK-7>APBPQ1,TCPIP*,qAC,PI1SNK-7:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB