Elecraft

Software Upgrades

Classic

List

Threaded

13 messages Options

BOB PHILBROOK

Software Upgrades

After reading countless reflector comments about firmware upgrades and releases, it appears to me that in many instances such so called upgrades are two steps forward and one in reverse.

You know the drill, fix this problem, add a new feature, and then find that something that worked in previous versions does not function as expected and now demands a fix and another firmware version.

Personally, I would like to see fewer firmware releases and more time spent vetting firmware before it is released. Firmware upgrades should be two steps forward -- period!

The rush to add new features and fix bugs in firmware appears to me to be too rushed to be efficient and effective. Tell me fellows, why the rush?

Bob, K9PAG
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Mike Cox

Re: Software Upgrades

Having already survived the Ten-Tec Orion I firmware and hardware
upgrade fiasco, I must admit that my experiences with the Elecraft
firmware migration has been a real pleasure. I eagerly download each new
beta version as soon as I know it's available. I have never regressed to
a previous edition. This was not the case with my Orion I. The ease of
loading a new version of the K3 firmware is an added plus over the Orion
(power on - hold the proper buttons - hold tongue just right while
crossing fingers). If there is some substantive issue with a new K3
version, a corrected version appears within hours (not weeks or months
as was the case with my Orion I). Also, the actual programmers of the K3
are accessible and responsive. I never did succeed in contacting an
Orion I programmer. Waiting over a year for Orion firmware that did not
occasionally crash like Windows 3.1 was frustrating! Considering the big
3 japanese manufacturers; if it doesn't work to your expectations,
simply wait for a subsequent model introduction and see if that's better.

If one is not comfortable with frequent K3 firmware upgrades, simply
ignore the "beta" versions. New "production" versions are not all that
frequent.

If one enjoys playing with new features and functions as soon as the
guys in Aptos make them available, then dive into the "betas". It's an
opportunity to participate in the engineering process! Hey, these guys
LISTEN to our feedback. I'm having a ball participating in the evolution
of this fine radio. I think they're doing it in a most acceptable fashion.

BOB PHILBROOK wrote:

> After reading countless reflector comments about firmware upgrades and releases, it appears to me that in many instances such so called upgrades are two steps forward and one in reverse.
>
> You know the drill, fix this problem, add a new feature, and then find that something that worked in previous versions does not function as expected and now demands a fix and another firmware version.
>
> Personally, I would like to see fewer firmware releases and more time spent vetting firmware before it is released. Firmware upgrades should be two steps forward -- period!
>
> The rush to add new features and fix bugs in firmware appears to me to be too rushed to be efficient and effective. Tell me fellows, why the rush?
>
> Bob, K9PAG
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Dave, G4AON

Re: Software Upgrades

In reply to this post by BOB PHILBROOK

Bob, some of the "rush" is to try and roll out features that are overdue
by months, plus how long do folks want to wait once a fault is discovered?

I have been running beta 2.23 since it came out and to me there is
nothing wrong with it, although I am not using the KRX3 and much of the
later firmware was to enable features in the KRX3.

There are still issues to be resolved, one I would like fixed is the
inability to adjust power while transmitting data which is tedious.
There are published items on the "to be implemented" list such as the
TCXO calibration to 0.5ppm.

Firmware can be rolled back to earlier versions, so as far as I am
concerned it's a "win win" situation.

73 Dave, G4AON
K3/100 #80
-----------------
After reading countless reflector comments about firmware upgrades and
releases, it appears to me that in many instances such so called
upgrades are two steps forward and one in reverse.
You know the drill, fix this problem, add a new feature, and then find
that something that worked in previous versions does not function as
expected and now demands a fix and another firmware version.
Personally, I would like to see fewer firmware releases and more time
spent vetting firmware before it is released. Firmware upgrades should
be two steps forward -- period!
The rush to add new features and fix bugs in firmware appears to me to
be too rushed to be efficient and effective. Tell me fellows, why the rush?

Bob, K9PAG
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Stephen Prior

Re: Re: Software Upgrades

I quite agree David, but I'm surprised that you are saying that the TX power
cannot be changed whilst transmitting, because I certainly can do that on
all modes so far as I can see with the latest beta that you have.

73 Stephen G4SJP

On 17/08/2008 20:37, "Dave G4AON" <[hidden email]> wrote:

> Bob, some of the "rush" is to try and roll out features that are overdue
> by months, plus how long do folks want to wait once a fault is discovered?
>
> I have been running beta 2.23 since it came out and to me there is
> nothing wrong with it, although I am not using the KRX3 and much of the
> later firmware was to enable features in the KRX3.
>
> There are still issues to be resolved, one I would like fixed is the
> inability to adjust power while transmitting data which is tedious.
> There are published items on the "to be implemented" list such as the
> TCXO calibration to 0.5ppm.
>
> Firmware can be rolled back to earlier versions, so as far as I am
> concerned it's a "win win" situation.
>
> 73 Dave, G4AON
> K3/100 #80
> -----------------
> After reading countless reflector comments about firmware upgrades and
> releases, it appears to me that in many instances such so called
> upgrades are two steps forward and one in reverse.
> You know the drill, fix this problem, add a new feature, and then find
> that something that worked in previous versions does not function as
> expected and now demands a fix and another firmware version.
> Personally, I would like to see fewer firmware releases and more time
> spent vetting firmware before it is released. Firmware upgrades should
> be two steps forward -- period!
> The rush to add new features and fix bugs in firmware appears to me to
> be too rushed to be efficient and effective. Tell me fellows, why the rush?
>
> Bob, K9PAG
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>

Dave, G4AON

Re: Software Upgrades

In reply to this post by BOB PHILBROOK

Stephen

Try, DATA A, audio into K3 via line input, RTTY (or any similar audio
data mode), set power to 20 Watts, go to TX and try to turn up the power
while transmitting. Nothing happens, the power remains at 20W.

73 Dave, G4AON
K3/100 #80, f/w 2.23

I quite agree David, but I'm surprised that you are saying that the TX power
cannot be changed whilst transmitting, because I certainly can do that on
all modes so far as I can see with the latest beta that you have.

73 Stephen G4SJP

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Dave, G4AON

Re: Software Upgrades

In reply to this post by BOB PHILBROOK

Further info on the "frozen" power level adjust on TX with data modes.

The problem appears to be a very slow ALC algorithm, on a constant data
stream the power level eventually gets there, on burst modes such as
Pactor and Amtor it never changes to higher levels but oddly will reduce
if turned down from a high power level.

Sorry about any confusion...

Dave, G4AON
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Stephen Prior

Re: Re: Software Upgrades

In reply to this post by Dave, G4AON

You are right David,

The power output indication (in the VFO B area) changes but the actual power
out as indicated on the K3 does not. Furthermore, if I go below 12W such
that the QRO PA goes out of circuit, the actual power will drop (not sure
what to) and will not return to 20W when I increase it.

Apologies for my rather 'blanket' dismissal of your observation!

73 Stephen G4SJP

On 17/08/2008 21:34, "Dave G4AON" <[hidden email]> wrote:

> Stephen
>
> Try, DATA A, audio into K3 via line input, RTTY (or any similar audio
> data mode), set power to 20 Watts, go to TX and try to turn up the power
> while transmitting. Nothing happens, the power remains at 20W.
>
> 73 Dave, G4AON
> K3/100 #80, f/w 2.23
>
> I quite agree David, but I'm surprised that you are saying that the TX power
> cannot be changed whilst transmitting, because I certainly can do that on
> all modes so far as I can see with the latest beta that you have.
>
> 73 Stephen G4SJP
>
>
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>

GM4KGK

Re: Software Upgrades

In reply to this post by Dave, G4AON

Dave G4AON wrote

There are still issues to be resolved, one I would like fixed is the
inability to adjust power while transmitting data which is tedious.
There are published items on the "to be implemented" list such as the
TCXO calibration to 0.5ppm.

I hope I'm not missing something but I seem to be able to vary the power in data modes from zero to any sensible level that doesn't run into ALC (about 70 watts max).
Set the PWR control to 100w (or 120w if you wish) and control the power output using the MIC level control on the front panel. (MIC SEL = LINE IN).
Or is that classed as cheating? :-)
Norman - GM4KGK

KK7P

Re: Software Upgrades

> Set the PWR control to 100w (or 120w if you wish) and control the power
> output using the MIC level control on the front panel. (MIC SEL = LINE IN).
> Or is that classed as cheating? :-)

Yes, I think it is :-)

The problem with this approach is that over time the slow ALC loop may
try to build the power level up to that which you've set with the PWR
control.

73,

Lyle KK7P

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

Bob Cunnings NW8L

Re: Software Upgrades

The K3 operating tip regarding PSK setup:

http://www.elecraft.com/K3/k3_operating_tips.htm#psk%20audio

really does need to be updated. It was written before the ALC system
changes that came with MCU 1.87.

Bob NW8L

On Mon, Aug 18, 2008 at 8:15 AM, Lyle Johnson <[hidden email]> wrote:

>> Set the PWR control to 100w (or 120w if you wish) and control the power
>> output using the MIC level control on the front panel. (MIC SEL = LINE
>> IN).
>> Or is that classed as cheating? :-)
>
> Yes, I think it is :-)
>
> The problem with this approach is that over time the slow ALC loop may try
> to build the power level up to that which you've set with the PWR control.
>
> 73,
>
> Lyle KK7P
>
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>

GM4KGK

Re: Software Upgrades

In reply to this post by KK7P

Lyle Johnson wrote

> Set the PWR control to 100w (or 120w if you wish) and control the power
> output using the MIC level control on the front panel. (MIC SEL = LINE IN).
> Or is that classed as cheating? :-)

Yes, I think it is :-)

The problem with this approach is that over time the slow ALC loop may
try to build the power level up to that which you've set with the PWR
control.

73,

Lyle KK7P

Hello Lyle
I have to bow to your superior knowledge in these matters, but over two or three PSK QSO's (say, 20-25 minutes) I haven't noted any increase in transmitted power from the 35-40 watts I start with.
What sort of time scale would you expect the ALC loop to require to get close to the level set on the PWR control?
I will look at it more closely in future.
73
Norman _ GM4KGK
K3 - #1139

dave.wilburn

Re: Software Upgrades

In reply to this post by BOB PHILBROOK

I have upgraded to every firmware beta and never had a problem.

David Wilburn
K4DGW

BOB PHILBROOK wrote:

Phil Salas

K3 Software Upgrades

In reply to this post by BOB PHILBROOK

Until a few days ago, I have only used fully released software. However,
because I now have the KRX3 installed, I needed to update my K3 with Beta
software. No big deal! The instructions for doing this are very clear.
And other than the extra (and very minimal) time it takes to download and
unzip the files, loading the Beta software was just as easy as loading the
released software. I'm using the Elecraft USB-to-serial adapter and Windows
Vista operating system.

Phil - AD5X

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com