[LOGic] Bug when running K3

[Allen R. Brier]

I use the Kenwood TS-850 driver for my K3. I have a lot of issues with it
and will list them in a future post. 

The problems with K3 won't get fixed until Dennis writes a new K3 driver. I
have been hoping he would do it for a long time now.

Allen N5XZ 



Message: 2
Date: Mon, 31 Oct 2011 11:25:26 -0000
From: "Bill VanAlstyne W5WVO" <w5wvo at cybermesa.net>
Subject: [LOGic] Bug when running K3 -- HELP!
To: <logic at mailman.qth.net>
Message-ID: <AF81E5A709C34521B37CE119A0DD98F4 at BILLHP9250>
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original

I?m running a barefoot K3, SN #888, with the latest firmware (BETA 4.42) but
no 2nd receiver (yet) or panadapter (yet). I?m using the Elecraft K2 rig
interface, since there isn?t one for the K3 in LOGic8.

I recently (six months) started working DX on HF CW with my K3. As you know,
most CW DX stations, especially DXpeditions, work SPLIT.

There a couple different ways of handing SPLIT on the K3. The first method I
tried, using the XIT/RIT, worked OK ? I would tune in the DX station, then
apply RIT and find the pile-up, then turn on XIT and turn off RIT. This all
works fine.

However, there is a more conventional single-receiver mode, and one which I
would like to adopt. This is to go to SPLIT mode (XIT/RIT OFF). tune in the
station on VFO A, lock it in, and find the pileup on VFO B. Once in the
chase, you can simply press and hold the REV button to force receive from
VFO B. The VFO knob can be tuned while the REV button is held in.

A better way, and one which I intend to go to one of these days, is to get
the K3?s 2nd receiver so I can listen to both the DX station and the pileup
at the same time, independently. But that will have to wait for the arrival
of more discretionary funding.

With regard to the REV mode: Whenever I hold it in to tune around the
pileup, LOGic8 gives me a message dialog all the wile while my finger is
holding it in REV mode. These are 1-off messages, I would guess at least one
per second. This doesn?t affect operation, but it fills the screen with a
stack of these unnecessary messages, which I then have to delete one at a
time.

Has anyone seen this? Better yet, solved it?

Bill W5WVO



------------------------------

_______________________________________________
LOGic mailing list
LOGic at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/logic


End of LOGic Digest, Vol 90, Issue 15
*************************************