2.1.33 Dax/Cat somewhat unstable...

  • 1
  • Question
  • Updated 2 years ago
  • Answered
It seems roughly since 2.0 that Dax and perhaps Cat have become increasingly unstable.

Today on my new laptop, Core i7, brand new installs of SSDR 2.1.33 and WSJT-X etc I was working FT8 on 20m.

I would make a few contacts then I would notice even though the bar was yellow in WSJT-X indicating transmit that the rig was not transmitting.

Shutting down WSJT-X and restarting Dax usually fixes it.  But it seems like I can only go about 5 contacts before a software restart is required.

This could be WSJT-X as I am using 1.8 with compiled in stuff for the 6600 to work.  But still I sometimes see that Dax TX channel stops working.  A restart of both WSJT-X and DAX will fix for a short while.

Kind of really annoying and makes the mode way less fun to operate.  Anyone else seeing issues?
Photo of Mark - WS7M

Mark - WS7M

  • 1375 Posts
  • 516 Reply Likes

Posted 2 years ago

  • 1
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9200 Posts
  • 3561 Reply Likes
Official Response
There is not any evidence that there have been increased instability issues with CAT and DAX since v2.0 was released.  There have been no changes to CAT and DAT in a long while other than adding SmartLink support for CAT.   However, we have seen an increase of issues related specifically to WSJT-X in Support, but during the same time, almost no reports with other CAT enabled third-party software.  Anecdotal evidence points to an issue with WSJT-X and not specifically to CAT and DAX.

Enve this post has a common thread; WSJT-X

Now I am not saying there isn't an issue with DAX, as we have acknowledged that there is something environmental with certain PC configurations that causes DAX buffer corruption that is resolved by closing and restarting DAX, but it does not affect everyone.  I can run my AMD machines for days constantly decoding digital modes with Fldigi and I never experience the issue.