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
20191023025257EW66880>APRS,TCPXX*,qAX,CWOP-6:@230252z0000.00N/00000.00E_254/000g000t057P000h70b10197ws31
20191023035256EW66880>APRS,TCPXX*,qAX,CWOP-1:@230352z0000.00N/00000.00E_235/000g001t056P000h73b10197ws31
20191023045256EW66880>APRS,TCPXX*,qAX,CWOP-2:@230452z0000.00N/00000.00E_235/000g000t056P000h69b10197ws31
20191023055256EW66880>APRS,TCPXX*,qAX,CWOP-7:@230552z0000.00N/00000.00E_235/000g000t053P000h74b10195ws31
20191023065256EW66880>APRS,TCPXX*,qAX,CWOP-2:@230652z0000.00N/00000.00E_234/000g001t053P000h75b10194ws31
20191023075257EW66880>APRS,TCPXX*,qAX,CWOP-5:@230752z0000.00N/00000.00E_234/000g001t053P000h75b10193ws31