Programming with CHIRP

🌐 Translate
Automatic translation is available via Google Translate: Open translated version.

Programming with CHIRP

This page explains how to use CHIRP with the dedicated Fusion driver included with each firmware release.

Warning

Use the CHIRP driver from the same firmware release as the one installed on your radio. Do not use Quansheng CPS. Do not use a generic UV-K5 or non-Fusion driver.

Compatibility

The dedicated driver is only for:

• UV-K1
• UV-K5 V3
• Fusion edition

It is not for:

• UV-K5 V1 / V2
• other Quansheng models
• other firmware editions

Because Fusion uses a different memory layout, another driver can read or write the wrong data.

Before you start

• make sure the radio really runs the matching Fusion release
• locate the included driver file in that release package
• the file name starts with f4hwn.fusion.chirp and ends with .py
• be ready to save a backup of the radio image before editing anything

Note

CHIRP may show this driver as experimental. That is expected.

Load the dedicated driver in CHIRP

1. Open CHIRP.
2. If File > Load Module... is not available, enable CHIRP Help > Developer Mode features first (Help menu), then restart CHIRP.

3. Use File > Load Module... and select the f4hwn.fusion.chirp...py file included with the firmware release.
4. Once the module is loaded, CHIRP should offer the UV-K1 & UV-K5 V3 (F4HWN Fusion) model entry.

Download from the radio

1. Turn the radio on.
2. Connect the radio with either a compatible USB-C cable or a compatible double-jack programming cable on the mic/spkr connector.
3. Make sure the connector is firmly inserted.
4. In CHIRP, choose Radio > Download From Radio...
5. Select the correct serial port.
6. Select Vendor: Quansheng.
7. Select Model: UV-K1 & UV-K5 V3 (F4HWN Fusion).
8. Start the download and wait until the radio image has been fully read.

Tip

If communication fails, disconnect the cable, turn the radio on first, then reconnect the cable. The dedicated driver warns that some setups may fail if the radio was powered on with the cable already attached.

Show the extra fields

After the download, enable View > Show Extra Fields in CHIRP (View menu).

This is important because the dedicated Fusion driver exposes several channel-specific fields through the Extra group. Without Show Extra Fields, some firmware-specific parameters remain hidden in the channel editor.

Typical examples include:

• TXLock
• BusyCL
• FreqRev
• PTT ID
• Compander
• Scanlists

Edit and upload

You can then edit memories, names, and the supported settings.

When you are ready:

1. Review your changes.
2. In CHIRP, choose Radio > Upload To Radio...
3. Use the same port, vendor, and model.
4. Wait until the upload is fully complete before touching the cable or turning the radio off.

Warning

Leave calibration-related or advanced items alone unless you know exactly what they do.

Beacon identification

The Fox Hunt / Beacon feature uses the CHIRP Message Line 1 setting as the Beacon callsign. The dedicated Fusion driver accepts up to 12 characters in this field.

When Beacon transmits, the firmware converts letters to uppercase, keeps letters, digits, and /, removes unsupported characters, and appends BEACON. If the resulting callsign is empty, the transmitted identification falls back to FOX BEACON.

After changing Message Line 1, upload the settings to the radio before starting Beacon mode. See Fox Hunt and Beacon for the transmission behavior and safety information.

Good practice

• always use the driver included with the same firmware release
• always download first, then save a backup
• after a firmware update, reload the newer driver module from that release
• use CHIRP for bulk programming, not Quansheng CPS

If something looks wrong

Check these points:

1. the radio is really a UV-K1 or UV-K5 V3
2. the radio really runs the Fusion edition
3. CHIRP loaded the dedicated Fusion driver, not another UV-K5 module
4. the cable is fully inserted
5. the selected serial port is the correct one

Related pages

• Getting started
• Radio operation
• Fox Hunt and Beacon
• Troubleshooting