APRS Packet Errors for dw6699 (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
20171216090103dw6699>APRS,TCPXX*,qAX,CWOP-5:@160901z3239.86N/09810.100W_186/001g000t041P000h52b10131ws31
20171216091102dw6699>APRS,TCPXX*,qAX,CWOP-5:@160911z3239.86N/09810.100W_186/001g000t041P000h52b10132ws31
20171216092102dw6699>APRS,TCPXX*,qAX,CWOP-5:@160921z3239.86N/09810.100W_186/000g000t041P000h52b10130ws31
20171216093102dw6699>APRS,TCPXX*,qAX,CWOP-5:@160931z3239.86N/09810.100W_186/000g000t041P000h53b10130ws31
20171216094102dw6699>APRS,TCPXX*,qAX,CWOP-5:@160941z3239.86N/09810.100W_186/000g000t041P000h53b10128ws31
20171216121102dw6699>APRS,TCPXX*,qAX,CWOP-4:@161211z3239.86N/09810.100W_185/000g000t041P000h55b10122ws31
20171216122102dw6699>APRS,TCPXX*,qAX,CWOP-4:@161221z3239.86N/09810.100W_185/001g000t041P000h54b10121ws31
20171216123102dw6699>APRS,TCPXX*,qAX,CWOP-4:@161231z3239.86N/09810.100W_185/000g000t041P000h54b10120ws31
20171216124103dw6699>APRS,TCPXX*,qAX,CWOP-4:@161241z3239.86N/09810.100W_186/001g000t042P000h54b10117ws31
20171216125102dw6699>APRS,TCPXX*,qAX,CWOP-4:@161251z3239.86N/09810.100W_186/000g000t041P000h54b10119ws31
20171216130102dw6699>APRS,TCPXX*,qAX,CWOP-4:@161301z3239.86N/09810.100W_186/000g000t042P000h54b10118ws31
20171216131103dw6699>APRS,TCPXX*,qAX,CWOP-4:@161311z3239.86N/09810.100W_186/001g000t042P000h54b10117ws31