[aprssig] Dup Messages from a WinAPRS Station

[Herb Gerhardt]

This does not appear to be a WinAPRS problem.  WinAPRS can only be set for
sending any message a maximum of 9 times.  At that point it will cease
sending the message or auto reply message unless the operator takes manual
keystroke action or the desired station that the message is addressed to all
of a sudden is received by the sending station and the sending station
computer is still on-line.  If that is the case, the sending computer will
attempt to send it 9 more times.  I know, clear as mud but I hope you can
follow the sequence.

I have no idea how any message could be sent over 1000 times by any program
and keep sending it whether it receives an ACK or not.  I believe there was
an older version of XASTIR that did try to keep sending a message until it
received an ACK but that problem was fixed in the later versions of XASTIR
several months ago.

Also keep in mind that APRS is a non-verified packet system.  So, just
because your station is sending out the ACK does not mean that the other
station is receiving it.  Just like you might be receiving a reply to your
message without ever having received the ACK for your message.  Lots of
transmissions die in collisions and do not make it to their desired station.

Seems to me like someone has something set up in their computer that keeps
resending the auto reply message.  Any other ideas on this topic?

Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site:  http://www.nwaprs.info


> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org
> [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of AA3JY at Winlink.org
> Sent: Sunday, October 23, 2005 9:34 AM
> To: aprssig at lists.tapr.org
> Subject: [aprssig] Dup Messages from a WinAPRS Station
>
>
> I've noticed this problem with the WinAPRS program. But for some
> reason their Auto Answer (AA:) seems to generate Dup Messages..an
> ACK is sent back from the receiving station but the sending
> station does not cancel the message(Auto Reply)
>
> example:
> N3XKU 	 AA3JY 	 10/23 11:27:41z 	 AA:Not around.
>
> ...been reciving these dup message in excess of approx. 1000+ times...
>
> I'm sure this is a simple fix.
>
> Regards,
>
> Clay AA3JY
> (Via WL2K)
>