Codeplug backup: how not to lose your radio settings

You spent half a day setting up zones, talkgroups and contacts — and then a botched flash, a "let's see what happens if…" experiment, or just a glitchy CPS update wipes it all out. So that stories like this don't end in hours of re-configuration, there's one simple rule: back up first, experiment later. Let's go over what and how to save, and how to quickly bring the radio back to a working state.

What a codeplug is (in brief)

A codeplug is a file with all of your radio's settings: channels, zones, talkgroups, RX groups, contacts, your DMR ID and general parameters. It is created and uploaded by the manufacturer's software — CPS (Customer Programming Software). If the codeplug itself is still fuzzy to you — start with the "Codeplug from scratch" guide, and come back here for the backup part.

Why back up at all

• Before flashing. Any firmware update or installing open-source firmware can wipe your settings. A backup is your insurance.
• Before experiments. Changing a pile of channels, trying someone else's codeplug — there's always a "point of return".
• Cloning to a second radio. Set up one, load the copy into an identical one. Saves hours.
• Bricks and service. If the radio stops booting, a working codeplug speeds up recovery.
• Selling or handing it over. You save your own setup, reset the radio for the new owner — and nothing personal leaks out.

How to save the codeplug from the radio

The principle is almost the same for every CPS; only the menu item names differ.

1. Install the correct CPS version for your model and firmware, connect the radio with a cable (drivers and the COM port are covered in the cables and drivers article).
2. Choose "Read from radio" — the program reads the current codeplug into the window.
3. "Save as…" — save the file to disk. The extension depends on the brand (each manufacturer has its own); all that matters is that this is a complete copy of the settings.
4. Give the file a clear name with a date: md-uv380_2026-06-11_working.ext — you'll thank yourself later.

Rules for a good backup

• Date in the file name. Not "codeplug_final_final2", but a date. Over time you'll accumulate many versions.
• Several copies. Don't keep them only on one laptop: cloud, a USB stick, a second PC. The cable and PC "don't see the port" at the worst possible moment — and the backup needs to be at hand.
• Note the CPS and firmware version. Especially for AnyTone: the codeplug is tied to the version. A note "CPS 1.2x / FW 1.2x" next to the file will spare you a headache.
• Keep the contact list separate. Large callsign lists are convenient to export as a separate CSV, so you can move them between radios independently of the codeplug.

Don't forget firmware and calibration

A codeplug holds the settings, but not the firmware itself. These are two different things, and they need to be backed up separately.

• Firmware. If you plan to install open-source firmware, keep a way to return to the factory one. For md380tools and OpenGD77, their tools have their own backup/restore functions.
• Calibration. On some radios the factory calibration (frequency accuracy, power) is stored in a separate memory area. Do not overwrite it with someone else's dump — you'll lose the factory tuning, and the radio will have to be calibrated again. If the flashing tool offers to save the calibration — do it.

How to restore

Restoring is the "reverse" of reading:

1. Open the saved file in the same CPS version you made the backup with.
2. Connect the radio and, if needed, check/enter your DMR ID.
3. Choose "Write to radio" and wait for it to finish — don't unplug the cable during the process.

A minute later the radio is back exactly as you saved it. It's for the sake of that one minute that it's worth keeping a fresh backup.