WriteLog, MK2R and K3, The Rest of the Story

[K5RC]

 

Half way through the 160 contest I changed computers from an AMD Turion
dual-core Processor to an Intel Celeron single-core processor. The WinKey
malfunctioned only once in 4 hours of testing. I then turned off all PTT
functions in the Microham Router and in the WL setup and used the VOX in the
K3. The system worked flawlessly for the remaining 15 hours of the contest.

Not sure if it was the computer, the dual-core processor or the PTT issues,
but at least the WinKey com problem seems to be solved. Of course, we did
not use the K3 bandswitch all weekend but we will test that next week in
Sprint.

 

Tom Taormina, K5RC

Virginia City NV

 

 

Ever since we got our K3's last fall, we've had a continuing problem with
both WinTest and WriteLog losing com with the Microham MK2R/Server. We've
had lots of dialogue with Microham and no response from WinTest.

I have swapped MK2R's with the one on the second station that runs the
FT1000D's. No difference.

 

This weekend we are using WriteLog for the CQ 160 contest. For no apparent
reason, the keyboard will start sending jibberish on its own. Just resetting
the MK2R does not help. Closing WL, turning off the MK2R and closing and
restarting the Microham server puts everything back in working order.

 

In CQ 160 the problem did not happen until 4 hours into the contest. Then it
recurred regularly for several hours and then it settled down again. What is
different this time (and why I finally subscribed) is that the operator
caught a glimpse of PTT ERR on the K3 once while this event was happening.

 

This morning I changed computers (the last thing to change besides the K3)
and, after several hours of running the CQ message over and over in TEST
mode, the problem recurred. I made sure the PTT and KEY RTS and DTR are OFF
and I now changed the Microham PTT configuration to QSK to stop it from
invoking any PTT. It is CQing again.

 

Anyone else had this issue? Any ideas?

 

Tom Taormina, K5RC

Virginia City NV

Home of W7RN and K7RC

http://k5rc.cc   FOC 1760

"Communication is the problem to the answer" - 10cc  

 


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Joe Subich, W4TV-4]

Tom,

Which version of WriteLog?  

What PTT settings in WriteLog?  
     Comm PTT checked for the K3?
     "On LPT pin 16/COM RTS" in CW PTT Setup?

Any PTT ports defined in microHAM Router?
    "Steer serial CW/PTT" checked?
    "Steer WinKey CW/PTT" checked?

What control method for MK2R - LPT ("Classic" control) or
microHAM Control Protocol (CW Keyer type = microHAM MK2R
in WriteLog)?

73,

   ... Joe, W4TV
 
 

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of K5RC
> Sent: Sunday, January 31, 2010 12:35 PM
> To: [hidden email]
> Cc: 'microHAM Support'
> Subject: [Elecraft] WriteLog, MK2R and K3, The Rest of the Story
>
>
>  
>
> Half way through the 160 contest I changed computers from an
> AMD Turion dual-core Processor to an Intel Celeron
> single-core processor. The WinKey malfunctioned only once in
> 4 hours of testing. I then turned off all PTT functions in
> the Microham Router and in the WL setup and used the VOX in
> the K3. The system worked flawlessly for the remaining 15
> hours of the contest.
>
> Not sure if it was the computer, the dual-core processor or
> the PTT issues, but at least the WinKey com problem seems to
> be solved. Of course, we did not use the K3 bandswitch all
> weekend but we will test that next week in Sprint.
>
>  
>
> Tom Taormina, K5RC
>
> Virginia City NV
>
>  
>
>  
>
> Ever since we got our K3's last fall, we've had a continuing
> problem with both WinTest and WriteLog losing com with the
> Microham MK2R/Server. We've had lots of dialogue with
> Microham and no response from WinTest.
>
> I have swapped MK2R's with the one on the second station that
> runs the FT1000D's. No difference.
>
>  
>
> This weekend we are using WriteLog for the CQ 160 contest.
> For no apparent reason, the keyboard will start sending
> jibberish on its own. Just resetting the MK2R does not help.
> Closing WL, turning off the MK2R and closing and restarting
> the Microham server puts everything back in working order.
>
>  
>
> In CQ 160 the problem did not happen until 4 hours into the
> contest. Then it recurred regularly for several hours and
> then it settled down again. What is different this time (and
> why I finally subscribed) is that the operator caught a
> glimpse of PTT ERR on the K3 once while this event was happening.
>
>  
>
> This morning I changed computers (the last thing to change
> besides the K3) and, after several hours of running the CQ
> message over and over in TEST mode, the problem recurred. I
> made sure the PTT and KEY RTS and DTR are OFF and I now
> changed the Microham PTT configuration to QSK to stop it from
> invoking any PTT. It is CQing again.
>
>  
>
> Anyone else had this issue? Any ideas?
>
>  
>
> Tom Taormina, K5RC
>
> Virginia City NV
>
> Home of W7RN and K7RC
>
> http://k5rc.cc   FOC 1760
>
> "Communication is the problem to the answer" - 10cc  
>
>  
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html