APRS Packet Errors for EW7252 (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
20170622231605EW7252>APRS,TCPXX*,qAX,CWOP-5:/222325z000.00N/0000.00E_190/005g007t078P003b09728h80cwMServer
20170622232245EW7252>APRS,TCPXX*,qAX,CWOP-5:/222332z000.00N/0000.00E_224/003g007t078P003b09728h80cwMServer
20170623034924EW7252>APRS,TCPXX*,qAX,CWOP-7:/230359z000.00N/0000.00E_117/003g006t076P003b09731h86cwMServer
20170623035604EW7252>APRS,TCPXX*,qAX,CWOP-5:/230405z000.00N/0000.00E_080/003g005t075P003b09731h86cwMServer
20170623043604EW7252>APRS,TCPXX*,qAX,CWOP-5:/230445z000.00N/0000.00E_106/002g006t075P003b09728h88cwMServer
20170623044244EW7252>APRS,TCPXX*,qAX,CWOP-3:/230452z000.00N/0000.00E_101/002g004t075P003b09728h88cwMServer
20170623044924EW7252>APRS,TCPXX*,qAX,CWOP-7:/230459z000.00N/0000.00E_095/004g007t075P003b09725h88cwMServer
20170623045604EW7252>APRS,TCPXX*,qAX,CWOP-4:/230505z000.00N/0000.00E_106/003g007t075P000b09725h87cwMServer
20170623050924EW7252>APRS,TCPXX*,qAX,CWOP-4:/230519z000.00N/0000.00E_104/002g004t075P000b09725h87cwMServer