APRS Packet Errors for EW66880 (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
20170817000505EW66880>APRS,TCPXX*,qAX,CWOP-7:@170005z0000.00N/00000.00E_316/000g000t084P000h78b10152ws31
20170817010505EW66880>APRS,TCPXX*,qAX,CWOP-1:@170105z0000.00N/00000.00E_316/000g000t079P000h90b10157ws31
20170817020506EW66880>APRS,TCPXX*,qAX,CWOP-2:@170205z0000.00N/00000.00E_314/000g000t079P000h91b10164ws31
20170817030506EW66880>APRS,TCPXX*,qAX,CWOP-4:@170305z0000.00N/00000.00E_314/000g000t078P000h93b10168ws31
20170817040506EW66880>APRS,TCPXX*,qAX,CWOP-7:@170405z0000.00N/00000.00E_288/000g000t077P000h94b10166ws31
20170817050506EW66880>APRS,TCPXX*,qAX,CWOP-3:@170505z0000.00N/00000.00E_346/000g000t076P000h93b10163ws31