WSJT with Flex 6500

Doug Allen

Problems- Nothing I've tried works for long.. I'm using a Flex refurbished 6500, Windows 10, and Smart SDR 2.4.9.   I've spent over 20 hours trying to get WSJT-x configured and have been successful three times, but then,for reasons not understood, the configuration fails.  I've read and watched everything I could find online.

PART 1- WSJT has always been configured the same: Radio- Flex 6xxx on 127,0.0.1:5003;and Sound Input- DAX Audio RX1 and Sound Output- DAX Audio TX.  I don't think these settings are a problem.  I have DAX ch 1 open on the flag and DAX showing blue as the primary audio source.   I don't think I have a WSJT SETTINGS PROBLEM with any of the above settings.  Please refer to WSJT SETTINGS PROBLEM if you think I'm mistaken

Part 2-  There are multiple windows ans Dell computer sound settings, and I think I have had problems with them..  Right now I have the Windows Sound Playback set to DAX Audio RX1 and Recording set to DAX Reserved Audio TX, the one with the two audio connector icon.   There are two other DEX Reserved Audio TX choices, one with a mic icon and the other with a radio icon which are not plugged in.    WSJT is NOT receiving the Flex audio and WSJT tune does NOT transmit.

Sometimes this combination of settings has worked, but not for long.   If you think I've ,ade a mistake in the PART two settings please be specific and refer to Part 2.  I'm almost 79 years old and probably need  more handholding than you young squirts,  

Part 3-
The following is likely at least one problem.  This is the second time it's occurred..  On the DAX panel, Mic Stream is OFF saying "driver error."  Three days ago I had the same indication, deleted the entire Smart SDR software and the downloaded it again.  For awhile it worked.  Then it didn't work, but there was no indication that there was a driver error."  After rebooting Smart SDR several times, the "driver error" problem showed in the DAX panel.  

Part 4  When I had 40M WSJT working I made a Global Profile and saved it.  I did the same with 6M WSJT, and 2M WSJT using an Elecraft transverter configured and working until today.  Even before the Mic stream "driver error"  appeared on the DAX panel, the profiles no longer were successful is configuring WSJT for those bands.

The only thing that works at the moment is CW.

I would appreciate any help.

Doug K4LY

Michael N3LI

Doug Allen

Ted VE3TRQ

Doug, in your Part 2 above: Dax Reserved Audio should never be connected to anything - it is reserved for Dax itself. Also, Windows sound output should normally only be directed to speakers, which should also be the Windows default output device. Windows default recording device should be the microphone you use for phone operation, then use the SSDR “PC” setting for phone input and output from/to SSDR (using the Windows default audio devices). Dax (in and out) is used to connect program input and output, i.e. for things such as WSJT-X and Fldigi. Hope that makes sense.

Lee - N2LEE

Michael N3LI

Check your sound drivers to see if a Windows update pooched them. The signature series is a Lamborghini of a radio with a Chevy Metro level computer OS running it. 

Life can improve a lot if you can get a Windows 7 computer, or block updates entirely.

Michael N3LI

You would think it is irrelevant, but how many people have tried to use the presumptive drivers in WSJT, and had problems? Anyhow, it should be on the Kenwood radio setting. 

Lee - N2LEE

You might have experienced CAT issues but if you are having audio issues the CAT driver has no effect.

Ken - NM9P

Doug....The problems most folks have had with the WSJT Flex driver have had to do with disconnection of the cat data and control stream, not the DAX audio stream. However, disconnection of either connection results in an unusable system. I have not had as much problem lately with the Flex driver. You are more than likely having problems, as others have mentioned, with your DAX drivers getting hosed by Windows 10 updates. Most recently manifesting as the devices basing improperly named, and thus, becoming unavailable. You will need to check them and see if they are all present in Windows Device Manager, and if ghost ports or devices are hiding in the background. Ken - NM9P

Ken - NM9P

Correct. The RESERVED device is reserved as the radio’s “end” of the virtual audio cable, so to speak. Imagine them as two ends of a cable...DAX Audio RX1 is the “loose” or “available” end of the cable. DAX RESERVED Audio RX1 is “plugged” into the radio’s internal circuitry. Ken - NM9P

Dudley WA5QPZ

Doug, As Ken said, your Windows Sound Drivers should have. Your speakers as audio out and some sound card input as the default sound card input. In other words, no Windows green check on any DAX driver, ever. This along will make your sound devices unstable as windows will keep trying to correct it.. On your overshoot your are discussing, if only on SSB, then be sure the audio gain is reduced so that the audio peaks do not go over 0 dbm in the level indicator. Make sure you TX delay is greater than 15 ms. And that the Dexp is on and around 70, the default setting. Your crossed default sounds could be part of the issue in digital modes, be sure sure to use DigU when running digital modes, always start low and work up. 73, Dudley WA5QPZ

Alan

Doug Allen

dlwarnberg

Doug Allen

Ted VE3TRQ

Before trying to correct anything else, you should make sure the devices are all correct. Uninstalling and re-installing will not necessarily correct things. Do as some have suggested and open a ticket with Flex to help you out.

Doug Allen

Alan,
 Thanks and yes, in the 20 hours or more trying to get WSJT to work, I did read about Slicemaster 6000 and downloaded it, but it did not fix my problems.

Doug Allen

Thanks Ted.  I need to figure out how do to that, and yes with things working OK except for the overshoot, I'm reluctant to do anything right now that may prevent me from using the transverter's  low power in the CQWW VHF test this weekend.  Higher power with the brick can wait.  

Bob G W1GLV

I've been using the loopback protocol (127.0.0.1:60001) since FT8 was announced and I've never had one iota of a problem with that CAT setup. Using the Kenwood setup is not too steady on a LAN system that the FLEX radios use.

Ken - NM9P

Even on digital modes, control your maximum drive to the XVTR port with the power output control, not audio levels, mic gains, etc. then on digi modes, use the audio controls to go below your maximum power. Always use DigU, not USB/LSB for WSJT modes. It takes the Processor and TX EQ out of the mix. Using mic gain to control maximum power output on SSB will allow random voice peaks to blast higher than your desired average output. Set your maximum power output with the power control slider, or better yet, in the transmit profile or transverter setup tab. Also on SSB, always use PROC at normal, DX, or DX+. It will hold your output more steady, and also adds talk power without distortion, if your Mic gain is adjusted correctly. (I.e. keep it out of the red, and if you are using lots of bass, run the gain even lower.). See my tutorials on YouTube.com/NM9P for comments about proper adjustment of mic gain, PROC, and TXEQ. On the “Tour of Transmit Profiles” video, I even discuss how (not) to make your Flex sound BAD. (They are a little dated, recorded back when the Mic Profiles were saved as part of the Transmit Profiles) Ken - NM9P

Ted VE3TRQ

Doug, to create a HelpDesk ticket, visit “https://helpdesk.flexradio.com/”.

Doug Allen

Thanks Ken,
Good info and I'll look at your You Tube videos.  I'm doing everything you suggest above.  Several suggested I submit a request to Flex, and I just did.   Hopefully, if I fix the MIC STREAM driver error problem that only allows me to successfully use DAX Reserved Audio TX for Windows Recording will be the solution, so I'll await a reply from Flex on that.  Everything is working at the moment on HF and 6M SSB, CW, and WSJT with the only problem the 2M overshoot.

Doug K4LY

Michael N3LI

Yes Lee, DAX is sound, CAT is ersatz Serial port. Doug almost certainly has multiple issues, and changing his rig in the program will be a very helpful thing if he is having troubles. Small steps. Correct all the problems.

Doug Allen

Ken - NM9P

Good. If you get Tim on the case, he will sort it out. He is a wiz on the DAX cleanup. I have used his techniques several times here. I’m an Alpha Tester, and also have been getting the early Windows releases, here. Do my DAX drivers get pounded a lot, here. But things have gotten better over the years, and it is easier to recover once you learn the routine.

Ted VE3TRQ

The way to tell if there is an error in mapping name to function of the Dax devices is to look at the _description_, not the name. If the description does not match the name, you have the Windows naming problem. You can see this by going to the Windows Audio control panel (Right click the speaker/sound icon in the tray, select “Open sound settings”, click “Manage sound devices” link, then verify the bold title (name) matches the description underneath).If you happen to pick the Reserved device, and that happens to be a (incorrectly) renamed normal Dax audio device, you could have a functioning system, even tho the names are wrong. The answer is to have it fixed, then point to the right Dax device in your digital apps. But if it is working for you now, and you need to use it, just wait until you are ready. ,The Mic stream problem may well be the same thing - I don’t do phone from the computer, so have no experience with Mic Audio Dax streams.

Steve K9ZW

@Doug - there are a few community members who also help folks with Windows problems (the DAX name scramble) - check out some of the other threads where people have DAX issues.  One of our community does an IRC style chat to help.

As a caution, unless you are pretty good with the fine details of Windows AND have made a backup/restore-point, be cautious about digging too far or deleting/changing too much lest the additional attempts do more damage to your system.  

I had one of my machines completely frustrate me with DAX issues (an HP Elite mini) and I was really glad to get Tim's expert help Teamviewer.  Watching the process I am also glad I asked for help, as their remote assist process involves checking a lot more than I would have known how to even find.  Additionally many of their check prior to taking any corrective steps are conditional evaluations.  

GL and hope you get sorted out quickly,

73

Steve
K9ZW

http://k9zw.wordpress.com 

Jay Nation