V-e-r-y interesting.... Is this something that could be configured/developed to
(say) implement 2nd VFO frequency reading with other rigs - specifically the
FTDX5000MP?
Steve
GW4BLE
Sent from my iPhone
On 8 Feb 2011, at 10:26, Ed Muns <w0yk@msn.com> wrote:
> SO2V with WriteLog and the K3
>
> Ed Muns, W0YK
>
>
>
> Contesting with the K3's two receivers is now even more effective with the
> enhancements in recent WriteLog versions 10.8x. This paper describes the
> feature for RTTY, but it is also useful for CW and SSB. Basically, an Entry
> Window is dedicated to each receiver (VFO) and transmit occurs on the VFO
> frequency whose Entry Window has "focus". SO2V denotes using the two VFOs
> (sometimes controlling two independent receivers) in the same radio. Two
> independent receivers are needed to simultaneously listen to both
> frequencies, one in each ear. This is usually used on the same band,
> although the K3 allows the receivers to be on different bands. (SO2R
> denotes using two separate radios in the same way and this is usually done
> on two different bands.)
>
>
>
> In WriteLog, the K3's second receiver (Sub-Receiver) is configured in the
> Ports Setup window as another K3, except that it is given the same COM port
> assignment as the main K3. (Note that this COM port is for computer control
> of the K3, different than the two COM ports described below for FSK/PTT
> keying.) On the Radio/Number of Radios menu, 2 is selected. Then, in each
> Entry Window, the frequency button is clicked and "Rig on Comm Port x"
> selected for the first (K3 Main Receiver) and "Rig(2) on Comm Port x"
> selected for the second (K3 Sub-Receiver). Enable SUB in the K3 and audio
> from each VFO is fed into the left and right ear, respectively. On the
> Radio menu, select Headphones Split so that the non-focus audio stream is
> not muted. Or, if you prefer muting, use Headphones Normal. I always
> listen to both VFOs (or, both radios in SO2R), but many contesters prefer
> muting for more focused concentration.
>
>
>
> For RTTY, two independent modems are needed, one for each receiver. If
> MMTTY is used for each modem, then two independent installations of MMTTY
> must be made. Using a standard stereo phone cable, the left (Main receiver)
> and right (Sub-receiver) audio streams feed the computer soundcard. The
> first instance of MMTTY is configured to decode the left channel and the
> second instance of MMTTY is configured to decode the right channel. Call
> signs selected, i.e., clicked, from each window are copied to the
> appropriate Entry window
>
>
>
> For FSK, two additional COM ports are required, again, one for each instance
> of MMTTY. Separate FSK/PTT keying interfaces are used, one on each COM
> port. At the K3, the two interfaces are connected to the FSK and PTT inputs
> on the K3. This makes them logically "wire-OR'd" for those who know what
> that means. Operationally, only one of the interfaces will be keyed by
> WriteLog/Rttyrite/MMTTY at a given time, so there is no conflict and either
> one drives the K3 when it's Entry Window has focus.
>
>
>
> I haven't explored this scheme using AFSK, but the principle is the same.
> Both instances of MMTTY should be able to drive the soundcard speaker, or
> Line Out, output which is connected to the K3 Line In jack.
>
>
>
> When focus is moved to the second Entry Window, the K3 is simply put into
> SPLIT mode so that transmission occurs on that frequency. Receive decoding
> remains fixed in each of the two Rttyrite MMTTY windows. When focus is
> moved back to the first Entry Window, SPLIT is removed so that any
> transmission occurs on the Main receiver's frequency, using the call sign in
> that Entry Window.
>
>
>
> If a KAT3 is installed in the K3, writelog.ini can be configured to swap
> between ANT1 and ANT2 as focus moves between the two Entry Windows. This is
> envisioned to provide SO2R with a single K3 on two different bands. Seems
> like it should work although I haven't tried it. I want separate radios for
> SO2R which is supported by commercial SO2R accessories like antenna
> switches.
>
>
>
> In addition, macros of K3 programmable commands can be defined in
> writelog.ini and assigned to keyboard keys as well as used in messages.
> This opens up lots of possibilities exceptional K3-WriteLog integration.
> Consult the WriteLog Help file for details (search on 'K3'.)
>
>
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|