Setup and troubleshooting · 8 min read

Programming a MOTOTRBO radio: CPS, cables and the errors that stop people

What a codeplug actually contains, why the software will not talk to the radio, and how to avoid a fleet that arrives unprogrammed.

On this page

What CPS is and what it does

CPS — Customer Programming Software — is the manufacturer tool that writes a codeplug into the radio. The codeplug is the whole personality of the device: channels, frequencies, channel spacing, talk groups, contacts, zones, button assignments and audio settings.

Two radios of the same model can behave completely differently depending on the codeplug inside them. This is why a radio is not 'ready to use' until it has been programmed against your channel plan.

CPS is version- and region-sensitive. A version built for one market will not necessarily write to hardware sold in another, and a CPS older than the radio's firmware will refuse the write.

Included with every order

We program every radio to your channel plan before it ships. You do not need CPS on day one unless you plan to change the configuration yourself.

The cable and driver layer fails first

Most 'the software does not see the radio' problems are not software problems. They are cable, driver or port problems, in roughly that order.

  • Wrong cable: programming cables are model-specific, and a charge-only cable will never work.
  • Missing USB-to-serial driver: the cable enumerates but no COM port appears.
  • Port taken by another application: the port is visible but locked.
  • Low battery: the radio drops out of programming mode part way through the write.

The errors people actually hit

Reading a radio and failing to write it back usually means the codeplug contains fields the CPS does not recognise — often because the radio was last programmed with a newer CPS or a different regional build.

A model or firmware mismatch error means the CPS build does not cover that hardware. Match the CPS generation to the radio, not the other way round.

A write that stops at a percentage is almost always power or cable related. Charge the battery fully and use a direct USB port rather than a hub before assuming the radio is faulty.

Keep a copy

Read and archive the original codeplug before you change anything. It is the fastest way back if a write goes wrong.

What to send us for programming

Send a channel plan in any readable form: a spreadsheet with channel name, receive frequency, transmit frequency, colour code or CTCSS/DCS, and which zone each channel belongs to.

Tell us the exact model and variant for each radio, because display and non-display models carry different button layouts. If you already have a working codeplug file, send it and we will match it.

Programming is done before dispatch, so it does not add a separate production step to your 3–7 day lead time. If you need the radios blank for your own programming, say so explicitly.

After delivery

Label every radio with its asset number and the codeplug version it carries. When a radio comes back from repair, you can then confirm what should be inside it.

Keep one reference radio per site programmed to the current plan and stored charged. It is the fastest way to clone a replacement and the only reliable way to prove what the fleet is meant to be doing.