That's great, many thanks Bill.

73, Richard, G4KRW

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

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

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

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

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.

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

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.

Which radio is yours?

Inviato da iPhone
Bruno Peticone

--
Bruno Peticone, IU0OAD

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:


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

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

TU es 73 de Bob KD2NFS 

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.

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

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