[Elecraft] K2 SPLIT AND DX CLUSTER SPOTS WITH LOGGER 32 & N1MM
Chris Page
g4bue at adur-press.co.uk
Mon Mar 13 11:24:28 EST 2006
Thanks to Don, Dan and Rich for their explanations of this problem.
Whilst noting what Don says about Logger 32 not sending the TX and RX
information for each of the K2's VFOs, and that being the reason it
will not work effectively, it cannot be the reason why it won't work
with N1MM. N1MM does send the TX and RX frequency information for
each VFO, at least whenever the spot on the DX Cluster contains a TX
and RX frequency, ie split operation on 40 and 80 metres CW.
N1MM does not have a Radio Debug window like Logger 32 and so I am
unable to see what the actual command that is sent by N1MM to the K2.
By the way Rich, what logging program are you using? It will be nice
to know of one that doesn't cancel the split option on the K2.
73 de Chris, G4BUE
On 13 Mar 2006 at 8:54, Don Wilhelm wrote:
> Chris,
>
> The K2 is operating properly - apparently Logger 32 programmers wanted
> Split to be cancelled or they would not have sent that string of
> commands. The KIO2 Programmers Reference clearly indicates that the
> 'FR' command always cancels Split mode.
>
> To work effectively with a program in Split mode, the program must be
> aware of which VFO you are using for transmit and which for receive.
> My guess is that Logger 32 did not want to deal with that potential
> for confusion because the transmit VFO can be quickly changed by a tap
> of the front panel button or by a KIO2 command - many things could
> easily get mixed up.
>
> 73,
> Don W3FPR
>
> > -----Original Message-----
> >
> > Thanks for your quick reply Dan.
> >
> > Logger 32 has a "Radio Debug Window" which shows the commands and
> > replies going between Logger 32 and the K2.
> >
> > When I click on a DX spot, Logger 32 sends the following message to
> > the K2:
> >
> > Set Radio Freq/Mode : FR0;FA00018080000;MD3;FA00018080000;
> >
> > 73 de Chris, G4BUE
> >
> > On 13 Mar 2006 at 6:28, Dan Barker wrote:
> >
> > > What commands do these programs send to the K2 when you "click on
> > > a spot"? That is the first question. If the documentation doesn't
> > > say, and the vendor won't tell, then you'll have to put a sniffer
> > > on it.
> > >
> > > Only after you find a command string that has an unexpected result
> > > can you say there is a problem with the K2. My belief is that the
> > > software is sending commands to force the K2 out of split.
> > >
> > > This could be the result of an error on the part of the programmer
> > > (unlikely) or the use of macros designed for other radios than the
> > > K2 (most likely).
> > >
> > > In any case, more documentation is needed before any problem has
> > > even been described!
> > >
> > > Dan / WG4S / K2 #2456
> > >
> > > <snip>
> > > when I click onto a Cluster spot, the K2 correctly
> > > goes to the frequency and mode of the spot, but the SPLIT option
> > > is cancelled and the K2 returns to its default setting of no
> > > SPLIT. </snip>
> > >
> > > <snip>The problem must therefore be
> > > with the design of the K2 and not the logging program.
> > > </snip>
> >
> > _______________________________________________
> > Elecraft mailing list
> > Post to: Elecraft at mailman.qth.net
> > You must be a subscriber to post to the list.
> > Subscriber Info (Addr. Change, sub, unsub etc.):
> > http://mailman.qth.net/mailman/listinfo/elecraft
> >
> > Help: http://mailman.qth.net/subscribers.htm
> > Elecraft web page: http://www.elecraft.com
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.375 / Virus Database: 268.2.1/279 - Release Date:
> > 3/10/2006
> >
> >
>
>
More information about the Elecraft
mailing list