RUNSLINUX / RADIO

Radio Programming

Build a channel list, choose your software or app, and export a reviewed plan.

Build a channel plan

Create analog FM/NFM channel memories and choose an export for your software or companion app. A downloaded file prepares settings; the matching app/software performs the transfer.

Your working plan is saved in temporary browser storage for this tab, so you can add more channels from the directory. It is not sent to our server. Clear the plan when finished, or close the tab.

Power levels are model-dependent, not wattage guarantees. For GMRS channels 8–14 use a suitable handheld, narrow mode, and no more than 0.5 W ERP.

Your channels

Drag-free controls work with keyboard and touch. Export renumbers memories sequentially from 1. Radio memory limits and channel-name lengths depend on the model.

CHIRP CSV import reads names, RX/duplex/offset, CTCSS or same-code DCS, polarity, mode, scan-skip, and comments. CHIRP power, tuning step, and vendor-specific fields are not preserved; imported power defaults to Low for review. RunsLinux JSON backups preserve all supported builder fields. Import is limited to 500 FM/NFM rows and a 1 MB file. Unsupported digital modes, cross-tones, split TX, or malformed rows reject the import with an explanation. CTCSS and same-code DCS are supported.

Choose a programming route

Phone and Bluetooth workflow

  1. For a supported BTECH PRO model, choose its app CSV above and download or share the file to your phone.
  2. In the matching BTECH app, import the CSV into a saved channel group. Check the imported settings before saving.
  3. Connect your radio through the manufacturer's app over Bluetooth, then review and sync the saved group.
  4. Read back several channels. Importing or sharing a file alone does not change the radio.

Phone sharing uses your browser's normal share sheet when file sharing is supported. Download remains available on other browsers. The site does not pair with, write to, or send PTT commands to a radio.

BTECH's current sharing/import guide Β· Exact-model support

Other radios

CHIRP compatibility is not required for RT Systems field-mapping or the template route. Use software for the exact model. RT Systems is paid, model-specific software; desktop OS support varies by product. For ODMaster/TIDRADIO, use its official supported-device workflow; a compatible file format is not verified here.

RT Systems CSV import guidance Β· TIDRADIO software Β· Radioddity downloads

Formats follow published documentation and have automated checks; physical-radio testing is still needed. BTECH export currently supports CTCSS, up to 30 channels per file; DCS encoding is not guessed. Its FM flag uses the documented app value 25000; this is not a statement that GMRS occupied emissions may exceed the FCC limit. Verify actual mode and deviation on the certified radio. RT Systems exports require column mapping, including transmit inhibit; CHIRP exports leave power for review in CHIRP.

CHIRP cable workflow

  1. Check support: find your exact radio model in CHIRP’s supported radios. Similar model names do not guarantee compatibility.
  2. Back up first: download the current radio image in CHIRP and save an untouched copy.
  3. Build and verify: check RX frequency, duplex, TX frequency, tone, and mode against the repeater owner’s details.
  4. Import CSV: import the downloaded CSV into the image you read from that radio. A CSV is not a replacement for a model-specific image.
  5. Review in CHIRP: confirm memory locations, RX/TX limits, tones, names, and model-specific options. TX-off support varies by radio.
  6. Upload and read back: upload only after reviewing the changes, then read back and check several channels.

Only enable transmission on frequencies and equipment you are authorized to use. This tool does not connect to or write your radio directly.