I went back and re-read your complaint. Seems you are missing the VarAC_Frequencies.conf file. That should be located in the folder with the Varac,exe program. It is a simple sequential listing of frequencies to use for VaraC. Here is mine: 1.849.750 1.850.000 1.850.750 3.563.500 3.594.250 3.595.000 3.595.750 5.330.500 5.346.500 5.357.000 5.371.500 5.403.500 7.104.250 7.105.000 7.105.750 10.132.250 10.133.000 10.133.750 14.104.250 14.105.000 14.105.750 18.105.250 18.106.000 18.106.750 18.107.250 18.108.000 18.108.750 21.104.250 21.105.000 21.105.750 24.926.250 24.927.000 24.927.750 28.104.250 28.105.000 28.105.750 50.330.000 A simple copy and paste to a text file then save as "VarAC_Frequencies.conf" saved into your VARAC folder should solve the problem. 73 de w8nsi Jim

On VaraC top line of Varac, go to settings then "Rig Control and Vara Config". When that opens, on the right is where you specify the location to find the VARA modem. I placed mine at C:\VARA\VARA.exe then next is port 8300 Locate where yours is and enter it there. Now when you open Varac it will open the modem for you. 73 de w8nsi Jim

Whether you are able to communicate is dependent on: [1] Propagation Conditions, [2] the Antenna, [3] the Radio If propagation is not there, numbers 2 and 3 won't make any difference. If you have great propagation, you can work the world on a bedspring antenna and a couple of watts. But generally speaking, you will need conditions allowing your signal to travel some distance. You will need the biggest antenna that you can place up in the air. You will need a radio with a decent receiver and enough transmit power (generally in the 100 watt class) to reach out to others. With items 1, 2, and 3 plus your ham radio license, you should be talking to the world. Low power is fun for enthusiasts but newbs do not need frustration at the beginning. Get busy studying for your license now.

Is anyone using a frequency on 160m? I am currently set up on 1830 kHz usb.

Hi Pat, I have 3.2.1 installed. If there is a 3.3.1 it is not linked at the download page here on the forum. 73 de w8nsi Jim

I have not heard any consensus on this. I have 10,130.750 for center (10,130.000 and 10,131.500 for QSYD and QSYU) set in my station but I have never heard or worked a VaraC contact of 30 meters. The trouble seems to be that differing countries have slightly different allocation. 🙂

irad d, I think that VaraC would be improved if it at least reported the current version to the other end somewhere in the handshaking for an internal log. I spotted WA5YZD from his beacon and connected. What you see in the transcript at the start of this sequence of messages is the full contact. No qsy was attempted during or prior to the connect with WA5YZD. I do not know what version VaraC he is running. I have VARA 4.5.7 and VaraC 3.2.1 here.

To KB3PCY good connect sigs good but them it faded and disconnected.

I am running the most current VARA-HF and VaraC releases. Rig is a TS-480.

It just keeps getting better and better. 🙂

Here is a page about it. I did not look closely to see if it could be downloaded from there. https://www.exefiles.com/en/ocx/mswinsck-ocx/ I never had this problem. I am running Win 10.

I have not had this happen here. I admit that I have not been really active with it yet but have had a qso or two. I will try it out today and see if I can get this to happen here. 73 de w8nsi Jim

@irad d People log in on netlogger just to show that they are available even if they have not done an on the air "here I am". Netlogger has a "lurker" list of stations who are watching but not recognized as being in a net. I mostly use the lurker list to see who is on. Then if/when I can connect it becomes a live chat. Netlogger functions more as a self listed spotter list than as a bbs.

Irad, Here in our region, Michigan- Ohio- Indiana- Illinois- Wisconsin, we call ourselves the Great Lakes Vara P2P Group, currently using Netlogger for our gatherings on the air. We have been using Winlink Express with Vara HF P2P. Since Vara P2P is station to station only, Netlogger solves a lot of problems. A few of us have added VaraC to the mix on a QSY frequency from the Winlink session and it works to be able to coordinate using Netlogger. The only practical method without a coordination method like Netlogger is to monitor and copy call signs, then snipe in to the copied calls as gaps/ lulls occur. We have found Netlogger to be the most elegant method for our purposes. For purposes of this discussion, say on 14105, the Netlogger session could be called the "14105 Worldwide VaraC Group" or similar words for whichever freq is chosen. QSY coordination can be done using the chat feature on Netlogger. It only requires one station to open and maintain the log for the session period. Can a dx spotter service be used similarly? Thoughts? Suggestions?

Last night 12/17/2021 the band was really jumping on 160 for the ft8 guys. VarAC should have been good too.

We need a write-up about the tags that are available and recognized by the system and how to use them. this will quick-start new users too.

Then to stay within the WARC 10.130 to 10.150 data segment I suggest 30 meter center frequency of 10.130.750 with lower of 10.130.000 and upper of 10.131.500 to stay within the WARC data segment. This gives 750 hz separation using the 500 hz setting of VarAC with the Vara modem. Thus all are upper sideband and appear as: 10.130.000 lower qsy channel 10.130.750 center main channel 10.131.500 upper qsy channel Does that look acceptable?