[Elecraft] [K3] FW 5.5 issue??

[Jim McDonald]

I installed the newest K3 firmware, 5.54, reset DXLab, MMTTY, and the K3 to 2125 and still get the 850 Hz error when transferring a spot from SpotCollector to the radio.

I changed all back to low tones, 1225/1445, and get the same error.

Tony, K4QE, reported that he had the problem until he reverted back to K3 firmware release, 5.38, so the firmware must be the problem.

I need the newer firmware for my K-Pod, so I'll live with the apparent defect RTTY in 5.54 until it's resolved.

73, Jim N7US


-----Original Message-----

Got it.  I installed the newest Beta, and it didn't fix the 850 Hz shift problem, so I need to experiment some more.

Jim N7US
Sent from Outlook on my iPad

		_____________________________

Jim,
You are remembering it incorrectly.  The 1, 2, 5, and 10 buttons only turn on SPLIT.
73, Tony K4QE
On Sat, Oct 1, 2016 at 9:06 AM, Jim McDonald <jim at n7us.net> wrote:
Joe,

-------------------------------------------------

The pitch in the K3 is still set to 1275 for my 1275/1445 low tones, and WW still has the Mark Offset of -1275 and an Optimal Offset of 1360.

I'm referring to the buttons 1, 2, 5, and 10 above the frequency in the VFO B panel of Commander.  They do still turn on split in the radio and offset the VFO B frequency correctly.  I thought they were also supposed to turn on my subreceiver and check the Dual receive box in the VFO A panel.  Maybe I am not remembering that correctly.

73, Jim N7US


-----Original Message-----


> In DXLab, when I click on RTTY DX spot in SpotCollector the K3 changes 
> the frequency in the K3 but it's 850 Hz higher than the frequency that 
> DXLab sends to the radio. I'm using K3 FSK D with
> 1275/1445 tones, NOT AFSK.

An 850 Hz offset *sounds like* either your K3 or WinWarbler has been reset to 2125/2295 Hz.  *CHECK BOTH* "Pitch" in the K3 and "Mark Offset"/"Optimal Offset" in the FSK panel of WinWarbler's Configuration dialog.

> I don't know if my other problem is attributable to the firmware 
> either. DXLab's rig control module, Commander, has a nice feature 
> (activated by clicking on a button in the VFO B panel) that will 
> switch the radio to split and turn on the subreceiver (called "dual 
> receive" in Commander). It used to do both of those but now only turns 
> on split but not the subreceiver.

I've used DXLab Suite (Commander) for years with the K3 and do not know what button in the VFO B panel to which you refer.  There are
*two* check boxes in the VFO A panel - one turns split on/off (equivalent to holding A -> B on the K3 front panel) and the other turns the Sub RX on/Off (equivalent to tapping Sub on the K3 front panel).

I'm using FW 5.52 at present and all radio control features of DXLab Suite work just the same as they have in prior versions of the K3 firmware.

73,

    ... Joe, W4TV


On 10/1/2016 12:33 AM, Jim McDonald wrote:
> I installed K3 FW 5.50 to use my K-Pod, which I like very much.  I 
> have a couple of weird problems using DXLab now that I can't explain 
> and wonder if the new FW might be related.
>
>
>
> In DXLab, when I click on RTTY DX spot in SpotCollector the K3 changes 
> the frequency in the K3 but it's 850 Hz higher than the frequency that 
> DXLab sends to the radio.  I'm using K3 FSK D with 1275/1445 tones, 
> NOT
AFSK.
>
>
>
> I don't know if my other problem is attributable to the firmware either.
> DXLab's rig control module, Commander, has a nice feature (activated 
> by clicking on a button in the VFO B panel) that will switch the radio 
> to split and turn on the subreceiver (called "dual receive" in 
> Commander).  It used to do both of those but now only turns on split 
> but
not the subreceiver.
>
>
>
> I'd very much appreciate someone also using FW 5.50 and DXLab would 
> check to see if my experience is unique to me or not.
>
>
>
> Thanks.
>
>
>
> 73, Jim N7US