APRS Packet Errors for CW3794 (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
20201001140441CW3794>APRS,TCPXX*,qAX,CWOP-5:@011404z0000.00N/00000.00W_000/000g000t073L061r000P000p000h28b10180VL1252
20201001143444CW3794>APRS,TCPXX*,qAX,CWOP-7:@011434z0000.00N/00000.00W_000/000g000t076L176r000P000p000h26b10183VL1252
20201001153443CW3794>APRS,TCPXX*,qAX,CWOP-3:@011534z0000.00N/00000.00W_070/000g002t084L391r000P000p000h25b10186VL1252
20201001163424CW3794>APRS,TCPXX*,qAX,CWOP-5:@011634z0000.00N/00000.00W_210/001g004t087L576r000P000p000h22b10190VL1252
20201001193417CW3794>APRS,TCPXX*,qAX,CWOP-5:@011934z0000.00N/00000.00W_163/000g003t100L843r000P000p000h13b10176VL1252