Error message in the VarAC logfile: 08/01/2022 11:33:28 - Sending beacons every 15 minutes 08/01/2022 11:33:28 - Sending beacon 08/01/2022 11:36:58 - Connecting 4Z1AC 08/01/2022 11:37:19 - Disconnected from 4Z1AC 08/01/2022 11:37:27 - Calling CQ 08/01/2022 11:37:28 - Error: VARAHF 4.5.0+ is required 08/01/2022 11:38:43 - Connecting ON2AD 08/01/2022 11:39:03 - Disconnected from ON2AD 08/01/2022 11:39:29 - Connecting PA0QRS 08/01/2022 11:40:17 - Disconnected from PA0QRS 08/01/2022 11:43:35 - Calling CQ 08/01/2022 11:48:28 - Sending beacon There was no apparent issue with VarAC operation at that time. I am using VARA-HF version 4.5.4.

I experienced difficulty connecting to VarAC users running SDR's on two occasions while testing version 3. In both cases, repeated attempts to connect to these users failed, but they could connect to me without difficulty. I also use an SDR. I was suspicious, since I have never experienced the "latency connection issue" described in the VARA-HF "manual". I used latency monitor, https://www.resplendence.com/downloads, a nice software tool for identifying the cause(s) of latency. Running latency monitor identified an issue with ndis.sys, which is a network driver issue. Apparently, a recent Windows 10 update updated something. I won't go through all of the "detective" work. I isolated the issue to the Intel network adapter. Searching the Intel driver site, I found an updated driver for the ethernet adapter. This driver was NOT identified by the Windows update process, or by the Dell driver update process. I downloaded the driver directly from Intel and installed it--latency issue solved. Latency monitor is a good tool for identifying any issues that might cause issues with "real-time" pc audio.

VarAC appeared to be hung up. The Connect to and Connect station selections were grayed out. The Send Beacon selection was flashing Send Beacon soon. I clicked the VarAC disconnect and abort buttons--noe effect. I disconnected VARA-HF and reconnected VARA-hf--issue solved. VARA-HF log excerpt: 2021-11-30 14:24:21 Inopportune command. Session is active yet: CONNECT 2021-11-30 14:23:47 Disconnected TX: 0 Bytes (Max: 0 bps) RX: 0 Bytes (Max: 0 bps) Session Time: 00:17 2021-11-30 14:23:42 Connecting to OM8ST... 5/5 2021-11-30 14:23:39 Connecting to OM8ST... 4/5 2021-11-30 14:23:36 Connecting to OM8ST... 3/5 2021-11-30 14:23:34 Connecting to OM8ST... 2/5 2021-11-30 14:23:30 Connecting to OM8ST... 1/5 VarAC log excerpt: 30/11/2021 09:23:30 - Connecting OM8ST 30/11/2021 09:23:48 - Disconnected from OM8ST 30/11/2021 09:24:21 - Connecting OZ1LNR 30/11/2021 09:40:36 - Disconnecting OZ1LNR 30/11/2021 09:40:43 - Aborting... 30/11/2021 09:40:54 - stopping to send beacons 30/11/2021 09:41:27 - Disconnecting VARA-HF... 30/11/2021 09:41:27 - Disconnected! 30/11/2021 09:41:27 - Unable to read data from VARA modem. Disconnecitng modem. 30/11/2021 09:41:27 - Unable to read data from VARA modem. Disconnecitng modem. 30/11/2021 09:41:34 - Connecting VARA-HF Main Modem Command interface... 30/11/2021 09:41:34 - Connecting VARA-HF Main Modem data stream... 30/11/2021 09:41:34 - Connecting VARA-HF Monitor Modem Command interface... 30/11/2021 09:41:34 - Connected to VARA-HF modem 30/11/2021 09:41:34 - Connecting VARA-HF Monitor Modem data stream... 30/11/2021 09:41:34 - Setting Bandwith to 500Hz

Sort the "Connect To" list by callsign. When I use the list, I am usually responding to either a beacon or a CQ, which has nothing to do with recent connections. Having the list sorted by recent connection is useless to me. At least provide an option to sort the list by callsign.

Replace the QTH field in the VarAC log with a State field and a Country field. Change the mode from VARA to DATA until LotW is updated to accept VARA as a mode.

I use AC Log (amateur contact log) by N3FJP. AC Log has a nice API that allows programs like VarAC to send log data directly to the AC Log database. I think the coding is relatively easy. The API spec's can be found here: http://www.n3fjp.com/help/api.html

It might be interesting if a station receiving a Beacon "message" automatically returned a simple receipt message with call sign and S/N ratio? Perhaps the receipt is only sent when the "away" flag is set at the receiving station? This would provide stations feedback re: propagation from their station.

How about using the DX cluster and self spotting when you are looking for a VarAC QSO?

The Ham Radio Control Library–Hamlib, for short–is a project to provide programs with a consistent Application Programming Interface (API) for controlling the myriad of radios and rotators available to amateur radio and communications users. See https://hamlib.github.io/ for more information. Incorporating HamLib would eliminate the need for OmniRig and allow supporting most current amateur radio transceivers. Larry, W1IZZ

Not at all critical, but it would be nice to have the "Connect to" dropdown list sorted by call. I would also like to configure the "I'm away" and "is typing" parameters in Settings. Larry, W1IZZ