K3 and Beta 3.44

[kd1na]

Everyone,
I installed Beta 3.44 (was at 3.42) and noticed the following:

When operating in TX DATA (DATA A Mode) I fine that my RF Output seems to really take a long time to properly adjust itself to the desired power out. Sometimes there is no output power even though the K3 is in transmit.  If I monitor the transmitted audio I fine there is none. (The computer is outputting audio).

During this problem if I hold the XMIT button I do get the desired output but trying in XT DATA mode still has no output though the K3 is in transmit.

If I go into USB and back into TX DATA (Data A) mode or power cycle the K3, then I have output power but it seems to take a long time to adjust itself.

Reinstalling Firmware 3.32 totally solves the above problems.

Just to be sure I wasn't imagining things I reinstalled Beta 3.44 and the problems reappeared, installing beta 3.42 fixed everything

It seems there is a problem with 3.44 Beta firmware unless I am screwing up somewhere.

73
Dave KD1NA
K3 934
______________________________________________________________
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

[Julian, G4ILO]

kd1na wrote

Everyone,
I installed Beta 3.44 (was at 3.42) and noticed the following:

When operating in TX DATA (DATA A Mode) I fine that my RF Output seems to really take a long time to properly adjust itself to the desired power out. Sometimes there is no output power even though the K3 is in transmit.  If I monitor the transmitted audio I fine there is none. (The computer is outputting audio).

During this problem if I hold the XMIT button I do get the desired output but trying in XT DATA mode still has no output though the K3 is in transmit.

If I go into USB and back into TX DATA (Data A) mode or power cycle the K3, then I have output power but it seems to take a long time to adjust itself.

Reinstalling Firmware 3.32 totally solves the above problems.

Just to be sure I wasn't imagining things I reinstalled Beta 3.44 and the problems reappeared, installing beta 3.42 fixed everything

It seems there is a problem with 3.44 Beta firmware unless I am screwing up somewhere.

Have you confirmed your input audio drive level is set for 5 bars of ALC?

Mine is, and I do not see the problem. I tried 80m, 20m and 10m for the purposes of the test. The first transmission on 80 and 20 I noticed that the power immediately starts at about 20% low, then increases over a couple of seconds to the requested value. Subsequent transmissions on the same band while you remain in data mode immediately give the requested value. If you change band or mode then change back the next data transmission shows this increase to the desired level.

I don't know if it would be different using the earlier firmware but this is not surprising behavior because what you have is a very slow ALC adjusting the output to give you what is required.

[hb9brj]

Don't know if the issue I'm observing is linked to the one described above:

When calling CQ in PACTOR FEC (simple 2-tone AFSK signal) in DATA-A mode, 5 ALC bars:
- up to FW 3.42: External wattmeter shows steady power close to the requested power level
- FW 3.44: External wattmeter keeps oscillating between 50...100% of requested power.

73, Markus HB9BRJ