[aprssig] WinAPRS fails to accept ACKed messages

Chris Rose kb8uih at sbcglobal.net
Fri Nov 26 09:20:18 EST 2004

I use WinAPRS but don't leave the computer linked to
TCPIP 24/7.  I just connect when I want to send a
message directly to another station that I know is
connected.  We ususally get acks and have an exchange
and then I disconnect.  We are 900 mi apart so RF
directly is out of the question.  

Locally, I have sent and received messages and haven't
had this problem.  

There is a message retry function to keep sending a
message that hasn't been acked that defaults to 5X. 
It can be changed however.  

The only way I know to not ack a message and stop
sending it is if the sending station is an aligator
and doesn't hear as well as it transmits.  

How about one in a heavy RF environment that can't
hear as well as it needs to?  I am not justifying
this, It is just a theory to explain your problem.

What station is it that won't ack the message and then
stop sending?


--- aa3jy at winlink.org wrote:

> I've been noticing this problem for awhile.. When I
> receive a message from a user of WinAPRS..my program
> will send out continous ACK's to that
> message..However the original message fails to be
> deleted by the returned *ACK*. I have to generate
> another message to the WinAPRS user to plse delete
> his last message..other wise I receive a screen full
> of the same message. If the WinAPRS user isn't by
> his keyboard for months..well..it's self
> explainatory. 
> I've been watching the TCP/IP screen and I can see
> dozens of messages not being cancelled or deleted by
> users of WinAPRS..Isn't there a time expiration
> feature with that program??
> Clay AA3JY
> (via Winlink)
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org

More information about the aprssig mailing list