Date   

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

 

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


locked Re: No transmit after some time #FT8

Yvon AE7YD
 

Thank you Bob,

On one of my computers, the Win10 Home it is already set to not go in sleep mode and the Win10 Pro which is my work computer doesn't go in sleep mode because I am always using it.
However I'll set up this one too to not go in sleep mode.

Any suggestions on which key words to search for as my search didn't return anything?

73, Yvon AE7YD



Monday, June 21, 2021, 12:35:59 AM, you wrote:


Hi Yvon,
 
There have been several threads on this type of problem. You just need to find the right keywords in search.
 
However, I had a similar problem a couple of years ago now and it turned out to be related to USB and a HDMI monitor. Apparently HDMI has an interaction with USB and can exhibit these smyptoms.
 
My cure was to never allow the monitor to sleep by altering the settings in windows(10). Since doing that I haven't had a re-occurance.
 
This may not be your issue but worth a try if your have HDMI. Otherwise you'll have to trawl the archives for other solutions.
 
HTH 73 Bob G8HGN
 
 

Sent: Monday, June 21, 2021 at 4:48 AM
From:
 "Yvon AE7YD " <Yvon@...>
To:
 main@WSJTX.groups.io
Subject:
 [WSJTX] No transmit after some time #FT8
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


--
Best regards,
AE7YD


locked Re: WSJT Sensitivity V MSHV #why ?

Derek Brown
 

Thanks to all who have picked up on this subject, at this point I am afraid I will declare myself out of the ongoing discussion, as I am about to move homes, and the chances of me getting back on 6M Es before next June are pretty slim, let alone any time after today, soon to have a unknown period of enfored non-operation, until I have a shack to setup in and antenna to connect to.

73 all derek G8ECI signing off from JO03 square to qsy 15km north to IO93

On Monday, 21 June 2021, 15:36:21 BST, Bill Somerville <g4wjs@...> wrote:


On 20/06/2021 17:55, Chris, HB9DFG wrote:
Hello all

With interest I have read through this thread and I thought to myself: why shouldn't I test this as well with JTMS, since I assumed that all other
programmes concerning the FT8 decoder should actually react in the same way. I once compared an older Version of MSHV but it lost a lot
of decodes compared with WSJT-X so I did not tried anew since then.

Well, I now have tested JTDX 2.2.156 and WSJT-X 2.4.0c19d62 a short time (for about 30-40min) on a quiet 2m-band. The computer is still a
WIN7-machine with 8GB RAM and an onboard Realtek audiocard set to the 16bit 48000kHz DVD system. BKTIMESYNC is in use here als well.

WSJT-Xs decoder was set to "deep" and "AP", JTDXs decoder was set to: threats=auto, decoder cycles=1, decoder sensitivity=use low thesholds

Besides the good decodes on both programs (with big differences in the dB values), I took out 13 wave files where either WSJT-X or JTDX did not
decode something.

Results:

- All in all I have picked one periode where WSJT-X had 3 decodes (include one a1), and FTDX got 2 of them. Both programmes were able to read the
   corresponding other wave files of this periode where JTDX couldn't read the "a priori" decode.
- An other periode got 2 decodes on JTDX and one on WSJT-X
- Also one periode got 1 decode on WSJT-X and no decode on JTDX
- The rest of the periods (10) got 1 decode on JTDX and no decode on WSJT-X
- WSJT-X could read JTDXs only no-decode
- JTDX could read 5 of WSJT-Xs 10 no-decodes

Maybe if time permits I will try to make an other test with my other W10-computer with the "soundcard" of my IC-9700.

Bill Somerville wrote earlier:
"...the only way to analyze the issue you report is for you to provide a .WAV file recorded by WSJT-X along with a list of the messages that you think
should have been decoded. Anything else is simply subjective speculation."


Fine Bill, did you already got such files to investigate and did you found out something interesting? Or would you like to get my wav-files to investigate?
If yes, where can I sent them as zipped files?

Best regards de
Chris, HB9DFG

Hi Chris,

thanks for doing this objective analysis work, the examples would be very useful. Do you have any free Cloud storage accounts like Dropbox, Google Drive, One Drive, etc. where you can upload the files and provide a download link?

73
Bill
G4WJS.





locked #Q65 Sending 60 rather than 73 #Q65

Jim @ K5ND
 

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.

73, Jim @ K5ND and sometimes K5ND/R


locked Q65 Sending 60 instead of 73 #Q65

Jim @ K5ND
 

Sent this earlier, but hasn't yet shown up, so trying again.

I worked WB8LYJ/R in grid FM25 on 6 meters Q65 at 50.275 Mode 30A. Received his RRR but then WSJT-X version 2.4 sent "WB8LYJ/R 60" rather than both call signs and 73.

Tried to use free text to enter the right message. It would not accept WB8LYJ/R - sending only the call sign and 60 - when entering "WB8LYJ K5ND 73" that worked.

WB8LYJ/R reported that he was using version 2.5. I was using version 2.4.

What's up? Rover curse? Thanks for any insight.

73, Jim @ K5ND and sometimes K5ND/R


locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

Ray
 

I agree. I am using Mac installed drivers with no issues, IC 7100 and IC 7300. When I upgraded the Mac OS it uninstalled the previous drivers that are no longer needed. RUMlogNG 

Ray
W8LYJ


locked Q65 sending 60 instead of 73 #Q65

Jim @ K5ND
 

This morning I worked WB8LYJ/R on 6 meters Q65-30A. Got the signal report and the RRR but when WJST tried to send 73 instead it sent "WB8LYJ/R 60"   Image of QSO attached. 

I tried various free text messages and the only one that would work was sending the call sign without the /R. 

I'm running version 2.4 and WB8LYJ was running version 2.5. That could be one source of the problem. 

What's up? Curse of rovers? Thanks for any insight.

73, Jim @ K5ND and often times K5ND/R

12281 - 12300 of 38067