The assumption now is that if you ask hamlib to open the rig than the rig must
be running...so if it's not turned on a power up is attempted.WSJT-X expects a
running rig too.
I had numerous requests for this capability from people running remote
operations. They didn't seem to have any problems turning their rig off but
they were using rigctl to do it.
The only time this is done is when the rig is opened.
So...if you turn off the rig while WSJT-X is running I guess WSJT-X is
reopening the rig causing the powerup again.
You could put in a powerdown checkbox and just call set_powerstat before you
call rig_close. That should work.
Mike W9MDB
On Monday, June 8, 2020, 04:44:16 PM CDT, Bill Somerville
<g4...@classdesign.com> wrote:
Mike,
I think you mean "set the frequency".
Any chance of not having Hamlib unilaterally messing with the rig power
on/off. A config option or just don't do it and leave it to the application to
decide if this is appropriate?
73
Bill
G4WJS.
On 08/06/2020 22:31, Black Michael via wsjt-devel wrote:
Do you have "Monitor returns to last used frequency" turned on?
That will cause the rig to wake up as it has to get the frequency.
Mike W9MDB
On Monday, June 8, 2020, 03:30:13 PM CDT, Al Pawlowski <k6...@almont.com>
wrote:
Personally, I do not need/want WSJTx to turn my radio on, or off, when
starting or closing. But, it is no big problem for me either way and might be
useful for some. I just thought it odd that WSJTx tries to turn the radio on
when when it closes and had not noticed it doing either previously.
Al Pawlowski, K6AVP
Los Osos, CA USA
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
