And if the answer is "yes" what is the explanation to your question ? Raimund .

#fdm-sw2 #fdm-s2

One annoyance of this restriction is when using programs like cw slimmer or fldigi. Generally but especially in a contest situation you want the S2 start and stop frequency to remain fixed as you work

#fdm-sw2 #fdm-s2

Once the SW2 OmniRig is not enabled still there are a few connection possibilities. In fact, you send Frequencies to the SW2 but there is no return value. Also it could be that you have to adjust the

#fdm-sw2 #fdm-s2

I checked it again. SW2 Omnirig NOT enabled. TCP is sending and receiving data from RX1...RX4. After closing + reopen the SW2 + Interface. When the Interface-OmniRig is activated then Frequency + Mode

#fdm-sw2 #fdm-s2

Hello Raimund, I really appreciate your looking into this but I'm having trouble understanding your proposal. For clarification, here's the setup I'm currently using. In this set-up, the transceiver (

#fdm-sw2 #fdm-s2

Hi Jeff, A part your reference to a sync-AM with SW2-Omni not enabled a normal connection is using the SW2-OmniRig. As mentioned we have 3 main connections: TCP, Virtual Serial Com-Port and SW2-OmniRi

#fdm-sw2 #fdm-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 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

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, 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

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

#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

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

I don't remember why, I think this is due to some restriction inside the software or to synchronize OmniRig with the center frequency and not the virtual receiver frequency. I will check. Vianney Le i

#fdm-sw2 #fdm-s2

I don't remember why, I think this is due to some restriction inside the software or to synchronize OmniRig with the center frequency and not the virtual receiver frequency. I will check. Vianney Le i

#fdm-sw2 #fdm-s2

Hi Jeff, I have tried various combinations with my / interface software. In particular SW2 without OmniRig enabled. I receive the SW2 data and send frequencies to the SW2. The connection is using: - T

#fdm-sw2 #fdm-s2

Hi Jeff, i enclose a screenshot that is self explanatory. You can do that. The Radio frequency is: 7.026,03 The "Frequencies worked display View" is evidencing the saved Freq: 7.025,05 Here with this

#fdm-sw2 #fdm-s2

Recently bought an S2 and loaded the latest fdm-sw2 software (3.027). Impressed with both but for some reason Channel 1, Rx1 is stuck in Lock To CF mode. This is really annoying for a number of reason

#fdm-sw2 #fdm-s2

This is due to some settings. Did you enable omnirig in the Remote Ctrl tab of the Setup window ? Regards, Vianney Le informazioni contenute in questo messaggio di posta elettronica sono riservate e c

#fdm-sw2 #fdm-s2

Yes. Why would using Omnirig require “Lock to CF”? Jeff

#fdm-sw2 #fdm-s2