🌐 Translate
Automatic translation is available via Google Translate: Open translated version.
This page explains how to use CHIRP with the dedicated driver included with each firmware release.
[!WARNING] Use the
CHIRPdriver from the same firmware release as the one installed on your radio. Do not use Quansheng CPS. Do not use a genericUV-K5driver or a driver from another firmware release.
The dedicated v6.1.0 driver supports every official v6.1.0 edition on:
UV-K1UV-K5 V3Fusion, FieldOps, Transfer, and LabsIt is not for:
UV-K5 V1 / V2Because this firmware uses its own memory and settings layout, another driver can read or write the wrong data. Always match the driver version to the firmware version, even when moving between official editions.
Do not assume that the older v6.0.0 driver is interchangeable with the v6.1.0 driver.
[!NOTE]
CHIRPmay show this driver as experimental. That is expected.
Before updating from an earlier firmware generation:
v6.1.0 edition.RESET ALL.v6.1.0 CHIRP driver and download a fresh image from the updated radio.[!WARNING] Do not directly import an old CSV over the complete new radio image. Copy and paste the channel rows into a freshly downloaded image so the new version’s settings layout remains intact.
CHIRP.File > Load Module... is not available, enable CHIRP Help > Developer Mode features first (Help menu), then restart CHIRP.File > Load Module... and select the f4hwn.fusion.chirp...py file included with the firmware release.CHIRP should offer the UV-K1 & UV-K5 V3 (F4HWN Fusion) model entry.[!NOTE] The module filename and CHIRP model label retain the historical
Fusionname. Thev6.1.0module is nevertheless the shared driver for all four official editions.
USB-C cable or a compatible double-jack programming cable on the mic/spkr connector.CHIRP, choose Radio > Download From Radio...Vendor: Quansheng.Model: UV-K1 & UV-K5 V3 (F4HWN Fusion).[!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.
After the download, enable View > Show Extra Fields in CHIRP (View menu).
This is important because the dedicated 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:
TXLockBusyCLFreqRevPTT IDCompanderScanlistsYou can then edit memories, names, and the supported settings.
When you are ready:
CHIRP, choose Radio > Upload To Radio...[!WARNING] Leave calibration-related or advanced items alone unless you know exactly what they do.
The independent Beacon application uses the CHIRP Message Line 1 setting as its callsign. The dedicated driver accepts up to 12 characters in this field.
When Beacon transmits in CALL mode, the firmware converts letters to uppercase, keeps letters, digits, and /, removes unsupported characters, and appends ` MOE. If the resulting callsign is empty, it transmits MOE`.
After changing Message Line 1, upload the settings to the radio before starting Beacon. See Beacon for transmission behavior and safety information.
CHIRP for bulk programming, not Quansheng CPSCheck these points:
UV-K1 or UV-K5 V3CHIRP loaded the driver from that same release, not another UV-K5 module