Set ardop ARQBW before waiting on busy detector

[martinhpedersen]

From pat-users (https://groups.google.com/g/pat-users/c/RM9ViYxK5qQ):

Using ardop, when I tune my radio to the frequency of a Winlink gateway and there is an active signal toward the edge of my audio passband, then the ardop busy detector prevents me from connecting until that signal stops. This is as it should be, unless I select a reduced bandwidth so that my signal wound not interfere with the other signal.

I believe that this unnecessary wait when I select a reduced bandwidth could be avoided if Pat would immediately set ARQBW to the bandwidth chosen in the connect dialog. It appears that Pat currently sends this bandwidth setting to ardop only after ardop reports that the channel is no longer busy.

The ardop busy detector ignores signals outside the specified bandwidth, but the bandwidth setting must be updated for this to be useful.

I have "ardop" "arq_bandwidth" "Max" set to 2000 in my pat config.json file to allow maximum bandwidth when listening for incoming p2p connections. So, Pat initially sets ARQBW to 2000MAX, and the ardop busy detector uses this value until the setting is changed. I assume that this is a common setting among ardop users.

Peter LaRue
KG4JJA