Re: scanstart/scanstop during connections
|
Thanks John. As of yesterday the script uses attach as a check for ports in use, and if in use, makes no attempt to proceed with a beacon. If not in use, it still uses scanstop to stop scanning, then sets the frequency, and then sends the beacon. Afterward it issues scanstart to normalize. The above is the result of adding a band-aid to the existing script, but it appears the script could simply issue attach, and if the port is not in use, proceed with the beacon & then detach - instead of using scanstop/scanstart. I was going out of my way not to be attached to a port when issuing the beacon, but I'm realizing now that it shouldn't matter.
Lee K5DAT
On Sun, Sep 8, 2024 at 10:46?AM John G8BPQ via <john.wiseman= [email protected]> wrote:
The scanstop and scanstart are intended for interactive use and
assume that the sysop knows what they are doing. It is safer to
attach the port, which will do an automatic stop and will be
rejected if the port is in use.
73,
John _._,_._,_
|
