Hi Grant,
Yes, that's what I meant by "... maintaining / deriving the capped Waterfall
local variable separately / independently." I'm sure Paul will acknowledge it
as a bug and fix it.
JoeKF5WBO
From: GRANT YOUNGMAN <n...@icloud.com>
To: wickedbeernut <kf5...@wickedbeernut.com>
Cc: elecraft@mailman.qth.net
Sent: Tuesday, May 3, 2016 9:48 PM
Subject: Re: [Elecraft] PX3: Apparent "bug" fw 1.42
Sounds rational. It does seem to me that the most logical approach, presuming
all of this is the case, would be to always pull the Waterfall height from
EEPROM, cap it when necessary in text decode mode, and otherwise leave it the
stored value. That would solve it.
Thanks … Grant NQ5T
>
>
> You're pointing out that if text decode is turned off, the Text menu /
> Waterfall value is not restored (i.e., not re-read from the EEPROM).
>
> If you power the PX3 off and on, the Text menu / Waterfall value is re-read
> from the EEPROM. If text decode is off, the Waterfall local variable is not
> capped. The Waterfall local variable is 139.
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
