APRS Packet Errors for EW3656 (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
20180716113606EW3656>APRS,TCPXX*,qAX,CWOP-3:@161136z51.3160 N/0.8894 E_174/002g003t089r000p000P000b10069h30L000.WD 166
20180716120106EW3656>APRS,TCPXX*,qAX,CWOP-3:@161201z51.3160 N/0.8894 E_109/002g005t091r000p000P000b10068h30L000.WD 166
20180716120606EW3656>APRS,TCPXX*,qAX,CWOP-7:@161206z51.3160 N/0.8894 E_158/001g001t091r000p000P000b10066h30L000.WD 166
20180716123605EW3656>APRS,TCPXX*,qAX,CWOP-3:@161236z51.3160 N/0.8894 E_185/002g003t094r000p000P000b10059h29L000.WD 166
20180716133606EW3656>APRS,TCPXX*,qAX,CWOP-3:@161336z51.3160 N/0.8894 E_270/001g003t082r000p000P000b10056h37L000.WD 166
20180716140605EW3656>APRS,TCPXX*,qAX,CWOP-7:@161406z51.3160 N/0.8894 E_180/001g001t080r000p000P000b10061h40L000.WD 166
20180716143605EW3656>APRS,TCPXX*,qAX,CWOP-4:@161436z51.3160 N/0.8894 E_352/001g003t088r000p000P000b10058h32L000.WD 166
20180716153105EW3656>APRS,TCPXX*,qAX,CWOP-4:@161531z51.3160 N/0.8894 E_305/000g003t083r000p000P000b10034h41L000.WD 166
20180716160606EW3656>APRS,TCPXX*,qAX,CWOP-4:@161606z51.3160 N/0.8894 E_225/001g001t084r000p000P000b10043h41L000.WD 166
20180716163105EW3656>APRS,TCPXX*,qAX,CWOP-7:@161631z51.3160 N/0.8894 E_081/001g003t084r000p000P000b10057h40L000.WD 166