KE7X KRC2 app note
Locked
 
|
Hello all,
Well, the KE7X KRC2 app note is yet another unfinished project I need to get back on. The KRC2 is a great little decoder box with tremendous flexibility in how you use it but it does require you to carefully study the schematic. Here are some of my more-or-less random observations. I hope to put these into a more cohesive form one of these days (soon). KRC2 Outputs: The KRC2 outputs can be used in high-side driver applications (where the external device needs + voltage) or low-side drivers (where the external device needs a signal pulled to ground). The KRC2 can do both simultaneously. Note that the high-side driver supplies +12 V when asserted but is NOT pulled to ground when it is not asserted. Similarly, the low-side drivers are not pulled up when not asserted. There are 16 high-side and 16 low-side outputs. You can map them anyway you like (even to do a BCD output) but note that the mapping will be the same on the high-side and the low-side. Although there isn't a native BCD coded output, you can make one by using the low-side drivers and supplying the needed pull-up in your external device (which is the way those devices should be designed anyway, but that's another story). Using the AUXBUS: As others have mentioned, the best way to use the KRC2 with the K3 is to use the AUXBUS output on the K3's ACC connector. A caveat is, like the KAT500, the KRC2 must be powered-up before the K3. If it isn't, the K3 will just sit there with a blank screen when you turn it on. That's very scary when it happens to you the first time! The reason that happens is that the KRC2 seems to load the AUXBUS down when it (the KRC2) is not powered-up. I'm not sure I understand why. Bottom line: Turn the KRC2 on first and keep it power-up. Using the Serial Port: Be very careful if you go this route. The problem is that the KRC2 was designed to use the K2's serial port, which if you recall, is a non-standard RS232 interface. If you connect the KRC2 to a standard serial port with the standard RS232 signals RI, CTS, RTS, DSR, and DTR, AND with the KRC2's jumpers W11-W15 connected you could (and probably will) damage the KRC2. Don't ask me how I know that. When jumpers W9, W10 and W22 are installed, the KRC2 can pass K3 serial data on to a PC, for logging or other operating. If you want to do that, the K3's serial data must be 19.2 Kbaud. I haven't played with this mode enough to see how the P3's baud rate fits into the whole scheme. Using the BCD Input: The K3 does put out BCD band data on the ACC jack and this can be used with the KRC2. I don't see problems with this approach other than the known problems associated with the K3's internal pull-ups that limit the loading it can drive on the BCD outputs. I think the KRC2 will work OK but you might not want to have other loads from other decoders on these signals. I have yet to play with this mode. Jack Brindle is a great and friendly resource for questions on the KRC2. I'll get back onto this writing project one of these days as it gets warmer in MT and I take refuge in the coolness of my basement shack. 73 and cheers, Fred KE7X Fred Cady "The Elecraft K3: Design, Configuration and Operation 2nd Edition" "The Elecraft KX3 - Going for the Summit" www.ke7x.com Also available at www.lulu.com (possible discount code JULYBOOKS13) fcady at ieee dot org ______________________________________________________________ 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 |
|
|
Thanks John, that's great information. How is the KRC2 receiving the band data? Via the AUXBUS?
Thanks, Fred (And thanks Ian for: "The manual says (on page 25 of rev C): "The remaining four drivers, labeled A, B, C and D, are TTL-compatible inputs or outputs depending on the operating mode. In normal KRC2 or analog modes, the terminals are outputs. In digital parallel input mode, they become inputs, and receive the BCD-encoded band data." It doesn't specify that the output format is BCD, but I can't imagine what else it would be... 73, ~iain / N6ML " Fred Cady fcady at ieee dot org From: John D'Ausilio [mailto:[hidden email]] Sent: Monday, July 01, 2013 8:42 AM To: Cady, Fred Subject: Re: [Elecraft] KE7X KRC2 app note Hi Fred .. I beg to differ with you re: BCD outputs from ABCD terminals. Absent any overriding configuration (like analog inputs), the ABCD terminals do in fact output BCD band info. I know this because I've been using those outputs to drive my microwave LO synthesizer for the last 4 years :) de w1rt/john On Mon, Jul 1, 2013 at 9:24 AM, Cady, Fred <[hidden email]<mailto:[hidden email]>> wrote: Hello all, Well, the KE7X KRC2 app note is yet another unfinished project I need to get back on. The KRC2 is a great little decoder box with tremendous flexibility in how you use it but it does require you to carefully study the schematic. Here are some of my more-or-less random observations. I hope to put these into a more cohesive form one of these days (soon). KRC2 Outputs: The KRC2 outputs can be used in high-side driver applications (where the external device needs + voltage) or low-side drivers (where the external device needs a signal pulled to ground). The KRC2 can do both simultaneously. Note that the high-side driver supplies +12 V when asserted but is NOT pulled to ground when it is not asserted. Similarly, the low-side drivers are not pulled up when not asserted. There are 16 high-side and 16 low-side outputs. You can map them anyway you like (even to do a BCD output) but note that the mapping will be the same on the high-side and the low-side. Although there isn't a native BCD coded output, you can make one by using the low-side drivers and supplying the needed pull-up in your external device (which is the way those devices should be designed anyway, but that's another story). Using the AUXBUS: As others have mentioned, the best way to use the KRC2 with the K3 is to use the AUXBUS output on the K3's ACC connector. A caveat is, like the KAT500, the KRC2 must be powered-up before the K3. If it isn't, the K3 will just sit there with a blank screen when you turn it on. That's very scary when it happens to you the first time! The reason that happens is that the KRC2 seems to load the AUXBUS down when it (the KRC2) is not powered-up. I'm not sure I understand why. Bottom line: Turn the KRC2 on first and keep it power-up. Using the Serial Port: Be very careful if you go this route. The problem is that the KRC2 was designed to use the K2's serial port, which if you recall, is a non-standard RS232 interface. If you connect the KRC2 to a standard serial port with the standard RS232 signals RI, CTS, RTS, DSR, and DTR, AND with the KRC2's jumpers W11-W15 connected you could (and probably will) damage the KRC2. Don't ask me how I know that. When jumpers W9, W10 and W22 are installed, the KRC2 can pass K3 serial data on to a PC, for logging or other operating. If you want to do that, the K3's serial data must be 19.2 Kbaud. I haven't played with this mode enough to see how the P3's baud rate fits into the whole scheme. Using the BCD Input: The K3 does put out BCD band data on the ACC jack and this can be used with the KRC2. I don't see problems with this approach other than the known problems associated with the K3's internal pull-ups that limit the loading it can drive on the BCD outputs. I think the KRC2 will work OK but you might not want to have other loads from other decoders on these signals. I have yet to play with this mode. Jack Brindle is a great and friendly resource for questions on the KRC2. I'll get back onto this writing project one of these days as it gets warmer in MT and I take refuge in the coolness of my basement shack. 73 and cheers, Fred KE7X Fred Cady "The Elecraft K3: Design, Configuration and Operation 2nd Edition" "The Elecraft KX3 - Going for the Summit" www.ke7x.com<http://www.ke7x.com> Also available at www.lulu.com<http://www.lulu.com> (possible discount code JULYBOOKS13) fcady at ieee dot org ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email]<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 |
|
|
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 --- On Mon, 7/1/13, Cady, Fred <[hidden email]> wrote: > From: Cady, Fred <[hidden email]> > Subject: [Elecraft] FW: KE7X KRC2 app note > To: "'Elecraft Reflector'" <[hidden email]> > Date: Monday, July 1, 2013, 11:12 AM > Thanks John, that's great > information. How is the KRC2 receiving the band data? Via > the AUXBUS? > Thanks, > Fred > > (And thanks Ian for: > > "The manual says (on page 25 of rev C): > > > > "The remaining four drivers, labeled A, B, C and D, are > TTL-compatible > > inputs or outputs depending on the operating mode. In normal > KRC2 or > > analog modes, the terminals are outputs. In digital parallel > input > > mode, they become inputs, and receive the BCD-encoded band > data." > > > > It doesn't specify that the output format is BCD, but I > can't imagine > > what else it would be... > > > > 73, > > > > ~iain / N6ML > " > > > > Fred Cady > fcady at ieee dot org > From: John D'Ausilio [mailto:[hidden email]] > Sent: Monday, July 01, 2013 8:42 AM > To: Cady, Fred > Subject: Re: [Elecraft] KE7X KRC2 app note > > Hi Fred .. I beg to differ with you re: BCD outputs from > ABCD terminals. Absent any overriding configuration (like > analog inputs), the ABCD terminals do in fact output BCD > band info. I know this because I've been using those outputs > to drive my microwave LO synthesizer for the last 4 years > :) > > de w1rt/john > > On Mon, Jul 1, 2013 at 9:24 AM, Cady, Fred <[hidden email]<mailto:[hidden email]>> > wrote: > Hello all, > Well, the KE7X KRC2 app note is yet another unfinished > project I need to get back on. > > The KRC2 is a great little decoder box with tremendous > flexibility in how you use it but it does require you to > carefully study the schematic. Here are some of my > more-or-less random observations. I hope to put these into a > more cohesive form one of these days (soon). > > KRC2 Outputs: > The KRC2 outputs can be used in high-side driver > applications (where the external device needs + voltage) or > low-side drivers (where the external device needs a signal > pulled to ground). The KRC2 can do both simultaneously. Note > that the high-side driver supplies +12 V when asserted but > is NOT pulled to ground when it is not asserted. Similarly, > the low-side drivers are not pulled up when not asserted. > > There are 16 high-side and 16 low-side outputs. You can map > them anyway you like (even to do a BCD output) but note that > the mapping will be the same on the high-side and the > low-side. > > Although there isn't a native BCD coded output, you can make > one by using the low-side drivers and supplying the needed > pull-up in your external device (which is the way those > devices should be designed anyway, but that's another > story). > > Using the AUXBUS: > As others have mentioned, the best way to use the KRC2 with > the K3 is to use the AUXBUS output on the K3's ACC > connector. A caveat is, like the KAT500, the KRC2 must be > powered-up before the K3. If it isn't, the K3 will just sit > there with a blank screen when you turn it on. That's very > scary when it happens to you the first time! The reason that > happens is that the KRC2 seems to load the AUXBUS down when > it (the KRC2) is not powered-up. I'm not sure I understand > why. Bottom line: Turn the KRC2 on first and keep it > power-up. > > Using the Serial Port: > Be very careful if you go this route. The problem is that > the KRC2 was designed to use the K2's serial port, which if > you recall, is a non-standard RS232 interface. If you > connect the KRC2 to a standard serial port with the standard > RS232 signals RI, CTS, RTS, DSR, and DTR, AND with the > KRC2's jumpers W11-W15 connected you could (and probably > will) damage the KRC2. Don't ask me how I know that. When > jumpers W9, W10 and W22 are installed, the KRC2 can pass K3 > serial data on to a PC, for logging or other operating. If > you want to do that, the K3's serial data must be 19.2 > Kbaud. I haven't played with this mode enough to see how the > P3's baud rate fits into the whole scheme. > > Using the BCD Input: > The K3 does put out BCD band data on the ACC jack and this > can be used with the KRC2. I don't see problems with this > approach other than the known problems associated with the > K3's internal pull-ups that limit the loading it can drive > on the BCD outputs. I think the KRC2 will work OK but you > might not want to have other loads from other decoders on > these signals. I have yet to play with this mode. > > Jack Brindle is a great and friendly resource for questions > on the KRC2. > > I'll get back onto this writing project one of these days as > it gets warmer in MT and I take refuge in the coolness of my > basement shack. > > 73 and cheers, > Fred KE7X > > > > Fred Cady > "The Elecraft K3: Design, Configuration and Operation 2nd > Edition" > "The Elecraft KX3 - Going for the Summit" > www.ke7x.com<http://www.ke7x.com> > Also available at www.lulu.com<http://www.lulu.com> (possible discount code > JULYBOOKS13) > > fcady at ieee dot org > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email]<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 |
|
|
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 <[hidden email]> 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 > > > --- On Mon, 7/1/13, Cady, Fred <[hidden email]> wrote: > >> From: Cady, Fred <[hidden email]> >> Subject: [Elecraft] FW: KE7X KRC2 app note >> To: "'Elecraft Reflector'" <[hidden email]> >> Date: Monday, July 1, 2013, 11:12 AM >> Thanks John, that's great >> information. How is the KRC2 receiving the band data? Via >> the AUXBUS? >> Thanks, >> Fred >> >> (And thanks Ian for: >> >> "The manual says (on page 25 of rev C): >> >> >> >> "The remaining four drivers, labeled A, B, C and D, are >> TTL-compatible >> >> inputs or outputs depending on the operating mode. In normal >> KRC2 or >> >> analog modes, the terminals are outputs. In digital parallel >> input >> >> mode, they become inputs, and receive the BCD-encoded band >> data." >> >> >> >> It doesn't specify that the output format is BCD, but I >> can't imagine >> >> what else it would be... >> >> >> >> 73, >> >> >> >> ~iain / N6ML >> " >> >> >> >> Fred Cady >> fcady at ieee dot org >> From: John D'Ausilio [mailto:[hidden email]] >> Sent: Monday, July 01, 2013 8:42 AM >> To: Cady, Fred >> Subject: Re: [Elecraft] KE7X KRC2 app note >> >> Hi Fred .. I beg to differ with you re: BCD outputs from >> ABCD terminals. Absent any overriding configuration (like >> analog inputs), the ABCD terminals do in fact output BCD >> band info. I know this because I've been using those outputs >> to drive my microwave LO synthesizer for the last 4 years >> :) >> >> de w1rt/john >> >> On Mon, Jul 1, 2013 at 9:24 AM, Cady, Fred <[hidden email]<mailto:[hidden email]>> >> wrote: >> Hello all, >> Well, the KE7X KRC2 app note is yet another unfinished >> project I need to get back on. >> >> The KRC2 is a great little decoder box with tremendous >> flexibility in how you use it but it does require you to >> carefully study the schematic. Here are some of my >> more-or-less random observations. I hope to put these into a >> more cohesive form one of these days (soon). >> >> KRC2 Outputs: >> The KRC2 outputs can be used in high-side driver >> applications (where the external device needs + voltage) or >> low-side drivers (where the external device needs a signal >> pulled to ground). The KRC2 can do both simultaneously. Note >> that the high-side driver supplies +12 V when asserted but >> is NOT pulled to ground when it is not asserted. Similarly, >> the low-side drivers are not pulled up when not asserted. >> >> There are 16 high-side and 16 low-side outputs. You can map >> them anyway you like (even to do a BCD output) but note that >> the mapping will be the same on the high-side and the >> low-side. >> >> Although there isn't a native BCD coded output, you can make >> one by using the low-side drivers and supplying the needed >> pull-up in your external device (which is the way those >> devices should be designed anyway, but that's another >> story). >> >> Using the AUXBUS: >> As others have mentioned, the best way to use the KRC2 with >> the K3 is to use the AUXBUS output on the K3's ACC >> connector. A caveat is, like the KAT500, the KRC2 must be >> powered-up before the K3. If it isn't, the K3 will just sit >> there with a blank screen when you turn it on. That's very >> scary when it happens to you the first time! The reason that >> happens is that the KRC2 seems to load the AUXBUS down when >> it (the KRC2) is not powered-up. I'm not sure I understand >> why. Bottom line: Turn the KRC2 on first and keep it >> power-up. >> >> Using the Serial Port: >> Be very careful if you go this route. The problem is that >> the KRC2 was designed to use the K2's serial port, which if >> you recall, is a non-standard RS232 interface. If you >> connect the KRC2 to a standard serial port with the standard >> RS232 signals RI, CTS, RTS, DSR, and DTR, AND with the >> KRC2's jumpers W11-W15 connected you could (and probably >> will) damage the KRC2. Don't ask me how I know that. When >> jumpers W9, W10 and W22 are installed, the KRC2 can pass K3 >> serial data on to a PC, for logging or other operating. If >> you want to do that, the K3's serial data must be 19.2 >> Kbaud. I haven't played with this mode enough to see how the >> P3's baud rate fits into the whole scheme. >> >> Using the BCD Input: >> The K3 does put out BCD band data on the ACC jack and this >> can be used with the KRC2. I don't see problems with this >> approach other than the known problems associated with the >> K3's internal pull-ups that limit the loading it can drive >> on the BCD outputs. I think the KRC2 will work OK but you >> might not want to have other loads from other decoders on >> these signals. I have yet to play with this mode. >> >> Jack Brindle is a great and friendly resource for questions >> on the KRC2. >> >> I'll get back onto this writing project one of these days as >> it gets warmer in MT and I take refuge in the coolness of my >> basement shack. >> >> 73 and cheers, >> Fred KE7X >> >> >> >> Fred Cady >> "The Elecraft K3: Design, Configuration and Operation 2nd >> Edition" >> "The Elecraft KX3 - Going for the Summit" >> www.ke7x.com<http://www.ke7x.com> >> Also available at www.lulu.com<http://www.lulu.com> (possible discount code >> JULYBOOKS13) >> >> fcady at ieee dot org >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email]<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 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 |
|
|
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 <[hidden email]> wrote: > From: Jack Brindle <[hidden email]> > Subject: Re: [Elecraft] FW: KE7X KRC2 app note > To: "Wes Stewart" <[hidden email]> > Cc: "Elecraft Reflector" <[hidden email]> > 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 <[hidden email]> > 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 ______________________________________________________________ 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 |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |