Improve QSO exchanges for partially correct callsigns

[w7sst]

When running a simulation, sometimes a callsign is copied incorrectly and entered into the Callsign exchange entry field. After hitting Enter, the partial callsign is sent. The calling station will respond with a corrected callsign and optionally the exchange information.

There are two scenarios.

1 - User sends partial call only (using F5 function key)

This condition can easily be created by following these steps:

1. start a simulation in Single Call mode.
2. Enter the calling callsign, but change the last letter.
3. Hit F5 to send the partial callsign.
4. This will now enter the osNeedCallNr state.
5. The calling station will send a response with the corrected callsign and optional exchange.

State osNeedCallNr

The following messages are sent after receiving a partially-correct callsign from the user without an exchange.
The first column shows the original messages and the second column shows the revised messages.

Original	Freq	Revised (v1.85)	Freq
DE <call>	50%	DE <call>	16.7% (1/6)
DE <call> <call>	50%	DE <call> <call>	16.7% (1/6)
.	.	<call> <call>	16.7% (1/6)
.	.	<call> <call> <exch>	16.7% (1/6)
.	.	<call> <exch>	33.3% (1/3)

The following is the new code showing the responses for this case (osNeedCallNr).

    // osNeedCallNr - They have sent an almost-correct callsign.
     osNeedCallNr:
      if (RunMode = rmHst) then
        Result := msgDeMyCall1
      else
        case Trunc(R2*6) of
          0: Result := msgDeMyCall1;    // DE <my>
          1: Result := msgDeMyCall2;    // DE <my> <my>
          2: Result := msgMyCall2;      // <my> <my>
          3: Result := msgMyCallNr2;    // <my> <my> <exch>
          4,5: Result := msgMyCallNr1;  // <my> <exch>
        end;

2 - User sends partial call and their exchange (using Enter key)

This condition can easily be created by following these steps:

1. start a simulation in Single Call mode.
2. Enter the calling callsign, but change the last letter.
3. Hit Enter to send the partial callsign and exchange
4. This will now enter the osNeedCall state.
5. The calling station will send a response with the corrected callsign and exchange.

State osNeedCall

The following messages are sent after receiving a partially-correct callsign and exchange information from the user.
The first column shows the original messages and the second column shows the revised messages.
Notice the revised messages are now always sending the exchange. I suppose I should leave out the exchange on one of these.

Original	Freq	Revised (v1.85)	Freq
DE <call> <exch>	50%	DE <call> <exch>	16.7% (1/6)
DE <call> <call> <exch>	25%	DE <call> <call> <exch>	16.7% (1/6)
<call> <call> <exch>	25%	<call> <call> <exch>	33.3% (1/3)
.	.	<call> <exch>	33.3% (1/3)

The following is the new code showing the responses for this case (osNeedCall).

    // osNeedCall - I have their Exch (NR), but need user to correct my call.
    osNeedCall:
      if (RunMode = rmHst) then
        Result := msgDeMyCallNr1
      else
        case Trunc(R2*6) of
          0: Result := msgDeMyCallNr1;  // DE <my> <exch>
          1: Result := msgDeMyCallNr2;  // DE <my> <my> <exch>
          2,3: Result := msgMyCallNr2;  // <my> <my> <exch>
          4,5: Result := msgMyCallNr1;  // <my> <exch>
        end;

[f6fvy]

Does the build mentioned in PR #313 include these mods to be tested ?

[w7sst]

No, not yet. I will post a build sometime today (it got too late last night).

…

-Mike

On Fri, May 31, 2024 at 5:31 AM Laurent Haas - F6FVY < ***@***.***> wrote: Is the build mentioned in PR #313 <#313> include these mods to be tested ? — Reply to this email directly, view it on GitHub <#317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZJSVSKGPUX4SF66VR6NGMDZFBUSHAVCNFSM6AAAAABISMJWNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRHE4TAOJVHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[w7sst]

Hi Laurent,
Here is the link to build v1.85-dev.3 which includes changes from all three Pull Requests (#315, #316, #317).

@f6fvy