WSJT-X version 2.4.0 c19062


Ed Pflueger
 

I have noticed since I went from the BETA version of WSJT-X 2.4.0 to the new version that there is considerable delay in transmit that was not apparent in the BETA version.  A friend of mine, ND4X and I are having the same issue.  Has anyone else noticed that you hear other stations transmitting before your rig keys up?  I am running a K3S and my friend has a K3 with all of the updates.

 

Thanks Ed.. AB4IQ

 

 


Dave (NK7Z)
 

Hi,
I have not seen a delay. Under FILE/SETTINGS/ADVANCED, there is a "Transmit Delay", option, which you can control transmit delay in .1 second steps, starting at zero..

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 10:23 AM, Ed Pflueger wrote:
I have noticed since I went from the BETA version of WSJT-X 2.4.0 to the new version that there is considerable delay in transmit that was not apparent in the BETA version.  A friend of mine, ND4X and I are having the same issue.  Has anyone else noticed that you hear other stations transmitting before your rig keys up?  I am running a K3S and my friend has a K3 with all of the updates.
Thanks Ed.. AB4IQ


Howard Saxion
 

I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS


Ed Pflueger
 

Mine and my friends are at .1 as we speak. Need to try for Zero I guess.

Thanks Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Dave
(NK7Z)
Sent: Friday, May 28, 2021 12:39 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

Hi,
I have not seen a delay. Under FILE/SETTINGS/ADVANCED, there is a "Transmit
Delay", option, which you can control transmit delay in .1 second steps,
starting at zero..

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 10:23 AM, Ed Pflueger wrote:
I have noticed since I went from the BETA version of WSJT-X 2.4.0 to
the new version that there is considerable delay in transmit that was
not apparent in the BETA version.  A friend of mine, ND4X and I are
having the same issue.  Has anyone else noticed that you hear other
stations transmitting before your rig keys up?  I am running a K3S and
my friend has a K3 with all of the updates.

Thanks Ed.. AB4IQ


Dave (NK7Z)
 

I had a friend call me today, his was at .1, and after the last update it went to .2... He is resetting his to .1.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 11:03 AM, Ed Pflueger wrote:
Mine and my friends are at .1 as we speak. Need to try for Zero I guess.
Thanks Ed.. AB4IQ
-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Dave
(NK7Z)
Sent: Friday, May 28, 2021 12:39 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062
Hi,
I have not seen a delay. Under FILE/SETTINGS/ADVANCED, there is a "Transmit
Delay", option, which you can control transmit delay in .1 second steps,
starting at zero..
73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources
On 5/28/21 10:23 AM, Ed Pflueger wrote:
I have noticed since I went from the BETA version of WSJT-X 2.4.0 to
the new version that there is considerable delay in transmit that was
not apparent in the BETA version.  A friend of mine, ND4X and I are
having the same issue.  Has anyone else noticed that you hear other
stations transmitting before your rig keys up?  I am running a K3S and
my friend has a K3 with all of the updates.

Thanks Ed.. AB4IQ


Dave (NK7Z)
 

Howard,

I have noticed that the first decode period seems to happen around five seconds prior to the end of a cycle, then the final decode occurs, at the last second of a cycle.

This makes essentially two periods in each cycle, where you can mouse click to respond.

Is it possible you are reacting to the first decode, and it only seems like a delay because the TX does not happen as you click the mouse, but at the end of the cycle?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 10:43 AM, Howard Saxion via groups.io wrote:
I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS


Ed Pflueger
 

I just set mine to Zero and no change. I did not have the new version of JTALERT running either. It did not make a difference whether JT alert was running or not. I guess the next best thing would go back to the BETA version and see if the issue goes away.

Ed..

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Dave (NK7Z)
Sent: Friday, May 28, 2021 1:05 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

I had a friend call me today, his was at .1, and after the last update it went to .2... He is resetting his to .1.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 11:03 AM, Ed Pflueger wrote:
Mine and my friends are at .1 as we speak. Need to try for Zero I guess.

Thanks Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf
Of Dave
(NK7Z)
Sent: Friday, May 28, 2021 12:39 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

Hi,
I have not seen a delay. Under FILE/SETTINGS/ADVANCED, there is a
"Transmit Delay", option, which you can control transmit delay in .1
second steps, starting at zero..

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 10:23 AM, Ed Pflueger wrote:
I have noticed since I went from the BETA version of WSJT-X 2.4.0 to
the new version that there is considerable delay in transmit that was
not apparent in the BETA version. A friend of mine, ND4X and I are
having the same issue. Has anyone else noticed that you hear other
stations transmitting before your rig keys up? I am running a K3S
and my friend has a K3 with all of the updates.

Thanks Ed.. AB4IQ











Ed Pflueger
 

I'm not Howard this is Ed but just even hitting the TUNE button there is a delay.

Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Dave (NK7Z)
Sent: Friday, May 28, 2021 1:12 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

Howard,

I have noticed that the first decode period seems to happen around five seconds prior to the end of a cycle, then the final decode occurs, at the last second of a cycle.

This makes essentially two periods in each cycle, where you can mouse click to respond.

Is it possible you are reacting to the first decode, and it only seems like a delay because the TX does not happen as you click the mouse, but at the end of the cycle?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 10:43 AM, Howard Saxion via groups.io wrote:
I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS






Ed Pflueger
 

I just went back to the BETA version and all is well. No delay now when I just hit the Tune button.

Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Howard Saxion via groups.io
Sent: Friday, May 28, 2021 12:43 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS


Dave (NK7Z)
 

Wow... That is nothing like my setups behavior...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 5/28/21 11:15 AM, Ed Pflueger wrote:
I'm not Howard this is Ed but just even hitting the TUNE button there is a delay.
Ed.. AB4IQ


Bob Hallock
 

Ed,
I had the same problem.  I went back to 2.3.o.
Bob K7TM

On Fri, May 28, 2021 at 10:24 AM Ed Pflueger <ab4iq@...> wrote:

I have noticed since I went from the BETA version of WSJT-X 2.4.0 to the new version that there is considerable delay in transmit that was not apparent in the BETA version.  A friend of mine, ND4X and I are having the same issue.  Has anyone else noticed that you hear other stations transmitting before your rig keys up?  I am running a K3S and my friend has a K3 with all of the updates.

 

Thanks Ed.. AB4IQ

 

 


Drew Vonada-Smith K3PA
 

Isn't this a WSJT issue?  Seems unlikely to be K3.


Joe Subich, W4TV
 

The programmers of WSJTX continue to keep their heads where the sun
doesn't shine with regard to controlling the K3/K3S. The *INSIST*
on waiting until x:00/x:15/x:30/:45 to set the transmit frequency
(VFO B) and mode. THEN they *wait* until the K3/K3s has confirmed
that transmit frequency/mode.

This has several problems. 1) the K3/K3S can take up to 500 ms t
react to a "Set VFO B" command. Add to that the time for "set
mode" and set data sub-mode commands, *then* the delay to poll the
rig for status after sending those commands to confirm that they
have "taken". WSJTX does not require frequency/mode confirmation
for all transceivers. In addition, if you are using a USB connection
(or USB to serial converter), the Windows USB subsystem *can* introduce
additional delay depending on the number of USB devices, whether you
have any hubs in use, and whether you have any mass data connections
(USB to network, USB hard drives, USB thumb drives, a cell phone, etc.).

I have argued for years (to deaf ears), that WSJTX needs to do the
split set-up at x:58/x:13/x:28/x:43 and/or eliminate the "poll for
confirmation" (as in other transceivers). In the meantime, the best
the user can do is 1) use a "real" serial port for radio control,
2) simplify the USB connection to place the K3/interface on its own
"root hub" in the computer, 3) eliminate all external hubs, 4)
eliminate any external USB storage/network devices and 5) get a
more powerful processor (the problems are worse with ATOM and
dual core CPUs).

73,

... Joe, W4TV

On 2021-05-28 1:43 PM, Howard Saxion via groups.io wrote:
I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS


ve3ki
 

In that regard, if you are having problems with delays, here are a couple of settings changes in WSJT-X that you might try as workarounds:

1. Try switching the "Split operation" from "Rig" to "Fake It" to see which one works better. "Fake It" does not involve sending and receiving information related to VFO B, so it might be faster.

2. You could also try changing "Mode' from "Data/Pkt" to "None", in which case it would be up to you to ensure that the rig is in DATA A. This also should simplify the poll/response process between the software and the radio.

73,
Rich VE3KI




On Fri, May 28, 2021 at 03:26 PM, Drew Vonada-Smith K3PA wrote:
Isn't this a WSJT issue?  Seems unlikely to be K3.


Gordon LaPoint
 

I have found that "Fake it" works better for the K3, but Joe is correct that the wsjtx programers should fix it so you can use split and not fake it.
I also use a Kenwood TS-590sg, which works perfect on timing using split.

Thanks,
Gordon - N1MGO

On 5/28/2021 15:40 PM, Joe Subich, W4TV wrote:

The programmers of WSJTX continue to keep their heads where the sun
doesn't shine with regard to controlling the K3/K3S.  The *INSIST*
on waiting until x:00/x:15/x:30/:45 to set the transmit frequency
(VFO B) and mode.  THEN they *wait* until the K3/K3s has confirmed
that transmit frequency/mode.

This has several problems.  1) the K3/K3S can take up to 500 ms t
react to a "Set VFO B" command. Add to that the time for "set
mode" and set data sub-mode commands, *then* the delay to poll the
rig for status after sending those commands to confirm that they
have "taken".  WSJTX does not require frequency/mode confirmation
for all transceivers.  In addition, if you are using a USB connection
(or USB to serial converter), the Windows USB subsystem *can* introduce
additional delay depending on the number of USB devices, whether you
have any hubs in use, and whether you have any mass data connections
(USB to network, USB hard drives, USB thumb drives, a cell phone, etc.).

I have argued for years (to deaf ears), that WSJTX needs to do the
split set-up at x:58/x:13/x:28/x:43 and/or eliminate the "poll for
confirmation" (as in other transceivers).  In the meantime, the best
the user can do is 1) use a "real" serial port for radio control,
2) simplify the USB connection to place the K3/interface on its own
"root hub" in the computer, 3) eliminate all external hubs, 4)
eliminate any external USB storage/network devices and 5) get a
more powerful processor (the problems are worse with ATOM and
dual core CPUs).

73,

   ... Joe, W4TV


On 2021-05-28 1:43 PM, Howard Saxion via groups.io wrote:
I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS






Jim Brown
 

On 5/28/2021 1:24 PM, Gordon LaPoint wrote:
I have found that "Fake it" works better for the K3, but Joe is correct that the wsjtx programers should fix it so you can use split and not fake it.
Years ago, I found that I needed to use Fake It with my K3, because I operate lots of contests on CW, RTTY, SSB, and when I used Split, it would leave the rig with settings I didn't want when I switched to those modes. And as Rich has suggested, I just now changed from Data/Packet to None.

73, Jim K9YC


Bob Hallock
 

Go back to to wsjr2.3.0


On Fri, May 28, 2021 at 12:26 PM Drew Vonada-Smith K3PA <drew@...> wrote:
Isn't this a WSJT issue?  Seems unlikely to be K3.


Ed Pflueger
 

Yes that’s correct but I wanted to know if it was happening to other users with the newest version of WSJT-X.  Not blaming anything on the K3S.  I thought maybe I had some Cockpit Trouble which usually points back to me.  LOL..  Then when a friend had the same issue I just had to ask.

 

By the way I ordered my K4D at 8:20 am on 5/17/ 2019 and I got my letter from Madelyn Monday and the shipping information this afternoon.

 

Ed.. AB4IQ

 

From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Drew Vonada-Smith K3PA
Sent: Friday, May 28, 2021 2:26 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

 

Isn't this a WSJT issue?  Seems unlikely to be K3.


Ed Pflueger
 

Well I understand the situation now. I'm still making contacts OK but it just seemed Odd that it took that long to transmit. That answers my question and Thanks. Case closed...

Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Joe Subich, W4TV
Sent: Friday, May 28, 2021 2:40 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062


The programmers of WSJTX continue to keep their heads where the sun doesn't shine with regard to controlling the K3/K3S. The *INSIST* on waiting until x:00/x:15/x:30/:45 to set the transmit frequency (VFO B) and mode. THEN they *wait* until the K3/K3s has confirmed that transmit frequency/mode.

This has several problems. 1) the K3/K3S can take up to 500 ms t react to a "Set VFO B" command. Add to that the time for "set mode" and set data sub-mode commands, *then* the delay to poll the rig for status after sending those commands to confirm that they have "taken". WSJTX does not require frequency/mode confirmation for all transceivers. In addition, if you are using a USB connection (or USB to serial converter), the Windows USB subsystem *can* introduce additional delay depending on the number of USB devices, whether you have any hubs in use, and whether you have any mass data connections (USB to network, USB hard drives, USB thumb drives, a cell phone, etc.).

I have argued for years (to deaf ears), that WSJTX needs to do the split set-up at x:58/x:13/x:28/x:43 and/or eliminate the "poll for confirmation" (as in other transceivers). In the meantime, the best the user can do is 1) use a "real" serial port for radio control,
2) simplify the USB connection to place the K3/interface on its own "root hub" in the computer, 3) eliminate all external hubs, 4) eliminate any external USB storage/network devices and 5) get a more powerful processor (the problems are worse with ATOM and dual core CPUs).

73,

... Joe, W4TV


On 2021-05-28 1:43 PM, Howard Saxion via groups.io wrote:
I have also noticed this on my K3 running WSJT 2.4.0 and the latest version of JTAlert. No configuration changes were made from the last candidate release version to 2.4.0 general release version. It is about a 1-2 second delay after “clicking” the station I want to QSO.
73, Howard WX7HS


Ed Pflueger
 

Thanks I’ll give that a shot.  I’m in RIG and Data/PKT and I’ll give them a quick change.  Well that sure sped things up after those changes.

 

Thanks Rich

 

Ed..AB4IQ

 

From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of ve3ki
Sent: Friday, May 28, 2021 2:54 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] WSJT-X version 2.4.0 c19062

 

In that regard, if you are having problems with delays, here are a couple of settings changes in WSJT-X that you might try as workarounds:

1. Try switching the "Split operation" from "Rig" to "Fake It" to see which one works better. "Fake It" does not involve sending and receiving information related to VFO B, so it might be faster.

2. You could also try changing "Mode' from "Data/Pkt" to "None", in which case it would be up to you to ensure that the rig is in DATA A. This also should simplify the poll/response process between the software and the radio.

73,
Rich VE3KI




On Fri, May 28, 2021 at 03:26 PM, Drew Vonada-Smith K3PA wrote:

Isn't this a WSJT issue?  Seems unlikely to be K3.