What happens if he turns the rig power and wsjt-x power all the way to
zero....no watts out.
Sounds a lot like RFI.
Also...try setting the audio out to the computer speakers and see if the USB
still drops out.
Mike W9MDB
On Thursday, November 5, 2020, 04:34:41 PM CST, Barry Jackson via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
Hi Bill and all.
For the last several months I have been trying to help a friend sort out
his set-up so he can use wsjtx.
He uses Windows 10 and an FT-991A and the problem, which we initially
thought was down to RF, is now probably not.
He can receive OK but on start of transmit the USB interface which is
handling both audio and CAT dies, leaving the radio in transmit and
wsjtx is then unresponsive.
Same with a dummy load with 5W and on VHF.
We began to suspect hardware and he switched USB cables, ports etc. etc.
As I don't have any Windows machines, I suggested that he test using
Linux. I made a minimal installation and sent it over ssh to him. Long
story short. It behaves just the same in Linux using all the same hardware.
I monitored the system from here (25 mile socially distanced :) while he
tested it and managed to get messages from journalctl as it happened:
90178196, major code: 10 (UnmapWindow), minor code: 0
Nov 05 20:20:15 iomega wsjtx[137323]: Hamlib: serial_open: Unable to
open /dev/ttyUSB0 - Input/output error
Nov 05 20:20:21 iomega wsjtx[137323]: Hamlib: serial_open: Unable to
open /dev/ttyUSB0 - Input/output error
Nov 05 20:20:26 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:20:51 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:20:57 iomega kwin_killer_helper[195351]: kf.i18n.kuit: "Tag
'p' is not defined in message {<__kuit_internal_top__><p>You tried to
close window \"WSJT-X v2.3.0-rc1 by K1JT, ...}."
Nov 05 20:20:57 iomega kwin_killer_helper[195351]: kf.i18n.kuit: "Tag
'p' is not defined in message {<__kuit_internal_top__><p>Do you want to
terminate this application?</p><p><warn...}."
Nov 05 20:20:57 iomega kwin_killer_helper[195351]: kf.i18n.kuit: "Tag
'p' is not defined in message {<__kuit_internal_top__><p>Do you want to
terminate this application?</p><p><warn...}."
Nov 05 20:21:16 iomega plasmashell[11518]: kf.plasma.core: findInCache
with a lastModified timestamp of 0 is deprecated
Nov 05 20:21:17 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:21:42 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:22:08 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:22:34 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:22:59 iomega pulseaudio[9271]: Failed to set hardware
parameters: Input/output error
Nov 05 20:22:59 iomega systemd[1]: Starting Flush Journal to Persistent
Storage...
Nov 05 20:22:59 iomega kwin_x11[11471]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 6968, resource id: 90178287, major code:
18 (ChangeProperty), minor code: 0
Nov 05 20:22:59 iomega systemd[6389]:
app-wsjtx-be03f03749a140b3836a1b494eeb999b.scope: Succeeded.
Nov 05 20:22:59 iomega systemd[6389]:
app-wsjtx-be03f03749a140b3836a1b494eeb999b.scope: Consumed 22.360s CPU time.
I think the Qt mutterings are irrelevant, but it seems that all
communication over the USB is instantly lost on transmit start.
The above was using wsjtx-2.3.0-rc1 and hamlib4-4.1 (A very recent daily
~3 days old)
Has anyone come across this before? Any ideas for further testing/diagnosis?
We can grab more info if necessary like backtrace, strace etc.
I am suspecting the radio's USB interface, but it may be something else.
Cheers,
Barry
G4MKT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
