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
20190422171726EW66880>APRS,TCPXX*,qAX,CWOP-4:@221717z0000.00N/00000.00E_050/001g008t080P000h56b10180ws31
20190422181726EW66880>APRS,TCPXX*,qAX,CWOP-7:@221817z0000.00N/00000.00E_305/000g007t080P000h52b10176ws31
20190422191726EW66880>APRS,TCPXX*,qAX,CWOP-7:@221917z0000.00N/00000.00E_070/002g007t081P000h50b10167ws31
20190422201726EW66880>APRS,TCPXX*,qAX,CWOP-5:@222017z0000.00N/00000.00E_083/005g006t081P000h56b10165ws31
20190422211726EW66880>APRS,TCPXX*,qAX,CWOP-6:@222117z0000.00N/00000.00E_053/000g012t080P000h57b10161ws31
20190422221726EW66880>APRS,TCPXX*,qAX,CWOP-1:@222217z0000.00N/00000.00E_081/001g004t078P000h58b10160ws31