APRS Packet Errors for N2NUO-15 (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
20171216223824N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171216230844N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171216233905N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217000924N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217003944N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217010315N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22
20171217013335N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217020355N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217023414N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217030435N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217033455N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served
20171217040514N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 57 served