Quote:The new K3 driver is more functional but does the same thing as the non-legacy Kenwood driver - it times out to all zeroes on frequency after awhile. Any click on the driver buttons or movement of the main dial on the K3 itself will reset the frequency ... for awhile.
This is really sounding like a rig problem. With the K3, most Kenwoods, and Icoms, LOGic just sits there and waits for the data to be sent, and updates the display accordingly. It does not continuously poll as with the Yaesu line.
HOWEVER, LOGic does poll the K3 and the like when it NEEDS the frequency for something -- like logging a QSO. USUALLY when the frequency goes to zero, it is after LOGic requests the frequency. In this scenario, LOGic will time out and disconnect from the rig. You have to do TOOLS/RESET RADIO & ROTOR INTERFACES to bring things back to life.
But as you describe it, the rig is apparently sending zeros to LOGic. I say this because you say once you turn the dial, it sends the correct frequency again. LOGic hasn't actually timed out. If it didn, you would have to RESET.
Next time it happens, try logging a QSO and see if the correct frequency is read.
I guess it is possible that LOGic is somehow blanking the display on its own. Is it just sitting there and goes to zero, or is there some action that causes this? I can test on my icom I suppose. The frequency display is the same for all rigs.
Quote:Clicking on a 6m phone spot put in into CW REV.
Ok, does it do this just for 6M, or any CW spot? What about setting it from the log? The CW button?
Tnx & 73,
DH