CHIRP channels into an Ailunce HD1
Drop the CHIRP file, a RepeaterBook export or a spreadsheet, and save Channels.csv for the HD1 programming software. It was imported into CPS V3.05 and exported back unchanged.
What goes in
Analog FM channels with frequencies, CTCSS or DCS, 12.5 or 25 kHz, power as Low, Mid or High, and receive-only channels as Prohibit TX. Names are cut to 14 characters, the most this CPS keeps. Names are written in plain English letters, since the CPS cannot show others. The software holds up to 3,000 channels; Scan Add is on for the first 72, as the CPS allows.
VFO A and B
The HD1 CPS reads the first two rows of the file as VFO A and B, whatever their number says. So the file carries the CPS’s own default VFO rows (145.325 and 410.325 MHz), and importing sets the VFOs back to them — set them again in the CPS if you use them.
Only frequencies the radio covers
This CPS does not check frequencies and garbles some — 29.6 MHz came back as 293.9 MHz. So only channels in 136–174 and 400–480 MHz go in; the rest are listed, not written to the radio.
In the CPS
Open your codeplug (or read it from the radio) and save a copy — importing replaces all the channels. Then Channel › Import with Channels.csv, and write to the radio. Zones are not imported by this CPS; add the channels to them afterwards.
What is tested — and what is not
Tested: imported into Ailunce HD1 CPS V3.05, which gave back the same channels. Not tested: other CPS versions and the HD1 GPS software. The files go to the programming software, not to the radio: what the CPS then writes to the radio is up to the CPS, and we cannot check that without the radio. The programming software runs only on Windows; the file can be made on any computer. Use at your own risk, and transmit only on frequencies you are licensed or allowed to use.
Questions
- And the contacts?
- See RadioID contacts for the HD1.