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
20200920200418CW3794>APRS,TCPXX*,qAX,CWOP-3:@202004z0000.00N/00000.00W_056/001g004t101L818r000P000p000h20b10150VL1252
20200920203442CW3794>APRS,TCPXX*,qAX,CWOP-5:@202034z0000.00N/00000.00W_129/001g006t101L786r000P000p000h20b10146VL1252
20200920210439CW3794>APRS,TCPXX*,qAX,CWOP-3:@202104z0000.00N/00000.00W_136/000g006t102L739r000P000p000h19b10141VL1252
20200920213435CW3794>APRS,TCPXX*,qAX,CWOP-4:@202134z0000.00N/00000.00W_165/000g004t103L683r000P000p000h19b10137VL1252
20200920220424CW3794>APRS,TCPXX*,qAX,CWOP-4:@202204z0000.00N/00000.00W_134/000g003t103L616r000P000p000h18b10134VL1252
20200920230437CW3794>APRS,TCPXX*,qAX,CWOP-3:@202304z0000.00N/00000.00W_263/001g006t103L434r000P000p000h17b10129VL1252
20200921003443CW3794>APRS,TCPXX*,qAX,CWOP-7:@210034z0000.00N/00000.00W_284/000g004t100L108r000P000p000h18b10128VL1252
20200921010428CW3794>APRS,TCPXX*,qAX,CWOP-7:@210104z0000.00N/00000.00W_257/000g004t099L026r000P000p000h18b10128VL1252
20200921013447CW3794>APRS,TCPXX*,qAX,CWOP-4:@210134z0000.00N/00000.00W_254/000g000t097L000r000P000p000h20b10128VL1252