[Elecraft] FW: P3 and K3 RS-232 baud rates

[Tommy Alderman]

On page 13 of the P3 Owner's Manual, in the section 'RS232 XCVR', the last
sentence states: "The K3 baud rate is set automatically by the P3 and cannot
be changed at the K3" Based on that, is it correct that if I set the P3 baud
rate to 4800 b, then the K3 will be operating at 4800 b even though
CONFIG:RS232 reads 38400b?

Thanks,

Tom - W4BQF
 

-----Original Message-----
From: elecraft-bounces at mailman.qth.net
[mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Tommy Alderman
Sent: Tuesday, September 14, 2010 6:12 PM
To: elecraft at mailman.qth.net
Subject: [Elecraft] P3 and K3 RS-232 baud rates

P3:	s/n 464		Firmware 00.32  	Rcvd 9/14/10
K3:	s/n 4521	Firmware 4.10		Rcvd 8/2/10
I have an old logging program that I do not want to lose or have to change.
My first problem, because this program is so old (YPlog) was solved by
selecting a Kenwood TS570D as the xcvr and setting the baud rate at 4800/1
stop bit. That works fine.

Today, W4TV published an email explaining how to reset the P3 baud rate from
its default of 38,400 back to 4800. That works. Unfortunately CONFIG:RS232,
when I change the baud rate from 38400 to 4800 and press MENU/CONFIG again,
the baud rate change is not saved in the K3 and I can no longer connect to
my logging program. The only work-around I have found so far is to turn off
the P3, set the K3 CONFIG:RS232 from 38400 to 4800, then press MENU/CONFIG,
then turn the P3 ON again, and all works correct.

Will there be a firmware update that will allow the P3 and the K3 to be set
at baud rates other than 38400 when BOTH the K3 and the P3 are turned on?  I
certainly hope so because this YPlog is the only logging program I have
found in some 20 years that will allow me to send CW at speeds over 60 wpm
without the CW stuttering due to I/O interrupts from a CPU.

Thanks and 73,

Tom - W4BQF

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00007.txt
Url: http://mailman.qth.net/pipermail/elecraft/attachments/20100914/5611189a/attachment.txt