APRS Packet Errors for K3ARL-1 (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
20091122004314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122005314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122010314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122011316K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122012314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122014315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122020314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122021314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122022314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122023314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122024314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122030314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122031314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122032314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122033314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122034315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122043314K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122044315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122045315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122051315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122053315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR
20091122063315K3ARL-1>BEACON,qAR,N3DXC-1:;APRS-RPTR