APRS Packet Errors for PI8CNL-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
20171216223127PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 4689747
20171216230107PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 3307784
20171216233127PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 6783480
20171216234207PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 1409093
20171217002307PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 1497768
20171217003128PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 3793436
20171217010407PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 1141014
20171217013128PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 0403660
20171217014507PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 1581518
20171217022607PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 4807050
20171217023128PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 6014682
20171217030707PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 1800800
20171217034807PI8CNL-10>PI8MNL,PI8HLM-12,qAO,PI8RKW:;PQ: 6346917