Programming a radio should be a build, not a CPS session.

How it works

Facts and preferences stay separate. RF data describes what exists; a profile describes what you want in a particular radio. Everything in between is deterministic and reviewable.

Prebuilt community codeplugs

CI builds these from public community profiles and RF data as the sources change, then publishes import files, printable references, and SHA-256 checksums. No codeplugger install is needed.

Supported radios

The table combines radio capabilities with checked-in export and hardware-verification details. Its generator checks that every radios/*/capabilities.json entry has a matching row.

hw verified against a physical radio · ✓ supported today · — not applicable or not implemented

Features

Built for people who keep more than one radio consistent, and want to know exactly what went into each one.

How the data flows

Public RF data and overlays feed a profile-based build; export a file or program a supported radio.

flowchart LR
  rf["📡 rf-survey"] -- "reception reports" --> ssrf["🗃 ssrf-lite"]
  ov["overlays · shared + private"] --> ssrf
  ssrf -- "validated RF data" --> cp["⚙ codeplugger"]
  prof["👤 profiles"] --> cp
  cp -- "export: CHIRP CSV · qdmr YAML · P4 TOML · benlink plan" --> files(["radio files"])
  files --> radios(["📻 radios"])
  cp -- "write: dmrconf · p64tool · chirp-writer · benlink" --> radios
  click rf "https://chicago-offline.github.io/rf-survey/" _blank
  click ssrf "https://chicago-offline.github.io/ssrf-lite/" _blank
  click cp "https://chicago-offline.github.io/codeplugger/" _blank
  click prof "https://chicago-offline.github.io/chioff-codeplugger-profiles-shared/" _blank
        

Ecosystem

codeplugger sits between open RF data and the tools that already talk to radios.

Quick start

Clone codeplugger and use uv. The install brings its own RF data, so a use case needs nothing else; profiles of your own want ssrf-lite and a profile repository checked out alongside.

# what is supported, and what can go on it
uv run codeplugger radios
uv run codeplugger use-cases

# compile, without touching hardware
uv run codeplugger build \
  --radio baofeng_bf888s --use-case gmrs

# or a community group's channels, by name
uv run codeplugger build \
  --radio baofeng_bf888s --profile chioff

# then write it, gated by the backend
uv run codeplugger program \
  --radio baofeng_bf888s --use-case gmrs \
  --port /dev/cu.usbserial-10 --confirm

uv run codeplugger-profile path/to/profile.yml \
  --ssrf-root ../ssrf-lite/ssrf \
  --ssrf-root ../chioff-ssrf-shared/ssrf

# analog radios: import in CHIRP
uv run codeplugger-profile profile.yml \
  --ssrf-root ../ssrf-lite/ssrf \
  --output-format chirp-csv > output.csv

# DM-32: qdmr YAML, then dmrconf write
uv run codeplugger-profile profile.yml \
  --ssrf-root ../ssrf-lite/ssrf \
  --output-format qdmr-yaml > codeplug.yaml

uv run codeplugger-fleet \
  --instance-registry ../my-profiles/instances.yml \
  --profiles-root ../my-profiles/profiles \
  --ssrf-root ../ssrf-lite/ssrf

version: "0.1"
id: "dm32_reference"
name: "DM-32 reference"
radio: "baofeng_dm32"
radio_instance: "dm32_green_01"
zones:
  - id: "community"
    name: "Community"
    assignments:
      - "asg_chio_all"
      - "asg_chio_road"
      - "asg_chio_repeater"