Add support to log QSOs directly to DXKeeper via TCP/IP

[ny4i]

While there is a UDP gateway to log contacts, this requires running a gateway program. For casual DX chasing-type contesting, I would rather have a direct TCP/IP connection to DXKeeper to log contacts. One other benefit is to add a delay between the logged time and the actual time the contact is sent. This allows to edit the contact if necessary. That timer should be on a parameter (EXTERNAL LOG DELAY = 60 SECONDS).

This code should be put in its own unit to be the start of making the connection toother loggers as well. The option to log to an external program should be disabled by default.

The following information is how to send a contact to DXKeeper. Note that the DXLab uses a base port (defaults to 52000). The DXKeeper port listens on the base port + 1 so add EXTERNAL LOG BASE PORT = 52000 as a parameter.

Interoperation via TCP

DXKeeper accepts a TCP message beginning with the externallog command directing it to log a QSO in a manner governed by multiple parameters:

- N is the total length of the ExternalLogADIF field and all specified option fields valid ADIF record of length M - the QSO to be logged Options - a subset of the [General Options](https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Options) available for importing QSOs Y - if present, submit the logged QSO to eQSL Y - if present, submit the logged QSO to LoTW Y - if present, deduce items missing from the QSO to be logged from the entity, primary subdivision, and USAP databases Y - if present, query the [currently selected Callbook](https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Callbook%20Tab), DXCC database, and RDA database for missing items Y - if present, query the eQSL database to determine if the callsign specified in the ADIF record is an authenticity-guaranteed member of eQSL, and if so set the QSO's [eQSL Member](https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#eQSL.cc%20mem) item to A Y - if present, query the eQSL database to determine if the callsign specified in the ADIF record has submitted QSOs to LoTW to LoTW within the [specified interval](https://www.dxlabsuite.com/dxkeeper/Help/QSLConfiguration.htm#Maximum%20age%20of%20most%20recent%20LotW%20upload), and if so set the QSO's [LotW Member](https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#LotW%20mem) item to Y Y - if present, query the [Override list](https://www.dxlabsuite.com/dxview/Help/Configuration.htm#Entity%20Overides) for the presence of the callsign specified in the QSO to be logged; if found, update the logged QSO with the information specified in the override Y - if present, submit the logged QSO to Club Log Y - if present, submit the logged QSO to QRZ For example, receipt of the message externallogP5DX 599 599 14.004 20M CW 20220411 072800 AA6YQ 1000 PM29 YYYYYYYY would result in logging a QSO with P5DX on 140004 kHz in CW on 2022-04-11 at 0728Z in Grid PM29 with 1000 watts; the override list would be checked for the presence of P5DX, missing items would be deduced from available databases, the currently-selected callbook would be queried for additional information, the logged QSO's eQSL and LoTW membership items would be set to Y, and the logged QSO would be submitted to Club Log, eQSL, and LoTW. ```

[ny4i]

Thanks. If you have not, can you put an installer for this under the latest directory so I can test?ThanksTomPrincipal Solutions ArchitectBetter Software Solutions, Inc. 727-437-2771813-205-6388 (mobile/text)On Jan 21, 2024, at 2:00 PM, Howie Hoyt @.***> wrote: Closed #707 as completed via #714.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>

[n4af]

Hi Tom Shud b Url on end of issue707 ?

On Sun, Jan 21, 2024, 15:00 Tom Schaefer @.***> wrote:

Thanks. If you have not, can you put an installer for this under the latest directory so I can test?ThanksTomPrincipal Solutions ArchitectBetter Software Solutions, Inc. 727-437-2771813-205-6388 (mobile/text)On Jan 21, 2024, at 2:00 PM, Howie Hoyt @.***> wrote: Closed #707 as completed via #714.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/issues/707#issuecomment-1902744771, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVLCUAIRL5G7CWO6SAIX6LYPVXWZAVCNFSM6AAAAAA726NBBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSG42DINZXGE . You are receiving this because you modified the open/close state.Message ID: @.***>