What you need
Three things, and you probably have all of them.
1. The radio
A Retevis RT95, Anytone AT-778UV or CRT Micron UV, powered from 12 to 14 V. Programming never keys the transmitter, but an antenna or a dummy load on the SO-239 is still good practice.
2. The programming cable
The USB cable made for this radio family. It plugs into the microphone jack on the front, so unplug the hand mic first. Ours is the Retevis cable with a WCH CH343 chip inside: macOS and Linux need no driver, and Windows 10 and 11 usually fetch the driver themselves. If the port never appears on Windows, install the WCH CH343 driver.
3. Chrome or Edge
Rigbench talks to the cable through Web Serial, which Chrome, Edge and other Chromium browsers support. Safari and Firefox do not. Any operating system works.
Connecting
- Unplug the hand mic and plug the programming cable into the mic jack. Plug the USB end into the computer.
- Power the radio on. It behaves normally while connected.
- Open the programmer and press Connect radio. The browser shows a list of serial ports; the CH343 cable appears as "USB Single Serial". Pick it.
- Rigbench identifies the radio and reads it. A quick read takes about 45 seconds. The radio beeps once when the session starts and once when it ends; that is normal.
- Press Full backup once and then Save .bin. About two minutes. Keep that file. It holds everything in the radio, including calibration data no other tool saves.
- Edit, then Write radio. Only changed blocks are sent, each is read back and checked, and Restore puts the previous contents back if you change your mind.
The cable, in detail
Every cable for this family is the same idea: a USB-to-serial chip wired to one pin of the mic jack.
What is inside
An RJ45 (8P8C) plug on one end, USB on the other, and a serial chip in between. Retevis cables use a WCH CH343 or CH340. Some Anytone and third-party cables use FTDI or Prolific chips. All of them work with Rigbench once the operating system sees a serial port.
Drivers
macOS: recent versions include the WCH driver; the port appears as cu.usbmodem… (CH343) or cu.usbserial… (FTDI, Prolific). Windows 10/11: usually installs itself; if not, the WCH CH343 driver from wch-ic.com. Prolific cables with a counterfeit PL2303 fail under the current Prolific driver ("phased out"): use an older driver or a different cable. Linux: built into the kernel; add yourself to the dialout group, and on Ubuntu remove brltty if it grabs the port.
Port names in the chooser
The CH343 shows up as "USB Single Serial". FTDI cables say "FT232R" or "USB Serial Port". If you see several ports, unplug the cable and see which one disappears.
Mic jack pinout
Front view of the radio, left to right. Colours are the stock hand-mic cable. Only pin 8 and a ground are used for programming.
| Pin | Colour | Signal |
|---|---|---|
| 8 | red | Serial data, single-wire half-duplex TTL at 9600 baud. Programming, the firmware loader and the radio's status stream all live here. |
| 7 | brown | +5 V for the mic keypad backlight |
| 6 | yellow | DOWN button |
| 5 | green | UP button and unsquelched speaker audio on the same pin. Anything you connect here without a series capacitor presses channel-up. |
| 4 | black | Mic ground. Use this as the ground for a homebrew cable. |
| 3 | white | Mic audio, about 3.3 V bias |
| 2 | blue | PTT |
| 1 | grey | Chassis ground (noisier than pin 4) |
Homebrew cable
A 3.3 V USB-to-TTL adapter is all it takes. The radio's data line is a single wire, so the adapter's transmit and receive both go to pin 8: TX through a 1 kΩ resistor (or a diode, cathode toward the adapter) to pin 8, RX directly to pin 8, adapter ground to pin 4. Because the line is shared, everything you send echoes back; Rigbench expects that. Do not use a 5 V adapter: the control head runs at 3.3 V.
If something goes wrong
| Symptom | Usually |
|---|---|
| No port in the list | Driver (Windows) or a cable that is charge-only. Try another USB port; check Device Manager or ls /dev/cu.* for the cable. |
| "Failed to open serial port" | Another program has the port open: the factory CPS, a terminal, or a second browser tab. Close it and reconnect. |
| Handshake timeout on the first try | The radio takes a few seconds to settle after a session ends. Wait five seconds and press Read again. If it keeps happening, power-cycle the radio. |
| "Untested" badge, Write greyed out | Your model or firmware version has not been through the write test yet. Reading and backups are fine. Email the backup so it can be added. |
| The radio shows something odd after a write | Press Restore, or open your saved .bin and write it. The calibration region is never written by Rigbench. |
For the workbench
Only if you are following the firmware work or want to try live control when it lands. Not needed for programming.
| Item | Why |
|---|---|
| 50 Ω dummy load, 25 W or more | Anything that can key the transmitter needs a load on the antenna jack. Live control and calibration tests will require one. |
| RT95 / AT-778UV separation kit | Lets the control head sit apart from the body. Also the easiest way to get at the internal ribbon connector, which is where the spacer will plug in. |
| Spare programming cable | If yours is charge-only or missing. Any RT95 / AT-778UV cable works. |
These are plain search links today. If they become affiliate links later, that pays for hosting and the page will say so.