This discussion started out as a question as to if the auto sequencer could
respond to a specific non standard message and I digressed it.   My 
apologies.

Back to that original question...   I pseudo coded the WSJT auto sequencer 
in
order to document it in the manual.   One of my projects is looking through 
the
JT9 auto sequencer to see if there are any improvements to be made either
to either the ISCAT one or the JT9 one.   This is the pseudo code as it 
exists now...

if TX Auto is checked and Auto is On
if Current TX Sequence equals TX1
  if Received Message equals valid TX1
   Set Signal Report
   Advance to TX2
  else if Received Message equals valid TX2
   Set Signal Report
   Advance to TX3
else if Current TX Sequence equals TX2
  if Received Message equals valid TX2
   Set Signal Report
   Advance to TX3
  else if Received Message equals valid TX3
   Advance to TX4
else if Current TX Sequence equals TX3
  if Received Message equals valid TX3
   Advance to TX4
  else if Received Message equals TX4
   Set TXStopCount to Auto73Count
   Advance to TX5
   Set Log QSO to blink
else if Current TX Sequence equals TX4
  if Received Message equals valid TX4
   Set TXStopCount to Auto73Count
   Advance to TX5
   Set Log QSO to blink
  else if Received Message equals valid TX5
   Set TXStopCount to Auto73Count
   Advance to TX5
   Set Log QSO to blink
else if Current TX Sequence equals TX5
  if Received Message equals valid TX5
   Set TXStopCount to 0
   Set Auto is ON to Auto is OFF
  else if Received Message equals valid TX4
   Set TXStopCount to Auto73Count
  else
   Decrement TXStopCount
   if TXStopCount equals 0
    Set Auto is ON to Auto is OFF

As you can see the auto sequencer is highly situational and the end game, 
when to
quit transmitting gets a little complicated.   There is an inherent catch 22 
that needs
to be dealt with and is to some degree in the pseudo code.  The reports I 
had during
the ISCAT craze this summer was that it was working OK.

The RR73 question really boils down to can the statement

if Received Message equals TX4

be modified to also recognize RR73 as a combined RRR and 73.   The answer is 
obviously yes
however in the context of the auto sequencer that really does not change 
much.  The
end game still needs to be played out so the station that sent RR73 is at 
some point
going to need to send a 73 anyway for things to gracefully stop under 
automatic
control.

Assuming we were to recognize RR73 as a valid RRR what else do we recognize? 
I have
seen variations of this such as R73, 73RR, etc.   This gets a little 
complicated and
someone will be left out.

Also a practice I have seen repeatedly is that of skipping the TX4 message
completely and going straight to TX5.   Should the auto sequencer recognize 
that as
valid?

My point, and my opinion for what it is worth, is that the auto sequencer 
should not
be in the business of attempting to recognize an infinite variation of 
possible
non standard messages.  That would  be a programming nightmare.   Once 
WSJT(x)
is set up with proper from and to calls (and possibly grid) the messages 
recognized by
the auto sequencer should be "by the book".  If the book changes, then and 
only then
should the auto sequencer change.

Does this mean non standard messages are not allowed?   No, it simply means 
they need
to be dealt with manually.   That leaves it up to the operator to decide if 
a non standard
message meets the QSO criteria for their station.

73 de Bill ND0B



by the auto sequencer should be fixed based on those standard messages.




------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to