[Elecraft] Questions on the KRC2 - part 3

[Jack Brindle]

> 14.  Will the buttons on the unit be able to detect tap as well as 
> hold?

Yes! In fact, there are 24 separate events that can be generated from 
the pushbutton switches. The action of a button hold is configurable, 
so that it may either trigger an event and thus an action, or it may be 
set up to cause a "shift" function, where the next key press determines 
the actual event. Again, the dem units provide an example. Holding the 
F4 key causes a "shift-4" condition. The next key pressed (1-4) will 
trigger an event (in this case a Switch17-Switch20 event) which will be 
interpreted by the command table. This is where we actually play with 
the local ACC settings in the demo, turning the ACC drivers on and off 
for the F1-F4 buttons.

> 15.  Could the switches be remotely mounted so the box could be located
> away from the operating position?  Important when running mobile.

The box could certainly be remotely mounted. The main limitation when 
used with the K2 is the length of the interconnect cable, which needs 
to be short due to the constraints of the AuxBus. Having said this, it 
would also be possible (although not in the current firmware, YET) to 
receive the band changes through the RS-232 serial port and not need 
the AuxBus. This is the way the KRC2 will work when used with a Kenwood 
radio. You lose the ACC and Transverter information coming from the K2, 
and there will be a very slight delay for the radio to output the new 
frequency/band information, but there is no reason it wouldn't work.

> 16.  How much of the internal state of the K2 can it detect?  Such as
> the real time clock?

Real-time clock information from the KAF2 and KDSP2 is not currently 
received and processed by the KRC2. Indeed the only AuxBus information 
we currently handle are the band, transverter and accessory messages. 
The KRC2 _does_ have an internal timer system which may be used to 
periodically trigger events. One example of their use would be to send 
a ten-minute CW identification. This example would require two command 
entries, one which initializes a timer for the period (ten minutes) and 
to run, and the second which picks up the timer event, switches the 
radio to CW mode (if not there already), sends the CW ID, and finally 
returns the K2 to whatever the previous operating mode was. The timers 
can be set to automatically repeat their actions by the user.

The KRC2 keeps track of the parameters the K2 puts out through the 
serial port, then compares later updates of these parameters to 
determine changes and thus create events. So, an event such as a VFOA 
Frequency change is caused by the KRC2 receiving two updates of the 
VFOA frequency which are not the same. It can also read the K2's 
display and bar graph information, note that something has changed, and 
create an event for you to announce the information. Much of this 
capability was designed for the accessibility functions of the box, but 
if it may be useful to others.

I am sure the complete manual will be very useful in determining a lot 
of what you can do with the KRC2. It is in the works and should be 
available in the near future. To paraphrase Orson Wells, "We shall 
release no kit before it's time..." He was referring to some great 
California wine, of course, but the idea counts. ;-)

> To see what I'm talking about as far as my mobile setup, check out:
>
> http://home.attbi.com/~thompsj/wsb/html/view.cgi-home.html-.html

Impressive picts! I suspect you will be able to do quite a bit with the 
KRC2 in your mobile station, including some things we haven't thought 
of previously. Suggestions are very welcome, and may be incorporated in 
future versions of the firmware. I look forward to a dialog with you 
and others on various ways to improve and enhance our cool little 
control box!


-Jack Brindle, WA4FIB
=======================================================================
MacDobs - helping to shift the paradigm for low-cost amateur astronomy.