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
20180217152953N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217160013N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217163033N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217170053N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217173113N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217180133N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217183153N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217190213N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217193233N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217200253N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217203313N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served
20180217210333N2NUO-15>APRS,TCPIP*,qAC,N2NUO-11:=42.02/-76.50?WxBot 1.22 85 served