ARCHIVE: Australian Ham Radio Discussion Forum ( AHRDF )

Full Version: Multiple instances of WSJTX
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have installed two unique instances of WSJTX on my laptop, one for my 7610 and the other for my 9700 and run both at the same time when doing meteor scatter. I had something strange occur the last time I used both. The 9700 decode screen was decoding exactly the same signals as the 7610 screen. The only way I can see this happening is a problem with the USB ports in the laptop. The 7610 uses ports 3 and 4 while the 9700 uses ports 7 and 8. I really doubt the stations I was copying on 6m were running identical transmissions on 2m.  Has anyone else come across this?
I have resorted to only running one instance of WSJTX at a time now to avoid the problem.
Hello OM..
sounds like you have worked out that each instance needs to be started with the '-r' parameter to give it a unique RIGNAME but that sometimes is not the whole answer.

next hurdle, the old windows device ID shuffle. This is usually associated with a connected device being removed or going to sleep, then Windows "Plug and Play" will come along and resort the devices in the class of the device it has seen the change in. So even though your WSJT-X says it is using the device 'usb-codec' for example, it may be connected to another audio stream. This most commonly is seen on TX where you get no audio going to the audio device feeding your radio or you get a popup saying invalid audio device.

A lot of the time this happens when a monitor goes to sleep that has an internal sound card, usually HDMI or DP port connected devices, I am guessing you laptop has an external monitor connected?

if any of this rings true, there are things you can do to combat this but its never a simple fix.
You can rename the audio ports to something more descriptive than "PCM2901 Audio Codec" or whatever yours shows up as.
This can be done on both Windows and Linux - doing that might help ensure the right audio channel ends up on the right WSJTx
This also assumes you have launched each WSJTx with its own profile.