I can confirm that updating to the latest WSJT-X fixes the issue.
I had the some problem, and it was particular to the K3. I had no delay
with the KX2, for instance.
73,
-- Dave, N8SBE
Quoting James Bennett via Elecraft :
Hi Folks,
Wondering if someone on the list might be able to solve
I upgraded to 2.5.0 last night at Jim’s suggestion and it worked! No more delay!
Ron W5SUM
Sent from my iPhone
> On Oct 12, 2021, at 7:13 AM, Bob Schwerdlin wrote:
>
> The current version of hamlib is, 4.3
>
> I had similar delay of TX issues with my FT-1000D and WSJT-X on Linux. After
>
The current version of hamlib is, 4.3
I had similar delay of TX issues with my FT-1000D and WSJT-X on Linux.
After I updated to hamlib 4.x from version 3.3, my issues went away.
Additionally, all the current rigs were updated in the library. Note,
they are all now four digit radio codes,
Jim,
Two possible fixes:
1) Use PTT via CAT command - most digital applications provide for it.
2) Check that your audio levels are sufficient - for the Elecraft gear,
you should have 4 bars of ALC solid with the 5th one blinking. See the
full explanation on my website www.w3fpr.com.
73,
On 10/11/2021 11:45 AM, David Olean wrote:
Update the software to the latest. That was a known bug in earlier
versions. I had the same problem with my K3.
Yes. It's a problem between WSJT-X and hamlib. WSJT-X was sending more
rig control commands than necessary. Also, don't tell WSJT-X to do
Problem solved - it was simply a matter of upgrading to version 2.5 of WSJT-X.
Works fine now. Thanks to all who replied!!
Jim Bennett / K7TXA
Eagle, ID
> On Oct 11, 2021, at 11:31 AM, James Bennett via Elecraft
> wrote:
>
> Hi Folks,
>
> Wondering if someone on the list might be able to
Update to the latest WSJTX and hamlib. The problem is due to a timing
issue in the older versions of hamlib not allowing WSJTX to begin audio
until it receives certain CAT responses from the K3/K3s. Older
versions of hamlib were doing too many (unnecessary) CAT commands.
73,
... Joe,
David -
I’ve played with the VOX Gain to no avail - at zero the rig never transmits,
and at 100 (where it has been sitting) I get the delay. Various settings in
between have no effect. The Delay controls how quickly the rig goes back into
receive mode after speaking. But, thanks for the hints!
James,
I had the same problem here running a Mac. Solved it by going to CAT, Mode =
None, Split = None.
I have no delay now.
John
WA1EAZ
> On Oct 11, 2021, at 1:31 PM, James Bennett via Elecraft
> wrote:
>
> Hi Folks,
>
> Wondering if someone on the list might be able to solve this one.
My K3 does the exact same thing and I’m running Windows 10
Ron W5SUM
Sent from my iPhone
> On Oct 11, 2021, at 12:55 PM, James Bennett via Elecraft
> wrote:
>
> Hi Folks,
>
> Wondering if someone on the list might be able to solve this one. I’m using a
> K3 and while CW is my main
Update the software to the latest. That was a known bug in earlier
versions. I had the same problem with my K3.
Dave K1WHS
On 10/11/2021 1:31 PM, James Bennett via Elecraft wrote:
Hi Folks,
Wondering if someone on the list might be able to solve this one. I’m using a
K3 and while CW is my
Hi Folks,
Wondering if someone on the list might be able to solve this one. I’m using a
K3 and while CW is my main passion, I do dabble in FT8 occasionally. I’ve
noticed that the radio does not start transmitting right at the start of the 15
second FT8 cycle. It will start anywhere from 2 - 5
12 matches
Mail list logo
