Date   

locked VS: VS: [WSJTX] Copy And Paste Not Working #general

Reino Talarmo
 

Hi David,

You explained that behaviour completely, thanks!
Well, there could be a lot of other minor issues WSJT-X could do better, but once your know what is happening you should just “obey” the “rules”, I think.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta David - AK2L
Lähetetty: 09 May 2021 02:41
Vastaanottaja: main@WSJTX.groups.io
Aihe: Re: VS: [WSJTX] Copy And Paste Not Working #general

 

Hi Reino,
Thanks for responding.  To answer your question... Yes, I can paste into Notepad just fine.
I think I see the problem.  Perhaps you can test this to see if you get the same behavior.
If I select a call sign with an extra space such as "3D2ZK ", copy it to the clipboard, and then try to paste it into WSJT-X, it fails to paste.
If instead I select a call sign with no extra spaces such as "3D2ZK", it seems to work.
Perhaps the clipboard handler in WSJT-X could be more forgiving by trimming whitespace off of the text rather than rejecting it completely.
AK2L, David


locked Re: Detected dropped audio source samples and Syslog #AudioIssues #logging

Richard Waterman
 

That's great, many thanks Bill.

73, Richard, G4KRW


locked Re: T/R 30s seems to be a default now in -RC4 #MSK144 #Q65

NR4U Bob AFMARS
 

Hello Bill,
Saturday, May 8, 2021, 6:10:10 AM, you wrote:
----------------------------------------------------

Hi Bob,
where different parameters are used for different bands and/or
modes we would always recommend using configurations
----------------------------------------------------
Thanks Bill, and others, especially Gary too(blushing_shy), I am setting up the configurations now.
And Like Roger, I will have at least 12, hi hi ...three rigs plus the SDR-for-RX variations

again, thanks for the reply(s)


--
Best regards,
Bob KD7YZ



--
--
Bob KD7YZ in NE Kentucky


locked Re: No PWR out on Tx #FT8

DF3ED
 

Hello Bob,

I see the same effect when I push the tune button before.
In the windows sound window I see that sound output
switches to the time when wsjt is in receive state and
sound output stops when wsjt switches to transmit state.
It is an inversion .....

Restart of wsjt without using tune button normaly helps me.

I think it is a bug .....
--

73 de DF3ED
Peter


locked WSJT-X Windows - FT-891 Data Mode doesn't receive any signals - Audio sound like broken speaker #FT8 #Yaesu

N3JF
 

The following is all about FT8 on the FT-891:

When I run the Windows latest version of WSJT-X and configure it to talk directly to my FT-891 through a Signalink USB, it works great when the communication mode is set to USB.

If I change the mode to Data/Pkt in WSJT-X, the audio coming from the radio's speaker becomes very quiet. If I turn it up, the audio sounds like a broken speaker... popping and crackling. The received audio tone out of the speaker is very low. Transmit audio sounds fine. When WSJT-X transmits, it'll adjust the TX frequency according to the TX frequency set in the Waterfall, but it doesn't always properly RESET it to 7.040MHz. When this happens, the transmitter "walks down the band".

If I configure WSJT-X to use FLRig and Data/Pkt mode, and set FLRig to use DATA-U, I hear more normal FT8 tone, but they're considerably more "muffled". In fact, I don't think I've made a single contact using DATA mode!

If I configure both FLRig and WSJT-X to use USB, I make contacts all day long.... However... when the radio first keys up, the microphone is live for about 1/4 - 1/2 a second and I can hear room noise/feedback while listening to my transmitted audio on another radio.  If I configure WSJT-X to talk directly to the FT-891 (no FLRig involved), the same thing happens... unless I configure WSJT-X to use RTS for PTT (RTS is disabled in the radio menu). I cannot do the same thing when using FLRig as all the available ports give me an error message.

Why doesn't WSJT-X work when it's connected directly to the FT-891 in DATA mode (deep popping/crackling audio from the speaker, WSJT-X doesn't hear ANY signals)?

Why does WSJT-X keep the mic live for a short period in USB mode before it starts transmitting FT8 tones?

Why does WSJT-X (intermittently, but very frequently) not correctly restore the radio to the correct receive frequency after transmitting?

I appreciate any help!

73


locked Re: VS: [WSJTX] Copy And Paste Not Working #general

David - AK2L
 

Hi Reino,
Thanks for responding.  To answer your question... Yes, I can paste into Notepad just fine.
I think I see the problem.  Perhaps you can test this to see if you get the same behavior.
If I select a call sign with an extra space such as "3D2ZK ", copy it to the clipboard, and then try to paste it into WSJT-X, it fails to paste.
If instead I select a call sign with no extra spaces such as "3D2ZK", it seems to work.
Perhaps the clipboard handler in WSJT-X could be more forgiving by trimming whitespace off of the text rather than rejecting it completely.
AK2L, David


locked Re: Loss of QSO data when logging previous QSO. #logging #IssueReport

 

Thanks Bill, I doubled clicked the partner’s report and that doesn’t populate the DX Grid. I have a personal problem that I can’t always double-click fast enough.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bill Somerville
Sent: 08 May 2021 18:20
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Loss of QSO data when logging previous QSO. #logging #BugReport

 

On 07/05/2021 15:31, Philip Rose via groups.io wrote:

> I have had the following scenario a couple of times. When I am completing a QSO, I send RR73 and wait for the QSO partner to either repeat his report, send 73 or send nothing before logging the QSO. If I am called by another station, I double click on that to start the QSO. I then log the first QSO. When I log it the DX Call and DX Grid of the second station are removed and the auto-sequencing stops.

> Is there a way to stop the act of logging from removing the details OF A NEW QSO.

> -- 73 Phil GM3ZZA

 

Hi Phil,

 

"Settings->Reporting->Clead DX call and grid after logging" controls

that behaviour. OTOH you can always double-click the message from the

second caller again to restart the sequencing with correct details.

 

73

Bill

G4WJS.

 

 


--
73 Phil GM3ZZA


locked Re: Detected dropped audio source samples and Syslog #AudioIssues #logging

Bill Somerville
 

On 08/05/2021 17:42, Richard Waterman wrote:
Hello,

I would be grateful if someone could answer a couple of questions for me:

Summary:
1. Am I right in believing that wsjtx_syslog.log started life when wsjt-x 2.3.0 was released?
2. Looking at the Syslog file, I see that I am getting frequent warnings "Detected dropped audio source samples".  What is the likely cause? Why do some warnings have a negative number?

Detail behind my questions:
I am running Windows 10 Pro, latest update on an i&-6700T processor with 16Gb RAM
Processor load rarely exceeds 20% loading (as seen using task manager) and is typically 4-5%
Running wsjt-x 2.3.1
Running latest JTAlert
Running Omnirig
Running Task Manager
Running TeamViewer
Other than that, just background Windows processes.

Warnings occur even with only a couple of stations received on an afternoon 80m band
Here is a short sample from earlier today:

[SYSLOG][2021-05-08 14:25:44.385395][64:53:48.030945][warning] Detected dropped audio source samples: -672 (-0.014 S)
[SYSLOG][2021-05-08 14:25:59.398520][64:54:03.043840][warning] Detected dropped audio source samples: 624 (0.013 S)
[SYSLOG][2021-05-08 14:27:59.400122][64:56:03.044920][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:28:59.398204][64:57:03.042325][warning] Detected dropped audio source samples: 480 (0.01 S)
[SYSLOG][2021-05-08 14:32:44.400249][65:00:48.043285][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:32:59.389673][65:01:03.032795][warning] Detected dropped audio source samples: -528 (-0.011 S)
[SYSLOG][2021-05-08 14:33:44.401526][65:01:48.044568][warning] Detected dropped audio source samples: 528 (0.011 S)
[SYSLOG][2021-05-08 14:37:44.390367][65:05:48.031884][warning] Detected dropped audio source samples: -480 (-0.01 S)
[SYSLOG][2021-05-08 14:45:29.392119][65:13:33.030680][warning] Detected dropped audio source samples: -480 (-0.01 S)

Radio is a KX3 interfaced via a ZLP Electronics USB Data interface with built in soundcard.
Radio left monitoring on receive 24/7.  No transmission, so there is no Rx/Tx switching

With regards to my syslog question, I occasionally look in the wsjt-x log directory (usually when I think ALL.txt might be getting a bit large) and this time noticed wsjtx_syslog.log.  Not seen that before.  Looking through release notes, I see a mention of additional logging in the notes for 2.3.0_rc2.  I installed 2.3.0 on 5th Feb 2021 and the earliest syslog file I have starts entries from 5th Feb.  There are three syslog files stored in the logs subdirectory of the log directory, dated 01 March 2021, 01 April 2021 and 01 May 2021.  The current syslog file is in the base log directory and is updated dynamically as warnings occur. Presumably, it will be saved to the logs directory on 01 June 2021.

Additional syslog questions: how many files will be kept before "rotation" occurs, as mentioned in the release notes and how do I configure what is logged?  I can't find anything in the user guide.

Would really appreciate any info.

73, Richard, G4KRW
Hi Richard,

small numbers like that can be ignored, we had to set the cut off somewhere. Negative numbers indicate more samples than expected. The counts are for each period of the current mode, there is never an exact expected count due to latencies between soundcard and software. In summary, you have nothing to worry about, if the discrepancies are of the order of 0.5 seconds and happen often then you would have a problem with your audio streaming throughput or system timekeeping.

Log files are rotated monthly or if they exceed a certain size, old rotated logs are deleted. IIRC 12 old logs are kept, the total amount of log data will be small. There are options to increase the logging verbosity using a configuration file, but for most users the default with no logging configuration file will be fine.

73
Bill
G4WJS.


locked Re: T/R 30s seems to be a default now in -RC4 #MSK144 #Q65

Gary - AG0N
 

On May 7, 2021, at 04:35, KD7YZ Bob <kd7yz@...> wrote:

Can't we have Q65 default to 30s and MSK144 always default to 15s when we touch the mode choice?
Thirty seconds is the normal time for MSK144.

Gary - AG0N


locked Re: No PWR out on Tx #FT8

JoAnn Donaldson <joannplano2005@...>
 

Have you selected the audio from your radio in the app. Also have you selected the TX audio to your radio? Have you setup PTT? These are the three items that you have to have setup for the App to work and for your radio to work.
Some radios have built in interfaces like the Flex Radio does. Other radios require an Sound Card Interface box that goes between your Radio and your computer.
To fully help you, we need to know what kind of radio you have, do you have a Sound Card Interface and etc.

JoAnn
AB8YZ


On Saturday, May 8, 2021, 4:50:12 PM CDT, Bill Somerville <g4wjs@...> wrote:


On 08/05/2021 12:34, Robert Necci KD2NFS wrote:
> All my FT8 settings appear to be correct, but no pwr out on the radio.
> Suggestions appreciated.
>
> TU es 73 de Bob KD2NFS

Bob,

more contextual information appreciated please?


73

Bill
G4WJS.






locked Re: No PWR out on Tx #FT8

Bill Somerville
 

On 08/05/2021 12:34, Robert Necci KD2NFS wrote:
All my FT8 settings appear to be correct, but no pwr out on the radio. Suggestions appreciated.

TU es 73 de Bob KD2NFS
Bob,

more contextual information appreciated please?

73
Bill
G4WJS.


locked Re: No PWR out on Tx #FT8

Arnold Lausevich <nk9o@...>
 

Speaker set to Codex?



Sent from my Samsung Galaxy , an AT&T LTE smartphone


-------- Original message --------
From: Robert Necci KD2NFS <Kd2nfs@...>
Date: 5/8/21 12:20 PM (GMT-06:00)
To: main@WSJTX.groups.io
Subject: [WSJTX] No PWR out on Tx #FT8

All my FT8 settings appear to be correct, but no pwr out on the radio. Suggestions appreciated.

TU es 73 de Bob KD2NFS 


locked Re: No PWR out on Tx #FT8

Bruno Peticone
 

Which radio is yours?

Inviato da iPhone
Bruno Peticone

Il giorno 8 mag 2021, alle ore 19:20, Robert Necci KD2NFS <Kd2nfs@...> ha scritto:

All my FT8 settings appear to be correct, but no pwr out on the radio. Suggestions appreciated.

TU es 73 de Bob KD2NFS

--
Bruno Peticone, IU0OAD


locked Detected dropped audio source samples and Syslog #AudioIssues #logging

Richard Waterman
 

Hello,

I would be grateful if someone could answer a couple of questions for me:

Summary:
1. Am I right in believing that wsjtx_syslog.log started life when wsjt-x 2.3.0 was released?
2. Looking at the Syslog file, I see that I am getting frequent warnings "Detected dropped audio source samples".  What is the likely cause? Why do some warnings have a negative number?

Detail behind my questions:
I am running Windows 10 Pro, latest update on an i&-6700T processor with 16Gb RAM
Processor load rarely exceeds 20% loading (as seen using task manager) and is typically 4-5%
Running wsjt-x 2.3.1
Running latest JTAlert
Running Omnirig
Running Task Manager
Running TeamViewer
Other than that, just background Windows processes.

Warnings occur even with only a couple of stations received on an afternoon 80m band
Here is a short sample from earlier today:

[SYSLOG][2021-05-08 14:25:44.385395][64:53:48.030945][warning] Detected dropped audio source samples: -672 (-0.014 S)
[SYSLOG][2021-05-08 14:25:59.398520][64:54:03.043840][warning] Detected dropped audio source samples: 624 (0.013 S)
[SYSLOG][2021-05-08 14:27:59.400122][64:56:03.044920][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:28:59.398204][64:57:03.042325][warning] Detected dropped audio source samples: 480 (0.01 S)
[SYSLOG][2021-05-08 14:32:44.400249][65:00:48.043285][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:32:59.389673][65:01:03.032795][warning] Detected dropped audio source samples: -528 (-0.011 S)
[SYSLOG][2021-05-08 14:33:44.401526][65:01:48.044568][warning] Detected dropped audio source samples: 528 (0.011 S)
[SYSLOG][2021-05-08 14:37:44.390367][65:05:48.031884][warning] Detected dropped audio source samples: -480 (-0.01 S)
[SYSLOG][2021-05-08 14:45:29.392119][65:13:33.030680][warning] Detected dropped audio source samples: -480 (-0.01 S)

Radio is a KX3 interfaced via a ZLP Electronics USB Data interface with built in soundcard.
Radio left monitoring on receive 24/7.  No transmission, so there is no Rx/Tx switching

With regards to my syslog question, I occasionally look in the wsjt-x log directory (usually when I think ALL.txt might be getting a bit large) and this time noticed wsjtx_syslog.log.  Not seen that before.  Looking through release notes, I see a mention of additional logging in the notes for 2.3.0_rc2.  I installed 2.3.0 on 5th Feb 2021 and the earliest syslog file I have starts entries from 5th Feb.  There are three syslog files stored in the logs subdirectory of the log directory, dated 01 March 2021, 01 April 2021 and 01 May 2021.  The current syslog file is in the base log directory and is updated dynamically as warnings occur. Presumably, it will be saved to the logs directory on 01 June 2021.

Additional syslog questions: how many files will be kept before "rotation" occurs, as mentioned in the release notes and how do I configure what is logged?  I can't find anything in the user guide.

Would really appreciate any info.

73, Richard, G4KRW


locked Re: #WSJTX_config BS188 MC-HF RS918 Clone config info for WJST-X? #WSJTX_config

Casimir Schesky <cfschesky@...>
 

Bill,

I believe I have tried those settings as one YouTube videos used the Yaesu 817 base settings and I copied it, but I will try again. I may have gotten something wrong. 
73 Casey KE8PFA 

On Sat, May 8, 2021, 6:23 AM Bill Somerville <g4wjs@...> wrote:
On 07/05/2021 20:42, Casimir Schesky wrote:
Hello,
Thank you for accepting me into this group.

I have been using WSJT-X on an IC7300 for about 3 months and it is fantastic software!  
Recently I bought a MC-HF RS918 SDR radio clone, called a B188, for QRP use in the field. I would like to use it with WSJT-X and have seen a number of YouTube videos using examples of this clone working with WSJT-X and also HRD. The settings folks are using in these videos don't seem to work for me with this radio, but I am a newbie and not a wizard by any means so I could be missing something.

Can anyone tell me what settings to use with this radio to integrate with USB to WSJT-X? I have enclosed a couple of pictures for more information.  The sign-on screen at boot up for this SDR radio says the following:

"BS188 Transceiver
Hardware License:  cc  by-nc-sa 3.0
K. Antanassov, MONKA, www.m0nka.co.uk
Version 2.12.00
Firmware License: GNU GPLv3"

Any help would be greatly appreciated!

73 and thanks,

Casey Schesky KE8PFA

Hi Casey,

the mcHF emulates a Yaesu FT-817 fro CAT control, I suspect your BS188 is similar. Have you tried selecting "Settings->Radio-Rig->Yaesu FT-817" an "Settings->Radio->PTT Method->CAT" along with suitable serial port parameters like baud rate?

73
Bill
G4WJS.





locked No PWR out on Tx #FT8

Robert Necci KD2NFS
 

All my FT8 settings appear to be correct, but no pwr out on the radio. Suggestions appreciated.

TU es 73 de Bob KD2NFS 


locked Re: Loss of QSO data when logging previous QSO. #logging #IssueReport

Bill Somerville
 

On 07/05/2021 15:31, Philip Rose via groups.io wrote:
I have had the following scenario a couple of times. When I am completing a QSO, I send RR73 and wait for the QSO partner to either repeat his report, send 73 or send nothing before logging the QSO. If I am called by another station, I double click on that to start the QSO. I then log the first QSO. When I log it the DX Call and DX Grid of the second station are removed and the auto-sequencing stops.

Is there a way to stop the act of logging from removing the details OF A NEW QSO.
-- 73 Phil GM3ZZA
Hi Phil,

"Settings->Reporting->Clead DX call and grid after logging" controls that behaviour. OTOH you can always double-click the message from the second caller again to restart the sequencing with correct details.

73
Bill
G4WJS.


locked VS: [WSJTX] Loss of QSO data when logging previous QSO. #IssueReport #logging

Reino Talarmo
 

Uncheck " Clear DX call and grid after logging " at Reporting tab.
73, Reino OH3mA

-----Alkuperäinen viesti-----
Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta Philip Rose via groups.io
Lähetetty: 07 May 2021 17:32
Vastaanottaja: main@WSJTX.groups.io
Aihe: [WSJTX] Loss of QSO data when logging previous QSO. #logging #BugReport

I have had the following scenario a couple of times. When I am completing a QSO, I send RR73 and wait for the QSO partner to either repeat his report, send 73 or send nothing before logging the QSO. If I am called by another station, I double click on that to start the QSO. I then log the first QSO. When I log it the DX Call and DX Grid of the second station are removed and the auto-sequencing stops.

Is there a way to stop the act of logging from removing the details OF A NEW QSO.
--
73 Phil GM3ZZA


locked VS: [WSJTX] WATERFALL DISPLAY #FT8

Reino Talarmo
 

Bins/pixel and actual window size.

N Avg 2

See User Guide 10.6.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta RICHARD LEHR
Lähetetty: 07 May 2021 16:46
Vastaanottaja: main@WSJTX.groups.io
Aihe: [WSJTX] WATERFALL DISPLAY #FT8

 

When running FT8 when I go to the waterfall display it shows up in the left hand corner upper and displays from 200 to 1145 hz on thescreen. Also itisvery slow. HowcanI expand the screen and speed up the waterfall?
Tnx- W3EK
W3EK@...


locked Re: T/R 30s seems to be a default now in -RC4 #MSK144 #Q65

roger.corbett@...
 

Ho Bob,
Have had a similar problem with the default TX frequency not staying at 1000Hz.
Best option for this would be to setup a configuration with all your defaults settings.
In my case I had to have the Settings->General-> Behaviour “Monitor returns to last used frequency” checkbox checked.
In fact you have to go through all your Configurations and make sure they all have the checked box checked. You only have to do this once and then it sticks.

To make a new configuration go to the “Configurations” menu, select “Default” and then “Clone’ from the menu extension.
Make all the setting you need and then its done no need to save anything but you should change the name of the configuration so you can remember which one to select.
Then to switch modes you just select the configuration from the list in the configuration menu.

Works well for me so hope that helps.
I currently have about 10-12 configurations!

73

Roger ZL3RC

On 7/05/2021, at 10:35 PM, KD7YZ Bob <kd7yz@...> wrote:

I switch modes on 6m and 2m quite a few times.

Lately I notice that, all too often, I am calling CQ on MSK144 but with 30s T/R time.

Sometimes I remember to check. But this morning right after I turned the rig on and selected MSDK144 on -RC4, I began calling CQ on MSK144.

About 3 minutes later I realized I was again in a 30s T/R series.

Can't we have Q65 default to 30s and MSK144 always default to 15s when we touch the mode choice?

All this only began after the introduction of Q65 choices. Well, at least in my cob-webby brain anyway.

'Defaults' are great. Use defaults for all the modes.



--
--
Bob KD7YZ in NE Kentucky


12461 - 12480 of 36948