开云体育

The following might help.?? It was posted to facebook when the new development version was released.

There is a new Development release of APRSIS32 (2024/01/16 15:25) that includes the following of particular interest to VARA APRS users:

0) Configure / Messages / RF Double-Ack to enable double acks on RF ports (default: off)
1) Enables / Ports / Digipeat to enable or disable digipeating (disabled if no <DigiXForm>s)
2) User configurable named <RetrySet>s governing the retry intervals for messaging.
3) Configure / Messages / Retry Set selects the default retries for new chats (QSOs)
4) The Chat window has a Retry Set drop-down menut that affects that chat only.
To get the new release, check the APRSIS32 About box.? If it doesn't say Development, then you'll need to change to the Development mode first.? See details at the links below.

Four custom RetrySets are provided when the new version is first executed.?? They are:
Default: 8,16,8,32,64,96,128
APRS-IS: 32,32,64,96,128
NoRetries:
Vara-HF: 45,90,180

The numbers are seconds between the retry transmissions.?? The total time required for a non-acknowledged message would be the sum of the numbers of a specific RetrySet.?? The number of retries is, of course, the count of intervals in the RetrySet.

If you want to customize these, or add your own new <RetrySet>s, you need to edit the APRSIS32.xml configuration file.?? The default XML entries are show below.

<RetrySet Name="Default">
<Intervals>8,16,8,32,64,96,128</Intervals>
</RetrySet>

<RetrySet Name="APRS-IS">
<Intervals>32,32,64,96,128</Intervals>
</RetrySet>

<RetrySet Name="NoRetries">
<Intervals></Intervals>
</RetrySet>

<RetrySet Name="Vara-HF">
<Intervals>45,90,180</Intervals>
</RetrySet>

Your entries may be surrounded by <!-- xxxx --> comments which are not necessary for new entries.

And as always, make sure you have the client CLOSED when you edit the XML configuration or your changes will be overwritten.

Oh, and I also discovered that the final retry step was not actually being used in APRSIS32.? That has been corrected in this release.