On 11/27/2018 12:07 PM, Jari A wrote:
... I work several qsos with RC5 on FT8, then got silent with FT8, so I
change to JT65 as I saw traffic on it.
I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8,
even JT9 is indicated below date/ time window.
Aaah! Now I understand
Hi Charlie, Jari, and all,
Thanks for your reports -- they are much appreciated. I'm sure you
understand that our recent work has mostly been related to HF interests
-- in particular, the new 77-bit protocols for FT8 and MSK144, and new
special messages for contesting.
We are certainly not
Thanks, Jari
Sounds like this is a different issue to what I was reporting.
73
Charlie
> Hi Charlie, others
>
> No, I work several qsos with RC5 on FT8, then got silent with FT8, so I
> change to JT65 as I saw traffic on it.
>
> I also note, that after I change from JT65 to JT9, RC5 keeps tx
Hi Charlie, others
No, I work several qsos with RC5 on FT8, then got silent with FT8, so I
change to JT65 as I saw traffic on it.
I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8,
even JT9 is indicated below date/ time window.
Rgds,
:Jari / oh2fqv
On Tue, Nov 27, 2018 at
Hi Jari
Did you start rc5 after getting a mode jump to JT9 with 1.9.1?
That is the only way I have found so far to see the effects of a mode jump
with rc5.
I posted some findings on this a few messages ago.
73
Charlie G3WDG
> Windows 7 64 bit
>
> JT65 errors:
>
> Double click to rx call sign
Windows 7 64 bit
JT65 errors:
Double click to rx call sign not working to reply
Waterfall pointers looks like JT9
Transmit audio FT8 ( sending my own call with locator )
Decodes JT65 fine.
error repeatable, restart did not change the error.
Rgds,
:Jari / oh2fqv