Done. Note that even in the s2, mute works when omnirig is enabled so it shouldn't be too hard. Also requested an option to mute when the detected signal level exceeds a user selectable value. Most SD

#fdm-sw2 #fmd-s2

Has anyone raised a feature request ticket about the lack of a mute option in the TCP server when used with the S2? It should be simple just to replicate the transmit command which obviously mutes a D

#fdm-sw2 #fmd-s2

True but expecting users to write software to fix problems is often a bridge too far IMHO. Jeff

#fdm-sw2 #fmd-s2

Hi Jeff, Great, that's exactly how it should be. A interconnection SW2 <> RIG using TCP/Omni/ComPort, depending on what we want to achieve, can resolve many problems that are coming up sometimes here

#fdm-sw2 #fmd-s2

Hi Raimund, My C# program for rig synchronization is working well. To solve the mute issue I ended up using a .Net package (available from nuget) which provides C# wrappers around the MS CoreAudio API

#fdm-sw2 #fmd-s2

Hi Jeff, when a TCP is connected correctly with the right millisecond interval you get and set the Frequency, Mode, S-Meter data ecc... as the primary data you need. In any case the read/set sequence

#fdm-sw2 #fmd-s2

I'm writing a program to synchronize my transceiver frequency to the fdm-s2 and visa-versa without using Omnirig which has some unfortunate side effects. It's working fine but now the SDR does not mut

#fdm-sw2 #fmd-s2

Hi Neil, If you are referring to the performance counter issue, I just ran the command prompt as admin and executed >lodctr /R in C:\Windows\system32 The audio issue was fixed in the audio tab of the

#fdm-sw2 #fmd-s2

Hi Jeff, did you have to change to the SysWOW64 folder, or did it work OK in system32? Would be useful to note so others will find the solution, and maybe we can update the FAQ. Mine definitely fails

#fdm-sw2 #fmd-s2

The performance counter was fixed using the method in the FAQ (thanks!) I fixed the audio crash by increasing the Soundcard Play Buffer Size (Audio tab in set-up) from 50ms to 1200ms Thanks Jeff

#fdm-sw2 #fmd-s2

Hi Jeff, the performance counter error is a common Windows fault. Easy to fix using lodctr /r from a Windows command prompt. You may need to chage to the SysWOW64 directory: What exactly happens when

#fdm-sw2 #fmd-s2

Hello Jeff, see this FAQ for the first issue : http://support.eladit.com/kb/faq.php?id=32 If the other issues persist, can you open a support ticket here http://support.eladit.com/open.php?&lang=en_us

#fdm-sw2 #fmd-s2

This was a first-time install on a high-end HP laptop running 64-bit Windows 7 The install ran to successful completion. When I run FDM-SW2 I always get this error: The GUI doesn't show CPU usage A mo

#fdm-sw2 #fmd-s2

Meanwhile I've found that there were additional USB-devices under the Human Interface Devices heading in Device Management that were enabled to power down. I unchecked all of them of course. I suspect

#fdm-sw2 #fmd-s2

That's OK and updated. Nota: I'm using only Box-PC's. Raimund .

#fdm-sw2 #fmd-s2

So would this be OK? On pressing the second button I get Framework 4.7 or later.

#fdm-sw2 #fmd-s2

Checked this and the Root hub for USB 3.0 was enabled to power down. Unchecked this, fingers crossed. Thanks!

#fdm-sw2 #fmd-s2

One thing you might want to check in Device Manager (in Windows) check the USB Root Hub. Check the Power Management option under Properties in Device Manager (Windows) and make sure the "Allow the Com

#fdm-sw2 #fmd-s2

For sure this is not depending on your FDM-SW2 or SDR Receiver. It is depending on your system and Platform configuration. Any suggestion is a guess as we don't have your PC in front. Often it is depe

#fdm-sw2 #fmd-s2

Thanks, good to know that I'm not the only one but not so good to hear that there isn't a solution (yet).

#fdm-sw2 #fmd-s2