If FREQ SCHEDULE is on at starting VarAC waits until the first change, but does not look up in the VarAC_frequency_schedule.inf immediately after start up and does not use the given frequency.
Example:
content of VarAC_frequency_schedule.inf
...
06:00,28.105.000
08:00,10.133.000
...
FREQ SCHEDULE was ON and after a new start at e.g. 6:15 FREQ SCHEDULE is ON (right!).
But VarAC doesn't use immediately 28.105 MHz, which would be the "actual slot frequency" between 6:00 and 8:00, it remains waiting from 6:15 (start of VarAC in this example) until the 1st change at 8.00 and after that goes to 10.133 MHz.
So after starting VarAC with activated scheduler it should look first in VarAC_frequency_schedule.inf and pick up for the actual time the given slot.
I must confess that we are talking about a high level of comfort 😉
73, Lutz, DH7LK
I am not in favor of doing this Lutz
I have given this a lot of thinking... weather the freq scheduler should be "ranges" or simply a list of times telling VarAC when to change.
In my opinion - when you start VarAC - you want to be where you left it which is more of an expected behavior.
73s
Irad