When opening a logger database in JT-Bridge, it will be read to collect QSO and QSL information. All QSOs logged in WSJT-X will update this information, but if a QSO is logged without JT-Bridge running, there is a menu item in the File menu to sync with the logger.
Here are some notes about each logging application
Aether
JT-Bridge
will search the Aether database for QSO information.
Received status in any of the QSL
methods indicates that the QSO is confirmed.
Only Aether DB file format is supported.
When logging a QSO to Aether, JT-Bridge will log call, frequency,
mode, sent report, received report, grid square, power and
comments from WSJT-X.
The transceiver frequency can be read and the PTT can be read and
set from WSJT-X.
MacLoggerDX
JT-Bridge will search the
MacLoggerDX database for QSO information.
The QSL R field is split by comma. These "sub"-fields are
searched for LoTW or eQSL. If it's not found, it is treated as
paper QSL if not beginning with N or n.
Configure MacLoggerDX for CAT control and QSO logging. See MacLoggerDX documentation. It's not recommended to use JT-Bridge for this.
JT-Bridge will search the RUMlogNG database for QSO
information.
R or X in the QSL, LoW or eQSL field
indicates that the QSO is confirmed on respective method (QSL for
paper, LoW for LoTW and eQ for eQSL).
Configure RUMlogNG for CAT control and QSO logging. See RUMlogNG documentation. It's not recommended to use JT-Bridge for this.
JT-Bridge will search the RUMlogNG Contest database for QSO
information.
When logging a QSO to RUMlogNG Contest database, JT-Bridge will log call, frequency, sent report, received report from WSJT-X. Time and mode will be taken from RUMlogNG.
Configure RUMlogNG for CAT control and QSO logging. See RUMlogNG documentation. It's not recommended to use JT-Bridge for this.