PingDX Bridge

Your 11 m FT8 and FT4 QSOs land in your logbook by themselves, straight from WSJT-X or JTDX.

How it works

A small program to run on the computer connected to your radio. Each time WSJT-X or JTDX logs a QSO, it sends it to your PingDX logbook. QSOs made on other bands are ignored. Without a network, they are kept and sent later. The same QSO is never logged twice.

Digital modes are not allowed on 11 m in every country: check the rules that apply where you operate.

Compatible programs and systems

Directly: WSJT-X (versions 2 and 3), WSJT-X Improved and JTDX, through their UDP output (default setting, port 2237).
Behind another program: GridTracker and JTAlert, which relay WSJT-X packets, and Log4OM with an outgoing UDP "ADIF" connection.
Not compatible: N1MM Logger+ (it broadcasts its QSOs in another format) and programs without UDP output. For those, export an ADIF file and import it into your logbook.
Modes: FT8 and FT4, saved as such. Only QSOs between 26 and 28 MHz are sent; other bands are ignored.
Systems: Windows 10 and 11 (64-bit), macOS (Apple or Intel chip), Linux (64-bit PC), Raspberry Pi (32 or 64-bit).

PingDX unreachable or Internet down: no QSO is lost. The bridge keeps them on the computer, even if it is closed in the meantime, and sends them as soon as PingDX answers.

Was the bridge closed while you operated? Those QSOs never reached it, but WSJT-X keeps them in its wsjtx_log.adi file (File → Open log directory): import it into your logbook, duplicates are skipped.

Download

Members only

PingDX Bridge sends your QSOs to your PingDX logbook: create a free account, or sign in, to download it.

Create an account Sign in

Getting started

1
Run the program
On first start, your browser opens on PingDX: click "Authorize". That's all, no key to copy. After that, a double-click is enough. Keep the window open while you operate: the green indicator at the top of PingDX shows it is connected.
2
Set up WSJT-X or JTDX
File → Settings → "Reporting" tab: UDP server 127.0.0.1, port 2237, and tick "Accept UDP requests". This is WSJT-X's default setting.
3
Show FT8 and FT4 in PingDX
In "My usage", turn on "Digital modes" to also pick FT8, FT4 and DIGI when you log a QSO by hand.
My usage

If your computer shows a warning

Windows: "Windows protected your PC" → click "More info", then "Run anyway". The program is not signed; this is expected.
Mac: use the one-line command above, then double-click "PingDX Bridge" on the Desktop. Installed this way, the Mac shows no warning.
Linux: a file downloaded with the browser is not executable. Use the one-line command above; PingDX Bridge then appears in the applications menu and opens in a terminal.

Try it without a radio

Start the program, then type "pingdx-bridge simulate" in another window: two test QSOs (14SIM01 in FT8, 14SIM01B in FT4) arrive in your logbook; delete them afterwards. With -dry-run nothing is sent: the QSOs are only printed.

pingdx-bridge simulate
pingdx-bridge -dry-run

WSJT-X also runs without a radio (Radio: "None"): its "Log QSO" button sends a real QSO to the program.

Update

Each time it starts, the program checks for a new version and offers to update: just press Enter. The indicator at the top of PingDX turns amber when your version is out of date. To do it by hand:

Windows: close the program, download the new file above and replace the old one.
Linux and Mac: run the one-line command again, or type pingdx-bridge update in a terminal.

Your settings and the link to your logbook are kept.

Uninstall

Windows: close the program and delete the pingdx-bridge-windows-amd64.exe file, then remove its access by revoking the "PingDX Bridge" key in Profile → Account → API keys.
Linux and Mac: type the command below in a terminal. The program removes its own access to your logbook, then deletes its settings, its shortcut (menu or Desktop) and itself.

~/.local/bin/pingdx-bridge uninstall

QSOs already saved stay in your logbook.

Special cases

Port 2237 is already taken (GridTracker, JTAlert…): have them relay to 2238 and run with -listen 127.0.0.1:2238, or use WSJT-X multicast with -multicast 224.0.0.1:2237.
To keep GridTracker behind the bridge: -forward 127.0.0.1:2238 relays every packet to it.
Programs that relay WSJT-X packets or send ADIF over UDP (GridTracker, JTAlert, Log4OM) are understood too.
To pair again (another account, access removed): run again with -reset.
Pending QSOs are kept on the computer and go out as soon as PingDX can be reached.

pingdx-bridge -listen 127.0.0.1:2238
pingdx-bridge -multicast 224.0.0.1:2237
pingdx-bridge -forward 127.0.0.1:2238
pingdx-bridge -reset

How it works

Compatible programs and systems

Download

Members only

Getting started

Run the program

Set up WSJT-X or JTDX

Show FT8 and FT4 in PingDX

If your computer shows a warning

Try it without a radio

Update

Uninstall

How it works

Compatible programs and systems

Download

Members only

Getting started

Run the program

Set up WSJT-X or JTDX

Show FT8 and FT4 in PingDX

If your computer shows a warning

Try it without a radio

Update

Uninstall