gt; Sent: Wednesday, November 25, 2009 2:18 AM
>> To: Barry N1EU
>> Cc: elecraft@mailman.qth.net
>> Subject: Re: [Elecraft] [K3] K3 in SS SSB
>>
>>
>> On Tue, Nov 24, 2009 at 12:54 PM, Barry N1EU
>> wrote:
>> > On Tue, Nov 24, 2009 at 6:12 PM, Iain MacDonnell
an.qth.net
> [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Iain
> MacDonnell - N6ML
> Sent: Wednesday, November 25, 2009 2:18 AM
> To: Barry N1EU
> Cc: elecraft@mailman.qth.net
> Subject: Re: [Elecraft] [K3] K3 in SS SSB
>
>
> On Tue, Nov 24, 2009 at 12:54 PM, B
On Tue, Nov 24, 2009 at 12:54 PM, Barry N1EU wrote:
> On Tue, Nov 24, 2009 at 6:12 PM, Iain MacDonnell - N6ML
> 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.
>>
>> FWIW, I tried this N1MM Lo
For the UNDO macro use FR0; to turn split off.
Name-Big Knob RIT On
SWT13;SWT13;FT1;LK$1;RT0;XT0;
Big Knob RIT off
SWT13;SWT13;FR0;LK$0;RT0;XT0;
- Original Message -
From: "Greg - AB7R"
To: "Barry N1EU"
Cc:
Sent: Tuesday, November 24, 2009 2:33 PM
Subject: Re: [
>At least up until now, the N1MM programmers reported that they couldn't
>really figure out whether the K3 was in split or not - I guess it's a CAT
>API software issue. So unless you religiously used alt-F7 to turn the K3
>split on/off, Logger would lose track of the split state. I know that the
Tried calling back.
BTW...if you want to do this, program your B>A FUNCTION in CONFIG to the PF1
key. Then
in the MM "TU" macro use {CAT1ASC K31;SWH45;} at the end. This will exectue
the PF1
key and set the VFO B freq back to VFO A.
Macro to set up using VFO A as RIT for Split:
This macro
On Tue, Nov 24, 2009 at 6:12 PM, Iain MacDonnell - N6ML 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.
>
> FWIW, I tried this N1MM Logger feature last night - I hadn't paid
> attention to it before
On Tue, Nov 24, 2009 at 10:04 AM, Barry N1EU 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 en
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 th
-Original Message-
> From: elecraft-boun...@mailman.qth.net
> [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Barry N1EU
> Sent: Tuesday, November 24, 2009 7:50 AM
> To: elecraft@mailman.qth.net
> Subject: Re: [Elecraft] [K3] K3 in SS SSB
>
>
>
>
>
>
Barry N1EU wrote:
>
>
> At least up until now, the N1MM programmers reported that they couldn't
> really figure out whether the K3 was in split or not - I guess it's a CAT
> API software issue.
>
Sorry, that's nonsense. The K3 has reports SPLIT status in the
auto-information messages and alwa
Randy Farmer wrote:
>
> In the "Tools" menu dropdown from the main logging window, tick the
> box that says "Reset Rx freq when running split". This doesn't appear
> to be "sticky"; you'll have to select it each time you start the
> program. Works great.
>
Works not so great with the K3, IM
12 matches
Mail list logo
