Using VarAC 11.2, Windows 11 (native), CAT for Icom 7800. Start at slot 1 and the slot space is empty. Use the slot slider to browse up or down, and eventually it gets confused. On 20 meters VarAC thought slot 1 was 14.105075. The only to correct the sequence error is to select the proper frequency from the dropdown for bands. Not that this is significant, but I only discovered this behavior when one of the OTH radars was active and I needed to know which slots were clear. The real culprit appears to be the slider still processes up and down requests while a previous move has not fully completed. If you need debugger logs on this please let me know what to switch on. I think I can reproduce this on demand without much trouble. Doug / N3JXB

For the Inbox, Outbox and Parking windows, remember the size and column width. They keep resetting to some default. Probably best to add a Restore Default button for them what adjusted it and then need to put it back to defaults. Doug / N3JXB

Rather than just the VMail feature, the Winlink/Airmail email feature, including attachments, could be incorporated. The messages could be composed while not linked to another station, essentially queued up for future delivery. Or composed while connected. Then when two stations are linked, VarAC would act as a data transport, Have something clickable to activate message transfer and then a peer to peer exchange would complete, and then drop back to standard VarAC communications when the message transfers are complete. The host that initiates the enhanced Winlink/Airmail linkup would send a message to the partner requesting the linkup. The receiving host would just ignore the request if it doesn't have the Winlink/Airmail feature or if the feature is disabled. This would bypass the 500 character limit that currently exists with VMail. It would add the capacity for attachments. The attachment feature could be used for ICS and ARC forms. One thing that could be added .. unsure of this one ... is the ability to use a host as a relay for other stations. For instance, operator A could have a list of stations that it can relay for. Others can attempt to post a relay to operator A's station, but station A would only accept relay for a list of predetermined calls. Essentially a station could become a messaging hub for others. Doug / N3JXB

Now that rev 9.1.0 added 2m and 70CM bands, and multiple types of VARA for each, it would really be helpful if there was a path setting for each VARA TNC type. Currently it seems that changing from VARA HF (SSB), then to VARA FM, requires the path for the EXE to be changed. And I can see the need for changing bands and modes to automatically close the TNC and open the proper TNC when there is an appropriate change. Doug / N3JXB

Using an Icom 7800 with CAT commands that work properly. On startup, VarAC does not have the rig change to the proper passband filter. In this case, I have the CAT set to select passband filter #2. Once I either change the band or slot, the proper passband is selected. I have attached the CAT section for the rig and the log. I activated debug mode for log collection. Steps I took to reproduce the issue: 1. Passband is on filter 1 2. Open VarAC 3. Frequency display is correct but passband is not set properly 4. Change slot once, passband is then set properly

Are there any plans to support DX Labs Commander for rig control? I have Commander working for many apps including FLDigi, WSJT-X, JTDX, MMSSTV, MultiPSK, and JS8Call. Commander works well for all these. If ARQ is a concern, I know it works properly with ALE400 chat mode in MultiPSK, and that is ARQ.

I have the Icom 7800 Xcvr and use CI-V rig control. My primary rig control is handles via the DXC Labs Suite, specifically the tool called Commander. I have FLDigi, MultiPSK, WSJT-X, JTDX, MMSSTV and JS8Call all working properly with Commander. I see no way to have VarAC use Commander, so I allow VarAC to use its own rig control. So far, on three different occasions, VarAC keyed the transmitter and then put out no audio and did not unkey the transmitter. The only way to get the rig back to receive was to completely close VarAC. But every time I lose the contact and the QSO is ended. I might also add the rig control INI lines for the 7800 are incorrect. The default is to place the rig into RTTY mode, and that is wrong. I was able to copy the USB-D command for the Icom 7600, change the rig control to 6A, and now it properly puts the rig into USB-D1. I don't know what tracing or logging would need to be submitted. This is the only app I have that get into a state where is does not unkey the rig. I will submit a new feature request to add DX Labs Commander for rig control, and maybe even DX Logger to record contacts.