开云体育

I want the LK button to be ON when I start up Fldigi. I know that a script can accomplish this task. I don't want to push the buttons to execute the script. I want the LK button ON every time I start Fldigi without having to push any other buttons.?

?

Can this be done? If so, how?

?

Thanks.

?

-Randy, W4IFI

?

It does not.

Don't get me going Bob on being inconvenienced, lazy, or pressed for time.? Neither is the case here. I'm working on a station automation project with NodeRed and Stream Deck. The LK button is one thing I am trying to get figured out.?

?

I'm looking for help here, not snark.

?

-Randy

The state of the LK button is not saved between sessions, however you can create a configuration script that will do just what you want.? Please see?

Thanks David. I did see that a script would do the trick. But the next move I'm seeking is to have the script run at startup. If there's not a method to do that within fldigi then I'll work on crafting a process in NodeRed.

?

-Randy

There is no automated script execution on startup.? Might be something to add in a future revision.

Hello David,

Welcome back :-)

I tried the configuration feature but it also doesn't appear to store or restore the Lk setting. Only a Macro or pushing the Lk Button (possibly via an external script) appears to work.

Basically, I would think it would be the most straightforward way (and place) to add this setting in the 'fldigi.prefs' configuration file, where we already have...

sqlonoff:0
afconoff:0


... by adding (storage and retrieval, of course)

reverseonoff:0


On the other hand, the reverse state can actually be stored in a per-mode-per-band way by activating the respective config option, but even when I tried doing so, defining an RTTY frequency entry for 20 m, setting 'Rv' ON and restarting fldigi, it would not auto-restore the selected state. But when 'touching' the frequency, e.g. changing it from '14085' (previous QRG auto-reloaded) to '14086', 'Rv' comes on immediately, if stored before for the 20 m band in RTTY. So it's there already but just not entirely functional for the purpose of a non-attended startup.


- - - - - -


But now get this:

After I tried this per-mode-per-band setting and switched this option OFF again, I noted that FLdigi actually started up with 'Rv' ON! Tried it several times...

Checked the setting, and yes, it's not band-dependent, so what's going on?

I thus opened the 'fldigi.prefs' configuration file, just the way I had described it above, and there it was, just with a slightly different key name:

reverse:1

Now I tried setting this key back to '0' and fldigi actually started with 'Rv' OFF again, so that's the way to get it done, it seems!


But beware: you'll have to manually edit (or, if not yet present, add) this line in the 'fldigi.prefs' configuration file and set it to 'reverse:1', with the per-mode-per-band option DEACTIVATED and while FLdigi does not run. Then you should be OK for the next FLdigi start(s) with 'Rv' auto-ON.

Bottom line: FLdigi appears to read and obey this global config setting, but it does not store the last state in there, even when 'Save config' is selected upon close down.
The opposite is the case using the per-mode-per-band option: Rv states are stored in the respective other file called 'mode_state.prefs', but the auto-reactivation only works when changing the tuned frequency (manually).


Hope this will provide a functional clue...


Thanks and 73s

Tobias
.-.-.