Topics

Latest beta

Vilhjalmur Sigurjonsson
 

Hi,

I have been testing WSJT-X on FT4 with latest Logger32 and I am quite happy.

This happened automatically with the cherry picker:

225537   1  0.0 2054 +  TF3VS W4ARK R-01

225545  Tx      2230 +  W4ARK TF3VS +01                     

225552  -6  0.0 2055 +  TF3VS W4ARK R-01                    ? a3

225600  Tx      2230 +  W4ARK TF3VS RR73                    

225622  -2  0.0 2053 +  TF3VS W4ARK R-01                    ? a2

225630  Tx      2230 +  W4ARK TF3VS RR73                    

225637   0  0.0 2054 +  TF3VS W4ARK 73

 

FB! (and only one QSO logged, hi).

 

But I saw another case that might be useful to look at, if possible.

A station called CQ and my CP called, the station replied but Logger32 did not call back. In that case the other station was responding to two stations simultaneously:

21:19:21 Cherry-picking HB9DHG started

                HB9DHG sent:  CQ HB9DHG JN46

                HB9DHG not worked on 20M/FT4

                Need JN46 on 20M/FT4

21:19:21 Sent message to WSJT-X to call HB9DHG

21:19:22 Transmitting to HB9DHG

21:19:36 HB9DHG replied:  TF3VS HB9DHG +12

21:19:36 HB9DHG sent:  SP5GRM HB9DHG +00

21:19:36 HB9DHG replied to SP5GRM

21:19:36 Sent Tx Halt message to WSJT-X

21:19:36 Cherry-picking HB9DHG ended *2

 

But this is mabe not worthwhile thinking about?

 

But anyway, this is getting very good, and stable in my opinion.

 

73 de Villi
TF3VS

 

 

Bob
 

Villi, I have seen this a few times. I suspect the station is using MSHV which supports multiple parallel QSOs. Logger32 uses WSJT-X or JTDX which do not support multiple parallel QSOs. So, if I am in QSO with someone and suddenly I see he replies to another station in the middle of my QSO, what can I do? Pull the plug. SeventyThree(s).

On August 24, 2019 at 7:34 PM Vilhjalmur Sigurjonsson <vilhj@...> wrote:

Hi,

I have been testing WSJT-X on FT4 with latest Logger32 and I am quite happy.

This happened automatically with the cherry picker:

225537   1  0.0 2054 +  TF3VS W4ARK R-01

225545  Tx      2230 +  W4ARK TF3VS +01                     

225552  -6  0.0 2055 +  TF3VS W4ARK R-01                    ? a3

225600  Tx      2230 +  W4ARK TF3VS RR73                    

225622  -2  0.0 2053 +  TF3VS W4ARK R-01                    ? a2

225630  Tx      2230 +  W4ARK TF3VS RR73                    

225637   0  0.0 2054 +  TF3VS W4ARK 73

 

FB! (and only one QSO logged, hi).

 

But I saw another case that might be useful to look at, if possible.

A station called CQ and my CP called, the station replied but Logger32 did not call back. In that case the other station was responding to two stations simultaneously:

21:19:21 Cherry-picking HB9DHG started

                HB9DHG sent:  CQ HB9DHG JN46

                HB9DHG not worked on 20M/FT4

                Need JN46 on 20M/FT4

21:19:21 Sent message to WSJT-X to call HB9DHG

21:19:22 Transmitting to HB9DHG

21:19:36 HB9DHG replied:  TF3VS HB9DHG +12

21:19:36 HB9DHG sent:  SP5GRM HB9DHG +00

21:19:36 HB9DHG replied to SP5GRM

21:19:36 Sent Tx Halt message to WSJT-X

21:19:36 Cherry-picking HB9DHG ended *2

 

But this is mabe not worthwhile thinking about?

 

But anyway, this is getting very good, and stable in my opinion.

 

73 de Villi
TF3VS

 

 


 


 

Vilhjalmur Sigurjonsson
 

Oh boy, just after  I sent the email this happened:

 

(The CP Event Viewer)

23:37:43 Cherry-picking W8WEJ started

                W8WEJ sent:  CQ W8WEJ EM99

                W8WEJ not worked on 20M/FT4

                Need EM99 on 20M/FT4

23:37:43 Sent message to WSJT-X to call W8WEJ

23:37:44 Transmitting to W8WEJ

23:37:59 Transmitting to W8WEJ

23:38:01 W8WEJ replied:  TF3VS W8WEJ +01

23:38:13 W8WEJ replied:  TF3VS W8WEJ RR73

23:38:15 Transmitting to W8WEJ

23:38:19 W8WEJ QSO logged

23:38:43 W8WEJ replied:  TF3VS W8WEJ RR73

23:38:43 Sent Tx Halt message to WSJT-X

23:38:43 Cherry-picking W8WEJ ended with RR73

 

23:38:58 W8WEJ is queued

 

23:38:58 Cherry-picking W8WEJ started

                W8WEJ sent:  TF3VS W8WEJ RR73

                W8WEJ called me, I'm replying

23:38:58 Sent message to WSJT-X to call W8WEJ

23:38:59 Transmitting to W8WEJ

23:39:13 W8WEJ replied:  TF3VS W8WEJ RR73

23:39:13 Sent Tx Halt message to WSJT-X

23:39:13 Cherry-picking W8WEJ ended with RR73

 

23:39:58 W8WEJ is queued

 

23:39:58 Cherry-picking W8WEJ started

                W8WEJ sent:  TF3VS W8WEJ RR73

                W8WEJ called me, I'm replying

23:39:58 Sent message to WSJT-X to call W8WEJ

23:40:00 Transmitting to W8WEJ

23:40:03 W8WEJ duplicate logging request

23:40:13 W8WEJ sent:  CQ W8WEJ EM99

23:40:13 Not even time for a quick 73?

23:40:13 Sent Tx Halt message to WSJT-X

23:40:13 Cherry-picking W8WEJ ended *1

 

(And the WSJT-X monitor)

 

233730 -14 -0.2 1562 +  CQ UA0ZC QO93

233737   4  0.0  719 +  CQ W8WEJ EM99

233745  Tx      2230 +  W8WEJ TF3VS HP94                    

233752   4 -0.0  721 +  TF3VS W8WEJ +01

233800  Tx      2230 +  W8WEJ TF3VS R+04                    

233807   4 -0.0  718 +  TF3VS W8WEJ RR73

233815  Tx      2230 +  W8WEJ TF3VS 73                      

233837  -4 -0.0  718 +  TF3VS W8WEJ RR73

233852  -6 -0.0  718 +  TF3VS W8WEJ RR73

233900  Tx      2230 +  W8WEJ TF3VS R-06                     

233907  -8 -0.0  720 +  TF3VS W8WEJ RR73                    ? a3

233952  -5 -0.0  724 +  TF3VS W8WEJ RR73

234000  Tx      2230 +  W8WEJ TF3VS 73                      

234007  -3 -0.0  720 +  CQ W8WEJ EM99

 

The logging window popped up the second time, the QSO is logged twice in WSJT-X log but Logger32 ignored the later instance so it is only once in my log, hi.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Vilhjalmur Sigurjonsson
Sent: laugardagur, 24. ágúst 2019 23:35
To: hamlogger@groups.io
Subject: [hamlogger] Latest beta

 

Hi,

I have been testing WSJT-X on FT4 with latest Logger32 and I am quite happy.

This happened automatically with the cherry picker:

225537   1  0.0 2054 +  TF3VS W4ARK R-01

225545  Tx      2230 +  W4ARK TF3VS +01                     

225552  -6  0.0 2055 +  TF3VS W4ARK R-01                    ? a3

225600  Tx      2230 +  W4ARK TF3VS RR73                    

225622  -2  0.0 2053 +  TF3VS W4ARK R-01                    ? a2

225630  Tx      2230 +  W4ARK TF3VS RR73                    

225637   0  0.0 2054 +  TF3VS W4ARK 73

 

FB! (and only one QSO logged, hi).

 

But I saw another case that might be useful to look at, if possible.

A station called CQ and my CP called, the station replied but Logger32 did not call back. In that case the other station was responding to two stations simultaneously:

21:19:21 Cherry-picking HB9DHG started

                HB9DHG sent:  CQ HB9DHG JN46

                HB9DHG not worked on 20M/FT4

                Need JN46 on 20M/FT4

21:19:21 Sent message to WSJT-X to call HB9DHG

21:19:22 Transmitting to HB9DHG

21:19:36 HB9DHG replied:  TF3VS HB9DHG +12

21:19:36 HB9DHG sent:  SP5GRM HB9DHG +00

21:19:36 HB9DHG replied to SP5GRM

21:19:36 Sent Tx Halt message to WSJT-X

21:19:36 Cherry-picking HB9DHG ended *2

 

But this is mabe not worthwhile thinking about?

 

But anyway, this is getting very good, and stable in my opinion.

 

73 de Villi
TF3VS

 

 

Bob
 

... for those who believe these silly QSOs must have that final '73' message, I try very hard to get it ... even if WSJT-X makes no retries after a QSO is 'logged'. Where I come from, this is what we call 'perdekak'. SeventyThree(s).

On August 24, 2019 at 7:49 PM Vilhjalmur Sigurjonsson <vilhj@...> wrote:

Oh boy, just after  I sent the email this happened:

 

(The CP Event Viewer)

23:37:43 Cherry-picking W8WEJ started

                W8WEJ sent:  CQ W8WEJ EM99

                W8WEJ not worked on 20M/FT4

                Need EM99 on 20M/FT4

23:37:43 Sent message to WSJT-X to call W8WEJ

23:37:44 Transmitting to W8WEJ

23:37:59 Transmitting to W8WEJ

23:38:01 W8WEJ replied:  TF3VS W8WEJ +01

23:38:13 W8WEJ replied:  TF3VS W8WEJ RR73

23:38:15 Transmitting to W8WEJ

23:38:19 W8WEJ QSO logged

23:38:43 W8WEJ replied:  TF3VS W8WEJ RR73

23:38:43 Sent Tx Halt message to WSJT-X

23:38:43 Cherry-picking W8WEJ ended with RR73

 

23:38:58 W8WEJ is queued

 

23:38:58 Cherry-picking W8WEJ started

                W8WEJ sent:  TF3VS W8WEJ RR73

                W8WEJ called me, I'm replying

23:38:58 Sent message to WSJT-X to call W8WEJ

23:38:59 Transmitting to W8WEJ

23:39:13 W8WEJ replied:  TF3VS W8WEJ RR73

23:39:13 Sent Tx Halt message to WSJT-X

23:39:13 Cherry-picking W8WEJ ended with RR73

 

23:39:58 W8WEJ is queued

 

23:39:58 Cherry-picking W8WEJ started

                W8WEJ sent:  TF3VS W8WEJ RR73

                W8WEJ called me, I'm replying

23:39:58 Sent message to WSJT-X to call W8WEJ

23:40:00 Transmitting to W8WEJ

23:40:03 W8WEJ duplicate logging request

23:40:13 W8WEJ sent:  CQ W8WEJ EM99

23:40:13 Not even time for a quick 73?

23:40:13 Sent Tx Halt message to WSJT-X

23:40:13 Cherry-picking W8WEJ ended *1

 

(And the WSJT-X monitor)

 

233730 -14 -0.2 1562 +  CQ UA0ZC QO93

233737   4  0.0  719 +  CQ W8WEJ EM99

233745  Tx      2230 +  W8WEJ TF3VS HP94                    

233752   4 -0.0  721 +  TF3VS W8WEJ +01

233800  Tx      2230 +  W8WEJ TF3VS R+04                    

233807   4 -0.0  718 +  TF3VS W8WEJ RR73

233815  Tx      2230 +  W8WEJ TF3VS 73                      

233837  -4 -0.0  718 +  TF3VS W8WEJ RR73

233852  -6 -0.0  718 +  TF3VS W8WEJ RR73

233900  Tx      2230 +  W8WEJ TF3VS R-06                     

233907  -8 -0.0  720 +  TF3VS W8WEJ RR73                    ? a3

233952  -5 -0.0  724 +  TF3VS W8WEJ RR73

234000  Tx      2230 +  W8WEJ TF3VS 73                      

234007  -3 -0.0  720 +  CQ W8WEJ EM99

 

The logging window popped up the second time, the QSO is logged twice in WSJT-X log but Logger32 ignored the later instance so it is only once in my log, hi.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Vilhjalmur Sigurjonsson
Sent: laugardagur, 24. ágúst 2019 23:35
To: hamlogger@groups.io
Subject: [hamlogger] Latest beta

 

Hi,

I have been testing WSJT-X on FT4 with latest Logger32 and I am quite happy.

This happened automatically with the cherry picker:

225537   1  0.0 2054 +  TF3VS W4ARK R-01

225545  Tx      2230 +  W4ARK TF3VS +01                     

225552  -6  0.0 2055 +  TF3VS W4ARK R-01                    ? a3

225600  Tx      2230 +  W4ARK TF3VS RR73                    

225622  -2  0.0 2053 +  TF3VS W4ARK R-01                    ? a2

225630  Tx      2230 +  W4ARK TF3VS RR73                    

225637   0  0.0 2054 +  TF3VS W4ARK 73

 

FB! (and only one QSO logged, hi).

 

But I saw another case that might be useful to look at, if possible.

A station called CQ and my CP called, the station replied but Logger32 did not call back. In that case the other station was responding to two stations simultaneously:

21:19:21 Cherry-picking HB9DHG started

                HB9DHG sent:  CQ HB9DHG JN46

                HB9DHG not worked on 20M/FT4

                Need JN46 on 20M/FT4

21:19:21 Sent message to WSJT-X to call HB9DHG

21:19:22 Transmitting to HB9DHG

21:19:36 HB9DHG replied:  TF3VS HB9DHG +12

21:19:36 HB9DHG sent:  SP5GRM HB9DHG +00

21:19:36 HB9DHG replied to SP5GRM

21:19:36 Sent Tx Halt message to WSJT-X

21:19:36 Cherry-picking HB9DHG ended *2

 

But this is mabe not worthwhile thinking about?

 

But anyway, this is getting very good, and stable in my opinion.

 

73 de Villi
TF3VS