locked Decoding Issue


Jerry VE9CD
 

Has anyone experienced decoding on every second pass? On JTDX, every pass decodes consistently. On WSJT-X the first 15 seconds decodes, the second 15 seconds do not and the third decodes again.


Dave
 

Check the Tx even/1st just to the right of the frequency display

Dave, W8QXR

On Jan 17, 2020, at 2:55 PM, Gerard Arsenault <jerrya@...> wrote:

Has anyone experienced decoding on every second pass? On JTDX, every pass decodes consistently. On WSJT-X the first 15 seconds decodes, the second 15 seconds do not and the third decodes again.


John Hill
 

Gerard,

Are you sure that you don't have the FT4 mode selected?

John W2HUV

On January 17, 2020 at 3:55 PM Gerard Arsenault <jerrya@...> wrote:

Has anyone experienced decoding on every second pass? On JTDX, every pass decodes consistently. On WSJT-X the first 15 seconds decodes, the second 15 seconds do not and the third decodes again.

 


Jerry VE9CD
 

Doesn't affect the decoding alternating. Whatever it decodes first, it doesn't decode the next one.but will decode the third one. I know it's weird.


Jerry VE9CD
 

It won't decode at all if the mode is not correct.


Steve Miller
 

Yes. If contact was attempted (completed or not, doesn't matter) on the even cycle (00/30), decodes there after will be only display for 15/45 cycle. Program just skips what was received on the 00/30 cycle. This will happen for a few minutes or longer before maybe self correcting itself.


 



On 19 Jan 2020 15:26, Steve Miller <k8sjm@...> wrote:
Yes. If contact was attempted (completed or not, doesn't matter) on the even cycle (00/30), decodes there after will be only display for 15/45 cycle. Program just skips what was received on the 00/30 cycle. This will happen for a few minutes or longer before maybe self correcting itself.
This is not what I see. I stop transmitting, my installation decodes every 15 second slot. There might be a secret switch somewhere that controls this.
73 Phil GM3ZZA


--
73 Phil GM3ZZA


Jerry VE9CD
 

The issue I have reported is happening when I am simply listening or watching the waterfall on alternate cycles. I am not attempting to transmit at all on any of the cycles. What really strikes me is that this does not happen when using JTDX, it is only on WSJT-X. (using Ver. 2.1.2 )