Open Rig Programmer v1.0.0
Open Rig Programmer v1.0.0 — an open-source, cross-platform
memory-channel programmer for the Yaesu FT-710, built as a free
alternative to RT Systems' YPS-FT710, with three further Yaesu models
registered read-only.
What it does
- Read every memory channel from the radio over CAT — the 99
regular memories plus the 9 PMS (Programmable Memory Scan) pairs —
into a codeplug file you can keep, diff and re-send. - Edit channels in a spreadsheet-style grid (GUI) with keyboard
navigation, paste, per-column editors and drag copy/swap/move. - Send changes back safely (FT-710): read-before-write, a snapshot
of the radio's existing contents taken before anything changes, a
reviewed diff you confirm against a digest, and per-channel verify
after each write. Anything that cannot be written is shown with the
reason rather than attempted. - CSV and CHIRP import/export, with a report of anything a CHIRP
file cannot express. - Read the radio's menu (EX) settings into the same file and view
or export them — every documented menu address for the connected
model (FT-710: 296; FTdx10: 197; FTdx101D/MP: 193). - Both a desktop GUI and a
rigprogCLI, sharing one core.
Supported radios, and what "supported" means for each
| Model | Read channels | Write channels | Read menu settings | Evidence |
|---|---|---|---|---|
| FT-710 | Yes | Yes | Yes | Proven against real hardware (docs/hardware-notes.md) |
| FTdx10 | Yes | No — disarmed | Yes | CAT manual + simulator only; no real radio has been connected |
| FTdx101D | Yes | No — disarmed | Yes | CAT manual + simulator only; no real radio has been connected |
| FTdx101MP | Yes | No — disarmed | Yes | CAT manual + simulator only; no real radio has been connected |
Writes to the three manual-derived models are disarmed in the code
itself (nothing is writable on a real-hardware session), not merely
untested. Each of those drivers carries a register of every assumption
it makes and the specific capture from a real radio that would verify
it — if you own one of these radios and want to help, open an issue.
What it deliberately does not do
- It does not write menu settings, and will not. This is a settled
design decision taken on evidence, not an unfinished feature — the
FT-710 CAT manual's menu chart proved wrong in both of the two
respects a read could check, and nothing in the read direction
establishes what the radio accepts in the write direction. The
reasoning, and what would have to change to revisit it, is in
docs/menu-write-decision.md. - It cannot erase a channel over CAT. These radios have no CAT
erase command; the app says so, and tells you the front-panel
procedure, rather than silently doing nothing. - It does not read per-channel CTCSS tone frequencies. The FT-710
does not report them over CAT (established against real hardware —
docs/hardware-notes.md), so the app preserves whatever is on the
radio instead of guessing.
Downloads
| Platform | What it is | File |
|---|---|---|
| macOS (Intel + Apple Silicon, universal) | GUI (.app, zipped) | open-rig-programmer-v1.0.0-darwin-universal.app.zip |
| macOS (Intel + Apple Silicon, universal) | CLI | rigprog-v1.0.0-darwin-universal.tar.gz |
| Linux amd64 | CLI | rigprog-v1.0.0-linux-amd64.tar.gz |
| Linux arm64 | CLI | rigprog-v1.0.0-linux-arm64.tar.gz |
There is no Linux GUI AppImage in this release: its build job runs
only on Linux CI, which is not in use for this release. Linux users
have the CLI, or can build the GUI from source (wails build in
app/; see docs/linux-setup.md for the build dependencies).
SHA256SUMS (attached below) covers every file above. Verify with:
sha256sum -c SHA256SUMS --ignore-missingChecking which version you have
rigprog version prints it; the GUI shows it at the right-hand end of
the status bar. Quote that string in any bug report. A build that
reports dev (unreleased build) did not come from this release page —
if you downloaded it here, please say so in the report, because that
would be a packaging fault.
Firmware requirement
Memory CAT (read and write) on the FT-710 requires firmware V01-10
or later. There is no CAT query for the firmware version — check the
radio's front panel or SD-card version screen before connecting.
macOS: first launch
The .app is only ad-hoc signed (no Apple Developer ID), so Gatekeeper
will refuse to open it the ordinary way the first time. In Finder,
right-click (Control-click) the app and choose Open, then confirm
in the dialogue that appears. This is only needed once; after that it
opens normally.
Linux: serial port access
- Add yourself to the
dialoutgroup and log out/in (ornewgrp dialout) before the CLI can open the radio's serial port:
sudo usermod -aG dialout "$USER". - ModemManager can probe a newly-plugged serial adapter and interfere
with it; excluding the radio's USB-serial bridge from ModemManager
via udev is recommended. Seedocs/linux-setup.mdfor the full
instructions and a ready-to-use udev rule.
What the hardware evidence covers — read this
Every "works on the radio" claim in this project comes from recorded
sessions against one physical UK FT-710, on macOS, and
docs/hardware-notes.md is the record. Channel reads and writes were
proven on that radio; the menu-settings read was proven separately.
One radio, one region, one firmware version.
What this release has not been exercised against:
- Linux with a real radio. The Linux CLI binaries are
cross-compiled and version-stamp-verified, and the serial stack is
the same code, but no real-radio session has been run on Linux yet.
docs/linux-setup.mdcarries the port-setup instructions; treat the
first Linux session as exploratory and read-only first. - Any FTdx10, FTdx101D or FTdx101MP. Everything about those three
models is derived from the manufacturer's CAT reference manuals
through a documented transcription-and-cross-check process, and
exercised against simulators built independently from the same
manuals. No real radio of any of the three has ever been connected.
That is why their writes are disarmed.
Anything the project has not observed is labelled as such in the code
and documentation rather than assumed. Reports from real hardware —
especially the three read-only models, and the FT-710 on Linux — are
the most valuable contribution this project can receive right now.