Re: [wsjt-devel] FT4 logging prompt

[Paul Kube]

>
> WSJT-X is open source.  You can make those changes you are suggesting,
> thereby customizing your station operations.


Yes I know that. But:

 However, do not be surprised if you actually loose a lot of
> confirmations... My station.  My logbook.  My rules.


Yes and so my proposal is to make the "short QSO" the default for WWDIGI.
The contest's rules, that everybody in the contest plays by. Contesters
will like the higher QSO rates. Maybe it will catch on more generally,
maybe not.

And I would be happy to implement this as a patch against 2.4.0-rc4 or
whatever version, if I had reason to think it would be accepted.

73, Paul K6PO


On Fri, May 7, 2021 at 5:34 PM Jeff Stillinger via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> WSJT-X is open source.  You can make those changes you are suggesting,
> thereby customizing your station operations.   There is no licensing
> restrictions that would stop you from doing so (see GPL 3).
>
> However, do not be surprised if you actually loose a lot of
> confirmations.   Yes, I am one of those stations that expect the basic
> exchange format as outlined in the User Guide to be completed in order to
> be confirmed.   My station.  My logbook.  My rules.   I will always
> complete any QSO regardless.  I just don't log for confirmation the ones
> that have missing pieces.  I strongly believe this helps maintain the
> integrity of awards.   But...  that is me.   Someone else may feel
> differently.   It's all good in the rf hood.
>
>
>
>
> On 5/6/21 3:28 PM, Martin Davies G0HDB wrote:
>
> The FT4 mode was introduced in WSJT-X version 2.1.0 in 2019; the release
> notes and announcements state that the mode is intended for use in HF
> digital contesting where 'quick-fire' exchanges such as those achieved
> using RTTY are desired.  I'd like to suggest a change that would help
> achieve this aim a bit better; the following applies to v2.1.0 and all
> subsequent versions up to and including v2.3.1 (I haven't yet tried any of
> the RC versions of v2.4.0).
>
> An FT4 (and an FT8!) QSO generally looks something like the following:
>
> CQ K1JT FN20
>   K1JT G0HDB IO82
> G0HDB K1JT -10
>   K1JT G0HDB R-08
> G0HDB K1JT RR73
>   K1JT G0HDB 73
>
> Currently, the logging window only pops open on my screen to prompt me to
> log the QSO when the final (Tx5) '73' message is being sent - this is to
> all extents and purposes superfluous because the QSO has been successfully
> completed when K1JT has sent his RR73 (and I've received it).  My sending
> the superfluous '73' message extends the overall duration of the QSO by
> adding a further Tx period at my end of the sequence so I can't move on to
> trying to start the next QSO.
>
> I'd like to suggest that the logging window is opened when I've *received*
> the other station's RR73 message and that sending the final Tx5 '73'
> message is either removed from the sequence altogether or is made
> optional.  This would help to improve the overall throughput of FT4 QSOs.
>
> The code to open the logging window on receipt of an incoming 'RR73'
> message and to desist from sending the Tx5 '73' message must already exist
> within the app because that's what already happens when I operate as a
> Hound in FT8 Fox & Hounds mode - when I receive the Fox's 'RR73' the
> logging window pops open and my system doesn't send the unnecessary Tx5
> '73' .
>
> I'd actually like to see the logging window open in any mode when I either
> send *or receive* an RRR or RR73 message - in my opinion that would align
> the prompting to log the QSO much more closely with the completion of the
> exchange of the essential information for the QSO and would leave the
> sending of a final '73' as an optional nicety.
>
> --
> 73, Martin G0HDB
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_6602682828413212526_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> --
> Jeff Stillinger - KB6IBB
> KB6IBB Laboratories
> Wylie, Texas - United States
>
> ___
> 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] FT4 logging prompt

[Martin Davies G0HDB]

On 7 May 2021 at 11:39, Paul Kube wrote:

> I agree with Martin and others, but let me suggest a slight compromise.
> 
> Instead of changing the default sequence for all FT4 QSO's, change it for
> FT8/FT4 in WWDIGI contest mode only, and advertise the change. This won't
> disrupt anyone's ideas about how general FT QSO's should be done;
> contesters will understand the change, and appreciate it. 2021 WWDIGI is
> August 28-29; should be time enough to implement it.

[Snipped]

Re: the suggestions from Paul, my view is that it would be sensible to change 
the default 
sequence so that logging is prompted on receipt of an incoming RRR or RR73 and 
the 
subsequent sending of the Tx5 73 is eliminated (or made optional - see below) 
should apply 
to all FT4 'Special Operating Activity' contest options, not only to the WWDigi 
contest option.  
However...

Some contests, eg. the RSGB FT4 Contest series, don't use any of the special 
contest QSO 
formats but use the general FT4 QSO format, as I'd indicated in my earlier 
posting.  I can 
understand that, even in such contest scenarios, some people might prefer to 
send a final 
Tx5 73 message after they've received the RRR or RR73 from the other party in 
the QSO, in 
order to provide that other party with an (IMO unnecessary) acknowledgement of 
receipt of 
the RRR or RR73.  This was why I had suggested that sending the Tx5 73 after 
logging a 
QSO on receipt of an incoming RRR/RR73 should be a configuration/settings 
option.  

Making the sending of the Tx5 73 optional after receipt of an incoming RRR/RR73 
would 
enable people such as me to disable the sending, albeit with perhaps an 
attendant increase 
in the risk that the sender of the RRR/RR73 wouldn't log their QSO with me 
because they 
hadn't received a 73 from me (even though they would have been prompted to log 
the QSO 
when they sent the RR73!).  Making the sending of the Tx5 73 optional would 
also make it 
possible for those people who want to send the final 73 to do so, to provide 
their QSO partner 
with confirmation of receipt of the latter's RRR or RR73.

As described in my original proposal on this topic I'd much prefer to see the 
sequence for all 
modes, not only FT4 but also FT8, MSK144, etc etc, amended so that logging is 
prompted 
when an RRR or RR73 is either sent *or received*, with the subsequent sending 
of Tx5 73 
made optional as described above, because IMO it would align the logging prompt 
better with 
the completion of the exchange of the essential information in the QSO.

With regard to the suggestion from Jeff that the WSJT-X app's code is 
open-source and that 
I could customise the code to implement my suggestions - that would be way, way 
beyond 
my programming skills, I'm afraid...  :-)

--
73, Martin G0HDB



-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


WPM$XTPI.PM$
Description: Mail message body
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel