Another small issue I have had is when I am on say 3710 KHz LSB
and send the macro FA00007050000;MD3;
the K3s goes to 7049.280 KHz CW sometimes. (720 Hz is my offset for CW)
If I send FA00007050000;MD3; again right away
it goes to 7050 KHz CW

Then when I send FA00003710000;MD1;
the K3s goes to 3710.720 KHz LSB sometimes
Again, if I send FA00003710000;MD1; again right away
the K3s goes to 3710 KHz LSB.

This has always been the case and has nothing to do with the wrong macro being 
sent...
am I not allowing for something in my macros?

Chuck Hawley
 [email protected]

 Amateur Radio, KE9UW


________________________________
From: Charles J. Hawley <[email protected]>
Sent: Wednesday, September 16, 2020 12:30 PM
To: [email protected] <[email protected]>
Subject: K-POD Issues, But I Love It!

I love this K-Pod, BUT I’ve sort of worn out 3 of them. The symptom is that the 
most used buttons get noisy and trigger another macro from another address. 
When I had the first one do that, I did extensive testing to eliminate rf 
noise, etc.
And a new unit however proved to work perfectly...for about 4 months. When it 
started doing the same thing Elecraft said it was highly unlikely and 
especially twice to the same guy, but they sent me another one anyway. Great 
company!
Now that one after a year is doing it again. I rearranged the macros to 
different buttons of the two macros I mostly use, and it works flawlessly again 
for those two. I doubt that Elecraft will keep sending me these things, maybe 
I’m missing something. But all I can come up with is noisy switches, double 
triggering. Anybody have similar issues?

Jack BMW Motorcycles
Chuck KE9UW
[email protected]

Sent from my iPad
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected] 

Reply via email to