Print

[N9KW]

I have WSJTX 2.5.4, a K3 and a Signalink USB with the following problem....waterfall functions, software decodes station activity on the band as well as individual frequency,  However, when I attempt to tune the K3 using the tune function of the WSJTX software, the Signalink PTT light turns red and the K3 switches into transmit mode (red light, and you can hear the relays), but there is no signal transmitted.  I have used this combination of equipment for about four years and thousands of FT8/FT4 contacts.  CW works fine with the K3.  Tune function of the K# works.

During an attempt to work TY0RU following a long absence from the bands and switching between F/H and regular, I assume I must have carelessly changed some setting in the WSJTX software.  Specifically I see that the radio setting for the transmitted audio source for the K3 is now the front/mike.  I believe (?) the audio source source should be the rear/data option on the radio settings for the WSJTX software.  However, I cannot change this setting, the audio source is grayed out.  I am not interested in CAT control and use VOX/PTT control of the K3.  I even question if somehow I even changed this setting.

Assuming I am correct, I deleted all previous versions and current version of WSJTX from my computer and download once again 2.5.4, thinking all of the settings for radio would be "clear"  with the "new/clean" download.  However, the settings remained unchanged in the configuration file and the radio settings drop down menu.  Obviously, I am not highly tech savy.

I am certain I am too close to this situation and my assumption of the cause of my problem is probably in error and not helpful in my search for a solution.  Need some help.  TNX....N9KW

[AA4PB]

The fact that the PTT is keying the SignaLink and the K3 means that you are getting Tx audio to the SignaLink okay. I suspect that there is a wiring issue with the Tx audio line between the SignaLink and the K3. Does your SignaLink connect to an accessory connector on the back of the K3? Perhaps you need to change a menu setting in the K3 to take tx audio from that connector. Another possibility is that the K3 tx audio control has been turned down to low.

Since the SignaLink-usb has its own built-in VOX circuit to key the PTT on the radio, WSJT-x should be set for vox. The SignaLink doesn't do CAT control so unless you have some type of external CAT connections you should just turn off all the CAT functions in WSJT-x.

[N9KW]

Problem resolved...this thread may close.  Several local hams who are very familiar with the K3 and WSJTX said the radio settings of WSJTX are not the cause of my problem.  I immediately switched my focus to possible audio issues.  The audio settings of WSJTX indicated I was using the CODEC mike and speaker...created some confusion.   After a bit of thinking I examined my computer's audio settings.  I discovered that my computer had turned OFF the CODEC speaker, while the CODEC mike setting was ON.

Very recently I started to use headphones with my computer while watching youtube videos regarding the bulding of a FM satellite portable station.  I believe that my use of headphones resulted in my computer changing the audio selection by turning OFF the CODEC speaker to accommodate the headphone use.

A few adjustments of audio level...success....worked ZA/IK2RLM with my 40W and vertical on 40M...LOTW confirmed!  Life is good!     N9KW

[K0UA]

In a word the way windows handles audio just sucks. It is always trying to second guess any settings you may have set. It always "knows better" how the audio settings should be set and it proves that any time it does an upgrade, or fails to find the device you have specified.

As an example failure to turn on the preset device before windows checks for it can cause windows to choose some other default audio device. I guess they do this so that "lay people" that have no understanding of audio settings will have something chosen to produce sound. But it is just a pain in the tookis for amateurs that want fixed settings of audio devices with certain software programs.

 If I had a dollar for every ham I have helped get set up for digital modes that calls back and says "now it ain't working" I would have a fistful of dollars . You must be ever vigilant to have your radios built in "modems" or external "modems" turned on and running when your software program (like WSJT-x) starts to come up and check for them. If they are not there, good old helpful windows will find some other (default) audio device to substitute for it.

It sucks but it is what it is. When something doesn't work that worked previously, there is a very good reason.  And that reason is usually Windows based.

[N9KW]

James, thanks for taking the time to read my original post.  I am familiar with the help you have provided hundreds of individuals with difficulties associated with their attempts to integrate a transceiver with WSJTX or other software.  Your past comments were helpful to me once I had eliminated my misguided view on the radio settings of WSJTX.  I appreciate your presence on this forum.  GL es DX!

[K0UA]

James, thanks for taking the time to read my original post.  I am familiar with the help you have provided hundreds of individuals with difficulties associated with their attempts to integrate a transceiver with WSJTX or other software.  Your past comments were helpful to me once I had eliminated my misguided view on the radio settings of WSJTX.  I appreciate your presence on this forum.  GL es DX!

Thanks John, If I have helped in any way, that makes me very happy.   73   James.