PSRTTY 1.07 integrations

HAMLOG and other integrations

HAMLOG target: Ver5.48

Uses the Turbo HAMLOG/Win public API introduced in Ver5.27c. On Windows, start one HAMLOG instance and open its QSO input window. Run both programs with the same privilege level.

Open Integration → HAMLOG integration settings. Check the connection; the responding window title is displayed.
Enable transfer when logging. This defaults to OFF. The default save mode fills HAMLOG input fields only; save the QSO in HAMLOG yourself. Alternatively, choose to request saving after transfer. Save these settings; they are shared by all profiles.
After PSRTTY saves a QSO to ADIF, it transfers it to HAMLOG. Manual logging and TU73 auto logging use the same path. PSRTTY increments the sent serial only once.

CALL, JST date/time, sent/received RST, frequency and RTTY mode are transferred. SENT and RCVD are retained in Remarks1; the station CALL is in Remarks2. Contest exchanges are not inferred as JCC/JCG codes. HAMLOG QSL, Code, GL, Name and QTH settings/lookup results are retained.

CALL / Name / QTH lookup

Lookup in the settings window enters a CALL in HAMLOG’s empty input window, invokes HAMLOG’s Enter processing and displays Name/QTH. Results depend on HAMLOG lookup settings and stored records and may be empty. Logging that same CALL fills the draft created by lookup. If the draft was edited in HAMLOG, automatic transfer is stopped to protect it. Save or clear the draft before proceeding.

Saving and transfer failures

In input-only mode, save the QSO in HAMLOG before recording the next QSO. Other QSO drafts are never overwritten. Automatic saving reads back and checks the transfer before invoking HAMLOG’s Save API. You can check the result in HAMLOG’s input window and log.

Failures show a dialog with the reason and suggested action. The PSRTTY ADIF record is already saved: do not add that QSO again. Interrupted transfers are journaled and not retried automatically. Check HAMLOG and manually enter only missing QSOs, or use File → HAMLOG CSV export. Records, edits and deletions in HAMLOG do not synchronize back to PSRTTY.

zLog target: 3.0.4.0 (ZLOG3040)

Integration → zLog Reiwa integration settings opens ADIF export. Selected QSOs are transferred by file, without live radio/log control. File → ADIF export opens the same export wizard.

In zLog, select the matching contest, station CALL and time settings. ADIF times are UTC; zLog converts them according to its contest settings.
Select the export format, period, station CALL, bands and QSOs, then save.
Import the ADIF file in zLog and check count, time, band, mode, both RSTs, both exchanges and multipliers. Avoid importing the same file twice.

Format	Exchange mapping
Standard ADIF	STX_STRING/SRX_STRING and numeric STX/SRX, as before.
General zLog	Also retains original SENT/RCVD and station CALL in COMMENT.
JARL WW RTTY	Received age also goes into AGE. Enter one or two digits.
CQ WW RTTY	Received zone goes into CQZ and state/province into STATE, e.g. 05 MA. Zone must be 01–40.

The target zLog ADIF importer does not include state/province in the CQ WW RTTY received exchange.After import, use the original RCVD in the note to correct affected exchanges and multipliers. Numeric fields may lose leading zeroes in their display; the original text is retained in string fields and notes. Check contest configuration and exchanges before submitting a contest log.

Radio controls

NB and NR read/write are enabled through Hamlib for listed Yaesu/Kenwood models except FT-817/818/857, with state readback. Yaesu uses the DNR label. FT-991/FT-991A, FTX-1, FT-710, FTDX10, FTDX101D/MP and FTDX3000 offer mode-specific receive widths. TS-590SG DATA/SSB width is adjusted by changing high cut while preserving low cut.

Hamlib 4.7.2 does not implement receive bandwidth control for TS-890S/TS-990S; use the radio controls for width. NB/NR remain available. Controls are disabled during TX or when connection/state retrieval fails.