How to connect 3 WSJT-X instances to 3 RXs

[KO4PRE]

I am trying to run 3 WSJT-X instances on 3 different bands fed by 3 RX channels defined in SDRC. I can get the 3 audio stream to the WSJT-X instances but when I set the band in one of the instances, all 3 instances change to that band. I am using DX commander to control the SDRC and the WSJT-Xs. Each WSJT-X instance has a unique rig name.

How can I configure the system so that each WSJT-X instance has an independent band selection? How can I have those instances control only the SDRC RX associated with WSJT-X instance?

How have other people solved this problem?

Thanks,

Bruce Schober
KO4PRE

[Max]

I am trying to run 3 WSJT-X instances on 3 different bands fed by 3 RX channels defined in SDRC.

How can I configure the system so that each WSJT-X instance has an independent band selection? How can I have those instances control only the SDRC RX associated with WSJT-X instance?

Thanks,

Bruce Schober
KO4PRE

I'm not sure that this can be accomplished. I feel others have asked and I don't recall seeing an answer.

On Simon's guide, he does say that up to 6 receivers can be addressed separately via CAT, FA to FF. I might be totally wrong, but to me that says you could have three rig definitions inside WSJT-X with each one modified to send the frequency change command to the correct RX.
https://www.sdr-radio.com/SerialPort#Commands

How on earth you get to be able to duplicate/edit the rig definitions (TS-2000) inside WSJT-X I have no idea. You would have to edit the HamLib file but where that is or how to edit it have no idea, or whether HamLib has the facility to address the different RXs in this way? If you find out I'd be interested to know!

Another option (although I've not tried it) may be to have three instances of SDRC, one per instance of WSJT-X, the just run each instance with one receiver, and each instance of WSJT-X on a different COM port. It's a bit unwieldly but I think it should work. Bit of a "sledgehammer to crack a nut" though.

By far the easiest me to me is run several instances of WSJT-X in "dumb" mode, with the rig controls to "None" and PTT set to VOX. This just allows you to disregard any rig control (i.e. WSJT-X does not moan that it can't see a rig) and then just do the frequency changes on the SDRC end for each RX. Doing this you could have as many RXs as you want, so set up a Favourite in SDRC with every band's FT8 on a different RX, bandwidth permitting, or several Favourites each with three frequencies close enough together to fit the SDRs bandwidth. So the right RX sends audio to the right copy of WSJT-X via the various VACs. Not elegant but would get the job done.

Someone else may have a better solution (or exactly what you want) but I don't recall seeing it before.

73

Max

[PA3BTS]

Hi Bruce,

Each receiver in SDR Console can be configured to put the output to any available audio channel. The trick is to create more audio channels. This can be done by Virtual Audio Cable (VAC) or VB-Audio.
When installed and configured for i.e. 3 extra audio channels (VAC1, VAC2 and VAC3), you can choose in Console a unique audio output per receiver (RX1 to VAC1, etc).
In WSJT-X open 3 instances and choose as input VAC1, VAC2 and VAC3.
This should work.

Succes!

Cornel
PA3BTS

[Max]

Hi Bruce,

Each receiver in SDR Console can be configured to put the output to any available audio channel. The trick is to create more audio channels. This can be done by Virtual Audio Cable

Cornel
PA3BTS

Hi Cornel

He's got no problem with the audio paths from the receivers. It's the control of individual virtual receivers from each instance of WSJT-X via individual COM ports that he has the issue with.

73

Max

[jdow]

Study the offerings the Com0Com people offer. hup4com MIGHT do the trick merging 4 WSJT-X into one. But, could WSJT-X be configured such that the replies it gets and commands it sends go to individual receivers?

{^_^}

[PA3BTS]

Ok, I see that now I reread the post. Sorry about that!

73, Cornel

[/quote]

Hi Cornel

He's got no problem with the audio paths from the receivers. It's the control of individual virtual receivers from each instance of WSJT-X via individual COM ports that he has the issue with.

73

Max
[/quote]

[jdow]

I just took a look at the TS2000 command set. It does not appear that one controller can be connected to multiple radios and select which one it is controlling. Lacking that command capacity there is basically no way to control receivers independently over serial control. I've not looked at the MIDI control properties. But I doubt one could easily build a wedge of some sort to accept some radio command set and translate that to appropriate MIDI commands. I believe, and could be very wrong here, that SDRConsole can control a small number of individual receivers through use of MIDI instrument addresses. Building a tool to accept TS2000 or something else on a serial port and spit it out as MIDI SDRConsole would require is more than I want to do now. It's "painful" to say the least. The Windows MIDI system is a bloody mess. You have to go down to bare metal and develop your own memory manager since the built in stuff within C++ does not find what it needs down at the MIDI driver level.

I have done this, for non-ham prices, and don't want the pain and suffering again. There are too many variables here. And all my work was MIDI SysEx messages not MIDI notes. That uses a different chunk of MIDI code not implemented in the devices I have. And I am not sure it works with Win 11. It's a retired tool of late. It originated back in the NT 3.51 days.

{o.o}