JTDX misses caller, calls CQ

K7GQ
Users

Posts: 16

JTDX misses caller, calls CQ Feb 3, 2023 19:00:39 GMT

Quote

Post by K7GQ on Feb 3, 2023 19:00:39 GMT

Today, for example, I was "running" on 12m. Occasionally, an eligible caller would respond however JTDX would call CQ. Generally, within the very same time slot, the CQ be the first line followed by a station calling on the next line displayed in the receive window. Below are the current settings:

BYPASS      OFF (filtering out NA, worked before)
AnsB4          ON

FT8 Threads 3
FT8 decoding cycles 2
QSO RX freq sensitivity medium
decoder sensitivity        use subpass
early start of decoder YES
Wideband DX call search YES

typical run values:
avg = 0.24
lag = +.49 to +.65

I could use some guidance or suggestions here to avoid this in the future.

Harry

Arvo ES1JA Administrator Posts: 364	JTDX misses caller, calls CQ Feb 3, 2023 21:05:57 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Arvo ES1JA on Feb 3, 2023 21:05:57 GMT Which Autoseq option (number) is in use? Have you used directional CQ? If caller line is after CQ line then use Autoseq 3/7 and problem should go away.
	Last Edit: Feb 3, 2023 21:42:01 GMT by Arvo ES1JA

K7GQ Users Posts: 16	JTDX misses caller, calls CQ Feb 3, 2023 22:06:01 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by K7GQ on Feb 3, 2023 22:06:01 GMT Hi Arvo Auto Seq 3 Directional CQ "EU" I don't see "3/7" or "7" choice

Arvo ES1JA Administrator Posts: 364	JTDX misses caller, calls CQ Feb 3, 2023 22:35:18 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Arvo ES1JA on Feb 3, 2023 22:35:18 GMT 7 is 3+4 option from Autoseq menu,but which callers were missed? Only callers from EU are accepted. Take a screenshot of whole jtdx screen.
	Last Edit: Feb 3, 2023 22:37:31 GMT by Arvo ES1JA

K7GQ
Users

Posts: 16

JTDX misses caller, calls CQ Mar 11, 2023 18:15:23 GMT

Quote

Post by K7GQ on Mar 11, 2023 18:15:23 GMT

This screen shot shows M0IPU calling me while that caller is ignored and I call CQ. My reply to the caller is done through manual intervention.

I realize the effect of the lag time and this scenario would make complete sense if the several lines were in the following order:

CQ EU K7GQ DM09
K7GQ M0IPU JO01

which would show the the decoder finished after the begin of the CQ transmission. However, it seems that the decoder finished BEFORE the CQ transmission - which makes little sense.

hopefully, the attachment is below:

Last Edit: Mar 11, 2023 18:17:13 GMT by K7GQ

Arvo ES1JA Administrator Posts: 364	JTDX misses caller, calls CQ Mar 11, 2023 19:23:13 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Arvo ES1JA on Mar 11, 2023 19:23:13 GMT Decoder finishes 2.11. sec. After transmission start (Lag value). And then tx message is changed from CQ. All correct. You need te revise decoder settings to bring Lag value down. Decode cycles 1 should be enough.
	Last Edit: Mar 11, 2023 19:25:19 GMT by Arvo ES1JA

JTDX misses caller, calls CQ

Post by K7GQ on Feb 3, 2023 19:00:39 GMT

Post by Arvo ES1JA on Feb 3, 2023 21:05:57 GMT

Post by K7GQ on Feb 3, 2023 22:06:01 GMT

Post by Arvo ES1JA on Feb 3, 2023 22:35:18 GMT

Post by K7GQ on Mar 11, 2023 18:15:23 GMT

Post by Arvo ES1JA on Mar 11, 2023 19:23:13 GMT