JTDX-VU v0.6.0

JTDX-VU for VUCG v0.6.0. AutoSeq goes for the stations your log needs, you can queue a station with a right-click, the Notifications settings are redesigned, and the Pwr slider becomes TX and RX sliders. Also fixes the Fake It split creeping up the band over TCI.

What's new in v0.6.0

• AutoSeq goes for what your log needs first. When it picks a CQ to answer, and when several stations call your CQ, AutoSeq takes a new DXCC first, then a DXCC new on this band, then one new in this mode, and only then the usual JTDX order. Always on; from Club Log when enabled.
• Queue a station. Right-click a decode > Queue CALL. AutoSeq calls it the next time it is decoded, before anyone else, and takes it off the queue once logged. The queue shows above the Rx Frequency pane.
• AutoSeq calls only stations decoded right now. JTDX could go back to a station that called you minutes ago and isn't heard any more; now every pick must be in the latest decode period.
• Notifications page redesigned (Settings > Notifications): one row per kind of "new" (CQ zone, ITU zone, DXCC, grid, prefix, call) in priority order, each with its Band / Mode checks, colour squares and Beep on one line, plus "Already worked", "Messages and markers" and a live preview. Explanations are tooltips.
• Background highlight on/off. Off keeps the decode panes' plain background and colours the text instead.
• New only tick above the decodes (replaces the four-way "Show:" dropdown): shows only decodes that get a "new" colour from Settings > Notifications, so what counts as new is chosen in one place.
• TX and RX sliders. "Pwr" is now TX. With TCI audio it shows the SDR program's own drive and moves with it - nothing changes your power until you move it (it used to show 0 after a start, and moving it set the SDR program's RF power). A new RX slider raises or lowers the received audio going to the decoder and level meter (-20 to +20 dB), for any radio.
• Auto CQ and 1 QSO exclude each other. Switching Auto CQ on clears 1 QSO; pressing 1 QSO during an Auto CQ run means "finish this QSO, then stop".
• AnsB4 and 1 QSO stay on across band changes. A band change now switches off only Auto CQ.
• Choose which wanted filters show: View > Wanted filters (or right-click a filter label) shows or hides Callsign, Prefix, Grid and Country one by one.
• JTTY calls heard lists only the stations sending, not the stations they call.

Fixes

• Fake It split over TCI no longer creeps up the band. At the start of each Tx the SDR program echoes the Tx frequency before it confirms PTT, and JTDX took that echo as the new receive frequency - a loop that could move the dial several kHz in one transmission. JTDX now keeps your receive frequency while it has asked for Tx and until the radio is back after it.
• UDP errors no longer pop up a box on every send (for example a UDP server macOS won't send to, such as 255.255.255.255). They show on the status bar, with a pointer to Settings > Reporting.

Not yet tried on air: the queue, wanted-first, the TX/RX sliders and Auto CQ / 1 QSO - please report anything odd.

Known issue (AetherSDR)

AetherSDR 26.9.5 stops sending TCI audio when no TCI client has been connected for more than 10 seconds (aethersdr/AetherSDR#6006). The fix (#6116, tested on a FLEX-6600 with JTDX-VU) is merged and will be in AetherSDR's next release. Until then restart AetherSDR when JTDX-VU says "no audio from the SDR program"; JTDX-VU reconnects with audio on its own.

Downloads

Platform	File	Runs on
macOS, Apple Silicon	JTDX-VU-0.6.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.6.0-macos-x86_64.zip	macOS 15 Sequoia or later
Windows x64	JTDX-VU-0.6.0-windows-x64.zip	Windows 10 / 11, 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.6.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.

How to install

macOS (Apple Silicon or Intel)

1. Download the zip for your Mac (Apple menu > About This Mac: "Apple
   M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip.
2. Drag JTDX-VU into Applications.
3. First launch. The app is ad-hoc signed, not notarized, so macOS
   blocks the first open:
   • macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
     the warning, then open System Settings > Privacy & Security,
     scroll down and click Open Anyway next to "JTDX-VU was
     blocked", and confirm.
   • macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
     Open.
   • Or, in Terminal: xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
4. Allow the microphone when asked; that is how macOS names access to
   your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
   System Settings > Privacy & Security > Microphone.
5. Shared memory (one-time, every Mac). The decoder needs more SysV
   shared memory than the macOS default; without it JTDX-VU stops with
   "Unable to create shared memory segment". In Terminal:

   sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432

   That lasts until the next restart. To make it permanent, download
   Darwin/com.jtdx.sysctl.plist from
   this repo and run
   sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
   It may need redoing after a macOS upgrade.
6. Set up your callsign, radio and audio in JTDX-VU > Settings…
   (Cmd+,).

Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.

Windows 10 / 11 (64-bit)

1. Download JTDX-VU-0.6.0-windows-x64.zip. Before unzipping,
   right-click the zip > Properties, tick Unblock, OK; this saves
   a warning for every file inside.
2. Right-click > Extract All… to a folder of your choice, for example
   C:\JTDX-VU. No installer and no administrator rights are needed.
3. Run bin\jtdx.exe in that folder. If Windows SmartScreen says
   "Windows protected your PC", click More info > Run anyway (the
   program is not code-signed). Right-click jtdx.exe > Send to >
   Desktop (create shortcut) for a desktop icon.
4. If Windows Firewall asks, allow access on private networks (JTDX-VU
   talks UDP to logging programs such as Log4OM, N1MM or JTAlert).
5. For rig control through OmniRig, install
   OmniRig separately. Hamlib, TCI
   and the other rig interfaces are built in.

Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.

Raspberry Pi / Debian 12 (arm64)

Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.

1. Download jtdx-vu-0.6.0-linux-arm64.deb, then in a terminal in the
   download folder:

   sudo apt update
   sudo apt install ./jtdx-vu-0.6.0-linux-arm64.deb

   Keep the ./ - it tells apt to install the file rather than look for
   a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
   jtdx package can't be installed alongside; apt offers to remove it.
2. For CAT control over a USB serial cable, give your user access to
   serial ports once, then log out and back in:

   sudo usermod -aG dialout $USER

3. Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
   jtdx in a terminal.

Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.5.3

JTDX-VU for VUCG v0.5.3. A small update to v0.5.2: the Auto CQ button is in the same place in every mode, and status-bar messages are no longer overlapped.

What's changed in v0.5.3

• Auto CQ is always directly under Monitor, in FT8 / FT4 / FT2 and in JTTY, so your hand finds it in the same place. In the FT modes Bypass, 1 QSO and AnsB4 now follow it; in JTTY, Halt Tx, Log QSO, Erase and Clear DX, as before. Small windows that hide Bypass / 1 QSO / AnsB4 no longer move it either.

Fixes

• Status-bar messages are readable. The "WD" watchdog box was drawn on top of messages such as "Band changed: ..." or "TCI reconnected". It now stays hidden while a message is shown and comes back when the message clears. "Band changed", "TCI reconnected" and "TCI audio back" clear after 10 seconds; the TCI warnings stay until the problem is gone.

Known issue (AetherSDR)

AetherSDR 26.9.5 stops sending TCI audio when no TCI client has been connected for more than 10 seconds - for example when you quit JTDX-VU and start it again a bit later (tracked as aethersdr/AetherSDR#6006). JTDX-VU tells you ("no audio from the SDR program - restart it"); restart AetherSDR and JTDX-VU reconnects with audio on its own.

Downloads

Platform	File	Runs on
macOS, Apple Silicon	JTDX-VU-0.5.3-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.5.3-macos-x86_64.zip	macOS 15 Sequoia or later
Windows x64	JTDX-VU-0.5.3-windows-x64.zip	Windows 10 / 11, 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.5.3-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.

How to install

macOS (Apple Silicon or Intel)

1. Download the zip for your Mac (Apple menu > About This Mac: "Apple
   M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip.
2. Drag JTDX-VU into Applications.
3. First launch. The app is ad-hoc signed, not notarized, so macOS
   blocks the first open:
   • macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
     the warning, then open System Settings > Privacy & Security,
     scroll down and click Open Anyway next to "JTDX-VU was
     blocked", and confirm.
   • macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
     Open.
   • Or, in Terminal: xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
4. Allow the microphone when asked; that is how macOS names access to
   your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
   System Settings > Privacy & Security > Microphone.
5. Shared memory (one-time, every Mac). The decoder needs more SysV
   shared memory than the macOS default; without it JTDX-VU stops with
   "Unable to create shared memory segment". In Terminal:

   sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432

   That lasts until the next restart. To make it permanent, download
   Darwin/com.jtdx.sysctl.plist from
   this repo and run
   sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
   It may need redoing after a macOS upgrade.
6. Set up your callsign, radio and audio in JTDX-VU > Settings…
   (Cmd+,).

Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.

Windows 10 / 11 (64-bit)

1. Download JTDX-VU-0.5.3-windows-x64.zip. Before unzipping,
   right-click the zip > Properties, tick Unblock, OK; this saves
   a warning for every file inside.
2. Right-click > Extract All… to a folder of your choice, for example
   C:\JTDX-VU. No installer and no administrator rights are needed.
3. Run bin\jtdx.exe in that folder. If Windows SmartScreen says
   "Windows protected your PC", click More info > Run anyway (the
   program is not code-signed). Right-click jtdx.exe > Send to >
   Desktop (create shortcut) for a desktop icon.
4. If Windows Firewall asks, allow access on private networks (JTDX-VU
   talks UDP to logging programs such as Log4OM, N1MM or JTAlert).
5. For rig control through OmniRig, install
   OmniRig separately. Hamlib, TCI
   and the other rig interfaces are built in.

Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.

Raspberry Pi / Debian 12 (arm64)

Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.

1. Download jtdx-vu-0.5.3-linux-arm64.deb, then in a terminal in the
   download folder:

   sudo apt update
   sudo apt install ./jtdx-vu-0.5.3-linux-arm64.deb

   Keep the ./ - it tells apt to install the file rather than look for
   a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
   jtdx package can't be installed alongside; apt offers to remove it.
2. For CAT control over a USB serial cable, give your user access to
   serial ports once, then log out and back in:

   sudo usermod -aG dialout $USER

3. Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
   jtdx in a terminal.

Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.5.2

JTDX-VU for VUCG v0.5.2. A small update to v0.5.1: Call Non-Stop now keeps going only while you are calling CQ, a band change switches automatic calling off, and TCI reconnects on its own and warns when audio stops.

What's changed in v0.5.2

• Call Non-Stop (the Auto CQ button in FT8 / FT4 / FT2) continues only after QSOs from your own CQ. When a station calls you, it goes straight back to CQ and the next caller after the QSO, as before. When you answer someone - double-click their CQ or their QSO, or type a call - Tx halts at the end of that QSO, as with 1 QSO.
• While Call Non-Stop is on, AutoSeq answers only stations calling you; it no longer jumps onto other stations' CQs (the "search CQ" call priority).
• Call Non-Stop is off in Hound mode, which halts after each QSO as it did in stock JTDX.
• A band change switches Auto CQ, AnsB4 and 1 QSO off, whether you change band in JTDX-VU or on the radio / SDR program, so a new band starts with no automatic calling. The status bar says which were on.
• TCI reconnects automatically. If the SDR program (AetherSDR, ExpertSDR, Thetis, ...) is closed or restarted, Tx halts and the status bar shows "TCI: ... reconnecting every 5 s" instead of the Rig Control Error box. Once the SDR program is running again, JTDX-VU reconnects and shows "TCI reconnected"; there is no need to restart JTDX-VU. Other rig types are unchanged.
• TCI audio watchdog. With TCI audio on, if no receive audio arrives for 10 seconds (transmit aside), JTDX-VU asks for it again once; if it still does not come, the status bar says "no audio from the SDR program - restart it" and JTDX-VU keeps retrying until audio is back ("TCI audio back"). AetherSDR 26.9.5 can stop sending TCI audio after the last audio client has been gone for more than 10 seconds; restarting AetherSDR clears it, and JTDX-VU can stay open.

Downloads

Platform	File	Runs on
macOS, Apple Silicon	JTDX-VU-0.5.2-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.5.2-macos-x86_64.zip	macOS 15 Sequoia or later
Windows x64	JTDX-VU-0.5.2-windows-x64.zip	Windows 10 / 11, 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.5.2-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.

How to install

macOS (Apple Silicon or Intel)

1. Download the zip for your Mac (Apple menu > About This Mac: "Apple
   M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip.
2. Drag JTDX-VU into Applications.
3. First launch. The app is ad-hoc signed, not notarized, so macOS
   blocks the first open:
   • macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
     the warning, then open System Settings > Privacy & Security,
     scroll down and click Open Anyway next to "JTDX-VU was
     blocked", and confirm.
   • macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
     Open.
   • Or, in Terminal: xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
4. Allow the microphone when asked; that is how macOS names access to
   your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
   System Settings > Privacy & Security > Microphone.
5. Shared memory (one-time, every Mac). The decoder needs more SysV
   shared memory than the macOS default; without it JTDX-VU stops with
   "Unable to create shared memory segment". In Terminal:

   sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432

   That lasts until the next restart. To make it permanent, download
   Darwin/com.jtdx.sysctl.plist from
   this repo and run
   sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
   It may need redoing after a macOS upgrade.
6. Set up your callsign, radio and audio in JTDX-VU > Settings…
   (Cmd+,).

Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.

Windows 10 / 11 (64-bit)

1. Download JTDX-VU-0.5.2-windows-x64.zip. Before unzipping,
   right-click the zip > Properties, tick Unblock, OK; this saves
   a warning for every file inside.
2. Right-click > Extract All… to a folder of your choice, for example
   C:\JTDX-VU. No installer and no administrator rights are needed.
3. Run bin\jtdx.exe in that folder. If Windows SmartScreen says
   "Windows protected your PC", click More info > Run anyway (the
   program is not code-signed). Right-click jtdx.exe > Send to >
   Desktop (create shortcut) for a desktop icon.
4. If Windows Firewall asks, allow access on private networks (JTDX-VU
   talks UDP to logging programs such as Log4OM, N1MM or JTAlert).
5. For rig control through OmniRig, install
   OmniRig separately. Hamlib, TCI
   and the other rig interfaces are built in.

Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.

Raspberry Pi / Debian 12 (arm64)

Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.

1. Download jtdx-vu-0.5.2-linux-arm64.deb, then in a terminal in the
   download folder:

   sudo apt update
   sudo apt install ./jtdx-vu-0.5.2-linux-arm64.deb

   Keep the ./ - it tells apt to install the file rather than look for
   a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
   jtdx package can't be installed alongside; apt offers to remove it.
2. For CAT control over a USB serial cable, give your user access to
   serial ports once, then log out and back in:

   sudo usermod -aG dialout $USER

3. Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
   jtdx in a terminal.

Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.5.1

JTDX-VU for VUCG v0.5.1. A small update to v0.5.0: Auto CQ now stops after a time limit, and the main window resizes properly with the two decode panes about half each.

What's new in v0.5.1

• Auto CQ time limit, 5 minutes by default. In JTTY, Auto CQ stops calling once the limit is reached (a CQ already on the air finishes) and says so in the status bar. In FT8 / FT4 / FT2, the Tx watchdog while Call Non-Stop is on is the same limit (it was a fixed 10 minutes). Set it from 1 to 60 minutes under Settings > JTTY > Auto CQ > Time limit.

Fixes

• Main window resizes properly. It could be shrunk until controls overlapped; it now stops at the size the controls need (about 1063x608 in FT8, 929x632 in JTTY - both fit a 1366x768 screen). In JTTY, extra height now goes to the received-text pane instead of empty gaps.
• Decode panes split about half each, in every mode. Since v0.5.0 the right-hand pane in the FT modes could not be made narrower than the JTTY macro panel, so the split stayed lopsided. The panes are now evened out at start-up, on every mode change and when the window is resized; nothing is squeezed below its minimum, and the divider can still be dragged.

Downloads

Platform	File	Runs on
macOS, Apple Silicon	JTDX-VU-0.5.1-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.5.1-macos-x86_64.zip	macOS 15 Sequoia or later
Windows x64	JTDX-VU-0.5.1-windows-x64.zip	Windows 10 / 11, 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.5.1-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.

How to install

macOS (Apple Silicon or Intel)

1. Download the zip for your Mac (Apple menu > About This Mac: "Apple
   M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip.
2. Drag JTDX-VU into Applications.
3. First launch. The app is ad-hoc signed, not notarized, so macOS
   blocks the first open:
   • macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
     the warning, then open System Settings > Privacy & Security,
     scroll down and click Open Anyway next to "JTDX-VU was
     blocked", and confirm.
   • macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
     Open.
   • Or, in Terminal: xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
4. Allow the microphone when asked; that is how macOS names access to
   your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
   System Settings > Privacy & Security > Microphone.
5. Shared memory (one-time, every Mac). The decoder needs more SysV
   shared memory than the macOS default; without it JTDX-VU stops with
   "Unable to create shared memory segment". In Terminal:

   sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432

   That lasts until the next restart. To make it permanent, download
   Darwin/com.jtdx.sysctl.plist from
   this repo and run
   sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
   It may need redoing after a macOS upgrade.
6. Set up your callsign, radio and audio in JTDX-VU > Settings…
   (Cmd+,).

Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.

Windows 10 / 11 (64-bit)

1. Download JTDX-VU-0.5.1-windows-x64.zip. Before unzipping,
   right-click the zip > Properties, tick Unblock, OK; this saves
   a warning for every file inside.
2. Right-click > Extract All… to a folder of your choice, for example
   C:\JTDX-VU. No installer and no administrator rights are needed.
3. Run bin\jtdx.exe in that folder. If Windows SmartScreen says
   "Windows protected your PC", click More info > Run anyway (the
   program is not code-signed). Right-click jtdx.exe > Send to >
   Desktop (create shortcut) for a desktop icon.
4. If Windows Firewall asks, allow access on private networks (JTDX-VU
   talks UDP to logging programs such as Log4OM, N1MM or JTAlert).
5. For rig control through OmniRig, install
   OmniRig separately. Hamlib, TCI
   and the other rig interfaces are built in.

Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.

Raspberry Pi / Debian 12 (arm64)

Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.

1. Download jtdx-vu-0.5.1-linux-arm64.deb, then in a terminal in the
   download folder:

   sudo apt update
   sudo apt install ./jtdx-vu-0.5.1-linux-arm64.deb

   Keep the ./ - it tells apt to install the file rather than look for
   a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
   jtdx package can't be installed alongside; apt offers to remove it.
2. For CAT control over a USB serial cable, give your user access to
   serial ports once, then log out and back in:

   sudo usermod -aG dialout $USER

3. Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
   jtdx in a terminal.

Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.5.0

JTDX-VU for VUCG v0.5.0. JTTY gets a screen of its own: the FT-only buttons are gone while you are in JTTY, and the space holds RST / name fields, a coloured list of calls heard, 24 macros in three banks and type-ahead. FT8, FT4 and FT2 look and work exactly as before.

What's new in v0.5.0 (JTTY)

• A tidy JTTY screen. Controls that do nothing in JTTY (Report, CL, Hound, AutoTX, AutoSeq, Wanted and the wanted filters, Bypass, 1 QSO, AnsB4, Enable Tx, Hint, SWL, AGCc, Filter, Decode, TX Even, the period progress bar) are hidden in JTTY and come back in the other modes. All the buttons - Tune, Monitor, Auto CQ, Halt Tx, Log QSO, Erase, Clear DX - are now in one column on the right, and the macro panel runs across the bottom.
• S / R / Name fields beside Tx / Rx. RST sent and received are logged (no longer a fixed 599 / 599); the name is filled from your log when you've worked the station before. Macros can use them as %RST and %NAME.
• Calls heard: every callsign in the JTTY decodes, newest first, coloured like Band Activity from your log or Club Log - new DXCC, new on this band, new in JTTY, new call, worked. Click one to make it the DX call and put Rx on its frequency.
• 24 macros in three banks: F1-F8, Shift+F1-F8 and Option (Alt on Windows/Linux)+F1-F8. The panel shows one bank at a time as labelled buttons (Bank 1/2/3); every key works whichever bank is showing. A Set picker on the panel switches macro sets. Macros and their button labels are edited in Settings > JTTY, one tab per bank.
• Type-ahead: a macro or typed message sent while another is on the air is queued ("Next: ..." on the panel) and goes out the moment the current one ends. Halt Tx or Esc clears the queue.
• A refused macro blinks. If a macro needs the DX call (or a name, Call next, a station detail) that isn't filled in, its button blinks red together with the empty field, as well as the status-bar message.
• New built-in macros. "Ragchew / DX" gains a ragchew bank (report + name, name/QTH, rig/antenna, QSL info, 73, QRS...) and a calling bank; "Contest (WSJT-X)" gains repeats and fills. Their %E exchange is now %RST / %RST %N - the same "599" until you change S. Your own macro sets keep their macros; banks 2-3 start empty for you to fill.

Fixes

• JTTY: at key-up the FT8 transmit code also ran, which could halt a JTTY send with "empty message", showed an old FT8 message as LastTx, and added a stray FT-style Tx line. Fixed.
• JTTY: Erase could leave the decode display editing text that was gone.
• JTTY: picking a call no longer wipes the grid your log had just filled in.
• Decode no longer starts the FT decoder while in JTTY.

Downloads

Platform	File	Runs on
macOS, Apple Silicon	JTDX-VU-0.5.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.5.0-macos-x86_64.zip	macOS 15 Sequoia or later
Windows x64	JTDX-VU-0.5.0-windows-x64.zip	Windows 10 / 11, 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.5.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum. JTDX-VU installs alongside a
stock JTDX on macOS and Windows; on the Pi the package replaces a stock
jtdx package.

How to install

macOS (Apple Silicon or Intel)

1. Download the zip for your Mac (Apple menu > About This Mac: "Apple
   M…" chip = arm64, "Intel" = x86_64) and double-click it to unzip.
2. Drag JTDX-VU into Applications.
3. First launch. The app is ad-hoc signed, not notarized, so macOS
   blocks the first open:
   • macOS 15 Sequoia and later: double-click JTDX-VU, click Done on
     the warning, then open System Settings > Privacy & Security,
     scroll down and click Open Anyway next to "JTDX-VU was
     blocked", and confirm.
   • macOS 14 Sonoma: right-click (Control-click) JTDX-VU > Open >
     Open.
   • Or, in Terminal: xattr -dr com.apple.quarantine /Applications/JTDX-VU.app
4. Allow the microphone when asked; that is how macOS names access to
   your radio's sound card. If you clicked Don't Allow, turn JTDX-VU on in
   System Settings > Privacy & Security > Microphone.
5. Shared memory (one-time, every Mac). The decoder needs more SysV
   shared memory than the macOS default; without it JTDX-VU stops with
   "Unable to create shared memory segment". In Terminal:

   sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432

   That lasts until the next restart. To make it permanent, download
   Darwin/com.jtdx.sysctl.plist from
   this repo and run
   sudo cp com.jtdx.sysctl.plist /Library/LaunchDaemons/.
   It may need redoing after a macOS upgrade.
6. Set up your callsign, radio and audio in JTDX-VU > Settings…
   (Cmd+,).

Upgrading: quit JTDX-VU, replace the app in Applications with the
new one, and repeat step 3 if macOS asks. Settings
(~/Library/Preferences/JTDX-VU.ini) and data
(~/Library/Application Support/JTDX-VU) are kept.

Windows 10 / 11 (64-bit)

1. Download JTDX-VU-0.5.0-windows-x64.zip. Before unzipping,
   right-click the zip > Properties, tick Unblock, OK; this saves
   a warning for every file inside.
2. Right-click > Extract All… to a folder of your choice, for example
   C:\JTDX-VU. No installer and no administrator rights are needed.
3. Run bin\jtdx.exe in that folder. If Windows SmartScreen says
   "Windows protected your PC", click More info > Run anyway (the
   program is not code-signed). Right-click jtdx.exe > Send to >
   Desktop (create shortcut) for a desktop icon.
4. If Windows Firewall asks, allow access on private networks (JTDX-VU
   talks UDP to logging programs such as Log4OM, N1MM or JTAlert).
5. For rig control through OmniRig, install
   OmniRig separately. Hamlib, TCI
   and the other rig interfaces are built in.

Upgrading: quit JTDX-VU and extract the new zip over the old folder
(or into a new one). Settings are stored in your Windows profile, not
in the program folder, so they are kept.

Raspberry Pi / Debian 12 (arm64)

Needs a 64-bit Raspberry Pi OS (Bookworm) or Debian 12 on arm64 - a Pi 4
or Pi 5 is recommended.

1. Download jtdx-vu-0.5.0-linux-arm64.deb, then in a terminal in the
   download folder:

   sudo apt update
   sudo apt install ./jtdx-vu-0.5.0-linux-arm64.deb

   Keep the ./ - it tells apt to install the file rather than look for
   a package by that name. apt pulls in Qt, Hamlib and FFTW. A stock
   jtdx package can't be installed alongside; apt offers to remove it.
2. For CAT control over a USB serial cable, give your user access to
   serial ports once, then log out and back in:

   sudo usermod -aG dialout $USER

3. Start JTDX-VU from the menu (Sound & Video / Ham Radio), or run
   jtdx in a terminal.

Upgrading: install the new .deb the same way; settings are kept.
Removing: sudo apt remove jtdx-vu.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.4.0 for VUCG

JTDX-VU for VUCG v0.4.0. JTTY grows up: Auto CQ, a JTTY page in Settings with macro sets, and click-to-pick callsigns. Plus a crash fix for TCI users and a Settings fix for small screens. Everything in v0.3.0 (JTTY, FT2, MSHV-style DXCC colours) is still here.

What's new in v0.4.0

• JTTY Auto CQ. Press Auto CQ (right-hand button column) and JTTY sends your CQ macro, listens for a gap (10 s by default), and calls again. Press it again to stop; that also halts a CQ that is on the air. Esc, Halt Tx, sending anything else, or picking a DX call stops it too, and so does a decode that contains your call (optional). In FT8/FT4/FT2 the same button is Call Non-Stop, as before.
• Settings › JTTY (new tab):
  • Auto CQ: which F-key to repeat, the gap, an optional call limit, stop when my call is decoded.
  • Station details for new macro variables: %OP (name), %QTH, %TX (radio), %ANT (antenna).
  • Macro sets: named sets of the eight F-key macros, each with its own %E exchange. Built in: "Contest (WSJT-X)" (599 %N) and "Ragchew / DX" (599). Your existing macros become "Default". The panel shows Serial Number only when the active set uses %N.
• Pick a call N1MM-style: single-click, double-click or select a callsign in either JTTY pane to put it in DX Call. Punctuation around it ("VU2CPL,") is ignored; /P and other suffixes are kept. The panes no longer jump to the bottom while you aim at a call.
• JTTY logging: Log QSO fills RST 599 / 599; JTTY QSOs are written as ADIF MODE MFSK / SUBMODE JTTY (like FT4); the QSO start time is taken when you pick or type the DX call.
• Monitor is the start/stop control; the Stop button is gone. The Send message box is a little larger.

Fixes

• Crash when quitting while TCI is still connecting (for example after the SDR app was closed first). Inherited from JTDX 2.2.159; fixed on macOS and Linux.
• Settings dialog on small screens: on a 1366×768 laptop (reported on Linux) the OK/Cancel buttons were below the screen edge. The dialog now fits the screen and scrolls its tabs when needed.

Downloads

Platform	File	Requirements
macOS, Apple Silicon	JTDX-VU-0.4.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.4.0-macos-x86_64.zip	macOS 15 or later
Windows x64	JTDX-VU-0.4.0-windows-x64.zip	Windows 10/11 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.4.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum.

Install

• macOS:
  • Unzip, move JTDX-VU to Applications, then right-click › Open the first time. The app is not notarized.
  • One-time shared-memory setting, then reboot:

    sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
    

    To keep it across reboots, copy Darwin/com.jtdx.sysctl.plist from the repo to /Library/LaunchDaemons/.
• Windows: unzip anywhere and run bin\jtdx.exe. For OmniRig rig control, install OmniRig separately.
• Raspberry Pi: sudo apt install ./jtdx-vu-0.4.0-linux-arm64.deb.

Upgrading from any earlier JTDX-VU keeps all your settings; your JTTY macros carry over as the "Default" macro set.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

JTDX-VU v0.3.0 for VUCG

JTDX-VU for VUCG v0.3.0. Two new modes — JTTY and FT2 — plus MSHV-style DXCC colouring refinements. Everything in v0.2.x (CNS, live Show filter, Club Log, alerts) is still here.

What's new in v0.3.0

• JTTY — WSJT-X 3.2's period-free, RTTY-style keyboard mode, ported from WSJT-X 3.2.0-rc1. Decodes continuously (no T/R period), transmits the moment you press Send, and has a controls page like WSJT-X's: F1–F8 with editable macros (%M my call, %H his call, %Q Call next, %N serial number, %E = 599 %N), a free-text entry, Halt (Esc), Call next and Serial Number. Double-click a callsign in a decode to make it the DX call. Default dial frequencies as in WSJT-X 3.2 (14.090, 7.090, 21.090 MHz …). Confirmed on air at VU2CPL.
• FT2 — FT4's protocol at twice the speed: 3.75 s periods, 41.67 baud, as introduced in MSHV. Same 77-bit messages and AutoSeq as FT4. Default dial frequencies follow MSHV (14.084, 7.052, 21.144, 28.184 MHz …). Decoding and transmitting are verified against simulated signals down to −14 dB; on-air interoperation with MSHV FT2 stations is still to be confirmed — reports welcome.
• DXCC colours as in MSHV: "New DXCC on Band" and "New DXCC on Mode" are now separate colours (Settings › Notifications), and the "Show:" filter is exactly MSHV's: All / New DXCC / New band / New mode, each its own test, live on everything already decoded.
• Band and mode buttons re-assert DIGU on the radio: pressing the current band re-tunes and re-sends the rig mode, a mode button asserts DIGU on that band, and a band press dropped by a busy CAT/TCI link is retried.
• Mode buttons for JTTY and FT2 can be added in View › Band & Mode Buttons….

Downloads

Platform	File	Requirements
macOS, Apple Silicon	JTDX-VU-0.3.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.3.0-macos-x86_64.zip	macOS 15 or later
Windows x64	JTDX-VU-0.3.0-windows-x64.zip	Windows 10/11 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.3.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum.

Install

• macOS:
  • Unzip, move JTDX-VU to Applications, then right-click › Open the first time. The app is not notarized.
  • One-time shared-memory setting, then reboot:

    sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
    

    To keep it across reboots, copy Darwin/com.jtdx.sysctl.plist from the repo to /Library/LaunchDaemons/.
• Windows: unzip anywhere and run bin\jtdx.exe. For OmniRig rig control, install OmniRig separately.
• Raspberry Pi: sudo apt install ./jtdx-vu-0.3.0-linux-arm64.deb.

Upgrading from any earlier JTDX-VU keeps all your settings. The JTTY and FT2 dial frequencies are added to your frequency list the first time you select each mode.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others.

JTTY is by Joe Taylor K1JT, Steve Franke K9AN, Rob Sherwood G4KLA and the WSJT-X development group (WSJT-X 3.2.0-rc1, GPL v3). FT2 was created by Martino IU8LMC (ARI Caserta); its reference implementation is in MSHV by Hrisimir Hristov LZ2HV, and JTDX-VU's port is a scaled copy of JTDX's own FT4 decoder. The band/mode buttons, the "show only new" filter and the DXCC colour scheme follow MSHV by LZ2HV.

Licensed under the GPL v3; the source is in this repository.

JTDX-VU v0.2.1 for VUCG

JTDX-VU for VUCG v0.2.1. A fix release on top of v0.2.0: CNS now respects the AutoSeq give-up counters. A station that doesn't answer is dropped after the number of calls set in Settings › Sequencing (e.g. 3), instead of being called forever. Everything else below is as in v0.2.0.

What's in v0.2.x (since v0.1.0)

• CNS (Call Non-Stop): a button at the end of the band/mode row, also in the AutoSeq menu.
  • After each logged QSO, JTDX-VU goes straight back to CQ or the next caller instead of halting Tx. In stock JTDX, auto-logging always stops Tx at the end of a QSO.
  • A station that doesn't answer is dropped after the AutoSeq counters (Settings › Sequencing), and one that answers someone else is dropped straight away. (v0.2.1)
  • The Tx watchdog is fixed at 10 minutes while CNS is on, so unanswered CQ still stops.
• Live "Show:" filter, as in MSHV:
  • Choosing All / New DXCC / New DXCC or band / New DXCC, band or mode now re-filters every decode already in Band Activity at once, not just later cycles.
  • A station you have just worked drops out automatically.
  • Traffic with your call and your QSO partner always stays visible.
• Windows fixes:
  • The OpenSSL DLLs are now bundled, so Club Log and Telegram work (no more TLS initialization failed).
  • Desktop alerts appear as tray notifications.
• Club Log "confirmed only" now treats stations worked but not yet confirmed as worked for dupe checks, so AutoSeq won't answer them again. DXCC / band status still counts only confirmed QSOs.

CNS, the live filter and the Windows fixes have been confirmed on air at VU2CPL.

Tips for hands-off FT8 (MSHV-style)

• Settings › Reporting: Enable automatic logging of QSO on, Prompt me to log QSO off.
• Main window: AutoSeq on, 1 QSO off, CNS on.
• With AnsB4 off, JTDX answers only stations that count as new under Settings › Notifications. Tick Check and highlight new calls + per band there so that un-worked stations are answered and dupes are skipped.

Downloads

Platform	File	Requirements
macOS, Apple Silicon	JTDX-VU-0.2.1-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.2.1-macos-x86_64.zip	macOS 15 or later. Its build takes a few hours, so it is attached later.
Windows x64	JTDX-VU-0.2.1-windows-x64.zip	Windows 10/11 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.2.1-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum.

Install

• macOS:
  • Unzip, move JTDX-VU to Applications, then right-click › Open the first time. The app is not notarized.
  • One-time shared-memory setting, then reboot:

    sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
    

    To keep it across reboots, copy Darwin/com.jtdx.sysctl.plist from the repo to /Library/LaunchDaemons/.
• Windows: unzip anywhere and run bin\jtdx.exe. For OmniRig rig control, install OmniRig separately.
• Raspberry Pi: sudo apt install ./jtdx-vu-0.2.1-linux-arm64.deb.

Upgrading from v0.1.0 or v0.2.0 keeps all your settings.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others. The band/mode buttons and the live "show only new" filter follow MSHV by LZ2HV.

Licensed under the GPL v3; the source is in this repository.

JTDX-VU v0.2.0 for VUCG

Superseded by v0.2.1 — in v0.2.0, CNS never gave up on a station that did not answer. Please use v0.2.1.

JTDX-VU for VUCG v0.2.0. Adds Call Non-Stop and a live "Show only new" filter, and fixes Windows.

What's new since v0.1.0

• CNS (Call Non-Stop): a button at the end of the band/mode row, also in the AutoSeq menu.
  • After each logged QSO, JTDX-VU goes straight back to CQ or the next caller instead of halting Tx. In stock JTDX, auto-logging always stops Tx at the end of a QSO.
  • It keeps calling a station until it answers, and moves on if that station answers someone else.
  • The Tx watchdog is fixed at 10 minutes while CNS is on, so unanswered CQ still stops.
• Live "Show:" filter, as in MSHV:
  • Choosing All / New DXCC / New DXCC or band / New DXCC, band or mode now re-filters every decode already in Band Activity at once, not just later cycles.
  • A station you have just worked drops out automatically.
  • Traffic with your call and your QSO partner always stays visible.
• Windows fixes:
  • The OpenSSL DLLs are now bundled, so Club Log and Telegram work (no more TLS initialization failed).
  • Desktop alerts appear as tray notifications.
• Club Log "confirmed only" now treats stations worked but not yet confirmed as worked for dupe checks, so AutoSeq won't answer them again. DXCC / band status still counts only confirmed QSOs.

CNS, the live filter and the Windows fixes have been confirmed on air at VU2CPL.

Tips for hands-off FT8 (MSHV-style)

• Settings › Reporting: Enable automatic logging of QSO on, Prompt me to log QSO off.
• Main window: AutoSeq on, 1 QSO off, CNS on.
• With AnsB4 off, JTDX answers only stations that count as new under Settings › Notifications. Tick Check and highlight new calls + per band there so that un-worked stations are answered and dupes are skipped.

Downloads

Platform	File	Requirements
macOS, Apple Silicon	JTDX-VU-0.2.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.2.0-macos-x86_64.zip	macOS 15 or later. Its build takes a few hours, so it is attached later.
Windows x64	JTDX-VU-0.2.0-windows-x64.zip	Windows 10/11 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.2.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum.

Install

• macOS:
  • Unzip, move JTDX-VU to Applications, then right-click › Open the first time. The app is not notarized.
  • One-time shared-memory setting, then reboot:

    sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
    

    To keep it across reboots, copy Darwin/com.jtdx.sysctl.plist from the repo to /Library/LaunchDaemons/.
• Windows: unzip anywhere and run bin\jtdx.exe. For OmniRig rig control, install OmniRig separately.
• Raspberry Pi: sudo apt install ./jtdx-vu-0.2.0-linux-arm64.deb.

Upgrading from v0.1.0 keeps all your settings.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others. The band/mode buttons and the live "show only new" filter follow MSHV by LZ2HV.

Licensed under the GPL v3; the source is in this repository.

JTDX-VU v0.1.0 for VUCG

JTDX-VU for VUCG — first release. A build of JTDX 2.2.159 for the VUCG community, with native builds for macOS, Windows and Raspberry Pi.

Downloads

Platform	File	Requirements
macOS, Apple Silicon	JTDX-VU-0.1.0-macos-arm64.zip	macOS 14 Sonoma or later
macOS, Intel	JTDX-VU-0.1.0-macos-x86_64.zip	macOS 15 or later
Windows x64	JTDX-VU-0.1.0-windows-x64.zip	Windows 10/11 64-bit
Raspberry Pi / Linux arm64	jtdx-vu-0.1.0-linux-arm64.deb	Raspberry Pi OS / Debian 12 (bookworm), 64-bit

Each file has a matching .sha256 checksum.

Windows zip re-issued 2026-09-28. The first upload was missing the OpenSSL DLLs, so Club Log refresh and Telegram failed with TLS initialization failed, and desktop alerts didn't appear. Both are fixed and confirmed on a Windows PC. Please download it again if you got it earlier.

Install

• macOS:
  • Unzip, move JTDX-VU to Applications, then right-click it and choose Open the first time. The app is ad-hoc signed, not notarized.
  • JTDX needs a larger shared-memory limit than macOS allows by default. Run this once, then reboot:

    sudo sysctl -w kern.sysv.shmall=32768 kern.sysv.shmmax=33554432
    

    To keep the setting across reboots, copy Darwin/com.jtdx.sysctl.plist from the repo into /Library/LaunchDaemons/.
• Windows: unzip anywhere and run bin\jtdx.exe. For OmniRig rig control, install OmniRig separately.
• Raspberry Pi: sudo apt install ./jtdx-vu-0.1.0-linux-arm64.deb. It replaces a stock jtdx package if one is installed, since both use the same file names.

JTDX-VU keeps its own settings and data. On first start it copies an existing JTDX setup across, so callsign, audio, rig and logs carry over. The original JTDX files are left untouched.

What's new compared with JTDX 2.2.159

• Club Log DXCC status (File › Club Log & Alerts).
  • JTDX's New DXCC / band / band+mode colours, filters and priorities can follow your whole Club Log log, not just JTDX's own.
  • Optionally, only QSOs confirmed by QSL, LoTW or eQSL count as worked.
• Needed-DXCC alerts for ATNO, new band or new band+mode.
  • Alerts go to a desktop notification and/or Telegram, with a per-station cooldown.
• One-click band and mode buttons above the decode panes, modelled on the MSHV switcher.
  • A band button tunes to the standard frequency for the current mode.
  • Choose which buttons appear in View › Band & Mode Buttons.
• "Show:" filter: trims Band Activity to stations you still need.
  • Traffic with your call and with your QSO partner is always shown.
• The main-window popup option no longer steals focus; it bounces the Dock icon instead.
• On macOS, the Settings dialog is no longer squashed.
• New app identity: JTDX-VU name, green "VU" icon, and version 0.1.0.

Tested so far

• macOS (Apple Silicon): in daily use at VU2CPL, including Club Log download (57k QSOs), Telegram and desktop alerts, and the band/mode buttons.
• Windows x64: Club Log download, Telegram and desktop (tray) alerts confirmed on a Windows PC after the re-issue. Audio and CAT on air are still to be confirmed.
• Raspberry Pi: the package passes a simulated install (all dependencies resolve on Pi OS bookworm) and the app starts. Not yet used on air.

Known limitations

• CAT control uses Hamlib 4.7.2 (macOS / Windows) or 4.5.4 (Pi), not the JTDX Hamlib fork.
• The macOS builds are not notarized: right-click › Open the first time.

Credits

Based on JTDX by Igor Chernikov UA3DJY, Arvo Järve ES1JA and the HF community. JTDX is itself derived from WSJT-X by Joe Taylor K1JT, Bill Somerville G4WJS, Steve Franke K9AN, Nico Palermo IV3NWV and others. The band/mode buttons follow the MSHV switcher by LZ2HV.

Licensed under the GPL v3; the source is in this repository.