Why would you have to reinvent the wheel with so little data available? I assume that given your background working with a lot of data will not be a problem, so go to the PSK reporter website and there you can request data for 24 hours or the whole week.Do that with calls from different continents and you have masses of data to work with. Since it is a static link, it can even be automated and downloaded as an ADIF file. https://pskreporter.info/cgi-bin/pskdata.pl?adif=1&days=7&senderCallsign=nc3z

In the folder of VarAC there is an file "VarAC_Last_Heard. You find there all the heard stations with the call, band and SNR. With excel you can inport these file and with some help from an excel Guru you can grab the info you are looking for. 73´s de DC4CP

If you are using Omnirig you can start 2 or 3 sessions of VarAC with the same radio so that you can test whether it really makes a difference if more beacons are sent. If you start the second beacon 8 min later or 5 min later with 3 sessions later you have something that can be used to see if it makes a different.

Soon your CQ's will no longer be visible to others or you would have to set a call with a slot to call CQ and then change it again without a slot otherwise there will be no connection possible.

Update working now , I removed all and started all over again. IN/OUT Rules added port 8100 TCP Add Vara.exe and VarAC.exe to both IN/OUT TCP allowing them on all network level. After an reboot all is working.

Yes, added an incomming and outgoing rule for 8100 TCP in firewall and added Vara HF and VarAC programm, both incomming and outgoing and relay enabled.

19:30:26 - Starting VarAC (V6.2.4) 19:30:26 - OS: Microsoft Windows NT 6.2.9200.0 19:30:27 - Debug mode disabled 19:30:27 - FREQ Schedule off 19:30:27 - Resetting to Slot 0 19:30:27 - OmniRig: Connecting to OmniRig... 19:30:27 - OmniRig: Connected successfully to OmniRig! 19:30:27 - OmniRig: RIG1 Selected 19:30:28 - Opening DB connection 19:30:28 - Current VarAC DB version: 1 19:30:29 - Connecting VARA Main Modem Command interface... 19:30:29 - Connecting VARA Main Modem KISS Command interface... 19:30:29 - Connecting VARA Main Modem data stream... 19:30:29 - Connecting VARA Monitor Modem Command interface... 19:30:30 - Connecting VARA Monitor Modem data stream... 19:30:32 - Failed to connect VARA Monitor modem 19:30:32 - Connected to VARA modem 19:30:32 - Setting Bandwith to 500Hz 19:30:32 - VarAC base directory: C:\TS-450S\VARA\ 19:30:32 - VARA version: VARA HF v4.6.5 19:30:37 - Preparing to broadcast to ALL 19:30:37 - Sending Async message: TO:ALL FROM:DC4CP Data:test No error but also no PTT or audio triggered.

Tested the new version, all seems OK now, just one entrie. made the test with the same station twice, one time PING and second time CONNECT and I got both times only one entri in my HRD logbook. Many tnx for the update. 73´s de DC4CP

To exclude mis-configuration I did the test this morning with the previous version and current version. The first entrie is with the previous version, the next 2 entries with current version. 73´s de DC4CP

Ignore my posting Irad, it is also working in V5.1.8 , only 5 visible but all other are read and changed.

Is there an raison why in newer versions VarAC is only reading the first 5 rows ? In previous versions it was possible to have more entry´s and so more events available even if they where not visible in VarAC.

No problems with an IC-9700 and Omnirig here.

Hi Irad, are the sounds embedded in the software or is VarAC using the Windows sounds. And if they are the Windows standard, is there a list of the sounds used so that we can change the sounds by swapping the windows files. my goal is to make the alert sounds softer, less loud, and different from the default Windows alert sounds.

In addition to this, is it possible to differentiate the beacons and MH list according to the bandwidth used ? In the command stream from VARA HF you see that VARA HF can make the distinction, but in VarAc this distinction is not visible. I've noticed that the addition of -9 to the callsign distinguishes between CQ and beacon, maybe something is possible here too.