K3 memory

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

K3 memory

David Windisch
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Brgds,
Dave, N3HE
Cincinnati OH
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory

Dick Dievendorff
I've had several reports of VFO B not being "honored" using the frequency
memory editor.  I've looked and don't see what I might have done to cause
this.  

Can you try this:  Enter a memory manually, with different frequencies VFO A
and B, and see if it switches with M-->V as it should?  Then read the
memories from the K3 into the frequency memory editor. Save the memories in
a file, and send me the .xml file for those memories and tell me which
memory works and which you entered manually and whether or not that works.

Thanks!

73 de Dick, K6KR


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of David Windisch
Sent: Wednesday, August 10, 2011 6:45 AM
To: [hidden email]
Subject: [Elecraft] K3 memory

Hi, all concerned:

I've been using v4.39 firmware for a while.

In a prior fw version, at least a year ago, using the K3 MemEd, I programmed
in, eg, vfo A=7000.00  and vfo B=7030.00,  so I can use the M>V button as a
bandswitch, and scan from A to B.  Worked fine afterwards.  Didn't have a P3
then; this was a simple workaround.

Been using a P3 and bandswitching with the BAND button since, and just now
noticed that the M>V function doesn't pick up the vfo B memory setting any
more when I tried it.

Read the memories with the MemEd; all As and Bs were as I set them; resent
them anyway; still no vfo B pickup.

Have I botched something up?

Brgds,
Dave, N3HE

--
View this message in context:
http://elecraft.365791.n2.nabble.com/K3-memory-tp6672414p6672414.html
Sent from the Elecraft mailing list archive at Nabble.com.
______________________________________________________________
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

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory

Jim Sheldon
Dick,
I tried it also, and it works when set manually, but it does NOT work through the memory editor and this is for both the 00 - XX memories or the band's 4 quick memories.

Jim Sheldon - W0EB

> I've had several reports of VFO B not being "honored" using the
> frequency
> memory editor.  I've looked and don't see what I might have done to
> cause
> this.
>
> Can you try this:  Enter a memory manually, with different
> frequencies VFO A
> and B, and see if it switches with M-->V as it should?  Then read
> the
> memories from the K3 into the frequency memory editor. Save the
> memories in
> a file, and send me the .xml file for those memories and tell me
> which
> memory works and which you entered manually and whether or not that
> works.
>
> Thanks!
>
> 73 de Dick, K6KR
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of David
> Windisch
> Sent: Wednesday, August 10, 2011 6:45 AM
> To: [hidden email]
> Subject: [Elecraft] K3 memory
>
> Hi, all concerned:
>
> I've been using v4.39 firmware for a while.
>
> In a prior fw version, at least a year ago, using the K3 MemEd, I
> programmed
> in, eg, vfo A=7000.00  and vfo B=7030.00,  so I can use the M>V
> button as a
> bandswitch, and scan from A to B.  Worked fine afterwards.  Didn't
> have a P3
> then; this was a simple workaround.
>
> Been using a P3 and bandswitching with the BAND button since, and
> just now
> noticed that the M>V function doesn't pick up the vfo B memory
> setting any
> more when I tried it.
>
> Read the memories with the MemEd; all As and Bs were as I set them;
> resent
> them anyway; still no vfo B pickup.
>
> Have I botched something up?
>
> Brgds,
> Dave, N3HE
>
> --
> View this message in context:
> http://elecraft.365791.n2.nabble.com/K3-memory-
> tp6672414p6672414.html
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> 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
>
> ______________________________________________________________
> 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
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory

Pierfrancesco Caci
In reply to this post by David Windisch
On Wed, 10 Aug 2011 06:44:33 -0700 (PDT)
David Windisch <[hidden email]> wrote:

> In a prior fw version, at least a year ago, using the K3 MemEd, I
> programmed in, eg, vfo A=7000.00  and vfo B=7030.00,  so I can use
> the M>V button as a bandswitch, and scan from A to B.  Worked fine
> afterwards.  Didn't have a P3 then; this was a simple workaround.
>
> Been using a P3 and bandswitching with the BAND button since, and
> just now noticed that the M>V function doesn't pick up the vfo B
> memory setting any more when I tried it.

Is vfoB already on 40 m when you recall the memory? I've noticed that
you need to do M>V, A=B, M>V again to get both VFOs on the same band.

--
Pierfrancesco Caci, ik5pvx <[hidden email]>
______________________________________________________________
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