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
20171212070823EW66880>APRS,TCPXX*,qAX,CWOP-3:@120708z0000.00N/00000.00E_289/001g007t044P000h73b10093ws31
20171212080815EW66880>APRS,TCPXX*,qAX,CWOP-7:@120808z0000.00N/00000.00E_235/000g005t043P000h76b10082ws31
20171212090821EW66880>APRS,TCPXX*,qAX,CWOP-3:@120908z0000.00N/00000.00E_244/001g004t043P000h77b10076ws31
20171212100807EW66880>APRS,TCPXX*,qAX,CWOP-3:@121008z0000.00N/00000.00E_281/000g003t042P000h79b10072ws31
20171212110814EW66880>APRS,TCPXX*,qAX,CWOP-4:@121108z0000.00N/00000.00E_256/000g004t042P000h81b10067ws31
20171212120813EW66880>APRS,TCPXX*,qAX,CWOP-2:@121208z0000.00N/00000.00E_243/002g004t041P000h83b10066ws31