Mike,
Meteorscatter requires patience, some QSOs can take over an hour. Some
special operating protocols are necessary.
The MS community (Using FSK441) historically has relied on the PingJockey web
posts to complete the QSO. When a station saw the RRR ST he announced on PJ
that “he had the Rs” and the qso was complete. The stations might or might not
have sent the final 73s.
The new WSJTX MSK mode is so good at decodes, there is now much more
opportunity for “random” Qs. This means posting on PJ is not (and should not
be necessary) to complete a QSO.
Here’s how it should work.
First station to decode RRR starts sending 73. He sends 73 indefinitely until
he sees a 73 reply back from the other station.
The last station to sending 73 needs a counter (4-10 typical) to determine the
number of times to send the final 73. This is the best way to assure that the
other station knows the QSO is complete.
Then and only then should the prompt to log box pop up.
Dan n5tm
From: Black Michael [mailto:[email protected]]
Sent: Sunday, January 01, 2017 4:50 PM
To: WSJT software development <[email protected]>
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
Oh...you mean the whole idea of RRR...not the logging prompt.
Others know better...but I think the impetus came from EME where it's already
long enough to get one QSO down. Why send anything more than what is
absolutely essential?
So we have 3 groups.
EME -- really long QSOs
HF -- EME without all the repeated attempts typically..so yeah...you could add
another 2 minutes per QSO I suppose...some do....
Fast mode -- zippity-do-dah with repeats.
We should do our best to accommodate all. If "protocol" wants to change
depending on mode it should be put in the manual. But then you have the EME/HF
guys who have to change habits from one to the other if you add another 73 to
HF.
de Mike W9MDB
_____
From: Seb <[email protected] <mailto:[email protected]> >
To: WSJT software development <[email protected]
<mailto:[email protected]> >
Sent: Sunday, January 1, 2017 4:30 PM
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
Mike if the intent was not to shorten the time for a QSO, then what was the
purpose?
Once again, see my example if I’m sending Tx3 and waiting for Tx4. The station
I’m working sends Tx4 once, and logs the contact because typically when we see
a popup, it generally means to do something. I might not hear his single
transmission of Tx4, whether it is on meteor scatter, EME or HF.
73 de Sebastian, W4AS
On Jan 1, 2017, at 5:15 PM, Black Michael <[email protected]
<mailto:[email protected]> > wrote:
It doesn't shorten the time for a QSO. You must be referring to the idea that
RRR is the last message for the CQ side. Seems the fast mode people still send
a 73 which isn't surprising. But the EME people and HF want the RRR to be last.
Can't argue with it being an option, can you? Should make everybody happy.
de Mike W9MDB
_____
From: Jay Hainline <[email protected] <mailto:[email protected]> >
To: 'Black Michael' <[email protected] <mailto:[email protected]> >; 'WSJT
software development' <[email protected]
<mailto:[email protected]> >
Sent: Sunday, January 1, 2017 4:08 PM
Subject: RE: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
I don’t know for certain why this was changed in the first place except the
JT65 HF crowd is always looking for a way to sidestep a sequence to shorten the
time for a QSO. This does not work in the meteor scatter VHF world where you
are relying on random data bits to fly in on a meteor for less than 1 second
and you are trying to decode just what the guy on the other end has received.
If it aint broke, don’t fix it.
I hope I don’t get black balled for being negative like the Ham Radio Deluxe
people do to users of their software. Lol ;-)
73 Jay KA9CFD
From: Black Michael [ <mailto:[email protected]> mailto:[email protected]]
Sent: Sunday, January 1, 2017 3:39 PM
To: WSJT software development < <mailto:[email protected]>
[email protected]>
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
I think the consensus solution would be to make it a user option.
Seems the meteor scatter people have the most problems with it since they were
quick to speak up.
I had proposed at one time to make the "Prompt me to log QSO" a tri-state box
so one could check 73, 73+RRR, or none. But seems the binary choice is clearer
and there are no other tri-state checkboxes in WSJT-X.
So this patch makes it optional with an added option line below the current
prompt option. All worlds should be happy with this.
<https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1>
https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1
de Mike W9MDB
_____
From: Seb < <mailto:[email protected]> [email protected]>
To: WSJT software development < <mailto:[email protected]>
[email protected]>
Sent: Sunday, January 1, 2017 1:26 PM
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
IMHO the introduction of the log QSO prompt when you are sending RRR does not
solve or help anything.
It is useless when you are doing meteor scatter. If I’m sending Tx3 and the
other station hears that and sends Tx4 and then logs the contact, it is not a
valid QSO because I have no idea if the other station has heard my report. I
will end up sending Tx3 several times until I just give up on the contact.
73 de Sebastian, W4AS
On Jan 1, 2017, at 9:38 AM, Jay Hainline < <mailto:[email protected]>
[email protected]> wrote:
This was introduced in r7431. I think its bad form to get a prompt to log the
QSO when you are sending RRR. How do you know if your QSO partner has received
it if he does not send 73 back to you??
Jay Hainline KA9CFD
Colchester, IL EN40om
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
