APRS Packet Errors for DW9751 (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
20180222184202DW9751>APRS,TCPXX*,qAX,CWOP-5:@221842z0000.00N/00000.00E_316/003g017t047P000b10245L142ws31
20180222185222DW9751>APRS,TCPXX*,qAX,CWOP-6:@221852z0000.00N/00000.00E_307/004g011t048P000b10246L142ws31
20180222190201DW9751>APRS,TCPXX*,qAX,CWOP-6:@221902z0000.00N/00000.00E_292/001g011t048P000b10246L142ws31
20180222191213DW9751>APRS,TCPXX*,qAX,CWOP-5:@221912z0000.00N/00000.00E_300/002g007t048P000b10246L142ws31
20180222192211DW9751>APRS,TCPXX*,qAX,CWOP-1:@221922z0000.00N/00000.00E_300/005g007t048P000b10245L142ws31
20180222193217DW9751>APRS,TCPXX*,qAX,CWOP-2:@221932z0000.00N/00000.00E_316/003g009t049P000b10245L142ws31
20180222194212DW9751>APRS,TCPXX*,qAX,CWOP-6:@221942z0000.00N/00000.00E_301/004g008t049P000b10243L142ws31
20180222195216DW9751>APRS,TCPXX*,qAX,CWOP-2:@221952z0000.00N/00000.00E_305/004g008t049P000b10242L142ws31
20180222200218DW9751>APRS,TCPXX*,qAX,CWOP-2:@222002z0000.00N/00000.00E_285/013g013t049P000b10240L142ws31
20180222201216DW9751>APRS,TCPXX*,qAX,CWOP-5:@222012z0000.00N/00000.00E_317/008g013t049P000b10240L142ws31
20180222202230DW9751>APRS,TCPXX*,qAX,CWOP-3:@222022z0000.00N/00000.00E_309/001g011t048P000b10238L142ws31
20180222203218DW9751>APRS,TCPXX*,qAX,CWOP-3:@222032z0000.00N/00000.00E_303/001g005t049P000b10236L142ws31