[Elecraft] K3 ver 03.79 and Palstar AT-AUTO

[Mike K2MK]

Hi Dick:

Thanks for the correction. I once experienced the problem that Bill
described and I thought I had it figured out by my quitting the Utility
program early. Obviously from your explanation this would not have caused
Bill's problem.

73,
Mike K2MK

> 
> The K3 Utility changes speed before firmware load and restores speed  
> right after firmware load. If you check the Verbose Logging View menu  
> option and observe the Activity Log part of the firmware tab and  
> perform a firmware load it should be clear when speed changes. In a  
> subsequent version of K3 Utility now in Field Test I have added rig S/ 
> N and RS 232 speed to the main window title bar to make the speed more  
> obvious.
> 
> Dick, K6KR
> 
>>
>>On Mar 20, 2010, at 8:32 AM, "K2MK" <k2mk at comcast.net> wrote:
>>
>> Hi Bill:
>>
>> I think that problem occurs if you turn off the K3 before quitting the
>> Utility program. It's the quitting of the Utility program that  
>> initializes
>> the sequence to return the baud rate that you previously had the K3  
>> set to.
>> It can't do it if the K3 is off.
>>
>> 73,
>> Mike K2MK
>>
>>> FYI
>>>
>>> Just in case someone else has this same problem,   I loaded the  
>>> latest K3
>>> firmware onto my rig and when the load was complete I found that my  
>>> K3
>>> would no
>>> longer control the Palstar tuner.
>>>
>>> It seems that the K3 Utility does not return the RS-232 port back  
>>> to the
>>> original baud speed setting that was used before the down load when  
>>> it is
>>> finished.  After I reset the RS-232 port speed back to the original  
>>> 9600
>> setting then the Palstar tuner started tracking again.
>>>
>>> 73,
>>> Bill - K6WLM
>>> KX1, K2, K3-100k
-- 
View this message in context: http://n2.nabble.com/K3-ver-03-79-and-Palstar-AT-AUTO-tp4768837p4769301.html
Sent from the Elecraft mailing list archive at Nabble.com.