I have an Idea.
Under normal operation, everyone on frequency can copy beacons and CQs. When 2 stations are connected, copying everything being said can be problematic. But beacons and CQ usually are decoded. This got me to thinking.
If there were a special setup within Settings (ala WSJT-X "Advanced Settings") where instead of having windows for becons and CQs there would be (by way of the special setting) windows for check-ins and Net Control (NCS) for a WAS Net, ARES Net, etc. When NCS announces preambles and calls for check-in, those messages could be decoded in the existing Data Stream window. Or maybe in the VARA monitor window. Because of VARAs 'busy' feature, when NCS calls for check-ins, all stations can hit the 'Check In' button and the program will sort out pile-up. When NCS gives a net member a turn to call a station he heard, they could 'connect', pass data, disconnect and pass back to NCS. Unless operating on FM or in GREAT band conditions, not all net members will hear the connected QSOs but as long as they can connect to their desired contact or NCS, messages will get through.
I'm not smart enough to think of all of the details, but it is a concept. But imagine a large number of operators existing on the same frequency participating in the same event.
Could this be possible with VarAC?
Steve Panattoni - N6RSH
I must say I am not a big fan of "I'm here - no traffic" nets. But what will kill this is the time in which a station need to make a connection, pass some data and close it. it can a 1 minutes in good conditions. But you got me thinking about something else when the new version will be out allowing scalability for QSOs. a monthly/weekly QSO party. I'll give it some thoughts. thank you :)
Closest , would be the run two vara modem sessions , one stand alone , in monitor mode , showing the RX audio ,
The other the tx/rx modem used for chat, then the monitor modem would show the channel traffic, but , only if the frames met the required s/n level , at your-rx , would have to be the HF version ,
Vara was designed to move large data volumes in the shortest possible time , the chat function was never part of the concept, originally provided as talk back during file transfer - hence features are not available in the original versions. there is no broadcast function, other than the beacon and cq, which have been provided , as part of the vara-c project.
With VARA being an ARQ mode it makes this sort of roundtable QSO an issue. ARQ is why VARA is so robust, but has the limitation for multi user nets.