[Elecraft] FW: KE7X KRC2 app note

[Wes Stewart]

Hi Jack,

Thanks for joining in the discussion.

Before proceeding there is one typo that I made below. When I say, "when it is Band5=B6,", it should say "when it is Band6=B6,"

I have read your comments carefully but I am still confused.  First, let me state once again: I have installed (I think, nothing is certain with this thing) the v1.6 (ACC) hex file and the configuration program dutifully reports that the installed version is indeed v1.6.  Nevertheless, I have used the "Hold F4 while powering on" method to set the default configuration.

My confusion with your comments is with the 6-meter case.  My table below is reporting what actually happens with v1.6 firmware and the Band6 configuration changed as noted.  The fact is there can be two different 6-meter responses.  I can't see by looking at any documentation where one of them is a "default."

I would be nice if the manual stated in plain English, something like, "If you connect the KRC-2 to a K3 via the AUXBUS the binary outputs A, B, C, D and the band sink/source outputs will be as shown in Table X, when CONFIG:AUX Band6=B6"  "If CONFIG:AUX Band6=B10 then the respective outputs will be as shown in Table Y."

I will make further comments to your other posting.

Wes

--- On Mon, 7/1/13, Jack Brindle <jackbrindle at me.com> wrote:

> From: Jack Brindle <jackbrindle at me.com>
> Subject: Re: [Elecraft] FW:  KE7X KRC2 app note
> To: "Wes Stewart" <n7ws at yahoo.com>
> Cc: "Elecraft Reflector" <Elecraft at mailman.qth.net>
> Date: Monday, July 1, 2013, 4:38 PM
> Wes;
> 
> The KRC2 is outputting the BCD representation of the band
> that the K3 is reporting to it. So in the 6m case, the KRC2
> asserts the XV1 pin when the K3 indicates 6m on the Auxbus.
> the default, however, is for the K3 to indicate 10m when on
> 6m, which is what the KRC2 faithfully outputs. The Band6
> setting was originally intended as a K2 compatibility mode
> for the KRC2, but is no longer needed with KRC2 V1.6
> firmware.
> 
> In any case, the BCD coding the KRC2 uses is described on
> page 26 of the KRC2 manual.
> 
> jack Brindle, W6FB
> 
> Sent from my iPad
> 
> On Jul 1, 2013, at 11:24 AM, Wes Stewart <n7ws at yahoo.com>
> wrote:
> 
> > I just looked at mine, which at the moment is on the
> AUXBUS.
> > 
> > The outputs are BCD with a twist.
> > 
> > 160m -> BCD = 1
> > 80m  -> BCD = 2
> > 60m  -> BCD = 10
> > 40m  -> BCD = 3
> > 30m  -> BCD = 4
> > 20m  -> BCD = 5
> > 17m  -> BCD = 6
> > 15m  -> BCD = 7
> > 12m  -> BCD = 8
> > 10m  -> BCD = 9
> > 6m   -> BCD = 11 if CONFIG:KRC
> Band6=B6
> > 6m   -> BCD = 9  if CONFIG:KRC
> Band6=B10  Note conflict with 10m.
> > 
> > When Band6=B10, the XV1 output is inactive, when it is
> Band5=B6, the XV1 output is active, which I consider
> "normal."
> > 
> > Also note the "Band6" display is what shows after a tap
> of the "1" key.  It's always unclear to me whether the
> display indicates what's going to happen after the key press
> or the current state of the parameter.  I'm assuming
> the latter.
> > 
> > Wes  N7WS