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
20170823040601EW66880>APRS,TCPXX*,qAX,CWOP-3:@230406z0000.00N/00000.00E_301/000g000t074P000h95b10138ws31
20170823050543EW66880>APRS,TCPXX*,qAX,CWOP-6:@230505z0000.00N/00000.00E_301/000g000t073P000h96b10138ws31
20170823060556EW66880>APRS,TCPXX*,qAX,CWOP-4:@230605z0000.00N/00000.00E_301/000g000t072P000h96b10137ws31
20170823070555EW66880>APRS,TCPXX*,qAX,CWOP-5:@230705z0000.00N/00000.00E_301/000g000t072P000h97b10132ws31
20170823080557EW66880>APRS,TCPXX*,qAX,CWOP-5:@230805z0000.00N/00000.00E_301/000g000t071P000h97b10124ws31
20170823090600EW66880>APRS,TCPXX*,qAX,CWOP-5:@230906z0000.00N/00000.00E_301/000g000t070P000h97b10124ws31