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.