CAT PORTS DISAPPEARED

Dawg Fan

Pat N6PAT

Dawg Fan

Dawg Fan

Dawg Fan

Dawg Fan

looks to me like the ports are also missing from this file.

Joseph

Pat N6PAT

k3Tim

Dawg,

From the cat xml file it looks like the port com 26 + com 126 and TCP 5002 are setup.

I run Win 10 Pro + 6500 and latest updates. Very seldom a problem with DAX and none with CAT.   Any idea what triggered this? 

There was a Win 10 update in the recent past that caused a problem. After an update I give the system several minutes after rebooting to settle in. Afterwards, opening the Sound panel and going to the playback and record will shake out any problems.  The "recording" menu of the Sound panel caused a BSoD, after rebooting once more all was good and SDR/CAT/DAX were fine.

Best,
Tim - 

Mike-VA3MW

Hi All

This is a very unusual problem and there is nothing in the Flex SmartSDR code that will actually delete your Com ports.   That makes it a difficult problem to solve especially if our support teams cannot replicate the problem.  The CAT port deletion is the symptom of some other problem within the computer.  

BSOD's are an indication of some sort of hardware issue with the computer.  It is so bad that the core part of Windows is not able to handle the error.  If uninstalling and re-installing SSDR didn't solve the problem, then you may have to do the following.

If you want to solve it (and you won't like the answer), I would either replace the computer or totally rebuild the computer from scratch and do a clean install.  The odds of this resolving your issue in the shortest amount of time is very high.  You can get a great deal on new PC's at Costco.  

Case in point.  My XLY's computer would crash every time she tried to print on her HP printer.  We switched it for a Canon.  Same issue.   I spent days trying to solve it, but without luck.  The solution was to buy a new hard drive (hard drives have a finite life and her computer was older than 3 years--they start to go into a constant repair mode) and re-install Windows (I only use Win 10 Pro).  Problem solved.   And, it was noticeably faster.  Happy Wife.... Happy Life and I got to buy a new radio too!

I also had a serious issue with the Silicon Labs drivers that Icom and Yaesu use for their USB/CAT ports.  Days of work and debugging later, and the only fix was to rebuild the computer from scratch.  In hindsight, I should have done this in the first place.

I have more similar stories, but you get the idea.  I'm sure others have similar stories.

Mike

Pat N6PAT

Are you serious? Replace the computer? Rebuild the computer? This happened on 2 different computers that I have. One is a 1 year old Win 10 and the other is a brand new i7-9700 that cost me over $1,100.

Are you saying that everyone that has this problem has a faulty computer? That's the first thing that I was told by many here when I had decode problems last year. I actually replaced the computer and it turned out to be a bad XO in the Flex 6700 that required you guys to fix it.

Jon_KF2E

I'm with Pat on this. To suggest that the right way to fix this issue is to replace your computer is ludicrous. Also, while hardware issues certainly can cause a BSoD the much more likely cause is a driver conflict. As we all know Flex has a long history of driver issues with SSDR/DAX and SmartCAT. I'm sure these issues are both complex and difficult to solve but they are Flexes problem to solve. Flex chose to support the Windows platform and Flex needs to figure out how to get it to work. 

I just spent a long weekend of frustration trying to work the ARRL SSB DX contest. I had radio reboots, issues with spots, setting lost on band changes and a host of other pain in the **** problems. I've used Flex radios for almost seven years and I have to tell you it is getting worse, not better. 

Please Flex, stop trying to expand your software and focus on getting what we have working reliably. Resolve the DAX/CAT driver issues, get existing features working and help us not live in fear of updates. 

Dawg Fan

Mike-VA3MW

I am offering it as a suggestion if you want it resolved in the shortest amount of time.   If you read carefully, you would see that I told you you would not like it.  It was a bit of an elephant in the room suggestion.  

The CAT and DAX issues are not prevalent across the install base, but a small part.  And, unfortunately, it is some other component of the OS that is impacting it as there are many moving parts that can impact what you are seeing.    Who knows what other programs that are installed on these computers that could be impacting Layer 0 operations since Windows is not a closed operating system.  

These comments are my personal opinion based on my personal experience in the industry.   I'm a seriously active Ham and this is what I would do if it was me regardless of who I work for.  It is one of the few things I  personally have control over.  As it turns out, a total reinstall for my Icom issue only took an hour, some other weird problems disappeared (not FRS related) and like I expected, it is now a much faster computer.  In hindsight, I was really glad I did it.

From an FRS perspective, we continue to work on SmartSDR and its support products.  You are always welcome to open a support case to have us follow up on it.   I want to reinforce the comments are mine only as a Ham operator contributing to a conversation.  

Tim - W4TME

The post with the CAT.settings file contents is a default CAT.settings file.  There was corruption to the original file and a new default one was generated.  Following the procedure in the HelpDesk article How to Re-associate CAT ports with Virtual Serial Ports will recover from the CAT.settings file corruption issue.

This happens when Windows does a forced shut down with SmartSDR CAT still running.  This occurs if a Windows Update reboots the PC or if the PC crashes.

Dawg Fan

I just went into device mgr, deleted all the old disabled ports, restarted windows, then restarted SDR CAT, manually input all my ports.  I am back up and running.  My frustration is having to deal with it in the first place.

Pat N6PAT

The question is why does this happen when updates take place? Why can't the CAT app be coded to guard against this (auto backup and restore functions) ?

Why don't I experience this with any of my other apps but consistently with the Flex CAT app?

Tim - W4TME

There is logic in place to attempt to write and properly close the XML file when the app close WM is received.  In a forced shutdown situation, this doesn't always happen successfully.

Dawg Fan

I just lost all the ports i input this morning.  If you go into device manager and view hidden ports they show up as greyed out.  I ran the routine you offered in your post and all remain.  Not sure what to do but manually delete them all again one by one then reinput them again....

Tim - W4TME

The HelpDesk has lots of good articles for addressing common issues.  The one you just reported, there the hidden devices are grayed out is addressed using the procedure in the article Removing Hidden or "Ghosted" Com ports

Dawg Fan

did that procedure this morning.  taking a break and will delete them and add them back again later today.

Robert Lonn

Jon_KF2E

Bill -VA3WTB

Tim - W4TME

Since the poster has received advice regarding the recovery of a corrupted CAT.settings file and additional options have been expressed. I am inclined to close this post at this time.

AB8YZ

Where is the CAT XML file located at?

Erik Carling EI4KF

Is there such a file? Or do you mean CAT settings file? That one is at

C:\Users\computer-name\AppData\Roaming\FlexRadio Systems\CAT.settings