No TX channels on DAX?

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
Had FLdigi working fine until last S/W update. Went to make a contact on PSK and had no transmit audio.  Easy fix right?  Went to config sound card and Playback audio had changed to PC speakers.  Just open the drop down and reselect the TX 1 stream.  There is not a single TX selection on any of the three dropdown windows.  Using windows 10, latest SDR, and FLDigi.  Any ideas?
Photo of Nick

Nick

  • 46 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of WX7Y

WX7Y

  • 571 Posts
  • 104 Reply Likes
check to see if WIN10 upgrade which started being pushed to everyone broke DAX and CAT drivers 
see the link from earlier today https://community.flexradio.com/flexradio/topics/windows-10-update-strikes-again 

hope this is your issue.

Bret
WX7Y
Photo of Michael Coslo

Michael Coslo

  • 854 Posts
  • 210 Reply Likes
I had the same issues. Uninstall everything then reinstall. This is life with Windows. W10 doesn't play nice with other programs.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
Nick - after taking the suggestions by WX7Y if you are still having issues, please submit a HelpDesk support ticket.
Photo of Ken - NM9P

Ken - NM9P, Elmer

  • 4025 Posts
  • 1248 Reply Likes
When my Win 10 Machines (I have 3 in different locations) recently updated from Win 10 (Home Premium) to Win 10 "Anniversary Edition" it broke my DAX drivers on some of them, as others have experienced.  

This has been a common event for me -- I joined the "insider preview" group long before Win 10 was released and experienced "breakage" several times a week until the official release.  Then it broke about every few weeks after that for a while.  

But I have adapted to the process of uninstall, reboot, delete phantom/hidden DAX & Serial ports using Device Manager, reboot, re-install SSDR, reboot, check ports again in Device Manager......
I have only once or twice had to go through Tim's whole procedure that includes registry cleanup, and only a few times had to go as far as removing VSPManager in order to get things sorted out.

It is a pain.....But it doesn't take that much time to do, once you get used to it.  
I have always chalked this up merely to being on the cutting edge of both SDR and Windows.....sometimes you bleed a little...

Ken - NM9P
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1734 Posts
  • 590 Reply Likes
Hi Ken,
I also recently updated my Win10 PRO machine to the "anniversary edition".    The update fouled up the DAX drivers for me this time too.  I got the "possible DAX driver error" when starting DAX control panel.   Win10 seems to have it out for drivers, I was also running the Win10 preview betas for a while so it was a frequent occurrence. 

The fix I've been using is pretty quick and focused on the DAX drivers only.   I use a modified version of Tim's instructions to uninstall and reinstall the DAX drivers.  That is the only thing I need to do (I don't uninstall SSDR, modify the registry, etc)  and it only takes about 4-5 minutes.   YMMV but this approach has worked for me a few times for this DAX error after a Windows update.  

The DAX Fix - Rather than use a CMD window and type in the commands, I just navigate to the folders and "right click" on each of he BAT files to run as "administrator."   This process is quicker and since there is no typing of commands it may also be less error prone.   Since I've had to do this a few times I set up a "quick access" shortcut to the FlexRadio Systems folder.   Then just go to the current SSDR version sub-folder and run the procs.   I saved my modified version of the process in a snapshot (below) for reference. 



If this doesn't fix your issue you haven't lost much time and can still take more drastic steps like uninstalling and re-installing everything.

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 - HW.................. V 1.8.4.84
SSDR / DAX / CAT...... V 1.8.4.168
Win10
Photo of Ken - NM9P

Ken - NM9P, Elmer

  • 4025 Posts
  • 1248 Reply Likes
Interesting technique.  I will need to remember this the next time it gets "broken."  

I was wondering if this whole thing could be made into a single batch file called "Redo_DAX_Drivers.bat" that could be run from within the current version's 64bit Drivers directory using relative addressing?  It could then be saved for the next time and used again, even if you are using a different release.....(Perhaps FRS could even put this in the 64-bit Drivers directlry themselves and save us the trouble?)

It has been long enough since I have done any "DOS-Level" batch files, that I am not sure I even remember how to do it, other than just using the simple text editor.  But how to tell it to run each individual BAT file as administrator?  (Or does it matter that my regular user name is an administrative  level already?)

Ken - NM9P
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
Al - the only issue with your modified procedure is that you do not retain any error codes that are displayed if the process fails because the command windows closes immediately after it runs.
Photo of Bill W2PKY

Bill W2PKY

  • 461 Posts
  • 79 Reply Likes
For some reason I lost a couple of DAX channels on the speaker sound control panel. I un-install SSDR including DAX and reinstall SSDR. Takes all of 15 seconds on my computer. Can't imagine what some users do to spend so much time reinstalling SSDR?????
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1734 Posts
  • 590 Reply Likes
Hi Tim,
Good point about the error messages,  although it's worked fine so far.   I can't remember the number of times I've run it that way but when I was installing the Win10 preview editions it was pretty often.   Even now it happens too often.  

Something to consider -- You could add a "pause" command at the end of each bat file.   You would get the "press any key to continue" message before it closes and the error message would be on the screen.   As Ken suggested it would be nice to have one BAT file that does it all.    



It may not be worth spending any time on this but then again given Windows propensity to foul up drivers it may be worth investing a few hours to make it easier for the users, less error prone (due to user typing errors in the CMD window)  and as a result potentially less effort for your support team. 

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 - HW.................. V 1.8.4.84
SSDR / DAX / CAT...... V 1.8.4.168
Win10

This conversation is no longer open for comments or replies.