1. main@WSJTX.groups.io
  2. Messages
   Date   
locked watchdoc v2.4.0 #Cat_RigControl

Pietro Molina
 

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
locked WSJT-X Reporting to PSK Reporter #Beacons

invl160 Davis
 

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
locked (K)Ubuntu's slow UI response #linux #wsjt-x

Hans Fong
 

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
locked Help with not seeing band activity #WSJTX_config

w1av
 

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?
locked VS: [WSJTX] #Q65 Sending 60 rather than 73 #Q65

Reino Talarmo
 

Hi Joe,

 

I also noted that Q65 behaves differently than the other modes in the 77-bit family. Q65 leaves out my call e.g. in message “WB7LYJ/R OH3MA 73”, when it automatically generates that message resulting “WB7LYJ/R 73”. When I append my call into it, then it is sent properly. The omission is repeated, when I change mode to Q65 or reselect Q65. The correct form will be back changing mode to any other mode e.g. FT8.

I tested v2.5.0-rc1 68a3d4 in Windows 10 and v2.4.0 c19d62 in Windows 7.

 

73, Reino OH3mA

 

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

locked Re: No transmit after some time #FT8

Yvon AE7YD
 

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 Mon, Jun 21, 2021 at 11:07 AM Yvon AE7YD <Yvon@...> wrote:

 Thank you Bill,

this makes sense and I'll try it. I'll report later if it did solve the problem.

73, Yvon AE7YD


Monday, June 21, 2021, 3:02:54 AM, you wrote:

> On 21/06/2021 04:48, Yvon AE7YD wrote:
>> Hello,
>>
>> I apologize if this has already been covered but search didn't bring > it up.
>> After some time WSJT-X will stop sending audio. That time is variable. > If I close the program and restart it, it works again. But after a > while it will stop again.
>> All other functions keep working fine.
>> The problem is not related with the radio or the PC as I have tried > with two different PC (one running Win10  home and the other running > Win10 Pro).
>> I also tried with 4 different radios Omega 900, Elecraft KX2, FTDX10 > and DR-4020, same problem.
>>
>> Thank you for any help.
>>
>> 73, Yvon
> Hi Yvon,

> the issue you describe is often due to MS Windows deciding to power down USB audio devices it thinks are not being used. You must disable the power management options for each USB Hub Device listed in Windows Device Manager under "Universal Serial Bus Controllers" (right-click device, select Properties, then Power Management, and uncheck the allow option).

> You also must disable the USB Selective Suspend option in the Windows "Power Options->Change plans settings (on the current plan)->Change Advanced Power Settings" open "USB settings", then "USB selecting suspend setting", and click the "Plugged in" option to select Disabled.

> As Bob, G8HGN, points out, there is another issue with HDMI monitor connections. HDMI connections include a USB audio connection which too can be unexpectedly powered down when a screen-saver or power-saver function activates. I don't know of any settings to stop that other than making sure graphics card/chip power management settings for the monitor and screen saver are disabled, YMMV.

> The root problem is that USB devices are "hot-pluggable" and adding or removing a device, while the system is running, will cause all other devices to be re-enumerated, this can change device identities but Windows does not inform applications using them that they have been shuffled.

> Note this issue affects audio devices but not virtual serial ports like those often used for CAT control, virtual serial ports over USB connections seem to be capable of blocking such power saving options, presumably because they are one-to-one connections and Windows can be sure when they are in use.

> 73
> Bill
> G4WJS.



--
Best regards,
AE7YD


--
Best regards,
AE7YD
locked Re: WSJT Sensitivity V MSHV #why ?

Bill Somerville
 

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.
locked Re: #Q65 Sending 60 rather than 73 #Q65

Tony Collett
 

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
locked Re: #Q65 Sending 60 rather than 73 #Q65

Jim @ K5ND
 

Thanks for the prompt review and response, Joe. 

WSJT-X just keeps getting better!

73, Jim @ K5ND
locked Re: #Q65 Sending 60 rather than 73 #Q65

Joe
 

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
locked Re: #Q65 Sending 60 rather than 73 #Q65

Philip Rose
 

As a point of interest, what is the difference between /R and /M?

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Jim @ K5ND
Sent: 21 June 2021 22:00
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #Q65 Sending 60 rather than 73

 

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

 


--
73 Phil GM3ZZA
locked Re: #Cat_RigControl WSJT-X/IC7610 FT8 Bandwidth control #Cat_RigControl

Bruce N7XGR
 

Doug,  Tis a simple task to increase the RX bandwidth.
Be in USB-D1 or D2 or D3 mode
Press and hold the FILTER button
Tap the desired filter button, FIL1 or FIL2 or FIL3
Tap the BW button
Rotate the VFO knob clockwise to increase the bandwidth
Tap the BW button again
Save these settings to the SD card when done--IMPORTANT
The DATA mode has 3 totally adjustable filter bandwidths
which is the same as in regular USB mode.
3 DATA filter settings and 3 regular USB filter settings.


On Mon, Jun 21, 2021 at 2:47 AM Doug Grant <dougk1dg@...> wrote:
I suspect this has been cpvered but I cannot find anything by searching the archives.

I am using WSJT-X v2.4.0 with an IC7610, controlling everything through the USB port.

Everything works fine, but I want to run the radio receiver at 3 kHz bandwidth instead of 2.4 kHz.

If I manually tap the FILTER button on the radio, I can select 3 kHz, but as soon as WSJT-X makes a transmission, the radio switches back to 2.4 kHz.

I am using the radio in USB mode, and tried the Data/pkt setting instead, which puts the radio in USB-Dx mode and none of those modes have a 3 kHz BW option (they are all even narrower than 2.4 and I cannot figure out how to make one of them 3 kHz)..

I suspect there is a simple way to do this a few menu steps down on either the radio or WSJT-X but I cannot find it.

Any ideas?

Thanks & 73,

Doug K1DG,



locked Re: WSJT Sensitivity V MSHV #why ?

Chris, HB9DFG
 

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
locked Re: No transmit after some time #FT8

Brian Stucker
 

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 Mon, Jun 21, 2021 at 11:07 AM Yvon AE7YD <Yvon@...> wrote:
Thank you Bill,

this makes sense and I'll try it. I'll report later if it did solve the problem.

73, Yvon AE7YD


Monday, June 21, 2021, 3:02:54 AM, you wrote:

> On 21/06/2021 04:48, Yvon AE7YD wrote:
>> Hello,
>>
>> I apologize if this has already been covered but search didn't bring > it up.
>> After some time WSJT-X will stop sending audio. That time is variable. > If I close the program and restart it, it works again. But after a > while it will stop again.
>> All other functions keep working fine.
>> The problem is not related with the radio or the PC as I have tried > with two different PC (one running Win10  home and the other running > Win10 Pro).
>> I also tried with 4 different radios Omega 900, Elecraft KX2, FTDX10 > and DR-4020, same problem.
>>
>> Thank you for any help.
>>
>> 73, Yvon
> Hi Yvon,

> the issue you describe is often due to MS Windows deciding to power down USB audio devices it thinks are not being used. You must disable the power management options for each USB Hub Device listed in Windows Device Manager under "Universal Serial Bus Controllers" (right-click device, select Properties, then Power Management, and uncheck the allow option).

> You also must disable the USB Selective Suspend option in the Windows "Power Options->Change plans settings (on the current plan)->Change Advanced Power Settings" open "USB settings", then "USB selecting suspend setting", and click the "Plugged in" option to select Disabled.

> As Bob, G8HGN, points out, there is another issue with HDMI monitor connections. HDMI connections include a USB audio connection which too can be unexpectedly powered down when a screen-saver or power-saver function activates. I don't know of any settings to stop that other than making sure graphics card/chip power management settings for the monitor and screen saver are disabled, YMMV.

> The root problem is that USB devices are "hot-pluggable" and adding or removing a device, while the system is running, will cause all other devices to be re-enumerated, this can change device identities but Windows does not inform applications using them that they have been shuffled.

> Note this issue affects audio devices but not virtual serial ports like those often used for CAT control, virtual serial ports over USB connections seem to be capable of blocking such power saving options, presumably because they are one-to-one connections and Windows can be sure when they are in use.

> 73
> Bill
> G4WJS.



--
Best regards,
AE7YD
locked Re: #Q65 Sending 60 rather than 73 #Q65

Jim @ K5ND
 

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
locked Re: #Q65 Sending 60 rather than 73 #Q65

Joe
 

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
locked Re: ALL.TXT Append Error #FT8 #IssueReport

Alan N5NA
 

Ok. The other possibility on my error was a backup was being executed at the time the append operation happened and causing the error about the file being in use. Starting a new file speeded up the backup. 
locked Re: ALL.TXT Append Error #FT8 #IssueReport

William Smith
 

When my ALL.TXT exceeds 100M I usually split it up, but only to make searching easier. I've had it at least to 279M without problems, so it's likely you corrupted something than the file got too big.

73, Willie N1JBJ

On Jun 21, 2021, at 2:42 PM, Alan N5NA <alan.n5na@...> wrote:

I was getting this error as well. I found my ALL.txt file was 68 MB so I renamed it and let WSJT-X create a new ALL.txt file. Since doing that I haven't had any more errors.

locked Re: ALL.TXT Append Error #FT8 #IssueReport

Alan N5NA
 

I was getting this error as well.  I found my ALL.txt file was 68 MB so I renamed it and let WSJT-X create a new ALL.txt file.  Since doing that I haven't had any more errors.
locked Re: No transmit after some time #FT8

Yvon AE7YD
 

Thank you Bill,

this makes sense and I'll try it. I'll report later if it did solve the problem.

73, Yvon AE7YD


Monday, June 21, 2021, 3:02:54 AM, you wrote:

On 21/06/2021 04:48, Yvon AE7YD wrote:
Hello,

I apologize if this has already been covered but search didn't bring > it up.
After some time WSJT-X will stop sending audio. That time is variable. > If I close the program and restart it, it works again. But after a > while it will stop again.
All other functions keep working fine.
The problem is not related with the radio or the PC as I have tried > with two different PC (one running Win10  home and the other running > Win10 Pro).
I also tried with 4 different radios Omega 900, Elecraft KX2, FTDX10 > and DR-4020, same problem.

Thank you for any help.

73, Yvon
Hi Yvon,
the issue you describe is often due to MS Windows deciding to power down USB audio devices it thinks are not being used. You must disable the power management options for each USB Hub Device listed in Windows Device Manager under "Universal Serial Bus Controllers" (right-click device, select Properties, then Power Management, and uncheck the allow option).
You also must disable the USB Selective Suspend option in the Windows "Power Options->Change plans settings (on the current plan)->Change Advanced Power Settings" open "USB settings", then "USB selecting suspend setting", and click the "Plugged in" option to select Disabled.
As Bob, G8HGN, points out, there is another issue with HDMI monitor connections. HDMI connections include a USB audio connection which too can be unexpectedly powered down when a screen-saver or power-saver function activates. I don't know of any settings to stop that other than making sure graphics card/chip power management settings for the monitor and screen saver are disabled, YMMV.
The root problem is that USB devices are "hot-pluggable" and adding or removing a device, while the system is running, will cause all other devices to be re-enumerated, this can change device identities but Windows does not inform applications using them that they have been shuffled.
Note this issue affects audio devices but not virtual serial ports like those often used for CAT control, virtual serial ports over USB connections seem to be capable of blocking such power saving options, presumably because they are one-to-one connections and Windows can be sure when they are in use.
73
Bill
G4WJS.
--
Best regards,
AE7YD
9601 - 9620 of 35397