K3: strange problem with HRD and latest FW

[tom kenville]

I flashed the new FW last nite.
uC 3.41
dl 2.37
fl 1.04

Problem has surfaced when running (it seems) with HRD.  HRD Ver 5.0 build
2290 Beta

In particular CW.  Seems that the paddle and straight key are mis-behaving.
Skips early part of break in.  perhaps the first 20-30 msec ?

Example:  sending W6TJK is get W6D..

Happens irrespective of TX-test mode, or TX with power to dipole.

When I disconnect HRD (ie. press the red X) the keyer now behaves.

Very disconcerting.

I have not changed HRD in some many months.


Seems to be OK with N1MM.
Mebbe time to go thetaway for logging hmm.

--
thanks and 73's
Tom Kenville  --  W6TJK
______________________________________________________________
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

[DC1RS]

No problems here, using also 3.41 and HRD Version 5.0 build 2306.

73 de Roland, DC1RS

[Julian, G4ILO]

tom kenville wrote

Problem has surfaced when running (it seems) with HRD.  HRD Ver 5.0 build
2290 Beta

In particular CW.  Seems that the paddle and straight key are mis-behaving.
Skips early part of break in.  perhaps the first 20-30 msec ?

Example:  sending W6TJK is get W6D..

Happens irrespective of TX-test mode, or TX with power to dipole.

When I disconnect HRD (ie. press the red X) the keyer now behaves.

Do you also find the front panel is slow to respond to some button presses? I think some programs poll the radio far too frequently for information and they are over-taxing the K3's controller. I think HRD is one of them. Is it really necessary to request the current frequency ten times a second?

The K3 has an auto-info mode that automatically updates computer software with all the information needed for logging whenever anything changes. There is no need for any logging program to poll the K3 at all, unless it is trying to display every setting of the radio which is what HRD is doing. But why is that necessary when you have the rig in front of you?

The reason some HRD users do not appear to have this problem *might* be connected to the baud rate you are using. I would think that using the fastest possible baud rate would minimize the load on the K3 CPU.