[Elecraft] New Firmware Issues with K3

[Alan Bloom]

I finally got HRD set up on a computer connected to the Internet so I
can connect to a DX cluster.  I was able to confirm the bug.

Turns out it has nothing to do with the P3 or the new K3 firmware.  It
does it with no P3 connected and K3 version 04.12.  Probably older
versions as well although I didn't try them.

The problem is that in HRD, when you double-click on a DX cluster spot
that is in a different band, HRD sends an FA command to change the K3
VFO A to the new band/frequency (which is fine) but then for some reason
it sends an FB command to re-set the VFO B to the old band/frequency.
That causes the K3 to do a band change back to the old band.

A work-around is to go into the K3 CONFIG menu and set VFO IND to YES.
That allows VFO A and VFO B to be on separate bands so that a band
change on VFO B does not cause VFO A to switch bands.

I'm going to contact the HRD designer to see if maybe there's some
setting in HRD to make it not do that.

Alan N1AL


On Thu, 2010-10-14 at 09:36 -0700, Alan Bloom wrote:
> Jim,
> 
> Thanks for the clarification.  So it only does it when changing bands
> using a DX cluster.  Unfortunately the computer that I use for testing
> does not have an Internet connection.  (For security reasons - it's has
> all my P3 development code which I really don't want to risk getting
> hacked.)  So I can't test with a DX cluster.  Does the problem occur if
> you change bands in HRD by clicking on a band button?
> 
> > I tested with HRD's command tester (Tools-Command  
> > Tester) and HRD reports an error response to the FA command.
> 
> I think that's just the way HRD works.  Any time you send a command that
> has no response (most set commands) it reports an "Error" in the
> received column.  I checked and it still does it with older K3 firmware
> (04.12) and no P3 connected.
> 
> Alan N1AL
> 
> 
> 
> On Thu, 2010-10-14 at 05:31 -0500, JAMES ROGERS wrote:
> > Alan,
> > 
> > 	You have to double click on a HRD DX cluster spot that will change  
> > the band to see it. That is the only way I can reproduce it here. It  
> > will change the band and display the new frequency, then return to the  
> > old band/frequency. I am running the latest firmware in the P3 and K3  
> > (00.36 and 04.14). I tested with HRD's command tester (Tools-Command  
> > Tester) and HRD reports an error response to the FA command.
> > 	
> > Jim, W4ATK
> > 
> > On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
> > 
> > > I don't see it here.  Running P3 firmware 00.36, K3 version 04.14 and
> > > HRD version 5.0.  I can mouse-click on a frequency in HRD and the K3
> > > QSYs normally and stays there.  I can also QSY using the P3 markers  
> > > and
> > > both the K3 and HRD are happy.
> > >
> > > Which software versions are you running?
> > >
> > > Does is only do it when you click on a DX cluster spot or does it also
> > > do it when you click on a frequency on the "dial" in the HRD screen?
> > >
> > > Alan N1AL
> > >
> > >
> > >
> > > On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
> > >> Loaded the new firmware updates for the K3 and P3 and now have issues
> > >> (until I reverted back) with HRD..
> > >>
> > >> With the older versions, while looking at the DX cluster (HRD), I  
> > >> could
> > >> mouse click on a spot and the K3 would QSY and stay there..
> > >>
> > >> Now (again) when I click it jumps to the new spot and right back to  
> > >> the
> > >> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and  
> > >> everything
> > >> worked OK.. Anyone else experiencing this..??
> > >>
> > >> de W4CCS