Hi,
Now we are cooking. I am glad you found the real problem. There is virtually
0 probability that reloading the same firmware will fix anything. There is
no such thing as a "busted firmware load" except the kind that leaves the
"CPU load" or similar message indicating that the bootloader firmwar
I called the Elecraft to get some help with this. After removing the K3
out of line, removed computer control, amps, tuner etc. The problem was
gone.
I was running radio control with my logging software. I found a tab
where that software was sending the odd FC offsets.
Just like computers,
Busted firmware load will make anything sick, including me.
73, Guy K2AV
On Thu, Nov 10, 2016 at 9:03 PM, W0MU Mike Fatchett wrote:
> I think I have solved this. I sent all the firmware to the radio again
> and the radio is behaving like my other K3.
>
>
> On 11/9/2016 8:31 PM, W0MU Mike Fatch
I think I have solved this. I sent all the firmware to the radio again
and the radio is behaving like my other K3.
On 11/9/2016 8:31 PM, W0MU Mike Fatchett wrote:
I am having issues with my K3. When I change bands and modes the FC
setting is not the default or * setting. I keep picking norm
On Wed, Nov 9, 2016 at 11:20 PM, Don Wilhelm wrote:
> The passband is per mode, per mode.
That would be "The passband is per band, per mode." ?
G.
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: h
Mike,
The passband is per mode, per mode.
You will have better results if you use HiCut/LoCut for SSB and
SHIFT/WIDTH for CW.
Attempting to us SHIFT/WIDTH for SSB will give you uncertain results
since the last used settings on a particular band will be restored when
you go back to that band.
I am having issues with my K3. When I change bands and modes the FC
setting is not the default or * setting. I keep picking normal and then
when I change bands it reverts back to some setting that sounds terrible.
This rig was just at Elecraft for updates. I have looked for settings
for thi
7 matches
Mail list logo
