Re: [wsjt-devel] Strange non QSO

2020-09-19 Thread Ronald Schmahl
I have gotten calls like that also. Usually it is remote or portable, crazy 
grid and very weak. I chalk it up to a rare mis-code. 
Ron K2PSD

Sent from my iPhone

> On Sep 18, 2020, at 10:09 PM, bergeracb--- via wsjt-devel 
>  wrote:
> 
> 
> I am attaching two photo files from a "QSO" I did not "really" have last 
> night to see if anyone can make sense of what happened. I had just installed 
> "Grid tracker" and was playing around with the controls. When I tried to 
> contact J69BB on FT8 I got the results shown in photo 1. A signal from a 
> station with a unknown Prefix from a Grid somewhere in the south eastern 
> Pacific Ocean, with signal reports sent and received, plus the Grid-square. 
> After WSJT-X again called J69BB automatically, it then sent a confirmation 
> and 73 to 1R6KOQ/R. FT8 then went on like nothing had happened.
> Photo 2 is the Grid-tracker display panel a few minutes afterward. This is 
> not very important to the community, but I sure would like to know what 
> happened. (maybe I am the first person to work a brand new volcanic island in 
> the Pacific. HI, HI.)
> 73 Al, N4AB
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread Neil Zampella
I believe you have to go to the URL listed at the bottom of the emails, 
and select the link on that page that says 'Click here to unsubscribe ... "


Neil, KN3ILZ

On 12/25/2018 2:59 PM, Rick Lindquist WW1ME/m wrote:
How does one unsubscribe from this list?  I  thought I had followed 
the right procedure, but I am still getting emails.


Thanks!

Rick, WW1ME


Sent via the Samsung Galaxy S7, an AT 4G LTE smartphone

 Original message 
From: Dan Malcolm 
Date: 12/25/18 2:24 PM (GMT-05:00)
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] strange non-qso

I understand Serge, but one way to find out is to see if you are in his
logbook via QRZ.  I agree it's difficult just looking at the QSO text, 
and I

appreciate Bill's comment.  I also agree with Bill that logging the QSO
makes the most sense.

__
Dan - K4SHQ


-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org]
Sent: Tuesday, December 25, 2018 10:29 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] strange non-qso

Dan

Thank you for your answer, however my questioning is on the software side,
not on the call itself.

With the following messages from WSJT-X, I feel - I can be wrong, but - I
feel that I cannot decide whether the QSO is completed or not completed.
See, the last message I read from the 4X station is not clear as to 
whether

this message is for me or for someone else.


73

Serge


On 25/12/2018 17:14, Dan Malcolm wrote:
> A search of QRZ found 4X19HNY and there is a pointer to their live log
> on that page.
>
> __
> Dan - K4SHQ
>
> -Original Message-
> From: F6BHK [mailto:f6...@f6bhk.org]
> Sent: Tuesday, December 25, 2018 9:30 AM
> To: WSJT software development 
> Subject: [wsjt-devel] strange non-qso
>
> Merry Xmas to all!
>
> The following QSO seems to me "strange":
>
> 151630 -17  0.4 1694 ~  CQ 4X19HNY
> 151646  Tx  1694 ~  <4X19HNY> F6BHK
> 151715  Tx  1694 ~  <4X19HNY> F6BHK
> 151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
> 151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
> 151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
> 151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15
>
> in the sense I am not able to be sure 4X19HNY has got my report. I
> would have expected <...> being  instead.
>
> 73
>
> Serge
>
>

--

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



---
This email has been checked for viruses by AVG.
https://www.avg.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread Rick Lindquist WW1ME/m
How does one unsubscribe from this list?  I  thought I had followed the right 
procedure, but I am still getting emails. 
Thanks! 
Rick, WW1ME 

Sent via the Samsung Galaxy S7, an AT 4G LTE smartphone
 Original message From: Dan Malcolm  Date: 
12/25/18  2:24 PM  (GMT-05:00) To: 'WSJT software development' 
 Subject: Re: [wsjt-devel] strange non-qso 
I understand Serge, but one way to find out is to see if you are in his
logbook via QRZ.  I agree it's difficult just looking at the QSO text, and I
appreciate Bill's comment.  I also agree with Bill that logging the QSO
makes the most sense.

__
Dan - K4SHQ


-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org] 
Sent: Tuesday, December 25, 2018 10:29 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] strange non-qso

Dan

Thank you for your answer, however my questioning is on the software side,
not on the call itself.

With the following messages from WSJT-X, I feel - I can be wrong, but - I
feel that I cannot decide whether the QSO is completed or not completed.
See, the last message I read from the 4X station is not clear as to whether
this message is for me or for someone else.


73

Serge


On 25/12/2018 17:14, Dan Malcolm wrote:
> A search of QRZ found 4X19HNY and there is a pointer to their live log 
> on that page.
>
> __
> Dan - K4SHQ
>
> -Original Message-
> From: F6BHK [mailto:f6...@f6bhk.org]
> Sent: Tuesday, December 25, 2018 9:30 AM
> To: WSJT software development 
> Subject: [wsjt-devel] strange non-qso
>
> Merry Xmas to all!
>
> The following QSO seems to me "strange":
>
> 151630 -17  0.4 1694 ~  CQ 4X19HNY
> 151646  Tx  1694 ~  <4X19HNY> F6BHK
> 151715  Tx  1694 ~  <4X19HNY> F6BHK
> 151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
> 151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
> 151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
> 151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15
>
> in the sense I am not able to be sure 4X19HNY has got my report. I 
> would have expected <...> being  instead.
>
> 73
>
> Serge
>
>

-- 

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread Dan Malcolm
I understand Serge, but one way to find out is to see if you are in his
logbook via QRZ.  I agree it's difficult just looking at the QSO text, and I
appreciate Bill's comment.  I also agree with Bill that logging the QSO
makes the most sense.

__
Dan - K4SHQ


-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org] 
Sent: Tuesday, December 25, 2018 10:29 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] strange non-qso

Dan

Thank you for your answer, however my questioning is on the software side,
not on the call itself.

With the following messages from WSJT-X, I feel - I can be wrong, but - I
feel that I cannot decide whether the QSO is completed or not completed.
See, the last message I read from the 4X station is not clear as to whether
this message is for me or for someone else.


73

Serge


On 25/12/2018 17:14, Dan Malcolm wrote:
> A search of QRZ found 4X19HNY and there is a pointer to their live log 
> on that page.
>
> __
> Dan - K4SHQ
>
> -Original Message-
> From: F6BHK [mailto:f6...@f6bhk.org]
> Sent: Tuesday, December 25, 2018 9:30 AM
> To: WSJT software development 
> Subject: [wsjt-devel] strange non-qso
>
> Merry Xmas to all!
>
> The following QSO seems to me "strange":
>
> 151630 -17  0.4 1694 ~  CQ 4X19HNY
> 151646  Tx  1694 ~  <4X19HNY> F6BHK
> 151715  Tx  1694 ~  <4X19HNY> F6BHK
> 151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
> 151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
> 151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
> 151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15
>
> in the sense I am not able to be sure 4X19HNY has got my report. I 
> would have expected <...> being  instead.
>
> 73
>
> Serge
>
>

-- 

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread F6BHK

Thanks Bill. Understand.

Merry Xmas

Cheers

Serge


On 25/12/2018 17:23, Bill Somerville wrote:

On 25/12/2018 15:29, F6BHK wrote:

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I 
would have expected <...> being  instead.


Hi Serge,

this is another variant on the known issue with hash collisions in 
WSJT-X v2.0.0. In this case the first message you receive with your 
callsign hashed:


151900 -19  0.3 1693 ~  <...> 4X19HNY RR73

is not printed correctly because WSJT-X has not stored your own 
callsign in the relevant hash table (not a hash collision but a 
missing hash code mapping to you callsign). Although it is not clear 
you can be quite certain that 4X19HNY has copied your call correctly 
since it was sent in full during the QSO in the message:


151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22

I would log the QSO as it almost 100% certain that the sign off 
message sent by 4X19HNY was " 4X19HNY RR73" and it will be in 
his log.


This issue is resolved for the next release of WSJT-X.

73 & Merry Christmas
Bill
G4WJS.





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread F6BHK

Dan

Thank you for your answer, however my questioning is on the software 
side, not on the call itself.


With the following messages from WSJT-X, I feel - I can be wrong, but - 
I feel that I cannot decide whether the QSO is completed or not 
completed. See, the last message I read from the 4X station is not clear 
as to whether this message is for me or for someone else.



73

Serge


On 25/12/2018 17:14, Dan Malcolm wrote:

A search of QRZ found 4X19HNY and there is a pointer to their live log on
that page.

__
Dan - K4SHQ

-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org]
Sent: Tuesday, December 25, 2018 9:30 AM
To: WSJT software development 
Subject: [wsjt-devel] strange non-qso

Merry Xmas to all!

The following QSO seems to me "strange":

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I would
have expected <...> being  instead.

73

Serge




--

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread Bill Somerville

On 25/12/2018 15:29, F6BHK wrote:

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I 
would have expected <...> being  instead.


Hi Serge,

this is another variant on the known issue with hash collisions in 
WSJT-X v2.0.0. In this case the first message you receive with your 
callsign hashed:


151900 -19  0.3 1693 ~  <...> 4X19HNY RR73

is not printed correctly because WSJT-X has not stored your own callsign 
in the relevant hash table (not a hash collision but a missing hash code 
mapping to you callsign). Although it is not clear you can be quite 
certain that 4X19HNY has copied your call correctly since it was sent in 
full during the QSO in the message:


151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22

I would log the QSO as it almost 100% certain that the sign off message 
sent by 4X19HNY was " 4X19HNY RR73" and it will be in his log.


This issue is resolved for the next release of WSJT-X.

73 & Merry Christmas
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] strange non-qso

2018-12-25 Thread Dan Malcolm
A search of QRZ found 4X19HNY and there is a pointer to their live log on
that page.

__
Dan - K4SHQ

-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org] 
Sent: Tuesday, December 25, 2018 9:30 AM
To: WSJT software development 
Subject: [wsjt-devel] strange non-qso

Merry Xmas to all!

The following QSO seems to me "strange":

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I would
have expected <...> being  instead.

73

Serge


-- 

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] strange non-qso

2018-12-25 Thread F6BHK

Merry Xmas to all!

The following QSO seems to me "strange":

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I would 
have expected <...> being  instead.


73

Serge


--

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel