Ham Radio Deluxe band switching

[boyscout]

Sorry if I've missed this topic in my search for it.

A few versions ago, Ham Radio Deluxe (HRD) software developed a problem with properly tuning my K3 when a DX Cluster report is selected.   The radio is supposed to tune itself to the band and frequency of the selected DX Cluster report, but if the reported contact is on a band different from the one the K3 is tuned to, it now only momentarily goes to that band before immediately returning to the band it was tuned to.

If the K3 is already on the band, then the frequency is tuned just fine.

Moderators in the Ham Radio Deluxe forum have pointed the finger at Elecraft, saying that its code is responsible for the problem.  Odd, because the K3 worked just fine with all versions of HRD until the HRD software was changed, but since we're getting no satisfaction there can folks here respond to this?  Is there something wrong with the K3's code that has only been revealed by the latest versions of HRD?

Thanks for any input.

[Julian, G4ILO]

boyscout wrote

Sorry if I've missed this topic in my search for it.

A few versions ago, Ham Radio Deluxe (HRD) software developed a problem with properly tuning my K3 when a DX Cluster report is selected.   The radio is supposed to tune itself to the band and frequency of the selected DX Cluster report, but if the reported contact is on a band different from the one the K3 is tuned to, it now only momentarily goes to that band before immediately returning to the band it was tuned to.

If the K3 is already on the band, then the frequency is tuned just fine.

Moderators in the Ham Radio Deluxe forum have pointed the finger at Elecraft, saying that its code is responsible for the problem.  Odd, because the K3 worked just fine with all versions of HRD until the HRD software was changed, but since we're getting no satisfaction there can folks here respond to this?  Is there something wrong with the K3's code that has only been revealed by the latest versions of HRD?

Thanks for any input.

I would have thought that by definition the K3 was the definitive implementation of the K3 software commands. If they do not work in the way a software developer expects then it is the software developer's job to work around them.

[Brendan Minish]

if you have VFO IND = NO the you will have this issue

HRD sets both VFO's by default, even where split is not required. in
this case it puts vfoB 'back where it found it

unless you have VFO IND on then both VFO's must be on the same band.
Setting VFOA jumps to the new band.
setting VFOB causes VFO A to revert to the same band as VFOB is on. this
is normal. the K3 is behaving as it should for the way it is configured.
Many of us prefer VFO IND = NO as I always want my main and sub on the
same band.

I raised this with Simon and would expect that it will be fixed soon.

frankly I can't see why the software would need to 'touch' VFO B unless
it's actually setting split mode.  

73
Brendan EI6IZ  




On Tue, 2009-09-08 at 03:15 -0500, Julian, G4ILO wrote:

>
>
> boyscout wrote:
> >
> > Sorry if I've missed this topic in my search for it.
> >
> > A few versions ago, Ham Radio Deluxe (HRD) software developed a problem
> > with properly tuning my K3 when a DX Cluster report is selected.   The
> > radio is supposed to tune itself to the band and frequency of the selected
> > DX Cluster report, but if the reported contact is on a band different from
> > the one the K3 is tuned to, it now only momentarily goes to that band
> > before immediately returning to the band it was tuned to.
> >
> > If the K3 is already on the band, then the frequency is tuned just fine.
> >
> > Moderators in the Ham Radio Deluxe forum have pointed the finger at
> > Elecraft, saying that its code is responsible for the problem.  Odd,
> > because the K3 worked just fine with all versions of HRD until the HRD
> > software was changed, but since we're getting no satisfaction there can
> > folks here respond to this?  Is there something wrong with the K3's code
> > that has only been revealed by the latest versions of HRD?
> >
> > Thanks for any input.
> >
> >
>
> I would have thought that by definition the K3 was the definitive
> implementation of the K3 software commands. If they do not work in the way a
> software developer expects then it is the software developer's job to work
> around them.
>
> -----
> Julian, G4ILO. K2 #392  K3 #222.
> * G4ILO's Shack - http://www.g4ilo.com
> * KComm - http://www.g4ilo.com/kcomm.html
> * KTune - http://www.g4ilo.com/ktune.html

--
73
Brendan EI6IZ

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[boyscout]

Brendan Minish wrote

if you have VFO IND = NO the you will have this issue

HRD sets both VFO's by default, even where split is not required. in
this case it puts vfoB 'back where it found it

Thanks for taking the time to post, Brendan, this "fixes" the problem just fine.

It may also explain why some K3 users have reported "no problem" with the latest releases of HRD beta 5... they either have this configuration set to 'yes' or in many cases they don't have a VFO B.

Thanks again!