[KRC2]
Locked
 
|
----- Original Message -----
From: [hidden email]
To: [hidden email]
Sent: Thursday, January 22, 2009 5:02 PM
Subject: [K3][KRC2] Greetings all;
I've been trying to get my KRC2 to function
properly with the
K3, but it's an uphill battle. It does not
appear to be willing
to talk to the PC, and does not update band
selection when
connected to the K3. Is there anyone who is
successfully
using this setup that could spare a few moments to
compare
notes on how to set up the KRC2 and what to expect
for
functionality. The documentation is woefully
sparse on this
subject with respect to the
K3.
TIA,
Van W1WCG
_______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
> I've been trying to get my KRC2 to function properly with the
> K3, but it's an uphill battle. It does not appear to be willing > to talk to the PC, and does not update band selection when > connected to the K3. Is there anyone who is successfully > using this setup that could spare a few moments to compare > notes on how to set up the KRC2 and what to expect for > functionality. The documentation is woefully sparse on this > subject with respect to the K3. I've been using the KRC2 with my K3s for 18 months now. I don't have the manual here right now, but I thought the latest version does give the configuration for the K3. If not, just follow the K2 configuration for the AUXBUS connection. Ed - W0YK _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
Yes.
Use the auxbus connection rather than RS232. You can also use the band out lines with pull ups. If you have a transverter, do not loop the signals besides auxbus through the KRC2. The KRC2 loads the "K3 on" and "Key" signals too much. The KRC2 does not understand 6m, at least my version with the accessibility firmware does not. 6m will appear as an undefined band, which happens to correspond to 160m. I am sure Elecraft are working on new KRC2 firmware. Mike |
|
|
I have just noticed the new firmware is now available for download. Version 1.5. The KRC2 can now map 6m to 60m or 10m. This effectively means you have a choice of which HF band to work as 6m. To select this you need to use an invisible feature in the menu for the KRC2 on the K3. Press Button 1 (A/B, 1, B.SET) on the K3 to toggle 6m being mapped to 10m or 60m. Update - I updated my firmware from 1.3 to 1.5 and needless to say, this facility still does not actually work. 6m is NOT mapped to 60m even though it is set to be in the K3 menus. What exactly is this from the K3 manual supposed to mean? "To ensure compatibility with both old and new KRC2 firmware, two different 6 meter band decodes are provided. Tap 1 to select BAND6=B6 (addr=10) or BAND6=B10 (addr=9). Refer to the KRC2 manual for further details." There is no such thing as B6 or B10 in any manual I could find. Are the addresses in HEX or Decimal? Presumably decimal as there is no address 10(Hex) in the KRC2 band map. Below is the only data available in the KRC2 manual, Table 6. The KRC2 manual text refers to Table 5 which does not appear to be relevant. Binary coding Hex Band Binary coding Hex BAND 0001 01 160m 1000 08 12m 0010 02 80m 1001 09 10m 0011 03 40m 1010 0A 60m 0100 04 30m 1011 0B unused 0101 05 20m 1100 0C XVT1 0110 06 17m 1101 0D XVT2 0111 07 15m 1110 0E XVT3 This implies that 6m should if set in the K3 to B6, select the 60m output. It does not do this. I should say the KRC2 band mapping is set to one to one, i.e not remapped via the firmware. |
|
|
While the use of the AuxBus connection is preferred for K3-KRC2 communications, it does not carry information needed by the KRC2ACC to announce radio status. For this the KRC2 needs to be connected to the radio using the serial port. To get full functionality from the KRC2ACC here, which include radio change CW announcements, band switching and ACC control from the radio, both serial port and AuxBus need to be connected. And don't forget that the serial port needs to be running at 4800 baud for all KRC2/KRC2ACC firmware versions prior to V1.5.
The V1.5 firmware adds recognition of 6 meters from the K3, and new microcontrollers from the factory have the bandmaps set to output the 6m selection on the XV1 pins. Users upgrading from earlier firmware versions will need to use the configuration tool to remap their bandmaps to enable this selection. Unfortunately there appears to be a problem with the KRC2 configuration tool communicating with the KRC2 which currently prohibits this. We are investigating the problem and potential fixes. Anyone contemplating use of the KRC2 or KRC2ACC with their K3 should download and read the KRC2 manual, revision C from the Elecraft website, Manuals & Downloads page. It has a revised section on connecting the KRC2 with various radios including the K3. Jack Brindle, W6FB Elecraft KRC2 Engineering On Jan 23, 2009, at 1:53 AM, AD6XY wrote:
- Jack Brindle, W6FB --------------------------------------------------------------------------------------------- _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
«
Return to [K3]
|
1 view|%1 views
| Free forum by Nabble | Edit this page |