WSJT-X v2.4.0 FT8 #wsjt-x


Ken
 

Running WSJT-X v2.4.0

I am running a K3, CAT control on Com 1, Mode: Data/Pkt, Split: Fake it.
TX delay set at 0.2 s. There may is an additional TX delay (K3 Menu) of 12 ms.

I am using NET TIME to set my PC clock which appears to be right on.
WSJT-X keys my K3 and power out (on my LP-500) occurs at approximately 17 sec and 47 sec. according to the WSJT-X Date/Time window.
The time in the Time window agrees with NET TIME which says my Time difference from UTC is +0.037 +/- 0.066 seconds.

Most stations on WSJT-X show a DT of 0.1 to 0.3.

When should TX start per WSJT-X at 15 sec and 45 sec ? That is what should the delay be 1 sec 2 sec, less ???
I have not noticed this with previous versions of WSJT-X, however I wasn't looking for it either.
It was brought to my attention today by a local Ham.

Has anyone else seen this ?
Is this a software issue ?
Is there some setting in WSJT-X that I may have missed.

It appears that I am working stations OK but I am concerned that this 2 second delay may be a problem?

Please advise.

Ken - W8KEN


Bill Somerville
 

On 07/07/2021 16:55, Ken via groups.io wrote:
Running WSJT-X v2.4.0

I am running a K3, CAT control on Com 1, Mode: Data/Pkt, Split: Fake it.
TX delay set at 0.2 s. There may is an additional TX delay (K3 Menu) of 12 ms.

I am using NET TIME to set my PC clock which appears to be right on.
WSJT-X keys my K3 and power out (on my LP-500) occurs at approximately 17 sec and 47 sec. according to the WSJT-X Date/Time window.
The time in the Time window agrees with NET TIME which says my Time difference from UTC is +0.037 +/- 0.066 seconds.

Most stations on WSJT-X show a DT of 0.1 to 0.3.

When should TX start per WSJT-X at 15 sec and 45 sec ? That is what should the delay be 1 sec 2 sec, less ???
I have not noticed this with previous versions of WSJT-X, however I wasn't looking for it either.
It was brought to my attention today by a local Ham.

Has anyone else seen this ?
Is this a software issue ?
Is there some setting in WSJT-X that I may have missed.

It appears that I am working stations OK but I am concerned that this 2 second delay may be a problem?

Please advise.

Ken - W8KEN

Hi Ken,

please try WSJT-X v2.5.0 RC3, that issue with unexpected PTT delays on K3 series rigs should be resolved.

73
Bill
G4WJS.


Ken
 

Hi Bill,

TU for your reply, which brings up a few more questions.
I run two instances of WSJT-X, one for my K3 used on HF & 6m (mostly FT8) and one for my other K3 (presently at Elecraft for repair and upgrade) used with a Xvtr for EME. I am also running Windows 7 Professional Service Pack 1.

1) If a install WSJT-X v2.50 RC3 in a separate directory, will it use my current ADI log file for HF ?
I use JTAlert and N3FJP ACLog to automatically log my HF contacts and I rely on the current color code to tell if I have worked stations before.

If I then switch to WSJT-X v2.4.0, will it still access the same log in case v2.50 RC3 doesn't work as expected ?

2) I am using WSJT-X v2.4.0 and MAP65 v2.7 R8182 with my IQ+ and UADC4 and (2) XPOL yagis for adaptive polarization and JT65B on 2m EME.
I am hesitant to run WSJT-X v2.50 RC3 with my UADC4 until all of the installation instructions and updated drivers are verified to work correctly.
I have seen reports on the reflector where people are having trouble with the new sound card drivers.

Have all of these issues been resolved yet ?
Do the WDM/KS drivers now install and work properly with the UADC4 ?
Do they install and work properly with Windows 7 Professional Service Pack 1 ?
Please see my attached email to HB9DRI and his response.

I am sorry to be such a pest, but I'm not a Software Expert (just a Mechanical Engineer) and if I load the new drivers and software and they don't work as expected, I do not have the expertise to investigate and resolve software problems. Although I am running Windows 10 on my Non-HAM PC, I haven't felt comfortable enough with it to upgrade my HAM PC yet. I know that several of my older programs just won't run on Windows 10.

Thank you for the great job you and the WSJT-X Development Team are doing to provide us with new innovative HAM software.

Again, thank you for your response

Ken - W8KEN



On 7/7/2021 2:50 PM, Bill Somerville wrote:
On 07/07/2021 16:55, Ken via groups.io wrote:
Running WSJT-X v2.4.0

I am running a K3, CAT control on Com 1, Mode: Data/Pkt, Split: Fake it.
TX delay set at 0.2 s. There may is an additional TX delay (K3 Menu) of 12 ms.

I am using NET TIME to set my PC clock which appears to be right on.
WSJT-X keys my K3 and power out (on my LP-500) occurs at approximately 17 sec and 47 sec. according to the WSJT-X Date/Time window.
The time in the Time window agrees with NET TIME which says my Time difference from UTC is +0.037 +/- 0.066 seconds.

Most stations on WSJT-X show a DT of 0.1 to 0.3.

When should TX start per WSJT-X at 15 sec and 45 sec ? That is what should the delay be 1 sec 2 sec, less ???
I have not noticed this with previous versions of WSJT-X, however I wasn't looking for it either.
It was brought to my attention today by a local Ham.

Has anyone else seen this ?
Is this a software issue ?
Is there some setting in WSJT-X that I may have missed.

It appears that I am working stations OK but I am concerned that this 2 second delay may be a problem?

Please advise.

Ken - W8KEN

Hi Ken,

please try WSJT-X v2.5.0 RC3, that issue with unexpected PTT delays on K3 series rigs should be resolved.

73
Bill
G4WJS.






Bill Somerville
 

Hi Ken,

comments in line below.

On 08/07/2021 05:16, Ken via groups.io wrote:
Hi Bill,

TU for your reply, which brings up a few more questions.
I run two instances of WSJT-X, one for my K3 used on HF & 6m (mostly FT8) and one for my other K3 (presently at Elecraft for repair and upgrade) used with a Xvtr for EME. I am also running Windows 7 Professional Service Pack 1.

1) If a install WSJT-X v2.50 RC3 in a separate directory, will it use my current ADI log file for HF ?
I use JTAlert and N3FJP ACLog to automatically log my HF contacts and I rely on the current color code to tell if I have worked stations before.
Yes.

If I then switch to WSJT-X v2.4.0, will it still access the same log in case v2.50 RC3 doesn't work as expected ?
Yes, but I recommend you try v2.5.0 RC3 and if it does not work let us know, you can revert to 2.4.0 by re-installing it at any time. There's no real need to have both versions installed.

2) I am using WSJT-X v2.4.0 and MAP65 v2.7 R8182 with my IQ+ and UADC4 and (2) XPOL yagis for adaptive polarization and JT65B on 2m EME.
I am hesitant to run WSJT-X v2.50 RC3 with my UADC4 until all of the installation instructions and updated drivers are verified to work correctly.
I have seen reports on the reflector where people are having trouble with the new sound card drivers.
Note that we do not provide WDM/KS sound card drivers, they are usually provided by the MS Windows Update system.

Have all of these issues been resolved yet ?
As far as I know yes with some minor restrictions which do not affect you setup.
Do the WDM/KS drivers now install and work properly with the UADC4 ?
Yes, but I do not think there was ever a problem with them. For some old multi-channel sound cards there seems to be a problem the devices being presented via the WDM/KS driver as pairs or stereo devices, these are not suitable for MAP65, a device with at least 4 channels is required. the UADC4 and most other multi-channel sound cards work fine with MAP65 when hosted by WDM/KS drivers.
Do they install and work properly with Windows 7 Professional Service Pack 1 ?
There is nothing to install.
Please see my attached email to HB9DRI and his response.
Alex is correct, there are no significant problems. As he notes it is possible to revert to using ASIO hosted audio devices if you really need to, but that is unlikely. To do so yo must build the portaudio Open Source library yourself to achieve this as licensing constraints prevent us providing a portaudio DLL compatible with ASIO. As of MAP65 v3.0.0 RC3 (included with WSJT-X v2.5.0 RC3) using a self built portaudio DLL to get ASIO support is working, instructions are here: https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/doc/building%20portaudio%20on%20Windows%20with%20ASIO%20support.txt , but note that is is very unlikely that you will need to do that since the UADC4 hosted by WDM/KS works just as well.

I am sorry to be such a pest, but I'm not a Software Expert (just a Mechanical Engineer) and if I load the new drivers and software and they don't work as expected, I do not have the expertise to investigate and resolve software problems. Although I am running Windows 10 on my Non-HAM PC, I haven't felt comfortable enough with it to upgrade my HAM PC yet. I know that several of my older programs just won't run on Windows 10.
The only dirver update you need to do manually is the generic USB driver to allow MAP65 to set the LO frequency of your IQ+ SDRs, that is done using a very simple to use tool (Zadig) which also allows reversion to the original libusb0.sys driver if really necessary, but note that the libusbK driver has good backwards compatibility and you will not need to revert to the old, obsolete, and unsupported libusb0.sys driver.

Thank you for the great job you and the WSJT-X Development Team are doing to provide us with new innovative HAM software.
You are welcome.

Again, thank you for your response

Ken - W8KEN

73
Bill
G4WJS.


Lloyd K8DiO
 

I’m glad that I’m using a simple SDR receiver with only one polarity. Smile
 
I feel that I am pretty computer knowledgeable but my head spins around
reading about driver files. Surprised smile
 
Lloyd


Bill Somerville
 

On 08/07/2021 12:02, Lloyd K8DiO wrote:
I’m glad that I’m using a simple SDR receiver with only one polarity. Smile
 
I feel that I am pretty computer knowledgeable but my head spins around
reading about driver files. Surprised smile
 
Lloyd

Hi Lloyd,

there is less complexity than some would have you think. For IQ+, or similar USB controlled SDRs, users we have switched to a newer generic USB control library and the old libusb0.sys driver, which dates back to the original Atmel MCU controlled SoftRock SDR boards, is now obsolete and not compatible. The Zadig tool we recommend makes updating to one of two alternative modern generic USB drivers (libusbK, or the MS standard WinUSB) very simple, it also supports switching between drivers if necessary.

For the 4-channel (2 times I/Q) soundcard method of feeding MAP65 with dual polarization input there are choices for which Windows audio sub-system hosts the device, MAP65 supports both WDM/KS and ASIO with the caveat that if you must use ASIO then you have to build the portaudio DLL yourself since we are not able to distribute a portaudio DLL including ASIO support. Note that portaudio is not a driver, it is a library layer that allows applications to easily receive and send audio to any of the audio devices connected to a system.

So in summary, an update of USB generic device driver is a one-off task done with a simple and reliable graphical tool. For most using a 4-channel soundcard  there is nothing to do other than select the appropriate WDM/KS multichannel audio device in the MAP65 I/O settings.

73
Bill
G4WJS.