Date   

locked Re: Callsigns get cleared before I can see them

neil_zampella
 

John .. current JT-Alert version is 2.16.15 .... with the updated 3 pass decoder in WSJT-X v2.2.2, the older versions of JT-Alert were not setup to cover the 3 passes.

 

Neil, KN3ILZ


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Joe,



I'll do that but I pretty much know what I will find..



73,

W9RF - Joe





On Monday, November 16, 2020, 8:38:50 PM CST, Joe Subich, W4TV <lists@...> wrote:



> Has the F/H protocol changed since WSJT-X 2.0?

This would be a question for K1JT on the WSJTX list - not here
as it is not a function of JTAlert.

Why don't you check the change log/Release Notes:
  <https://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt>

73,

    ... Joe, W4TV


On 2020-11-16 8:01 PM, ray cathode via groups.io wrote:
>  Here is my latest test with
> JTalert ver 2.16.15WSJT ver 2.2.2F/H mode30 meters
>
> 235315 Tx 1114 ~ 7Q7RU W9RF EM57
> 235330 -14 -0.3 349 ~ W9RF 7Q7RU -04
>
> 235345 Tx 349 ~ 7Q7RU W9RF R-14
>
> 235415 Tx 649 ~ 7Q7RU W9RF R-14
>
> 235445 Tx 649 ~ 7Q7RU W9RF R-14
>
> 235500 -14 -0.3 349 ~ EA2KB 7Q7RU -09
>
> 235515 Tx 649 ~ 7Q7RU W9RF R-14
>
> 235545 Tx 649 ~ 7Q7RU W9RF R-14
>
> 235600 -14 -0.3 349 ~ W9RF 7Q7RU -04
>
> 235615 Tx 349 ~ 7Q7RU W9RF R-14
>
> 235630 -9 -0.3 289 ~ W9RF 7Q7RU -04
>
> 235645 Tx 289 ~ 7Q7RU W9RF R-09
>
> 235700 -11 -0.3 289 ~ W9RF 7Q7RU -04
>
> 235715 Tx 289 ~ 7Q7RU W9RF R-11
>
> 235730 -9 -0.3 289 ~ CQ 7Q7RU KH67
>
> 235745 Tx 589 ~ 7Q7RU W9RF R-11
>
>
> sent into never never land
> 2nd try
> JTalert ver 2.16.15WSJT ver 2.2.2F/H mode TURNED OFF
> 30 meters
>
>
> 005830 -4 0.0 289 ~ CQ 7Q7RU KH67
> 005845 Tx 1325 ~ 7Q7RU W9RF EM57
>
> 005900 -6 -0.1 289 ~ W9RF 7Q7RU -01
>
> 005915 Tx 1325 ~ 7Q7RU W9RF R-06
>
> 005930 -6 -0.1 289 ~ W9RF 7Q7RU RR73
>
> 005945 Tx 1325 ~ 7Q7RU W9RF 73
>
> 010000 -8 -0.2 289 ~ CQ 7Q7RU KH67
>
>
>
>
>
>      On Monday, November 16, 2020, 5:09:11 PM CST, ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io> wrote:

>    Laurie,
>
> Has the F/H protocol changed since WSJT-X 2.0?
>
> 73,
> W9RF - Joe
>

>
>      On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:

>  Their website says they are using WSJT-X v2.0 which is very old and might explain some of the oddities of operation ...
>
> One would think that, embarking on such a long-distance and expensive DXpedition, they would be sure to have the most up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.
> jim  w2jc
> On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:
>> Are you sure 7q7ru is using WSJTX> and not a [garbage] clone like MSHV or> JTDX? > > Some of the clones do not implement> the F/H protocol correctly but do> allow for multiple simultaneous> QSOs.  It may be that 7q7ru is using> one of the incompatible software> packages and using the *NON F/H* mode> in WSJTX is the correct way to> operate!
>   
>
>
>
>
>
>






locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Gary,

All my contacts with them has been confirmed via Clublog with a RR73 and me clicking on "log qso"

(I run DXKeeper also)

Next time you try, don't use F/H and see how it works out.


73,

W9RF - Joe








On Monday, November 16, 2020, 8:31:32 PM CST, Gary Gorniak <w9bs@...> wrote:


You might want to check ClubLog to see if they logged your QSO.  I had the same problem as you when I worked them on 30m.  I tried for hours to initiate another contact with them, without success.  Today I checked ClubLog, and indeed they logged the QSO.  I reconstructed the entry for my log (DXKeeper) by using the ALL.txt file in WSJT-X to retrieve the necessary info.

 

GL and 73

Gary – W9BS

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of ray cathode via groups.io
Sent: Monday, November 16, 2020 8:02 PM
To: Support@HamApps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] unsuccessful contacts with 7q7ru

 

Here is my latest test with

JTalert ver 2.16.15

WSJT ver 2.2.2

F/H mode

30 meters

 

235315 Tx 1114 ~ 7Q7RU W9RF EM57

235330 -14 -0.3 349 ~ W9RF 7Q7RU -04

235345 Tx 349 ~ 7Q7RU W9RF R-14

235415 Tx 649 ~ 7Q7RU W9RF R-14

235445 Tx 649 ~ 7Q7RU W9RF R-14

235500 -14 -0.3 349 ~ EA2KB 7Q7RU -09

235515 Tx 649 ~ 7Q7RU W9RF R-14

235545 Tx 649 ~ 7Q7RU W9RF R-14

235600 -14 -0.3 349 ~ W9RF 7Q7RU -04

235615 Tx 349 ~ 7Q7RU W9RF R-14

235630 -9 -0.3 289 ~ W9RF 7Q7RU -04

235645 Tx 289 ~ 7Q7RU W9RF R-09

235700 -11 -0.3 289 ~ W9RF 7Q7RU -04

235715 Tx 289 ~ 7Q7RU W9RF R-11

235730 -9 -0.3 289 ~ CQ 7Q7RU KH67

235745 Tx 589 ~ 7Q7RU W9RF R-11

 

 

sent into never never land

 

2nd try

 

JTalert ver 2.16.15

WSJT ver 2.2.2

F/H mode TURNED OFF

30 meters

 

 

 

005830 -4 0.0 289 ~ CQ 7Q7RU KH67

005845 Tx 1325 ~ 7Q7RU W9RF EM57

005900 -6 -0.1 289 ~ W9RF 7Q7RU -01

005915 Tx 1325 ~ 7Q7RU W9RF R-06

005930 -6 -0.1 289 ~ W9RF 7Q7RU RR73

005945 Tx 1325 ~ 7Q7RU W9RF 73

010000 -8 -0.2 289 ~ CQ 7Q7RU KH67

 

 

 

 

 

On Monday, November 16, 2020, 5:09:11 PM CST, ray cathode via groups.io <ray_cathode1@...> wrote:

 

 

Laurie,

 

 

Has the F/H protocol changed since WSJT-X 2.0?

 

 

73,

 

W9RF - Joe

 

 

 

 

On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:

 

 

Their website says they are using WSJT-X v2.0

which is very old and might explain some of the

oddities of operation ...

 

graphic

 

One would think that, embarking on such a long-distance and

expensive DXpedition, they would be sure to have the most

up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

 

jim  w2jc

 

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

 

> Are you sure 7q7ru is using WSJTX

> and not a [garbage] clone like MSHV or

> JTDX?

>

> Some of the clones do not implement

> the F/H protocol correctly but do

> allow for multiple simultaneous

> QSOs.  It may be that 7q7ru is using

> one of the incompatible software

> packages and using the *NON F/H* mode

> in WSJTX is the correct way to

> operate!

 

  


locked Re: Callsigns get cleared before I can see them

Jim Cooper
 

On 16 Nov 2020 at 17:56, John Peck wrote:

> Jim, Not sure what you mean by the "decodes" window. And I have a
> reasonably fast computer.

graphic

see the two arrows ... 

graphic

Have you enabled this option?  It helps keep the calls visible
for a longer time under some conditions.

de w2jc



  


locked Re: unsuccessful contacts with 7q7ru

Joe Subich, W4TV
 

Has the F/H protocol changed since WSJT-X 2.0?
This would be a question for K1JT on the WSJTX list - not here
as it is not a function of JTAlert.

Why don't you check the change log/Release Notes:
<https://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt>

73,

... Joe, W4TV


On 2020-11-16 8:01 PM, ray cathode via groups.io wrote:
Here is my latest test with
JTalert ver 2.16.15WSJT ver 2.2.2F/H mode30 meters
235315 Tx 1114 ~ 7Q7RU W9RF EM57
235330 -14 -0.3 349 ~ W9RF 7Q7RU -04
235345 Tx 349 ~ 7Q7RU W9RF R-14
235415 Tx 649 ~ 7Q7RU W9RF R-14
235445 Tx 649 ~ 7Q7RU W9RF R-14
235500 -14 -0.3 349 ~ EA2KB 7Q7RU -09
235515 Tx 649 ~ 7Q7RU W9RF R-14
235545 Tx 649 ~ 7Q7RU W9RF R-14
235600 -14 -0.3 349 ~ W9RF 7Q7RU -04
235615 Tx 349 ~ 7Q7RU W9RF R-14
235630 -9 -0.3 289 ~ W9RF 7Q7RU -04
235645 Tx 289 ~ 7Q7RU W9RF R-09
235700 -11 -0.3 289 ~ W9RF 7Q7RU -04
235715 Tx 289 ~ 7Q7RU W9RF R-11
235730 -9 -0.3 289 ~ CQ 7Q7RU KH67
235745 Tx 589 ~ 7Q7RU W9RF R-11
sent into never never land
2nd try
JTalert ver 2.16.15WSJT ver 2.2.2F/H mode TURNED OFF
30 meters
005830 -4 0.0 289 ~ CQ 7Q7RU KH67
005845 Tx 1325 ~ 7Q7RU W9RF EM57
005900 -6 -0.1 289 ~ W9RF 7Q7RU -01
005915 Tx 1325 ~ 7Q7RU W9RF R-06
005930 -6 -0.1 289 ~ W9RF 7Q7RU RR73
005945 Tx 1325 ~ 7Q7RU W9RF 73
010000 -8 -0.2 289 ~ CQ 7Q7RU KH67
On Monday, November 16, 2020, 5:09:11 PM CST, ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io> wrote:
Laurie,
Has the F/H protocol changed since WSJT-X 2.0?
73,
W9RF - Joe
On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@jimcooper.org> wrote:
Their website says they are using WSJT-X v2.0 which is very old and might explain some of the oddities of operation ...
One would think that, embarking on such a long-distance and expensive DXpedition, they would be sure to have the most up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.
jim  w2jc
On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:
Are you sure 7q7ru is using WSJTX> and not a [garbage] clone like MSHV or> JTDX? > > Some of the clones do not implement> the F/H protocol correctly but do> allow for multiple simultaneous> QSOs.  It may be that 7q7ru is using> one of the incompatible software> packages and using the *NON F/H* mode> in WSJTX is the correct way to> operate!


locked Re: unsuccessful contacts with 7q7ru

Gary Gorniak
 

You might want to check ClubLog to see if they logged your QSO.  I had the same problem as you when I worked them on 30m.  I tried for hours to initiate another contact with them, without success.  Today I checked ClubLog, and indeed they logged the QSO.  I reconstructed the entry for my log (DXKeeper) by using the ALL.txt file in WSJT-X to retrieve the necessary info.

 

GL and 73

Gary – W9BS

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of ray cathode via groups.io
Sent: Monday, November 16, 2020 8:02 PM
To: Support@HamApps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] unsuccessful contacts with 7q7ru

 

Here is my latest test with

JTalert ver 2.16.15

WSJT ver 2.2.2

F/H mode

30 meters

 

235315 Tx 1114 ~ 7Q7RU W9RF EM57

235330 -14 -0.3 349 ~ W9RF 7Q7RU -04

235345 Tx 349 ~ 7Q7RU W9RF R-14

235415 Tx 649 ~ 7Q7RU W9RF R-14

235445 Tx 649 ~ 7Q7RU W9RF R-14

235500 -14 -0.3 349 ~ EA2KB 7Q7RU -09

235515 Tx 649 ~ 7Q7RU W9RF R-14

235545 Tx 649 ~ 7Q7RU W9RF R-14

235600 -14 -0.3 349 ~ W9RF 7Q7RU -04

235615 Tx 349 ~ 7Q7RU W9RF R-14

235630 -9 -0.3 289 ~ W9RF 7Q7RU -04

235645 Tx 289 ~ 7Q7RU W9RF R-09

235700 -11 -0.3 289 ~ W9RF 7Q7RU -04

235715 Tx 289 ~ 7Q7RU W9RF R-11

235730 -9 -0.3 289 ~ CQ 7Q7RU KH67

235745 Tx 589 ~ 7Q7RU W9RF R-11

 

 

sent into never never land

 

2nd try

 

JTalert ver 2.16.15

WSJT ver 2.2.2

F/H mode TURNED OFF

30 meters

 

 

 

005830 -4 0.0 289 ~ CQ 7Q7RU KH67

005845 Tx 1325 ~ 7Q7RU W9RF EM57

005900 -6 -0.1 289 ~ W9RF 7Q7RU -01

005915 Tx 1325 ~ 7Q7RU W9RF R-06

005930 -6 -0.1 289 ~ W9RF 7Q7RU RR73

005945 Tx 1325 ~ 7Q7RU W9RF 73

010000 -8 -0.2 289 ~ CQ 7Q7RU KH67

 

 

 

 

 

On Monday, November 16, 2020, 5:09:11 PM CST, ray cathode via groups.io <ray_cathode1@...> wrote:

 

 

Laurie,

 

 

Has the F/H protocol changed since WSJT-X 2.0?

 

 

73,

 

W9RF - Joe

 

 

 

 

On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:

 

 

Their website says they are using WSJT-X v2.0

which is very old and might explain some of the

oddities of operation ...

 

graphic

 

One would think that, embarking on such a long-distance and

expensive DXpedition, they would be sure to have the most

up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

 

jim  w2jc

 

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

 

> Are you sure 7q7ru is using WSJTX

> and not a [garbage] clone like MSHV or

> JTDX?

>

> Some of the clones do not implement

> the F/H protocol correctly but do

> allow for multiple simultaneous

> QSOs.  It may be that 7q7ru is using

> one of the incompatible software

> packages and using the *NON F/H* mode

> in WSJTX is the correct way to

> operate!

 

  


locked Re: Callsigns get cleared before I can see them

AB8WD-Willie
 

JT ALERT

Manage settings 
Window
Text messages


locked Re: Callsigns get cleared before I can see them

John Peck
 

John KC4LZN, yes that is exactly what is happening to me! Glad to know I am not alone!


locked Re: Callsigns get cleared before I can see them

Joe - W9RF
 

Jim,


I have the same problem but have never mentioned it.

If you are just setting back and not making any contacts the decode (band activity) window erases soon after the activity stops and displays a new group of calls, but if you make a contact and log it the window will close much faster and be blank for several seconds.

BTW my computer is not slow either.

73,

W9RF -Joe




On Monday, November 16, 2020, 7:56:34 PM CST, John Peck <johnpeck@...> wrote:


Jim, Not sure what you mean by the "decodes" window. And I have a reasonably fast computer.


locked Re: Callsigns get cleared before I can see them

John Peck
 

Willie, I can't find that screen on my system. Exactly how do you get to it? Thanks, John


locked Re: Callsigns get cleared before I can see them

John Peck
 

Laurie, thanks for your prompt response, and here is more information. I haven't been on the air since May. Winter is here and I aim to pick up the hobby once again. I figured all my software was out of date so I downloaded and installed WSJT-X v2.2.2 and JTAlert 2.16.4. I think they are the current versions. I am sure whatever is happening is my fault, probably something got screwed up with the re-installs. What I believe is happening is that JTAlert displays the very first stations decoded, but clears those fields when the next batch of signals is decoded, then clears the display again when the final batch shows up. This three level decoding is new to me, so I'm sure I am misinterpreting something. I just don't see what benefit there is to the "early" decoding if it flashes on and off the screen too fast for me to read it, let alone click on it. Sorry to be a bother. I spent several hours today trying to figure this out and I am stumped. John


locked Re: Callsigns get cleared before I can see them

John KC4LZN
 

I have to agree with John.

I'm running 2.16.1 and WSJT-X (Ver 2.2.2) goes through what appears a second sweep checking for missing signals and when it finds them, it posts them and JTAlert seems to clears the first sweep and posts the results of the second sweep.

Make sense?

73
John
KC4LZN

On Mon, Nov 16, 2020, 20:56 John Peck <Johnpeck@...> wrote:
Jim, Not sure what you mean by the "decodes" window. And I have a reasonably fast computer.


locked Re: Callsigns get cleared before I can see them

John Peck
 

Jim, Not sure what you mean by the "decodes" window. And I have a reasonably fast computer.


locked Re: Idea for Text Message Users

HamApps Support (VK3AMA)
 

On 12/11/2020 11:26 am, WB8ASI Herb wrote:
Laurie,   I'm a big fan of using the Decodes Window, and like being able to have recent option of reducing my Display Lines to zero.  I would still like to see if my QSO partner is using Text Messaging, but now I don't see the "underline".   Not exactly sure where best to show it?   I still use the Log Fields view, so maybe an underline or green spot on callsign for those online chat?   Or some indicator on the Decodes Window for those available for an online Test Message thank-you.  73, Herb WB8ASI

Here you go...

From the release notes of the next JTAlert release...
  New Features:

    - Decodes Window Online Indicators: Callsigns that are online for text message
       receipt will be shown with an underline, the same as the main JTAlert
       Callsigns display. A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.  

    - Text Messages: Can now be initiated via the Callsign right-click context menu
       of the Decodes Window.

    

de Laurie VK3AMA


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Here is my latest test with
JTalert ver 2.16.15
WSJT ver 2.2.2
F/H mode
30 meters

235315 Tx 1114 ~ 7Q7RU W9RF EM57

235330 -14 -0.3 349 ~ W9RF 7Q7RU -04

235345 Tx 349 ~ 7Q7RU W9RF R-14

235415 Tx 649 ~ 7Q7RU W9RF R-14

235445 Tx 649 ~ 7Q7RU W9RF R-14

235500 -14 -0.3 349 ~ EA2KB 7Q7RU -09

235515 Tx 649 ~ 7Q7RU W9RF R-14

235545 Tx 649 ~ 7Q7RU W9RF R-14

235600 -14 -0.3 349 ~ W9RF 7Q7RU -04

235615 Tx 349 ~ 7Q7RU W9RF R-14

235630 -9 -0.3 289 ~ W9RF 7Q7RU -04

235645 Tx 289 ~ 7Q7RU W9RF R-09

235700 -11 -0.3 289 ~ W9RF 7Q7RU -04

235715 Tx 289 ~ 7Q7RU W9RF R-11

235730 -9 -0.3 289 ~ CQ 7Q7RU KH67

235745 Tx 589 ~ 7Q7RU W9RF R-11



sent into never never land

2nd try

JTalert ver 2.16.15
WSJT ver 2.2.2
F/H mode TURNED OFF
30 meters



005830 -4 0.0 289 ~ CQ 7Q7RU KH67

005845 Tx 1325 ~ 7Q7RU W9RF EM57

005900 -6 -0.1 289 ~ W9RF 7Q7RU -01

005915 Tx 1325 ~ 7Q7RU W9RF R-06

005930 -6 -0.1 289 ~ W9RF 7Q7RU RR73

005945 Tx 1325 ~ 7Q7RU W9RF 73

010000 -8 -0.2 289 ~ CQ 7Q7RU KH67






On Monday, November 16, 2020, 5:09:11 PM CST, ray cathode via groups.io <ray_cathode1@...> wrote:


Laurie,


Has the F/H protocol changed since WSJT-X 2.0?


73,

W9RF - Joe




On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:


Their website says they are using WSJT-X v2.0
which is very old and might explain some of the
oddities of operation ...

graphic

One would think that, embarking on such a long-distance and
expensive DXpedition, they would be sure to have the most
up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

jim  w2jc

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

> Are you sure 7q7ru is using WSJTX
> and not a [garbage] clone like MSHV or
> JTDX?
>
> Some of the clones do not implement
> the F/H protocol correctly but do
> allow for multiple simultaneous
> QSOs.  It may be that 7q7ru is using
> one of the incompatible software
> packages and using the *NON F/H* mode
> in WSJTX is the correct way to
> operate!

  


locked Re: Callsigns get cleared before I can see them

AB8WD-Willie
 

screenshot shows how to delay screen closure on jtalert


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Jim,


Their call/call back/confirm (if that's how you explain it) is absolutely terrible, I would guess lees that 5%

I've been trying with ver 2.2.2 WSJT but they are only working nostly JA's for now.


73,

W9RF - Joe








On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:


Their website says they are using WSJT-X v2.0
which is very old and might explain some of the
oddities of operation ...

graphic

One would think that, embarking on such a long-distance and
expensive DXpedition, they would be sure to have the most
up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

jim  w2jc

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

> Are you sure 7q7ru is using WSJTX
> and not a [garbage] clone like MSHV or
> JTDX?
>
> Some of the clones do not implement
> the F/H protocol correctly but do
> allow for multiple simultaneous
> QSOs.  It may be that 7q7ru is using
> one of the incompatible software
> packages and using the *NON F/H* mode
> in WSJTX is the correct way to
> operate!

  


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Laurie,


Has the F/H protocol changed since WSJT-X 2.0?


73,

W9RF - Joe




On Monday, November 16, 2020, 5:04:14 PM CST, Jim Cooper <jtalert@...> wrote:


Their website says they are using WSJT-X v2.0
which is very old and might explain some of the
oddities of operation ...

graphic

One would think that, embarking on such a long-distance and
expensive DXpedition, they would be sure to have the most
up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

jim  w2jc

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

> Are you sure 7q7ru is using WSJTX
> and not a [garbage] clone like MSHV or
> JTDX?
>
> Some of the clones do not implement
> the F/H protocol correctly but do
> allow for multiple simultaneous
> QSOs.  It may be that 7q7ru is using
> one of the incompatible software
> packages and using the *NON F/H* mode
> in WSJTX is the correct way to
> operate!

  


locked Re: unsuccessful contacts with 7q7ru

Jim Cooper
 

Their website says they are using WSJT-X v2.0
which is very old and might explain some of the
oddities of operation ...

graphic

One would think that, embarking on such a long-distance and
expensive DXpedition, they would be sure to have the most
up to date version of all their software ...  but apparently not.   Apparently Malawi is the safest place in the world to be this week, so we do owe a lot of thanks for them to follow thru on the DXpedition.

jim  w2jc

On 16 Nov 2020 at 17:24, Joe Subich, W4TV wrote:

> Are you sure 7q7ru is using WSJTX
> and not a [garbage] clone like MSHV or
> JTDX?
>
> Some of the clones do not implement
> the F/H protocol correctly but do
> allow for multiple simultaneous
> QSOs.  It may be that 7q7ru is using
> one of the incompatible software
> packages and using the *NON F/H* mode
> in WSJTX is the correct way to
> operate!

  


locked Re: unsuccessful contacts with 7q7ru

Björn SM7IUN
 

Since WSJT-X is open source even the garbage clones use Joe's decoder so decoding performance should be equivalent.

If the DX systematically fails to complete QSO this means there is QRM in the listening slots on the DX's frequency.

Björn SM7IUN

Den mån 16 nov. 2020 kl 23:44 skrev ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io>:

Joe,


I'm pretty much convinced of that.

Since you have reminded me, that's what I remember about the clones, no F/H but appears to be in F/H mode.

I am running an older version of WSJT but Laurie suggested I upgrade to the newest one.

Going to do that and test a little more tonight.


You are right about the garbage clones they might be using, could be why you see 10-20 calls moved down to the 0-500 slot then never get answered..


73,

W9RF - Joe





On Monday, November 16, 2020, 4:24:32 PM CST, Joe Subich, W4TV <lists@...> wrote:



Joe,

Are you sure 7q7ru is using WSJTX and not a [garbage] clone like MSHV
or JTDX?

Some of the clones do not implement the F/H protocol correctly but
do allow for multiple simultaneous QSOs.  It may be that 7q7ru is
using one of the incompatible software packages and using the
*NON F/H* mode in WSJTX is the correct way to operate!

73,

    ... Joe, W4TV


On 2020-11-16 5:12 PM, ray cathode via groups.io wrote:
>  Laurie,
>
>
>
> I suppose it could be but did the parameters for F/H change since 2.1.2?
> I'll upgrade and see what happens
>
>
> 73,
> W9RF - Joe
>
>
>
>
>      On Monday, November 16, 2020, 4:05:42 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:


>
> On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
>> There might be some validity in your reasoning BUT I will stick with
>> the PLAIN FT8 (at least for 7q7ru)
>>
>> 9 times of making contact then getting put up to the 500_ slot is not
>> coincidence.
>>
>>
>> I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode
>> (4'th call) fairly bad signal reports.
>>
>>
>
> Could it be your very old WSJT-X version?
> 2.1.2 is rather dated.
>
> de Laurie VK3AMA
>







4321 - 4340 of 36454