[aprssig] APRS CSMA Settings
Stephen H. Smith
wa8lmf2 at aol.com
Tue May 20 15:23:34 CDT 2014
On 5/20/2014 4:05 PM, Robert Bruninga wrote:
> Not at all. That is connected packet. The whole reason for APRS was to
> get away from that very inefficient way of using packet...
This statement would appear to be completely irrelevant to the original comment
APRS messaging may not be "connected", but the sending station DOES continue
trying repeatedly to send the message if it doesn't get an ack.
You are the one that keeps casigating UIview for NOT using the decaying retry
algorithm, so you do seem to acknowledging that APRS clients should be making
multiple retries until either ACK or timeout.....
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
> Of Bob Poortinga
> Sent: Tuesday, May 20, 2014 1:15 PM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] APRS CSMA Settings
> WB4APR writes:
>> This does not apply to APRS at all. APRS never retries (other than
>> simply waiting for the next beacon repeat... 10 minutes for local
>> direct packets, and 30 minutes for 2 hop fixed beacons).
> I thought that the sending station of an APRS messages retries until it
> gets an acknowledgment using an exponential back-off algorithm.
> Bob Poortinga NG9M
More information about the aprssig