On Tue, Nov 24, 2009 at 10:04 AM, Barry N1EU <[email protected]> wrote:
>
>
>
> Joe Subich, W4TV-4 wrote:
>>
>>
>>> Whether or not the K3 CAT API has been enhanced to make it
>>> easier to read the split state, Logger isn't supporting it yet.
>>
>> The K3 CAT API makes it extremely easy to tell whether Split
>> is engaged.
>>
> Thanks to Julian and Joe for clarifying where the issue lies. Perhaps if
> someone could lend a K3 to K3CT, he could fully support the K3 in N1MM
> Logger. Unfortunately not all K3's own a K3 ;-)
FWIW, I tried this N1MM Logger feature last night - I hadn't paid
attention to it before. It seems to work fine. I put the K3 into Split
mode with the buttons on the front - not via N1MM Logger, and it was
detected correctly. I didn't run a 48 hour contest with it, but a
quick test seemed to suggest it works well.
The only "gotcha" I noticed is that if you adjust your *RX* frequency
(VFO A) by more than the "tuning tolerance", it will actually knock
you out of Run mode. I think that's a bug - it should not happen that
way when in Split, I think. I'm going to ponder it some more, and
maybe submit a bug report.
~Iain / N6ML
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
