A second instance of VarAC is a great solution!

I haven't used this feature yet (no FM peers yet). Also, I don't understand your comment about PTT. My concerns are: 1) the HF modem type is a different executable on a different path than the FM modem type 2) I would like to be able to easily switch between HF and FM 3) As the Setting page is now written, I would have to change both the VARA modem type AS WELL AS the file path (and in my case port). I often have HF, HF Monitor and FM sessions running simultaneously (on different ports). It works well. 4) The VARA-FM modem doesn't support monitoring yet. The labels on the Optional monitor configuration should just be for HF, not FM I would suggest moving the "VARA modem type" control off of the Settings page and onto the main page, next to the 500/2300 radio buttons. I think that if VARA-FM is selected, then the speed radio buttons will need to be disabled.

I'm running 2.6.2. I tried the QYSD gesture on a QSO this morning. A pop-up was "eventually" displayed. I assume that occurred after the request was delivered to the other party. My message said to change frequency quickly to avoid losing the connection. Well, I did QSY down and did lose the connection. Eventually we did connect up and resumed our conversation. So, it worked, kinda!!! I do think that a non-modal, non-blocking popup would be useful. On the receiving side, I think there should be two buttons: [Agree] and [Disagree]. If the receiver clicks on [Agree]: 1) transmit the [Agree] message back to the original requestor 2) use rig control to QSY up or down. If rig control not enabled, message the user to change frequency 3) close the popup When the requester receives an [Agree] response, 1) use rig control, etc. 2) close the popup If the recipient clicks on [Disagree] 1) send a message back to the requester 2) close the popup When the requester receives a [Disagree] message 1) tell the user in the popup 2) close the popup The popup should be non-modal so that both parties can continue to chat. Perhaps allow the recipient to also send back an QSY amount other than .750 Cheers, Bob

Yes, file transfer would be great. I would suggest just plain binary file transfer; no need to distinguish between files vs pictures, etc. Maybe pop up a dialog box with an estimate of the transfer time and a "Are you sure?" button,. One additional suggestion, could you implement "streams" too, so that there can be CONCURRENT chat and file transfer, in both directions. Right now, Jose's VARA Chat either allows chat or file transfer, but not both concurrently. Maybe "tagging" the foreground versus background streams, so that it can remain compatible with Jose's Chat. Maybe negotiation with Jose to extend VARA itself is in order. I don't know the right/best way to allocate bandwidth between foreground/chat and background/file but as a first cut, foreground ALWAYS has priority.

We've been using 3590 USB hear too in Washington State ...

Hi Irad, Thanks! I'm not running OmniRig ... yet, and the drop down control doesn't drop down. So, that might be a separate issue. There is still a need for the community and/or the BDFL to propose standard frequencies for 80, 30, 17, 12, and 10m. Yet another issue; perhaps you should start a timer when a QSO starts and when the time expires, pop up a box politely suggesting that the parties agree to change frequency to free up the watering hole frequency. Perhaps 5 minutes? Cheers, Bob (Be

Excellent! I also like the count-down timer on Next Beacon!

Similar complaint, but only the bottom get cut on my 1366x768 laptop screen. Plugging in a second monitor helps😀