[Elecraft] K3 jumps band when mode is changed - K144XV

[jpk5lad at cox.net]

This message is just to describe a problem I had with the new 
K144XV transverter and my K3.  The problem has been solved 
and solution given at the end but this is just for the archives to 
help if someone later runs into a problem like this.
-----------------------------------------------------------------------------

My newly installed K144XV transverter created an interesting 
problem.  Any time I tried to switch to 2 meter frequencies or, 
when I finally reached the 2 meter frequencies and tried to 
change mode, the K3 would quickly switch back to the 6 meter 
band with a displayed frequency -  54.000.  I also tried to use 
Ham Radio Deluxe to change bands and modes and my K3 
reacted exactly the same way.  It was as though I could not 
deliberately change modes on 2 meters.  I wrote Gary in Support 
and received the following email.

Jim,
    
    I am afraid don't understand what you mean. Could you provide 
some more detail?
    
    I tried HRD too, and did not see any problems. Perhaps I did 
not do the same things you did?
    
    I assume you did get all of the XV1 menus setup correctly, and 
you are using the latest firmware version 3.77 / 2.53?
    
73, Gary AB7MY
==================================================
support at elecraft.com
Elecraft Technical Support  
  
On 3/16/2010 2:44 PM, jpk5lad at cox.net wrote: 
    
OK Gary --
    Yes, I've set up the menus correctly as per the instructions.  
    
    I am also running the correct firmware (see attached 
screenprint)
    
Let me identify each step and how it reacts:
    1. OK, I have the K3 sitting on 50.125 USB.
    2. I press the BAND switch once on the right and it switches to 
  	2 meters but within a second it switches back and still
	shows 50.125.  I didn't get a chance to see the 2 meter
	setting before it changed back.
    3. I press BAND switch again once on the right and it goes to 
	144.200 CW.
    4. I press MODE switch on the right to go to USB and K3
	switches (within a half second) to 54.0000 USB.
    5. I press BAND switch again once on the right and it goes to
	144.200 USB.
    6. I press FREQ ENT and punch in 146700 since I have a
	repeater on that frequency at my house.  I press  the 
	AFX <-- and the K3 shows 146.7000 USB.
    7. I press MODE switch on the right once to go to FM and
	within a second the K3 has switched to show 54.00000 FM.
    8.  I press BAND switch again once on the right and K3 goes 
	to 146.700.00 FM.
    9,  Now I enter 144200 via the FREQ END and AFX <-- route
	and the K3 switches to 144.200.00 FM.
    10. I press MODE switch on the right once trying to change it 
	to USB.  It changes mode to AM and within a second the 
	K3 switches to 54.000.0 AM 
    11. By going back and forth multiple times on the BAND and
	MODE switches I can finally get the K3 to read 144.200.0 
		USB but between every band or mode switch press, it
	reverts back to 54.000.00.
    
    I hope this is an adequate description of what's happening but 
if not, ask again and I'll try some more.
    
Thanks and 73,
Jim - K5LAD
    
    
The HRD reaction is basically the same thing, i.e., instruct it in 
HRD and it jumps to the instruction, then within a second it jumps 
back to 54.00000
-------------------------------------------------------------------------
Gary wrote back suggesting:

That doesn't happen here.
Do you have the BND MAP menu set so the 2m band is OUT?
Also try pressing the A>B button twice to copy the VFO A info to 
VFO B, 
in case it is corrupted. Do this on both 6m and 2m once you get 
VFO A set to a freq. and mode in the band that you want.
-------------------------------------------------------------------------
support at elecraft.com
Elecraft Technical Support  

On 3/16/2010 3:30 PM, jpk5lad at cox.net wrote:
Nope, The BND MAP showed 2M, as well as all the others, as IN.

I tried the A>B trick but it's still doing the same crazy things.

Anywho, it's still acting crazy.

73, Jim - K5LAD
-------------------------------------------------------------------------
Jim,

If you can't figure out why it is doing that, and a reload of the 
latest firmware doesn't help, it might be worth the trouble to do an 
EEINIT and then redo all of the calibrations and setups.

It's the end of the day here, so please email Wayne 
(n6kr at elecraft.com) or the k3 support address below if you need 
some help while I am away.

Good luck! :-)
-------------------------------------------------------------------------
Gary and Wayne --

That did it!  I reloaded the current firmware and the problem has 
cleared.  In the back of my skull, I'm thinking that I might have 
been doing something else on my computer while I originally 
uploaded the v 2.77 firmware and it, perhaps, messed something 
up.  Anyway, I did not need to do an EEINIT but the reloading of 
the firmware did the trick.

Thanks for all the help and 73,
Jim - K5LAD

BTW - I think I will summarize this and send it to the reflector so it
will be in the archives in case someone else has the same type 
problem.


--------------------
I hope this can help someone else who has the same type of 
problem.  




===============================
Life is like a football ---
It ain't round ... It'll bounce funny on ya.

http://www.hayseed.net/~jpk5lad/