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
20171017234805PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 6199669
20171018002910PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 8296256
20171018004221PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 3749409
20171018011013PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 6056973
20171018014300PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 5361188
20171018015105PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 4717881
20171018023212PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 7056179
20171018024338PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 4139714
20171018031310PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 7313446
20171018034420PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 8691132
20171018035404PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 8955341
20171018043510PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 1701726
20171018044455PI8CJP-10>PA3CJP,qAO,PI8RKW:;PQ: 0706506
20171018051610PI8CJP-10>PD0JEW,qAO,PI8RKW:;PQ: 2274015