Hi Irad and group,
I´ve two questions/suggestions concerning the frequency scheduler. Q1:
Is it expected behaviour that the freqency scheduler only changes "in realtime" at the time which is stated in the scheduler? To make my question more clear:
e.g. my scheduler says 0900 14.105.000 and 2000 7.105.000
I start up my VarAC at 1200
I click FREQ SCHEDULE ON
Hi Irad,
what about the option to connect to another station via telnet or SSH like in Winlink. You can choose different modem types there and also telnet.
This would be a useful option to expand a regional or local cluster inside a VPN i.e.
Another example would be, to use the station as GW or VMail GW to hf if allowed.
Maybe important for OMs that has limited nor access for an Antenna but they could use VarAC as well (VMail).
73 Andre / DL4QB
VarAC QSOs are 100% radio based and I want to keep it this wa . SSH links would generate a world of INTERNET QSOs. Not in my favour.
Below follows the cat control file I've been using for the IC-726 [Icom IC-726]
CmdType=HEX
PTTOn=
PTTOff=
ModeUSB=FEFE30E00101FD
ModeUSB_D=FEFE30E00101FD
Hi there and thank you for sharing. We already have IC-726 in the list for a few months now. I am attaching the file we have and I would love to hear from you if what you suggest is the same and if not - what are the differences:
[Icom IC-726]
CmdType=HEX
ModeUSB=FEFE30E0060102FD
ModeUSB_D=FEFE30E00604FD
ModeFM=FEFE30E00605FD
SetFreq_Data_method=BCD
SetFreqVfoA_Cmd=FEFE30E005{}FD
SetFreqVfoA_param_length=10
SetFreqVfoA_hz_res=1
ReadFreqVfoA_Cmd=FEFE30E003FD
ReadFreqVfoA_Result_Data_method=BCD
ReadFreqVfoA_Result_hz_res=1
ReadFreqVfoA_Result_Length=22
ReadFreqVfoA_Result_Freq_Start_Pos=11
ReadFreqVfoA_Result_Freq_Length=10
DefaultPortWaitTimeMs=200
Not a bug report, but the CAT control file I've been using for the Kenwood TK-90. [Kenwood TK-90]
CmdType=TEXT
PTTOn=TX[ENT]
PTTOff=RX[ENT]
ModeUSB=MD2[ENT]
ModeUSB_D=MD2[ENT]
Hello Alister
Thank you for sharing. We have this in the CAT file from ZS6LVL. Please let me know which one is the prefered option.
[Kenwood Tk-90]
CmdType=TEXT
PTTOn=TX[ENT]
PTTOff=RX[ENT]
ModeUSB=MD2[ENT]
SetFreq_Data_method=TEXT
SetFreqVfoA_Cmd=FA{}[ENT]
SetFreqVfoA_param_length=11
SetFreqVfoA_hz_res=1
ReadFreqVfoA_Cmd=FA[ENT]
ReadFreqVfoA_Result_Data_method=TEXT
ReadFreqVfoA_Result_hz_res=1
ReadFreqVfoA_Result_Length=14
ReadFreqVfoA_Result_Freq_Start_Pos=4
ReadFreqVfoA_Result_Freq_Length=10
VarACStartCmd=
VarACExitCmd=
Hi Irad,
thanks for your answer.
What you describe is rather easy to answer. When no time is defined, nothing happens. You give the example 12:00-13:00 20m. Out of the given times simply nothing happens if I activate the scheduler e.g. at 15:00. If I startup my rig at 12:34 and I activate the scheduler, the rig switches to 20m. That´s the only thing I meant. By the way: I do not request the ability to enter time-ranges like "from 15:00" "to 17:00". It is good as it is.
See my example:
I´ve set my rig
0900 20m
2000 40m
e.g. I run on 15m, doing QSOs at a time of 14:45. Then I decide to switch on the scheduler at 14:50. In this moment, the scheduler recognizes the time and switches over to 20m. That is what I meant. Think about, it is not a major subject of course.
73 de Lenz!