APRS Packet Errors for EW6668 (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
20171210183617EW6668>APRS,TCPXX*,qAX,CWOP-3:@101836z3925.100N/07705.100W_246/006g011t034r000p005P005h68b10152eCumulusDsVP
20171210184517EW6668>APRS,TCPXX*,qAX,CWOP-3:@101845z3925.100N/07705.100W_245/007g011t034r000p005P005h69b10151eCumulusDsVP
20171210190317EW6668>APRS,TCPXX*,qAX,CWOP-3:@101903z3925.100N/07705.100W_245/004g008t034r001p006P006h69b10150eCumulusDsVP
20171210191217EW6668>APRS,TCPXX*,qAX,CWOP-3:@101912z3925.100N/07705.100W_245/003g007t034r001p006P006h68b10150eCumulusDsVP
20171210192117EW6668>APRS,TCPXX*,qAX,CWOP-3:@101921z3925.100N/07705.100W_246/004g009t035r001p006P006h65b10149eCumulusDsVP
20171210193017EW6668>APRS,TCPXX*,qAX,CWOP-3:@101930z3925.100N/07705.100W_249/004g009t035r001p006P006h63b10149eCumulusDsVP