Greetings:
Specifically with the SA818 modules, if the node hasn’t transmitted for a few seconds, the first bit of audio is kind of distorted and fades in. If the ID starts too soon, the first part will, in fact, get clipped off.
I changed most of the wait-times stuff to better accommodate the SA818 from the defaults, using wait-times_hd.
Here’s what I came up with, which works reasonably well on a SHARI.
[wait-times_hd]
; Sample for half-duplex
telemwait = 700 ; Time to wait before sending most telemetry
idwait = 1000 ; Time to wait before starting ID
unkeywait = 700 ; Time to wait after unkey before sending CT’s and link telemetry
calltermwait = 1000 ; Time to wait before announcing “call terminated”
In the node’s main stanza, I also shortened hangtime from 2000 to 100. This makes it much easier to get in on busy nodes if you still want to keep courtesy tones active. For simplex nodes, I personally comment out the line for linkunkeyct, so there is no courtesy tone when linked nodes unkey, but I also keep remotetx, so I know I’m getting into my own node. This makes things even more responsive, but not quite as much as disabling courtesy tones altogether.
I’ve never been a fan of the default Allstarlink courtesy tones, so I’ve changed those on all my systems as well, but that’s just personal preference.
On my HSR full duplex box, which uses two SA818’s, I shorten the unkeywait and telemwait times to 100, since it is more likely the transmitter will be, well, transmitting, and this is less of a problem than with a simplex node. I also increase the hangtime to 5 seconds to make it less likely that the fade-in thing will be encountered between transmissions, and extend totime to something ridiculously long, since I know these low-powered radios can transmit for a long time without anything bad happening.
I do still keep idwait at 1000 in the event the radio isn’t transmitting when the ID goes off.