Bret et al,
Haven't we beat this horse to death? Do the mod yourself if you feel you
have the skills to do so. Have a fellow ham give you a hand or if not, send
your K3 back to Aptos and pay to have it done. End of story! 15 plus
e-mails is a huge waste of Inbox space.
73, Bob K3UL
_
I don't understand the fear of menu items. Honestly care not either
way but I know a few people who simply wanted to be certain that the
software saw the mod. Perhaps say it sees it on the first power up.
But that would require that you update the firmware before putting the
mod in place and would
On Sun, 30 Aug 2009 10:17:38 -0700, Brett Howard
wrote:
In line:
>Dmm doesn't provide assurance that you have the right points. I
>personally wanted assurance and so I used my k1 a dummy load and my
>dmm to test.
That's a good way to test, but why load the menu and precious firmware
bytes up wi
Dmm doesn't provide assurance that you have the right points. I
personally wanted assurance and so I used my k1 a dummy load and my
dmm to test. I think there are others who would appreciate assurance
that the mod is in place correctly and don't want to hook a
transmitter directly to their receiver
On Sun, 30 Aug 2009 11:53:51 -0500, "R. Kevin Stover"
wrote:
Agree!
Tom, N5GE
n...@n5ge.com
K3 #806, K3 #1055, PR6,
XV144, XV432, KRC2,
W1 and other small kits.
http://www.n5ge.com
http://www.swotrc.net
>If mod installers don't have at least a cheap DMM to do testing with,
>they have no busin
If mod installers don't have at least a cheap DMM to do testing with,
they have no business anywhere near the K3 RF board with a soldering
iron. Why continually add things to the menu?
Brett Howard wrote:
> It would give mod installers without means to test a way to assure
> themselves that they
It would give mod installers without means to test a way to assure
themselves that they have properly carried out the task.
On 8/30/09, Ken Wagner K3IU wrote:
>
> I believe that the boot up detection is only to determine whether the
> jumper is installed, not whether it has been activated by a st
I believe that the boot up detection is only to determine whether the
jumper is installed, not whether it has been activated by a strong
signal. I really don't see a need to report that the jumper is installed
on the display since one would surely remember if the jumper has been
installed.
It
Where I think it should be reported is in the kxxx area of the menu.
So in the area where you turn on the krx3 and knb3 and what not you
could have a non editable entry for kesp3 or some other creative part
number.
On 8/30/09, Brian Alsop wrote:
> I wonder since this is a "software detected" mod
I wonder since this is a "software detected" mod at setup if the
firmware program could report it is there. (alternatively, maybe the K3
can report it like it does key err) I'm not keen on zapping the front
end with a high signal level from an uncalibrated source to find out if
it is working.
How does one test this without a calibrated signal source?
Why was 80M chosen for the test frequency? Most ops have preamp off and
many have attenuation in.
It appears one needs something like an 80db over S9 sig for it to cut in.
73 de Brian/K3KO
No virus found in this outgoing message.
Che
11 matches
Mail list logo
