APRS Packet Errors for PI8CJP-10 (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
20171018092212PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 3010961
20171018094757PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 7721562
20171018100310PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 3775830
20171018104411PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 1617964
20171018104834PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 1427767
20171018112511PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 4585078
20171018114910PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 1670781
20171018120611PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 9754317
20171018124711PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 9568528
20171018124944PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 6470860
20171018132811PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 8515467
20171018135019PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 3436357
20171018140911PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 1126695
20171018145011PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 7412293
20171018145055PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 5070771