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
20171017145508PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 5728186
20171017155531PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 2914605
20171017165524PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 3139768
20171017175524PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 3033427
20171017182019PI8CNL-10>PA7O,PI8HLM-12,qAO,PI8RKW:;PQ: 2678020
20171017182643PI8CNL-10>PI9D,PI8HLM-12,qAO,PI8RKW:;PQ: 1628599
20171017185517PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 9136408
20171017195519PI8CNL-10>PI8CJP,PI8HLM-12,qAO,PI8RKW:;PQ: 0478671