No WSJT-X Transmit Output

  • 1
  • Question
  • Updated 3 years ago
  • Answered

Finally set up my Flex 6300 last weekend after it sat in the box for months.  What an amazing radio!

I'm getting it dialed in for digital modes.  Set up DM-780 yesterday and it works flawlessly on RTTY, BPSK, etc.  Todays project (which I thought would be straightforward) is to bring up WSJT-X.  Receive side works perfectly, but can't get any power out on transmit.  CAT and PTT functions work fine.  When I key up, I see a solid signal on the DAX control panel TX1 meter, radio keys, red light on the radio front panel illuminates, TX Ready changes to RED on the main display, but no deflection at all on the level or RF power meters.  No deflection on the external wattmeter.

I have read a bunch of posts and don't see where I am dropping the ball.  Could be a problem with WSJT-X, but if that were the case I wouldn't expect to see the DAX control panel TX meter deflect (which I do) when I put WSJT-X in "tune" mode.

I'm running SmartSDR v1.3.8.126 and the Kenwood TS-2000 rig configuration in WSJT-X.

Any suggestions appreciated!

Tnx & 73,

Glen

Photo of W9LS

W9LS

  • 4 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Jay / NO5J

Jay / NO5J

  • 1577 Posts
  • 228 Reply Likes
Glen
Did you click the DAX transmit button turning it blue, on the P/CW subpanel?
73, Jay - NO5J
Photo of W9LS

W9LS

  • 4 Posts
  • 0 Reply Likes

Hi Jay,

This is my first post, so you are my first replier.  Thanks!

Yes, the P/CW DAX button is blue.  Everything is configured pretty much the same as my DM-780 setup, which works fine.  I'm using slice 1 with TX enabled and DAX channel 1 selected.  DAX channel 1 is selected for TX in the DAX control panel.  WSJT-X output points to DAX Audio TX1 and I see it on the DAX control panel, but no smoke from the tailpipe.

I love the digital audio exchange concept, but it makes it hard to put a scope probe somewhere for troubleshooting :-)

73,

Glen/W9LS

Photo of W9LS

W9LS

  • 4 Posts
  • 0 Reply Likes

OMG!  I was poking around the menus and managed to completely hang the radio.  Had to hard boot and when it came back on line, TX was working just like in the brochure!  Almost fell off my chair since I had a receiver idling on frequency that came blasting to life.

The transmission resulted in my first SDR JT-65 QSO, with the power dialed back to 5 watts.

This was not my first re-boot of the evening, so will remain cautiously optimistic that the software weevils have left for the long weekend.

Tnx & 73,

Glen - W9LS

Photo of Jay / NO5J

Jay / NO5J

  • 1577 Posts
  • 228 Reply Likes
Ok, for now I'm not spotting the problem either, if it worked with HRD it ought to work with WSJT-X, which in my opinion is easier to setup.
Someone else will likely beat me to the answer. You might try upgrading to v1.4.16 if nobody else spots the problem. I doubt that's the problem though. Rebooting or power cycling everything sometimes works when nothing else, will fix things.there is a transmit inhibit control on the setup form that I never mess with, check for that too. It's likely just something we've now both overlooked.
73, Jay - NO5J
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 930 Posts
  • 172 Reply Likes
Glen, I have the same problem with SSDR 1.4.16 and WSTJ-X 1.5. It crops up about twice every week. It just happened to me, when I looked at an instruction
video on youtube at the same time. I usually solve that by closing down WSJT-X, CAT and DAX and restarting them. If I am very fast, I can even rescue that QSO!
My configuration is: SSDR-MiniDeluxe-WSJT-X (in HRD mode)-JTAlertX
73, Alex DH2ID
(Edited)
Photo of km9r.mike

km9r.mike

  • 425 Posts
  • 62 Reply Likes
I lost my detailed reply explaining this while signing in  so I will go straight to my conclusion. Ensure the "DAX" button on the P/CW panel on the right hand side of SSDR window is illuminated. The only way I could duplicate your indications was to deselect DAX in the P/CW panel.
Photo of W9LS

W9LS

  • 4 Posts
  • 0 Reply Likes
Thanks to all!  Problem was solved by another radio reboot.  Others have observed this condition and advised that rebooting was the most straightforward fix.