[wsjt-devel] Feature or Flaw

2023-04-04 Thread John McKee via wsjt-devel 
I tried sending this from my gmail account, and it was held for review, 
presumably because I am not registered with WSJTX under that account.
So, I am sending it again under my att.net  account for your 
review:

*


I was today attempting a QSO with ZD7CTO, and after a long series of calls to 
him, I finally received a response at 213015 to which I replied at 213030.  No 
response from ZD7CTO, so I sent two more responses at 213100 and 213130.  Then, 
the WSJT-X changed me from Tx 3 to Tx 1, and began the QSO process again as 
seen at 213200… this happened several times more, necessitating my repeatedly 
changing to Tx 3 to complete the QSO finally at 213930……
 
My question: is this a feature (being changed back to Tx 1 after a QSO is 
answered by the DX station), OR is it a flaw in the program??
 
John, NT5EE




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

Re: [wsjt-devel] 3Y0J F/H operation - was my "R+rpt" report received ?

2023-02-17 Thread John McKee via wsjt-devel 
I have been following this thread, and offer my experience with the  "? a2” 
decode

At 230213_153645 is my last Tx - probably due the F/H turning off my Tx Enable 
after 4 or 5 transmissions
At 230213_154115, I hear JT Alert notify me that a callsign I am chasing (3Y0J) 
has appeared and I receive the line indicating to me that 3Y0J has replied; 
transmitted from Freq 450  with -23dB signal and containing the cryptic “? a2” 
at the end
At 230213_154145, I Enable Tx from Tx 1
At 230213_154215, I Tx again from Tx 1
At 230213_154245, I have realized that I should be giving 3Y0J a report so I 
click Tx 3 and send him R-23…notice here that my Freq has been changed from 
1852 to 750, ostensibly by 3Y0J (or by WSJT-X ?)
I transmit two more times, and then consider myself to be one of the lucky ones 
who has finally had a Bouvet QSO, thinking so because my freq has been changed 
which is usually what happens when the Fox recognizes the Hound….

It wasn’t until later on 230213 that I realized that the Fox was transmitting 
on Odd time instead of the usual Even time…then I read about the sequencing 
problems the 3Y0J team had been having so am thinking that the reply I received 
from Fox was legitimate.

I’ll just leave this here…….



From my All.txt file, here are my results with offsets by me to enhance clarity:

230213_15364518.107 Tx FT8  0  0.0 1020 3Y0J NT5EE DM81
230213_15371518.107 Rx FT8 16 -0.5 1206 3Y0J KK6MES CM96
230213_15371518.107 Rx FT8  9 -0.3 2632 3Y0J K6LAC DM13
230213_15371518.107 Rx FT8  2 -0.4 1434 3Y0J KC1BUF FN43
230213_15371518.107 Rx FT8 -2 -1.3 1282 3YOJ KEQXS EM
230213_15371518.107 Rx FT8  7 -0.9 2198 3Y0J KD6OKH CM88
230213_15374518.107 Rx FT8 13 -0.3 2632 3Y0J K6LAC DM13
230213_15374518.107 Rx FT8 20 -0.5 1206 3Y0J KK6MES CM96
230213_15374518.107 Rx FT8  9 -0.9 2198 3Y0J KD6OKH CM88
230213_15374518.107 Rx FT8 -4 -1.3 1282 3YOJ KEQXS EM
230213_15374518.107 Rx FT8 -8 -0.4 1435 3Y0J KC1BUF FN43
230213_15374518.107 Rx FT8-15 -0.6 1117 3Y0J KI5UKI EM30
230213_15381518.107 Rx FT8 14 -0.5 1206 3Y0J KK6MES CM96
230213_15381518.107 Rx FT8 -4 -1.3 1280 3YOJ KEQXS EM
230213_15381518.107 Rx FT8  9 -0.3 2632 3Y0J K6LAC DM13
230213_15381518.107 Rx FT8 -8 -0.6 1560 CQ W3TAC FM19
230213_15381518.107 Rx FT8 -5 -0.4 1435 3Y0J KC1BUF FN43
230213_15381518.107 Rx FT8-13 -0.6 1117 3Y0J KI5UKI EM30
230213_15384518.107 Rx FT8 -1 -1.3 1281 3YOJ KEQXS EM
230213_15384518.107 Rx FT8 -1 -0.6 1560 CQ W3TAC FM19
230213_15384518.107 Rx FT8  0 -0.4 1434 3Y0J KC1BUF FN43
230213_15384518.107 Rx FT8 12 -0.3 2633 3Y0J K6LAC DM13
230213_15391518.107 Rx FT8  7 -0.6 1560 CQ W3TAC FM19
230213_15391518.107 Rx FT8  2 -1.3 1281 3YOJ KEQXS EM
230213_15391518.107 Rx FT8 -2 -0.4 1435 3Y0J KC1BUF FN43
230213_15394518.107 Rx FT8  0 -1.3 1281 3YOJ KEQXS EM
230213_15394518.107 Rx FT8  7 -0.6 1560 CQ W3TAC FM19
230213_15394518.107 Rx FT8  1 -0.3 1435 3Y0J KC1BUF FN43
230213_15401518.107 Rx FT8  8 -0.6 1560 CQ W3TAC FM19
230213_15401518.107 Rx FT8  5 -0.5 1153 3Y0J N2YBB FN30
230213_15401518.107 Rx FT8  0 -1.3 1282 3YOJ KEQXS EM
230213_15401518.107 Rx FT8 -8 -0.4 1435 3Y0J KC1BUF FN43
230213_15404518.107 Rx FT8  3 -0.5 1153 3Y0J N2YBB FN30
230213_15404518.107 Rx FT8 -1 -1.3 1281 3YOJ KEQXS EM
230213_15404518.107 Rx FT8  3 -0.4 1435 3Y0J KC1BUF FN43
230213_15411518.107 Rx FT8  5 -0.5 1153 3Y0J N2YBB FN30
230213_15411518.107 Rx FT8  1 -1.4 1282 3YOJ KEQXS EM
230213_15411518.107 Rx FT8 -5 -0.4 1434 3Y0J KC1BUF FN43
230213_15411518.107 Rx FT8-23  0.7  450 17WCP RR73; NT5EE 
<3Y0J> +06? a2
230213_15414518.107 Tx FT8  0  0.0 1852 3Y0J NT5EE DM81
230213_15421518.107 Tx FT8  0  0.0 1852 3Y0J NT5EE DM81
230213_15424518.107 Tx FT8  0  0.0  750 3Y0J NT5EE R-23
230213_15431518.107 Tx FT8  0  0.0  750 3Y0J NT5EE R-23
230213_15434518.107 Tx FT8  0  0.0  750 3Y0J NT5EE R-23


> On Feb 17, 2023, at 14:35, Jon Anhold via wsjt-devel 
>  wrote:
> 
> It isn't a pirate. The "? a2" indicated that this was an A Priori decode.
> 
> On Fri, Feb 17, 2023 at 1:57 PM Fred Carvalho via wsjt-devel 
> mailto:wsjt-devel@lists.sourceforge.net>> 
> wrote:
> John answered
> My guess on this is that the a2 decode you received with your report was
> not real. It was on 752hz offset, not ~304hz where they were transmitting.
> 
> 
> John is right. I have never seen 3Y0J transmitting that high. He was actually 
> below (300-400Hz). However it does not look like a false decode.
>