WSJTX FT8 intermittent decode of my call on receive #FT8 #help


ka2qit
 

FT8 time sync is correct, however when station returns to my call software in monitor mode does not always recognize my call sign. They keep calling me! I have reinstalled the program, no change. The software was operating correctly for several years. I am using latest version. Any ideas? Tnx and 73 de Bob KA2QIT


Reino Talarmo
 

FT8 time sync is correct, however when station returns to my call software in monitor mode does not always recognize my call sign. They keep calling me! I have reinstalled the program, no change. The software was operating correctly for several years. I am using latest version. Any ideas? Tnx and 73 de Bob KA2QIT

Hi Bob,

Your need to present your WSJT-X settings and an example of that situation before we can help you. Especially are you sure the most relevant boxes Auto Seq and perhaps Call 1st are checked?

73, Reino OH3mA


Dave Garber
 

sounds like auto seq is not on, I would check it.
Dave Garber
VE3WEJ / VE3IE


On Sat, Nov 20, 2021 at 6:04 PM ka2qit via groups.io <ka2qit=yahoo.com@groups.io> wrote:
FT8 time sync is correct, however when station returns to my call software in monitor mode does not always recognize my call sign. They keep calling me! I have reinstalled the program, no change. The software was operating correctly for several years. I am using latest version. Any ideas? Tnx and 73 de Bob KA2QIT



ka2qit
 

I reset to default parameters, same issue. auto seq box checked, tx even/1st. unchecked, hold tx freq unchecked, call 1st unchecked. Decode deep. dot/on. I am baffled by this. It must be frustrating to those responding to my call. I've been working FT8 for several yrs. now w/o issue, until now!. Xcvr Icom 718, rigblaster nomic, Dell Inspiron 560, win 7 pentium 3.2 ghz 64 bit, 265 of 450 gb free, 4gb of ram installed. Thanx for ur help all, Bob KA2QIT


Tom Melvin
 

Call 1st - Tick it

  • Call 1st enables automatic response to the first decoded responder to your CQ

    If not ticked - as in your case it is up to you to decide who to answer.

    Regards

    Tom
    GM8MJV


On 22 Nov 2021, at 00:22, ka2qit via groups.io <ka2qit@...> wrote:

I reset to default parameters, same issue. auto seq box checked, tx even/1st. unchecked, hold tx freq unchecked, call 1st unchecked. Decode deep. dot/on. I am baffled by this. It must be frustrating to those responding to my call. I've been working FT8 for several yrs. now w/o issue, until now!. Xcvr Icom 718, rigblaster nomic, Dell Inspiron 560, win 7 pentium 3.2 ghz 64 bit, 265 of 450 gb free, 4gb of ram installed. Thanx for ur help all, Bob KA2QIT





Reino Talarmo
 

I reset to default parameters, same issue. auto seq box checked, tx even/1st. unchecked, hold tx freq unchecked, call 1st unchecked. Decode deep. dot/on. I am baffled by this. It must be frustrating to those responding to my call. I've been working FT8 for several yrs. now w/o issue, until now!. Xcvr Icom 718, rigblaster nomic, Dell Inspiron 560, win 7 pentium 3.2 ghz 64 bit, 265 of 450 gb free, 4gb of ram installed. Thanx for ur help all, Bob KA2QIT

Hi Bob,
I am also baffled by your description of the situation. Your stated in the original post:
FT8 time sync is correct, however when station returns to my call software in monitor mode does not always recognize my call sign. They keep calling me!
Now what you mean by the “returns to my call”? Do you mean that you are calling CQ or you have answered to their CQ?
If the first situation, then your setting Call 1st should be checked. If the latter, then I am lost.
73, Reino OH3mA
 
 


ka2qit
 

I am replying to their cq call. A strong received sig. -1, 0, +1 software does not recognize my call sign on target station reply. Normally my call sign goes red. (?) Bob ka2qit


Bill Somerville
 

On 22/11/2021 13:15, ka2qit via groups.io wrote:
I am replying to their cq call. A strong received sig. -1, 0, +1 software does not recognize my call sign on target station reply. Normally my call sign goes red. (?) Bob ka2qit
Hi Bob,

please provide an extract from your ALL.TXT file (found in the WSJT-X log files directory "Menu->File->Open log directory") that covers an example of this behaviour?

73
Bill
G4WJS.


ka2qit
 

Bill, In this sequence W0QU replied to my call, it took me a couple of passes before he came up as red. When i replied I did not receive his acknowledgement . initially. Signal strength was good on both. Pse see below: 

211122_215030    14.074 Rx FT8      7  0.1 1046 CQ W0QU EM48
211122_215045    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215115    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215145    14.074 Rx FT8    -13  0.2 1138 VE2IM N0BEL EN34
211122_215200    14.074 Rx FT8    -10  0.1 1048 KA2QIT W0QU -10
211122_215200    14.074 Rx FT8    -16  0.1 1510 CQ KE5CDE EM10
211122_215200    14.074 Rx FT8    -18  0.1 1497 VE2FYZ N5LWL -07
211122_215215    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT R-10
211122_215245    14.074 Rx FT8    -10  0.2 1140 CQ N0BEL EN34
211122_215300    14.074 Rx FT8     -7  0.1 1435 VE3OKD K5EW EM40
211122_215300    14.074 Rx FT8    -12  0.1 1512 CQ KE5CDE EM10
211122_215300    14.074 Rx FT8    -19  0.1 1050 KA2QIT W0QU RRR
211122_215300    14.074 Rx FT8    -17  0.2 1488 KB4FHU W0GMV EM28
211122_215315    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT 73


Dave Garber
 

I see he start being heard at +7, but by the time you were able to finish, he was down to -19.     that could be a reason for it taking so long.   you may not have been decoding him all the time

Dave Garber
VE3WEJ / VE3IE


On Mon, Nov 22, 2021 at 5:12 PM ka2qit via groups.io <ka2qit=yahoo.com@groups.io> wrote:
Bill, In this sequence W0QU replied to my call, it took me a couple of passes before he came up as red. When i replied I did not receive his acknowledgement . initially. Signal strength was good on both. Pse see below: 

211122_215030    14.074 Rx FT8      7  0.1 1046 CQ W0QU EM48
211122_215045    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215115    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215145    14.074 Rx FT8    -13  0.2 1138 VE2IM N0BEL EN34
211122_215200    14.074 Rx FT8    -10  0.1 1048 KA2QIT W0QU -10
211122_215200    14.074 Rx FT8    -16  0.1 1510 CQ KE5CDE EM10
211122_215200    14.074 Rx FT8    -18  0.1 1497 VE2FYZ N5LWL -07
211122_215215    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT R-10
211122_215245    14.074 Rx FT8    -10  0.2 1140 CQ N0BEL EN34
211122_215300    14.074 Rx FT8     -7  0.1 1435 VE3OKD K5EW EM40
211122_215300    14.074 Rx FT8    -12  0.1 1512 CQ KE5CDE EM10
211122_215300    14.074 Rx FT8    -19  0.1 1050 KA2QIT W0QU RRR
211122_215300    14.074 Rx FT8    -17  0.2 1488 KB4FHU W0GMV EM28
211122_215315    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT 73




Martin G0HDB
 
Edited

Bob:

The extract from your ALL.TXT file shows that your system apparently didn't decode anything at all in the timeslots at 215100, 215130 and 215230; you could probably have expected to receive a reply from W0QU in at least the first of those timeslots after you'd called him at 215045.

The complete absence of decodes in the aforementioned timeslots would suggest that there's something at your end that's adversely affecting your reception; do you have a high and/or a variable ambient noise level, or is there something else in your system and setup that might be affecting the accumulation of the audio samples that WSJT-X needs for its decoding?

It's also rather odd that the file extract doesn't show a transmission from you at 215145 - this would have been expected because you were calling W0QU in the 'odd' timeslots, eg. 215045 and 215115, so in the absence of a reply from W0QU to your transmissions at 215045 and 215115 your system should have re-sent the 'W0QU KA2QIT FN21' message at 215145 but it's not shown in the list.  Instead, the file shows that you were receiving rather than transmitting in the 215145 timeslot, and that you got a decode of N0BEL calling a VE2.  Had you inadvertently disabled your transmission for some reason?

--
Martin G0HDB


 

Bob,

 

An interesting feature is the drift on received signals. W0QU, KE5CDE and N0BEL seem to have drifted 1 or 2 Hz up over the course of the displayed period.

 

73 Phil GM3ZZA

Sent from Mail for Windows

 

From: ka2qit via groups.io
Sent: 22 November 2021 22:12
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJTX FT8 intermittent decode of my call on receive #help

 

Bill, In this sequence W0QU replied to my call, it took me a couple of passes before he came up as red. When i replied I did not receive his acknowledgement . initially. Signal strength was good on both. Pse see below: 

211122_215030    14.074 Rx FT8      7  0.1 1046 CQ W0QU EM48

211122_215045    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21

211122_215115    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21

211122_215145    14.074 Rx FT8    -13  0.2 1138 VE2IM N0BEL EN34

211122_215200    14.074 Rx FT8    -10  0.1 1048 KA2QIT W0QU -10

211122_215200    14.074 Rx FT8    -16  0.1 1510 CQ KE5CDE EM10

211122_215200    14.074 Rx FT8    -18  0.1 1497 VE2FYZ N5LWL -07

211122_215215    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT R-10

211122_215245    14.074 Rx FT8    -10  0.2 1140 CQ N0BEL EN34

211122_215300    14.074 Rx FT8     -7  0.1 1435 VE3OKD K5EW EM40

211122_215300    14.074 Rx FT8    -12  0.1 1512 CQ KE5CDE EM10

211122_215300    14.074 Rx FT8    -19  0.1 1050 KA2QIT W0QU RRR

211122_215300    14.074 Rx FT8    -17  0.2 1488 KB4FHU W0GMV EM28

211122_215315    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT 73

 


--
73 Phil GM3ZZA


Bill Somerville
 

On 22/11/2021 22:12, ka2qit via groups.io wrote:
Bill, In this sequence W0QU replied to my call, it took me a couple of passes before he came up as red. When i replied I did not receive his acknowledgement . initially. Signal strength was good on both. Pse see below:

211122_215030    14.074 Rx FT8      7  0.1 1046 CQ W0QU EM48
211122_215045    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215115    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT FN21
211122_215145    14.074 Rx FT8    -13  0.2 1138 VE2IM N0BEL EN34
211122_215200    14.074 Rx FT8    -10  0.1 1048 KA2QIT W0QU -10
211122_215200    14.074 Rx FT8    -16  0.1 1510 CQ KE5CDE EM10
211122_215200    14.074 Rx FT8    -18  0.1 1497 VE2FYZ N5LWL -07
211122_215215    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT R-10
211122_215245    14.074 Rx FT8    -10  0.2 1140 CQ N0BEL EN34
211122_215300    14.074 Rx FT8     -7  0.1 1435 VE3OKD K5EW EM40
211122_215300    14.074 Rx FT8    -12  0.1 1512 CQ KE5CDE EM10
211122_215300    14.074 Rx FT8    -19  0.1 1050 KA2QIT W0QU RRR
211122_215300    14.074 Rx FT8    -17  0.2 1488 KB4FHU W0GMV EM28
211122_215315    14.074 Tx FT8      0  0.0 1046 W0QU KA2QIT 73
Hi Bob,

something seems wrong with your Rx, I would expect many more decodes around 22:00 UTC on 20m in your region, in fact you had no decodes printed at all at 21:50:00, 21:51:30, and 21:52:30. Notably these periods all follow a transmission by you, is your system heavily loaded? Are you using a narrow IF filter?

73
Bill
G4WJS.


ka2qit
 

Martin,
Yes I did disable the xmission as I kept sending the same sig rpt. While I assume the other station continued confirming, (due to sig strength). I do have a high noise level and will try another sequence with the noise blanker engaged, and run an uninterrupted sequence.

Thanks for all the comments. Bob KA2QIT 


SA5QED/David
 

I am sometimes experiencing similar QSO patterns. 
Is it possible that QU does not have Autosequencing checked?

73
SE5M
David


Martin G0HDB
 

On Tue, Nov 23, 2021 at 03:43 PM, ka2qit wrote:
Martin,
Yes I did disable the xmission as I kept sending the same sig rpt. While I assume the other station continued confirming, (due to sig strength). I do have a high noise level and will try another sequence with the noise blanker engaged, and run an uninterrupted sequence.
Hi again Bob, you haven't said what make and model of rig you're using, but are you operating it with AGC on or off?

If your rig is an Icom IC-7600 or IC-7610, or maybe some other make and model, then operating with AGC off is not always the optimum approach especially when there are large signals on the band.  More specifically, when operated with AGC off the audio output from an IC-7600 and an IC-7610 starts to become severely distorted at quite modest input signal levels, eg. around S4.  The presence of such distortion on the audio being fed into WSJT-X can really screw up the decoding.

If you are operating your rig, whatever make and model it is, with AGC off then I'd suggest you try turning AGC on and setting the audio levels to give a reading of in the region of 65dB, instead of 30dB, on the WSJT-X audio level bargraph when you're receiving only band noise.  In addition, I'd adjust your rig's input attenuator, if it has one, and/or the RF gain control so that you get an S-meter reading in the region of S0 to S1 when receiving only band noise - this will help ensure that there's little or no AGC action caused by your local noise.  There's no point at all in having the noise causing an S-meter reading in the region of, for example, S5-6 (or higher!).

--
Martin G0HDB


ka2qit
 

Martin and all,

I turned my input gain down to about 35db, it apperars to be operating normally now on auto sequence.

Thanks for your help y'all! Bob KA2QIT


Michael Black
 

You should adjust your rig's audio level to 30dB on a quiet spot for WSJTX.  It's mentioned in the manual.
30dB is the minimum level to overcome quantization error and is the proper level for all digital modes.

Mike W9MDB




On Saturday, November 27, 2021, 03:59:27 PM CST, ka2qit via groups.io <ka2qit@...> wrote:


Martin and all,

I turned my input gain down to about 35db, it apperars to be operating normally now on auto sequence.

Thanks for your help y'all! Bob KA2QIT