On 22/06/2021 11:49, w1av via groups.io wrote:

I have not run WSJT X in about 1 month. I fired up my IC 7300 and ran WSJT X....everything seems to be looking like its working...I see signals on waterfall....the level meter showing about 60%. But I get NO STATIONS showing up in the band activity pane! I havent made any changes to computer....all cables connected. The frequency on radio and WSJTX the same...everything looks OK but no band activity.....Any ideas where I should start looking?

OM,

I will assume you are running MS Windows, have you followed the suggestion in the User Guide installation instructions to install a third-party time synchronization tool?

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#INSTALL_WIN

73
Bill
G4WJS.

On 22/06/2021 14:16, Hans Fong wrote:

Compiled WSJT-X from the latest source code on a Kubuntu 20.04 machine, connected to my (for me new) TS-2000. Everything works, except for the delay when e.g. double clicking a call in the band activity column, saving a log entry, selecting an audio device, etc. The entire WSJT-X window freezes for at least a couple of seocnds after which operation resumes as normal. Delay times differ from 2 seconds (FT-4) to 7.5 seconds (FT-8), 9.5 seconds (saving a log entry). I don't have the impression that the program stops working, it's just a delay in the UI.

I also tried other versions, like the stock one from the Kubuntu 20.04 (2.1.12), the lastest deb 2.4.0 and some of the beta versions, but they all suffer from the same delay. So I guess it is a (K)Ubuntu thing, but what? The command line doesn't give me any verbose messages.

Any hints or tips welcome. Been searching the web, but it seems no one has this problem, as I haven't been able to find any reference to this phenomenon.
73 de Hans
BX2ABT.com

Hi Hans,

you are the first to report that issue as far as I know. Other than making sure your distribution packages are all up to date I don't have any suggestions.

73
Bill
G4WJS.

On 22/06/2021 17:46, invl160 Davis wrote:

I am operating a TransAtlantic VHF SDR Beacon Monitoring station here in St.John's NL GN37.  The callsign for this 2M receive only station is VO1FN.
Since inception in May there has been one decode of K1TEO 1760 KMS on 144.174Mhz FT8.

When I look on the PSK Map i do not see VO1FN as a Monitor.  There is a link to click that will bring up large markers to show VHF Monitors reporting but VO1FN does not appear.  I cannot find any information about how WSJT-X reports to PSK Reporter site.  Is there away to "force" a report ?...I am looking for a way to have VO1FN appear on the map.  Will this only happen if it is able to hear signals and report on a regular basis ?

Frank VO1HP

Hi Frank,

receiving station reports are sent to PSK Reporter regardless of whether decodes suitable for spotting are received, all you need do is enable PSK Reporter spotting in "Settings->Reporting" and have a working Internet connection. What happens at the PSK Report server end is not something I can comment on, perhaps a question on the PSK Reporter support mailing list is your best option.

73
Bill
G4WJS.

On 22/06/2021 18:25, Pietro Molina wrote:

With v 2.4.0 when the watchdog jumps up my FT817 continues to transmit and an error appear in the frequency window

Furthermore after a few minutes without any tx the frequency window become red with a great number ( > 9.000.000) and band indication show "Oop". If I'm transmitting all is ok. A second watchdog??

Anyone had this problem? (FT818 rig)

I2OIM

Hi Pietro,

do you have the option "Settings->General->Allow Tx frequency changes while transmitting" checked?

73
Bill
G4WJS.

With v 2.4.0 when the watchdog jumps up my FT817 continues to transmit and an error appear in the frequency window
 
Furthermore after a few minutes without any tx the frequency window become red with a great number ( > 9.000.000) and band indication show "Oop". If I'm transmitting all is ok. A second watchdog??

Anyone had this problem? (FT818 rig)

I2OIM

I am operating a TransAtlantic VHF SDR Beacon Monitoring station here in St.John's NL GN37.  The callsign for this 2M receive only station is VO1FN.
Since inception in May there has been one decode of K1TEO 1760 KMS on 144.174Mhz FT8.

When I look on the PSK Map i do not see VO1FN as a Monitor.  There is a link to click that will bring up large markers to show VHF Monitors reporting but VO1FN does not appear.  I cannot find any information about how WSJT-X reports to PSK Reporter site.  Is there away to "force" a report ?...I am looking for a way to have VO1FN appear on the map.  Will this only happen if it is able to hear signals and report on a regular basis ?

Frank VO1HP

Compiled WSJT-X from the latest source code on a Kubuntu 20.04 machine, connected to my (for me new) TS-2000. Everything works, except for the delay when e.g. double clicking a call in the band activity column, saving a log entry, selecting an audio device, etc. The entire WSJT-X window freezes for at least a couple of seocnds after which operation resumes as normal. Delay times differ from 2 seconds (FT-4) to 7.5 seconds (FT-8), 9.5 seconds (saving a log entry). I don't have the impression that the program stops working, it's just a delay in the UI.

I also tried other versions, like the stock one from the Kubuntu 20.04 (2.1.12), the lastest deb 2.4.0 and some of the beta versions, but they all suffer from the same delay. So I guess it is a (K)Ubuntu thing, but what? The command line doesn't give me any verbose messages.

Any hints or tips welcome. Been searching the web, but it seems no one has this problem, as I haven't been able to find any reference to this phenomenon.
73 de Hans
BX2ABT.com

I have not run WSJT X in about 1 month. I fired up my IC 7300 and ran WSJT X....everything seems to be looking like its working...I see signals on waterfall....the level meter showing about 60%. But I get NO STATIONS showing up in the band activity pane! I havent made any changes to computer....all cables connected. The frequency on radio and WSJTX the same...everything looks OK but no band activity.....Any ideas where I should start looking?

I followed all the instructions received and now it is working without power output interruptions.

Thank you to everybody.

73, Yvon AE7YD


Monday, June 21, 2021, 5:20:43 PM, you wrote:

I've also seen WSJT-X stop producing TX audio on 2.4.0. I have the USB sleep turned off, which did help. It's an odd issue because my particular PC (Win10, up to date) has no physical connection to the rig. The audio has to get as far as the SmartSDR DAX process running on the same PC.

On 21/06/2021 19:56, Chris, HB9DFG wrote:

Hello Bill

I will try it via WETRANSFER so I see when it has been downloaded by you. The Link will stay on for about a week and you can
forward it to others who are interested for testing. Think your QRZ.com mail adress will be fine.
There will be two ZIPs, one with the WSJT-files and one with the JTDX-files, there is a "w" or a "j"in front of the usual timestamps
so you always know where the file is coming from.

I am very curious what you will find out :-)

Thank you very much for taking the time to investigate this and may be I will make some more tests in a not so crowded band with
weaker signals like on 2m or 6m.

Best regards de
Chris, HB9DFG

Hi Chris,

thanks for those .WAV files. I was under the impression that you had more information about which ones failed to decode certaon messages. If you do have a list of messages not decoded for each WSJT-X .WAV file you have provided that would be most helpful?

73
Bill
G4WJS.

On Tue, Jun 22, 2021 at 04:50 PM, Joe wrote:

Thanks for the additional information.  I can confirm this is a defect.  It will be fixed in the next release.

  -- 73, Joe, K1JT

Hi Joe
I also managed to invoke this "defect" last night on FT8  using V2.4.0
I manually changed TX5 to say "KV4BV JO02 73" but the actual transmitted message was "KV4BV JO02 60" as seen on my own yellow transmitted message box and by a friend who monitored it being sent on air. Guess I if I had tried to send G4NBS JO02 73 it would have behaved normally?

73
Tony G4NBS

Thanks for the prompt review and response, Joe. 

WSJT-X just keeps getting better!

73, Jim @ K5ND

Hi Jim,

On Mon, Jun 21, 2021 at 02:00 PM, Jim @ K5ND wrote:

Hi Joe,

Attached is the screen shot from the original QSO.

After the first three "60" messages, I used free text to send the other messages.  

Now when I type in WB8LYJ/R and press "generate std msgs" it shows "WB8LYJ/R 73" in the TX5 message, without my call sign. It then sends "WB8LYJ/R 60"

I've attached that screen shot as well. Hope those images shed some light on what I'm experiencing.

73, Jim @ K5ND

Thanks for the additional information.  I can confirm this is a defect.  It will be fixed in the next release.

  -- 73, Joe, K1JT

Hello Bill

I will try it via WETRANSFER so I see when it has been downloaded by you. The Link will stay on for about a week and you can
forward it to others who are interested for testing. Think your QRZ.com mail adress will be fine.
There will be two ZIPs, one with the WSJT-files and one with the JTDX-files, there is a "w" or a "j"in front of the usual timestamps
so you always know where the file is coming from.

I am very curious what you will find out :-)

Thank you very much for taking the time to investigate this and may be I will make some more tests in a not so crowded band with
weaker signals like on 2m or 6m.

Best regards de
Chris, HB9DFG

Hi Joe,

Attached is the screen shot from the original QSO.

After the first three "60" messages, I used free text to send the other messages.  

Now when I type in WB8LYJ/R and press "generate std msgs" it shows "WB8LYJ/R 73" in the TX5 message, without my call sign. It then sends "WB8LYJ/R 60"

I've attached that screen shot as well. Hope those images shed some light on what I'm experiencing.

73, Jim @ K5ND

Hi Jim,

On Mon, Jun 21, 2021 at 11:05 AM, Jim @ K5ND wrote:

I just worked WB8LYJ/R in FM25 on 6 meters using Q65 30A. After the RRR was received, WSJT sent "WB8LYJ/R 60" rather than the two call signs and 73. Even using the free text message, it would not send WB8LYJ/R. Instead I had to enter WB8LYJ K5ND 73 which it did send.

I was using version 2.4. WB8LYJ/R told me he was using version 2.5.

What's up? Rover curse?

Thanks for any insight.

Have you done anything to try to reproduce this issue?  I have not been able to reproduce it here. 

"WB8LYJ/R K5ND 73"  is a perfectly legitimate message, and as far as I can see it is generated, transmitted, and received correctly just like any other valid message in the "77-bit" WSJT-X modes (FST4, FT4, FT8, and Q65).

Please send us more details, if you believe something is wrong.

                    -- 73, Joe, K1JT