[Elecraft] K3 Couple of issues during CQWW RTTY

[D Joyce]

Hi Brian:  I haven't been on RTTY too much recently so the problem hasn't 
occured for some time.  That being said, I'm going to see if I can pin 
things down a bit and report back.

The setup is a K3 with a microKeyer II running with a KPA500 at about 300W. 
I'm using MMTTY (within DX4Win) for non contest operations and MMTTY with 
N1MM for contests - FSK in both cases.

Thanks for your comments.

73,  Doug  VE3MV



----- Original Message ----- 
From: "Brian Alsop" <alsopb at nc.rr.com>
To: <elecraft at mailman.qth.net>
Sent: Monday, October 01, 2012 5:45 PM
Subject: Re: [Elecraft] K3 Couple of issues during CQWW RTTY


> Hi Doug,
>
> Interesting. How do you know it's the K3 and not the logging program.
> Or some other piece of hardware doing interfacing?  Could RFI be a
> cause?  You don't say what your setup for RTTY is.
>
> I'm been running RTTY contests with the K3 for years using a hardware
> TNC in FSK. At times we've been up to 1500 watts. I've never seen this
> first problem despite being mostly S&P with lots of band and large freq
> changes.  I've only been bit by the 75 baud problem once.  That was when
> 75 baud was introduced in firmware and became the default.  After fixing
> that once, it has never been seen again.
>
> Then again, maybe I've just been lucky.
>
> 73 de Brian/K3KO
>
>
>
>
>
> On 10/1/2012 20:54, D Joyce wrote:
>> Hi Joe:  I've had a problem similar to your #1 for over a year now.  In 
>> my
>> case while running FSK the K3 (Ser 2432) would switch from 45 to 75 baud 
>> all
>> by itself in the middle of the contest - it may have been after a band or
>> large frequency change, I don't remember now.  I also had a problem with 
>> the
>> K3 remembering the custom settings for the Filter Presets I & II.  They
>> seemed to be lost following a power on/off cycle.
>>
>> The last time I checked with Support I was told that Wayne was aware of 
>> one
>> or both of these and would be working on them once the design work on the
>> KX3 was completed.  I haven't checked lately so don't know the current
>> status.
>>
>> As to your problem #2, I haven't seen any of that since I'm running FSK
>> rather than AFSK.
>>
>> 73,  Doug  VE3MV
>>