Hi Just noticed my Icom IC-9700 does it as well - personally would like this to be an option - or a way to turn off the rig when exiting the application that started it up.
Tom -- 73 Tom GM8MJV (IO85) > On 8 Jun 2020, at 23:48, Bill Somerville <g4...@classdesign.com> wrote: > > Mike, > > how would calling rig_set_powerstat before calling rig_close stop Hamlib > unilaterally turning on some rigs. Also since only a few rigs can be turned > on by CAT commands the whole premiss that there is some new assumption that > the rig is turned on before Hamlib can do a rig_open is bogus. What's wrong > with an error return from rig_open that the application can deal with, > including calling rig_set_powerstat if it wants to. Libraries that control > hardware should not do things that have not been asked for. At least make > this new and unnecessary behaviour optional and controllable by the client > that is using the Hamlib library, it's not your job to. Do things that are > asked for, making it possible to do such things when asked for by the client > is fine. > > 73 > Bill > G4WJS. > > On 08/06/2020 23:35, Black Michael via wsjt-devel wrote: >> 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> <mailto: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> >>> <mailto: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
