Using the latest VarAC and the latest VARA HF, an operator and I tested sending/receiving pictures. First test was in 500 Hz (narrow). When we switched to 2300 Hz (wide) the first connect failed. Without changing VarAC, subsequent connects went back to 500 Hz even though it showed 2300 Hz in the app. We could clearly see the signals were only 500 Hz wide in the waterfall. To correct the problem we both disocnnected, clicked over to 500 Hz and then back to 2300 Hz, and then the connect actually linked at 2300 Hz. The thing is, using wide was never tested in older versions because we weren't sending pictures. This glitch could easily exist in older versions. And to gather a log for submission requires connecting with another station that has the VARA licensed AND working on a QRG that is not among one of the "slotted" operating places. It's not an easy test to setup for log collection. But it seems the problem is easy enough to replicate.

Using Omnirig and VarAC, all of the rev 7.x.x.x builds, the initial operating frequency is blank. If rig control is direct then VarAC successfully queries and identifies the frequency. But if Omnirig is selected, the frequency appears to not be queried and is displayed as blank. This really becomes an issue when trying to connect to another station that called CQ. When trying to connect VarAC believes the other station is on a different band. The only workaround I found is to do a band change when first opening the app. For instance, just changing to 40 meters 7.105 and then moving back to 20 meters 14.105, the frequency is correct. And the whole time the VFO is accurate.