APRS Packet Errors for IR3CA-2 (last 24 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
20180617024939IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617033442IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617073817IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617095321IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617095825IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617101831IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617145830IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617185205IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617185710IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617211717IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617212717IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617221717IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617222224IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617230714IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617232225IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180617234219IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122
20180618014229IR3CA-2>APNUB3,qAR,IZ3GME-1:!4600.64N/0122