Hello, I have noticed that changing frequency from the drop menù will change frequency in both VFO A and B in my icom 756 pro2, while only the VFO A should be modified without affecting frequency and mode set in VFO B.
73 de Phil, iz1fks
To see this working, head to your live site.
same here on a 756 Pro III
Thanks for the info about pro III; it's really strange because there is not a CAT CI-V command for vfo A or B for these TRX, but just one command and the frequency of the selected VFO only should be changed
@iz1fks & @htperry
This is an Omnirig configuration.
If you know the right CAT command, you can manipulate this section in the "IC-756 Pro.ini" file under the omnirig directory.
[pmFreq]
;Set operating frequency
Command=FEFE5CE0.05.0000000000.FD
Value=5|5|vfBcdLU|1|0
ReplyLength=17
Validate=FEFE5CE0050000000000FD.FEFEE05CFBFD
Hi Irad, I'm using OmniRig with other software (i.e. JS8CALL and Log4OM) but this issue doesn't appear there, only the active VFO is set to the required frequency. I checked about it in the CI-V command manual but there is no a specific command for setting VFO A or B in these rigs, just the single command you have posted, but it should set only the active VFO, I have not understood why these issue happen only with VarAC. I had perfomred some sniffing with both js8call and VarAC changing frequency once after opening sniffing sw, and detected that the set frequency command is invoked twice using VaraAC while just one using Js8call. I attached both sniffing files, hope this can help. 73 de Phil
I believe Shooting the same command twice is not the problem.
But on the other hand - I can't tell for sure why you experiencing this.
Next version will do direct can control (only for freq settings... not reading). And also wont fire twice the omnirig command. You will be able to track of the number of omnirig command fires on the VarAC. og both in file and on screen:
thanks Irad, I'll try next version to see what will happen both with omnirig and direct command way and I'll report you. If you have a beta version to share I could try it even before next release. 73 de Phil, iz1fks
@iz1fks Hi Phil. did you check the latest version 3.4 and see if it solves your issues with CAT commands ?
Hi Irad, I've just installed the new version, from first tests this is the situation:
Frequency control -> OmniRig : no changes from previous version behaviour
Frequency control -> CAT: it looks working fine !! only the active VFO is updated as it should.
there is a small bug about "CAT Configuration" settings (at least with Win7); the settings remain not active (in grey) until selection of CAT option in PTT Configuration, only after this selection CAT Configuration can be modified, but changing to CAT only in Frequency Control is not enabling "CAT Configuration".
I have tested also COM RTS PTT, it seems it's working fine but the PTT ON button test does set the rtx in ptt on just for few milliseconds and then switching off without can use ptt off button. this not happen using cat or omnirig for ptt where the two test pushbutton are working well. thank you and 73
Thank you Phil for reporting the bugs. Yes - the CAT cant read the current VFO frequency. only setting it. for now. In the future I will work on it.
I addressed the bugs your just mentioned. Can you please use this VarAC.exe to check if those bugs are gone ?
the RTS/DTR Test button
The gray out of the CAT when selecting only CAT freq.
https://drive.google.com/file/d/1ctOfnmgG2TQ9eG7l9jVmJYGminiZn4Ff/view?usp=sharing