Open Rig Programmer v1.3.0: a free memory-channel programmer for
Yaesu and Icom radios. Read the memories into a file, edit them in a
grid or a spreadsheet, send them back over the radio's ordinary USB
cable. Desktop app and rigprog command line for macOS, Windows and
Linux.
Which radios are supported, and how far each has been tested, is in
docs/radio-notes.md.
Only the FT-710 has ever been connected to this program; every other
radio's writes stay switched off until you switch them on for that
radio, as the
README
describes under Switching on writes for an unverified radio.
What changed in this version
- Windows. An installer (app + command line) and a command-line zip,
each for amd64 and ARM64, built on a Windows host by the release
pipeline. Installed and driven end to end on a Windows 11 ARM64
virtual machine with a real FT-710 attached (05/09/2026): driver,
serial ports, app, command line, two writes and a byte-identical
restore. The amd64 app has never been launched by anyone, and no
physical Windows PC of either architecture has been tried. - The Yaesu FT-891 is now supported, for reading and for opt-in
writes, on the same terms as every other manual-derived model. Its
menu addresses are four digits where the other Yaesu radios use six,
and files accept either. Its CAT speed is a guess (38400; menu 0506 on
the radio is the only remedy), its USB socket presents two serial
ports and the manual does not say which carries CAT, and the manual
contradicts itself about whether a memory channel may be read at all,
so a refused read of a channel plainly in use is reported as what it
is. A CHIRP file'sCW,CWRandRTTYrows are not imported on
this radio. - The serial port is opened with RTS and DTR requested low on every
platform, so a radio wired for RTS/DTR keying is never keyed by the
act of connecting. - CSV import tolerates a UTF-8 byte-order mark and CRLF line endings,
as saved by Windows spreadsheets. - An unanswered Icom field can no longer slip past the send gate by
being saved and reloaded, or by a round trip through CSV. IC-7610,
IC-7760 and IC-7851 refuse a frequency the record cannot hold at read
time, with the value and the limit. - Every Icom tier column has an editor in the grid, chosen by the
field's kind, and the connection bar says when the radio is a
receiver. - The application has an icon of its own on all three platforms.
- The README is rewritten for radio owners; per-radio limits live in
docs/radio-notes.md; aCHANGELOG.mdlists every release.
Everything else is internal and carries no change a user can see. The
stored comparison output of every previously registered radio is
unchanged apart from the lists of supported models, which gain the
FT-891.
Downloads
| Platform | What it is | File |
|---|---|---|
| macOS (Intel + Apple Silicon, universal) | App (.app, zipped) | open-rig-programmer-v1.3.0-darwin-universal.app.zip |
| macOS (Intel + Apple Silicon, universal) | Command line | rigprog-v1.3.0-darwin-universal.tar.gz |
| Windows amd64 | App + command line (installer) | open-rig-programmer-v1.3.0-windows-amd64-installer.exe |
| Windows arm64 | App + command line (installer) | open-rig-programmer-v1.3.0-windows-arm64-installer.exe |
| Windows amd64 | Command line only (zip) | rigprog-v1.3.0-windows-amd64.zip |
| Windows arm64 | Command line only (zip) | rigprog-v1.3.0-windows-arm64.zip |
| Linux amd64 (Debian, Ubuntu, Mint) | App + command line (.deb) | open-rig-programmer_1.3.0_amd64.deb |
| Linux arm64 (Debian, Ubuntu, Mint) | App + command line (.deb) | open-rig-programmer_1.3.0_arm64.deb |
| Linux amd64 | Command line | rigprog-v1.3.0-linux-amd64.tar.gz |
| Linux arm64 | Command line | rigprog-v1.3.0-linux-arm64.tar.gz |
The Windows installers are native-only: the amd64 installer refuses to
run on an ARM64 PC even though ARM64 Windows can emulate x64 programs.
The Debian package installs the app, the command line, a desktop entry
and the ModemManager udev rule; sudo apt install ./<file> resolves
its GTK and WebKit dependencies (built and tested on Ubuntu 24.04;
Ubuntu 22.04, Debian 12 and the Mint releases built from them carry the
same packages but have not been tried). On other distributions take
the command-line tarball, a single static binary.
SHA256SUMS covers every file above. Verify with:
sha256sum -c SHA256SUMS --ignore-missing # Linux
shasum -a 256 -c SHA256SUMS --ignore-missing # macOS
certutil -hashfile <file> SHA256 # Windows, one file at a timeFirst launch
- macOS: the app is only ad-hoc signed, so Gatekeeper refuses it
the first time. Right-click the app, choose Open, and confirm. Once. - Windows: the installer is unsigned. Edge may flag the download,
and SmartScreen shows Windows protected your PC the first time:
click More info, then Run anyway. The app needs Microsoft's
WebView2 runtime, which Windows 11 already ships; if it is missing
the installer is set to download it, a path this project has not
tried. On ARM64 install Silicon Labs' CP210x
driver by hand before connecting; the radio shows as two COM ports
and only one answers. See
docs/windows-setup.md. - Linux: join the
dialoutgroup and log out and in; keep
ModemManager off the radio (the .deb installs the rule; the tarball
needs it by hand). See
docs/linux-setup.md.
FT-710 firmware: memory programming needs V01-10 or later. There is
no CAT query for the version; check the radio's front panel.
Which version you have: rigprog version prints it (on Windows,
.\rigprog.exe version from the folder that holds it; the installer
adds nothing to PATH). The app shows it at the right-hand end of the
status bar. Quote it in any bug report; a build reporting
dev (unreleased build) did not come from this page.
What the hardware evidence covers
Every "works on the radio" claim comes from recorded sessions against
one UK FT-710, on macOS and, since 05/09/2026, on a Windows 11
ARM64 virtual machine;
docs/hardware-notes.md
is the record. Not yet exercised against a real radio: Linux (the
packages have been installed and launched on Ubuntu 24.04 virtual
machines, never with a radio attached, so which serial node is the CAT
port and whether the udev rule keeps ModemManager off it are
unconfirmed); Windows on amd64, or any physical Windows PC; and
every radio other than the FT-710, all of which come from the
makers' manuals and simulators built from them, which is why their
writes are opt-in. Each of those drivers carries a register of every
assumption it makes and the capture from a real radio that would
settle it. If you own one of these radios, a read of a single channel
is the most valuable thing you could send:
open an issue.