Subject: Slice Master losing CW Skimmer connection / Launch tab changes to “Never”

AK1MD

Hello all,

I’m seeing a recurring issue with Slice Master and CW Skimmer and wanted to ask if anyone else has experienced this.

Behavior I’m seeing:

• Slice Master initially launches CW Skimmer correctly
• After a short time, Slice Master loses the connection
• CW Skimmer then closes on its own
• In Slice Master, the Launch tab changes from the expected setting to “Never”

Once this happens, CW Skimmer will not relaunch automatically.

For context:

• Re-downloaded and installed the latest Slice Master 6000 (v0.11.0g)
• SmartSDR / FlexRadio version: 4.1.3
• CW Skimmer: 2.1
• Operating system: Windows 11

I’m trying to determine whether this is:

• a known Slice Master issue,
• a CW Skimmer interaction problem, or
• possibly a Windows 11–related or security/permission issue.

If anyone has seen this behavior — or found a fix or workaround — I’d really appreciate hearing about your setup and what resolved it.

Thanks in advance for any insights.

73,
Alex AK1MD

AK1MD

After changing the audio input/output device in the CW Skimmer Audio settings, CW Skimmer has stopped shutting down, and Slice Master now appears to maintain the connection properly. For some reason, one of the Flex Radio audio drivers had been automatically selected there.

Previously, when clicking on a callsign in CW Skimmer, the callsign would be copied and pasted automatically into the DXLog entry window. That behavior is no longer happening. CW Skimmer still decodes and displays calls normally, but clicking a spot no longer transfers the callsign into DXLog.

This was working correctly in the past, and I haven’t intentionally changed anything in that part of the setup. The only significant change recently is updating SmartSDR / FlexRadio to version 4.1.5.

Erik Carling EI4KF

I cannot be sure as it is a long time since I used this type of skimmer, but I seem to remember on the Telnet Tab there should be a 'Allow Skimmer Commands' check box. Is it set to on? I may be off base here but worth a look.