Baud rates and more baud rates.

[James Rogers]

For years the following setup worked well. USB Connected
K3s/P3/KPA500/KAT500. CAT is COM10. Device manager says COM10 is set for
9600 baud, no parity, 8 data bits, 1 stop bit (9600,n,8,1). HRD is my
main control and logging program. Everything is all hooked up and
working well.

Then I installed SatPC32 tracking software for future satellite work.
The K3s is configured with TRN1 for my XV144 2M transverter. I turn on
SatPC32's CAT switch and I can see the K3 display pausing for a split
second every time SatPC32 sends a frequency update to the K3s. But the
K3s is not getting the update. Checked the P3 baud rate and it  is
38,400 (remember this has not been a problem until now).  So I begin
adjusting its baud rate and eventually drop to 4800 baud. Bingo! it is
all working together, frequency updates to the K3s are getting there,
everything is cool....

Until I get out of satellite "mode" and go back to HRD. Now HRD is not
communicating with the K3s, until I set COM10 for 4800 baud as well.
That actually makes good sense. The same baud rate throughout the entire
connected system, but how did it work before with COM10 CAT baud rate a
9600, and the P3 running at 38,400?

If you look in the K3s manual (p.63) for the RS232 menu item you will
notice that it says the default is 4800b. To set it to any other value,
you must get out of USB mode and use the RS232 port. At that point it is
no longer COM10 but is whatever port your USB/Serial adapter is assigned
by the computer.

COM problems are sometimes difficult to resolve. I found an invaluable
aid in Eltima software's "Serial Port Monitor".  The pro version is
recommended. At 150 bucks, it is worth the money and is packed with
features.

FWIW, Jim, W4ATK

______________________________________________________________
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
Message delivered to [hidden email]

[Don Wilhelm]

Jim,

Take a look at all the other RS-232 devices in your system - and that
includes software applications.  Look specifically at the baud rate.
Then set the K3 and P3, your COM ports, and other devices to the same
rate.  It should be the highest rate supported by your equipment and
applications - so the response times are the fastest they can be and
will not interfere with normal operation.

There is no benefit to be gained by running at a lower rate, that will
only take longer for the responses to flow between boxes.

What I am saying is that if everything but one or two boxes is capable
of 38,400, but you have one whose top rate is 19,200, then you should
set everything to 19,200.

Normally set the COM port for the highest speed it can handle and let it
go at that.  The application(s) will usually throttle the communications
back as necessary.

I don't know why the K3 defaults to 4800 baud, it is certainly capable
of 38,400.

73,
Don W3FPR


On 9/28/2017 10:43 AM, Jim Rogers wrote:

> For years the following setup worked well. USB Connected
> K3s/P3/KPA500/KAT500. CAT is COM10. Device manager says COM10 is set for
> 9600 baud, no parity, 8 data bits, 1 stop bit (9600,n,8,1). HRD is my
> main control and logging program. Everything is all hooked up and
> working well.
>
> Then I installed SatPC32 tracking software for future satellite work.
> The K3s is configured with TRN1 for my XV144 2M transverter. I turn on
> SatPC32's CAT switch and I can see the K3 display pausing for a split
> second every time SatPC32 sends a frequency update to the K3s. But the
> K3s is not getting the update.

______________________________________________________________
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
Message delivered to [hidden email]