problem solved thanks to Irad and some troubleshooting with packet CI-V sniffing. icom 756pro2 .ini file used by omnirig need to be modified: [pmFreqA] Command=FEFE64E0.05.0000000000.FD Value=5|5|vfBcdLU|1|0 ReplyLength=17 Validate=FEFE64E0050000000000FD.FEFEE064FBFD [pmFreqB] Command=FEFE64E0.05.0000000000.FD Value=5|5|vfBcdLU|1|0 ReplyLength=17 Validate=FEFE64E0050000000000FD.FEFEE064FBFD direct single VFO command to set frequency is not supported with IC756pro2/3 but a selection of the VFO A or B is performed by VarAC, anyway it is necessary to modify [pmFreqA] ( and optionally [pmFreqB] sub vfo) in order to be able to use single VFO option in Varac setup window. 73 de Phil, iz1fks

problem solved thanks to Irad and some troubleshooting with packet CI-V sniffing. icom 756pro2 .ini file used by omnirig need to be modified: [pmFreqA] Command=FEFE64E0.05.0000000000.FD Value=5|5|vfBcdLU|1|0 ReplyLength=17 Validate=FEFE64E0050000000000FD.FEFEE064FBFD [pmFreqB] Command=FEFE64E0.05.0000000000.FD Value=5|5|vfBcdLU|1|0 ReplyLength=17 Validate=FEFE64E0050000000000FD.FEFEE064FBFD direct single VFO command to set frequency is not supported with IC756pro2/3 but a selection of the VFO A or B is performed by VarAC, anyway it is necessary to modify [pmFreqA] ( and optionally [pmFreqB] sub vfo) in order to be able to use single VFO option in Varac setup window. 73 de Phil, iz1fks

Hi @irad d , I performed several tests with CAT on my IC-756P2 using sniffing on the CI-V bus and detected some behaviour I think could be impreved or fixed: 1.      COM port PTT (RTS) works fine, but the PTT Test (PTT ON -PTT OFF buttons in the setup window) don't work with COM port setting and "access COM port denied" is reported in CAT test error log. 2.      I have to use omnirig for other piece of software, but unfortunately I cannot use omnirig with Varac due to the VFO A/B issue reported here: https://www.varac-hamradio.com/forum/varac-hf-discussion-forum/ic-756pro2-vfo-a-b-cat-frequency 3.      I use VarAC native CAT interface to control rig and enabled"read freq. every 2 sec" too. Since I have also omnirig running on the same COM port shared, I have noticed that frequency in VarAC stop updating if Omnirig poll interval is set less than 2 seconds (I usually set it at 100ms) Only the freq polling is affected the frequency write to the rig is working fine. I have the possibility to use two physical com ports on the same CI-V bus but the behaviour is the same.  I think it would be useful an option flag to disable VarAC CAT polling, but enabling frequency update only listening the packets on the bus polled by omnirig or other software (e.g. Omnirig, FLrig both using polling to update freq/mode). By the way with frequency reading from bus also Icom CI-V transceive function could be used alone with VarAC embedd CAT interface 73 de Phil,iz1fks

Same issue with v7.3. The last windows 7 compatible version is 7.0.8 73 de Phil

@irad d I think that's related to a modification to varac.ini file performed by v7.1. Downgrading without replacing the ini file with a clean one didn't solve the issue; downgrading deleting the ini file and setting the new one did. I don't know what in the new ini fails with communication to vara hf in windows 7 but that might be the cause. 73 de Phil,iz1fks

I have rebuilt the Varac.ini file and with 7.08 it looks the issue is solved...

same issue here, but downgrading software version to 7.08 or previous v6 doesn't solve the issue and I don't understand the reason... I had also crash of Varac during qso and VarAC32 thread doesn't disappear from windows task manager. I have tried to use VARA FM modem instead just for test and no issue at all even with latest Varac version, I suspect there is something related to tcp socket communication with VARA HF 73 de Phil,iz1fks

I tested Varac using VARA FM, no issue at all at the stratup. the issue is only with Vara HF

Yes, I'm betwwen hams that reported Win7 worked, but now I have tried to downgrade to previous Varac versions that always worked fine (6.6.13) while now have the same issue here reporteted. I cannot findf out which is the communication problem between VARA and Varac at the stratup...

I installed VARA+VarAC into a laptop where these software never where installed before, same behaviour with a VarAC32 thread in task manager after shutting down. The laptop has win7 as well. 73 d ePhil

if I try to disconnect and connect again modem after varac is opened, no issue is detected: vara modem closes and start again and it's immediately connected. the issue is only at the Varac startup

I attach the varAC.ini here as well as settings screen. The com related popup is doesn't apper anymore now so I can't attach it (anyway I can say it was a VARA modem related pop-up). I have enabled the debug mode and attach new log as well. I tried RMS express that use the same VARA installation and no issue there.

set to 15, no changes, only much slower and VARA modem restarted 3 times. By the way after shutting down Varac an Varac.exe*32 thread is still visibile in the win task manager. I attach here the new log after VarahfLaunchDelaySeconds=15 73

It looks like there is a problem with socket communication between VarAC and Vara modem. Vara modem is restarted and after a while Varac is loaded and it works, but when closed a Vara32 thread is still available in the task manager. I attach the setting screenshot, but i don't think could be really useful and the varac log as well where errors are visible. thanks for support 73 de Phil

I have replaced VARA ini file. Situation impreved, no more pop-up at the startup. Anyway from the varac log you can see there is a leg in communication between varac and VARA, in fact VARA modem i slaunched twice and several seconds are need to have Varac open on the screen. I attach the new varac log thanks for support 73 de Phil

Yes Gary, the COM is related to VARA modem, tried to replace ini file but still problems when Varac is launched. i attach new varac log after ini replacement. The issue is also that when closing varac an instance is still available in task manager threads and you need to kill them manually 73 de Phil

I agree 100%. unfortunately there is still noticeable this strange behaviour to use only 20 & 40 meters when a new mode appears. We shall follow MUF not habits. Use of WARC frequency should became familiar during week end if the bands are occupied by rtty contests. 73 de Phil,iz1fks

MUF decides which is the best band at each of the day. unfortunately with new modes peaople are reluctant to shift from 20 and 40 to other band, i don't understand why

sorry, but in a general way I cannot agree. That is nothing more advanced than tcp port numbers for connection to VARA available in the configuration window. If a deselectable option next to kiss port number had been available I would have immediately tried it without annoying you here in the forum :)) ! and it could be immediately operative closing the tcp connection without shutting down VarAC. best 73

thanks Irad for the go around, perhaps it could be useful to have this setting to enable/disable VarAC kiss interface available inside VarAC itself in a future release. 73, Phil