I've got the dual monitor problem solved--thanks, Evan AC9TU--but I still can't reliably get rig control with WSJT-X. Audio and decode is fine, but not tune, transmit or frequency readout--most of the time.
Sometimes it works--but most of the time I get no rig control. I'm not sure why it sometimes connects and sometimes it doesn't. I have followed the instructions of KE8KYP Scott, but again it usually doesn't result in rig control. See my photos.
Iv'e tried first exiting FLDIGI, then starting sbitx from a terminal, even rebooting. The video syas "I don't need FLDIGI" and exits. Does FLDIGI interfere if it's running or does it not matter?
Any suggestions??
Jack, N6LN

The cat control is somehow working after a hard reboot with disconnecting the HDMI monitor--for some reason it continues to supply power to the Raspberry Pi and has to be unplugged for a proper reboot. I now see frequency displayed and the TUNE button works. But that only happens on DIGITAL mode, not FT8 mode, and even on DIGITAL mode the maximum output is only 3.5 watts with Drive = 100. CW output is set at 24 watts.
Has anyone got WSJT-X working via FT8 mode selection? And if it has to be done with the DIGITAL mode, how can the power be increased?
Jack, N6LN

?Hi Jack,

I have a dual monitor system and run WSJT-X working both FT8 and WSPR modes. ?My setup is the same as your Hamlib setup but if I read your message right, FLDIGI is not running on my radio. ?This is my start up sequence (all from the 7 inch display) after power up:
?
1. Launch mouse limit program to restrict touchpad to DSI screen only.
2. Launch sBitx and log in.
3. Close FLDIGI
4. Launch WSJT-X.

I too could never get reliable WSJT-X operation with FLDIGI running but after following the above steps, it works every time.

Good luck, Scott?

Scott, I still have no rig control although I get audio and the WSJT-X can decode. Interestingly I no longer get a working WSJT-X waterfall...it's black, even with decodes. I've rechecked the audio input and output selections. My WSJT-X works fine on my uBitx with an outboard dedicated Raspberry Pi, but that one is version 2.3.0. The sBitx version was 2.4.6. I even removed the 2.4.6 through preferences add/remove software and reinstalled the 2.3.0 version (that was the only choice) and it still doesn't connect with rig control--no frequency (stays red) and not tune function. So I uninstalled in and reinstalled WSJT-X and this time the only choice was 2.0.0 ! And still no rig control. Ive tried to install manually versions 2.6.1 and 2.7.0-rc2 but apparently there are dependency problems preventing installation. This is with my DE, but I have the same rig control problem with WSJT-X on my V2, running the same updated image.

I can transmit fine with the embedded FT8 mode, and at full power (the DIGITAL mode gave only 3 watts output, WHEN WSJT-x was working with rig control connection 2 days ago...and that problem has been reported by others) but I might as well just use FT8 with my uBitx which DOES work with WSJT-X at 3.5 watts, and which I used to work a station yesterday. But the FT8 with the sBitx? is hard to read with small letters 4 feet away, even with an external monitor, especially the blue call letters. There must be a way to get back rig control with WSJT-X on the sBitx. It was working before. I don't know what setting or other workaround I'm missing.
Jack, N6LN

I'm not sure this was the problem but somehow WSJT-X now has rig control. I was googling and found
which gives the steps:

After some time working with it, I can use the WSJT-X with the sBitx in DIGITAL mode at about 3 watts. I use dual monitors. I have made 2 contacts. The system is unstable, though. The DSI sbitx screen unpredictably freezes requiring a cmd line search for the sbitx process and termination with a kill command. In other cases the web link to the sbitx loses rig control, for example changing from 20 meters to 15 meters shows on the web interface but the real frequency won't change unless it's changed via the DSI touchcreen with a finger or a USB mouse. At other times the WSJT-X loses its rig control link unexpectedly (button goes from green to red, and frequency reads 000) and at other times the WSJT-X will not consistently start with rig control at all, although audio and decoding usually works. It seems as though a hard reboot of the entire rig is the best way to get WSJT-X to start properly with rig control, but sometimes that doesn't work either.
Has anyone got theirs to work in a stable fashion?
Thanks,
Jack, N6LN

开云体育

Jack, why don’t you measure the audio level going into the first mixer using each of the modes, so that you would at least figure out which side of the system isn’t producing enough signal.?

Hi Jack,

Sorry you are having trouble. ?You describe some of the trouble I was having until I did a complete software rebuild. ?After that, the system started to behave. ?I do not know why. ?The only thing that is goofy w is if I change frequency within WSJT-X, CAT does not change the frequency on the radio. ?However, if I change it on the radio, the WSJT-X frequency will follow after a few seconds delay. ?Since I typically don’t change frequency during a session, it does not cause great concern. ?It does bother me that it does not work both ways but I do want it to work.

I have started looking into Hamlib for another radio/purpose. ?I suspect that at least part of the problem(s) is how the Hamlib definitions are written and maybe there is a missing piece. ?I don’t really know but that is my theory. ?Hopefully I don’t run into a Mad Hatter situation.

Scott, I haven’t looked into HamLib and I’m not sure how it works, but I can try reinstalling it, perhaps with a newer release if that’s available. I did finally get confirmed contacts with the embedded FT8 mode which has much more power (it’s strange—while I’ve limited the output to about 20-25 watts for safety on CW by adjusting the hw_settings.ini scale coefficients the output on FT8 is 40-50 watts at Drive=100 requiring me to back off quickly) and the confirmed QSOs were both an answer to my CQ and another where I responded to someone else’s CQ. But WSJT-X is so much easier to read (my vision is 20/20 with the proper reading glasses) when the external monitor is about 4 feet away. The font is simply bigger. And WSJT-X of course does more things. I will have to get the oscilloscope out and do some checks as Gordon suggested when I have some time.
Thanks,
Jack, N6LN

Success! I reinstalled HamLib. I went to Preferences - Add/Remove Software and did a search on HamLib. I clicked on all the choices with the exception of SoapySDR. Now I call up a terminal on the DSI screen, cd to sbitx directory, start ./sbitx, close out Fldigi, start WSJT-X and move it to the HDMI monitor screen, and the WSJT-X now connects for rig control. l log in through the 8080 weblink on a third monitor on another computer and? I can change frequency by web control, and the frequency changes register appropriately back on the WSJT-X HDMI window from the rig. And I just completed a FT8 QSO to Texas, so it works.
73,
Jack, N6LN

Spoke too soon. It’s still unstable. I can’t get WSJT-X to establish rig control in spite of exiting WSJT-X, making sure zombie processes are terminated, restarting sbitx, rebooting, etc. ?It’s back to using WSJT-X on my uBitx v6 with the Elekits digital board.
Jack, N6LN