I recently switched to a much shorter USB cable between the rig and my PC (6 Ft long vs 14 Ft log). There never was a problem when using the longer cable, but since switching, I've experienced what others have mentioned on the Facebook group. The only way to extinguish the indicator, is to keep decreasing the "microphone" setting in Windows 11 till about 70 %. At that point, the indicated volume in VARA-HF is so low that nothing is decoded. My receive bandwidth is 600 Hz, as usual. No changes have been made to rig settings. The only difference is the shorter cable. All other digital software continues to work as expected (JTDX, FLDIGI/FLRIG, Multi-PSK). 73, Joe

I've just installed parallels and have 2 weeks to try before I biy. I'd really like to get VarAC/VARA-HF working in WIN 11 on my M1 Mini. Win 11 runs fine, but is not seeing the rig. Maybe I need to install the CP210X driver? Also, as mentioned in the title, VarAC insists I do not have my callsign entered, despite the fact that all the info shows up when I'm in the "settings" screen. Any help would be appreciated.

I think it would be great if there was a way to see which station was used as a relay with VMAIL that has been received, and perhaps even a way to automatically send a reply back the same way. I.E. I received a VMAIL from station xxxx that was sent via a relay. I have no way of determining what relay station was used, when looking at the VMAIL later, as it only show the author of the VMAIL. Perhaps something like wd4aaa@wd4bbb in the callsign field for the author of the VMAIL if it was sent via wd4bbb. This information could also be saved, so that a reply, or new message would be routed the same way. ...Just a thought, as I don't know what restrictions are imposed by VARA. Perhaps some programming "black magic" could be used to indicate the relay when VMAIL send or received, which would make VarAC initiate a contact to the relay station, and then send mail to the originator?

Please consider having the new flags cleared after a link timeout with a station. I have noticed these flags getting sent again from a prior failed link, on the calling freq. And this can also lead to duplicate requests to change frequency etc. Thanks

Please make the font for the name displayed next to the callsign larger. Thanks!

Since switching to the latest VarAC, I've not been able to send VMAIL to a target station on a channel OTHER than the CF. If the target station does not respond to a QSY request, and the sender does not touch a key, there the sender is put back on the CF and nothing happens till a timeout occurs. Both stations are using the latest version. If the sender requests a QSY, and the target does not reply, AND then the sender aborts, the VMAIL will be sent on the CF IF there is enough time remaining (less likely, with the time on the CF reduced to 4 minutes). It USED to be that the sender could request a QSY, and the target station would QSY even when "AWAY', and the transfer could take place. This appears to no longer be the case. If a "live" OP is required at both ends of the connection, for a VMAIL to be sent, then this (in my opinion) is a mistake, as it forces VMAIL back onto the CF.

I initially requested this feature over a month ago, but think it got lost in the shuffle, as I never saw it commented on, so I'm asking again. Please consider a feature where a CQ would re repeated "X" number of times (up to some pre-set limit, built into the program). After the time limit had expired (where the program now goes back to the CF), the 2nd would begin, and so on, up to the limit that was set. The operator could disable the CQ by hitting the ESCAPE key, reverting to the calling freq, ro clicking in the "box" on the right side of the screen, to abort as now.

It would be great if the callsign history could be edited "after the fact", (station and opereator/QTH info) and perhaps even include a "comments" area.

This has happened 3 times in the past two days. Most recently, I went in to look at settings after disconnecting from a QSO. The window displayed properly, and I closed it (I think, by the usual method of clicking of the red X, but I'm not sure). After that, VarAC continued to run, but the program was totally unresponsive to any keyboard or mouse input. I regained control by right clicking on the task bar and noticed the settings window still was active. Once I closed it (right click, then "close window") I was able to re-start VarAC, VARA-HF, etc.

I was on Jose's site this morning and see that he has released version 4.7.4. I could not find any info on what this release does, in the way of bug fixes, or other changes. Should we upgrade to it?

I'd like to see an option where a CQ would repeat say, 5 cycles. (Of course, before calling CQ, you'd sniff the slot, to make sure it was clear.). The way I see this working would be to have the CQ go out again on the calling QRG, after the first waiting period had expired. Then, VarAC would return to the initial slot to listen for a reply If a station answered the CQ, the cycle would stop, and (obviously) after the 5th cycle, the cycle would stop.

I have had several QSO's over the past couple of weeks where I have had the old "link lockup/timeout" bug assert itself. I thought it was just me, but I've also had several others I've been in QSO with mention that they've had the same thing happen. (I'm referring to the issue where VARA-HF simply stops polling the link, and anything that is in the TX buffer is also not sent.). When this happens, the station I'm in QSO with ALSO stops polling the link. 73, Joe

I've been away from Linux for about 5 years, and am totally lost when it comes to navigating GitHub and downloading the various things that need to be installed to get this running. If you are so inclined, I'd really appreciate some help. E-mail exchanges would be fine, and if It becomes evident that I need more assistance, then I'll be glad to work over the phone, if you have the time. My email is wd4kav *at* gmail.com

How about adding a function to VarAC where the software would not permit a ping or VMAIL to proceed if the received signal strength at the station sending the ping was below a certain value when the connection was first made. A popup would appear saying something like "sorry the path is too poor now to permit VMAIL transfers or pings", and this would be followed by a disconnect. My experience has been that any value worse than -15 would be a good starting point to inhibit these functions. Perhaps something like this would help open up the calling frequency a bit? 73, Joe

It would be great if the signal strength of a beacon or CQ would also be spoken when the narrator feature is enabled.

If a QSY command is received while typing, the popup is not displayed, my station QSY's, but the station that sent the command does not QSY. This is when using VarAC 6.3.3

I've been noticing the "CQ with Hz bandwidth error" for the past several days. I've held off on reporting this, since I was unable to hear (or see) a wide signal, and wanted to make sure that VarAC was possibly hearing better than I was (grin). VarAC operates perfectly despite this report. 18:42:09 - A CQ with Hz bandwidth was heard. Only 500Hz are allowed on calling frequencies. Ignoring... 18:42:52 - PSKReporter: Logged successfully (KT5LA) 18:42:52 - PSKReporter: Sending accumulated records 18:43:47 - PSKReporter: Logged successfully (N1JMC) 18:43:47 - PSKReporter: Sending accumulated records 18:46:58 - A CQ with AHz bandwidth was heard. Only 500Hz are allowed on calling frequencies. Ignoring...

I closed a VMAIL I had read, with the "X" In the top right corner of it's window, and could not go further. I was unable to open any VMAILS that were displayed. After exiting VarAC I saw a "thread" error, plus one other error that I now can't remember. Windows "Snipping tool" did not display as it should have, so I was unable to grab a screen shot (sorry). Sorry for being so vague, but NO COFFEE yet. Guess I need to wait on running VarAC till fully caffeinated ! ....Joe

How about the ability to send a broadcast for a specific type of alert? For example, weather alerts for a specific state would be something like WXAL or WXWA (meaning "weather alert for Alabama", or "Weather Alert for Washington"? These type of alerts could optionally print in a different color, and perhaps have a unique sound. 73, Joe