CW Skimmer -

WI9Q

CW Skimmer is failing to run with SmartSDR after a port issue that seems to have been resolved with Helpdesk assistance. However, Flex Support refuses to help as they insist it is a CW Skimmer issue and not SmartSDR. Oh well, I'm disappointed but they call the shots. Hopefully the hive mind can assist.

When attempting to start CW Skimmer through Slicemaster, it tries to start CW Skimmer, then reports lost connection with CW Skimmer.

If I start CW Skimmer manually (not using SliceMaster), and click on Start/Stop Radio, I get the following error:  “The specified device is already in use.  Wait until it is free, and then try again.”

I have tried creating a new OmniRig port, but get the same behavior.  I am able to connect to my Kenwood and Icom radios on the same computer successfully; once SmartSDR starts, and the that radio is selected, I get the above error.

I have also tried uninstalling and reinstalling OmniRig.

Thoughts on next steps to run this down?

Mike-VA3MW

You might find that using SDC Server is easier to set up.

https://www.lw-sdc.com/

WI9Q

Hi Mike. Knew that comment was coming :). In fact, I use SDC and indeed it works well. That said, my use case requires CW Skimmer, so will be looking to resolve this. I've had no issues setting up CW Skimmer on any of my computers or rigs until now. Something changed that looks to be locking the port, but even adding a new CAT port doesn't do any good. Any ideas?

KS0CW

I downgraded to 3.8.19 to fix... Something in .21 appears to be the instigator

WI9Q

OK, after receiving some guidance from Alex @ CW Skimmer, it was not a com port issue. And, the error message I was seeing was not a CW Skimmer error message; it was system-generated. After digging further, the issue was related to the Flex audio port. After removing the Flex audio ports in Device Manager, and then letting Windows reload the audio ports corrected the issue.

I suspect that the audio ports became an issue at the same time that Flex CAT lost all the com ports. Again, the issue was not COM port related.