In this article, we will cover the basic knowledge that every radio amateur should master to make basic use of radio systems. In my case, I will focus on the use of the Quansheng uv-K5(8)/uv-K6 device. Don’t be fooled by the name; although it may be referred to in two different ways, uv-K5(8)/uv-K6, both models are exactly the same in terms of electronics and aesthetics. In fact, there is no model called K6 on the official website.

It is worth noting that this device is illegal even with a radio amateur license, as it operates beyond the frequencies designated for amateur radio use. Additionally, I must mention that I am not an expert in this field, so there may be inaccuracies or errors in the text presented here. In such cases, I would appreciate any suggestions for improvement through the Telegram group .

The article is composed of the following sections:

• PMR446
• PMR7-7
• Quansheng UV-K5(8)/UV-K6
• Operation modes
• Light indicator
• Tones and codes
• Modulation kinds
• Repeaters
• Reverse mode
• Functions
• Buttons and functions
• Display indicators
• DTMF calls
• Scrambling
• Air copy
• Frequency scanner
• Remote kill
• Frequency unlock
• Mono installation
• Updater
• CPS
• CHIRP
• Backup configuration/calibration files
• Tips
• Resources

PMR446

The PMR446 (Personal Mobile Radio, 446 MHz) walkie-talkies is a frequency for personal use without the need for a license.
These walkies cover the frequencies:

Analogic: 446.00625 MHz  - 446,19375 MHz  / Step: 12.5 kHz
Digital:  446.003125 MHz - 446.196875 MHz / Step: 25 kHz

They allow for code configuration and operate with a Narrow bandwidth.
PMR446 walkie-talkies must comply with the following requirements:

Antenna:       Fixed
Maximum power: 0.5w
Approved by:   European Economic Community(CE), NO China Export(CE).

PMR7-7:

Emergency or consultation channel, can be used if you are lost or to check if there is a shelter or village nearby.
Very limited, it would have to be by chance that someone passes by or that the walkie-talkie signal reaches a shelter with the radio tuned to this frequency. Once emergency communication has been established, the parties involved should switch to another channel and free up 7-7.

Frequency: 446.08125 Mhz
Subtone:   85.4 MHz

Quansheng UV-K5(8)/UV-K6:

This walkie-talkie has been designed to transmit on typical amateur radio frequencies:

Image	Diagram	Technical specifications
		Power: 1/3/5W FCC(FM-VHF): 144 MHz ∽ 148 MHz FCC(FM-UHF): 420 MHz ∽ 450 MHz CE(FM-VHF): 144 MHz ∽ 146 MHz CE(FM-UHF): 430 MHz ∽ 440 MHz FM-VHF: 136 MHz ∽ 174 MHz FM-UHF: 400 MHz ∽ 470 MHz

NOTE: In the table above, reference is made to FCC: Federal Communications Commission - USA, CE: European Community - CE, and the frequency range where nothing is indicated, which represents the rest of the world.

But this walkie-talkie is capable of listening on many more bands, notably the AM band used by commercial aircrafts, so we will be able to listen to their conversations even though the reception quality may be very poor.

FM:            F1 50∽76 MHz         (RX only)
FM:            F2 108∽135.9975 MHz  (RX only)
FM:            F3 136∽173.9975 MHz  (TX and RX both)
FM:            F4 174∽349.9975 MHz  (RX only)
FM:            F5 350∽399.9975 MHz  (RX only)
FM:            F6 400∽469.9975 MHz  (TX and RX both)
FM:            F7 470∽599.9975 MHz  (RX only)
WFM(Radio FM):    76∽108       MHz  (RX only)
AM:            F2 108∽135.9975 MHz  (RX only)

As we can see, the walkie-talkie can only operate in AM mode in the F2 108∽135.9975 MHz band; the rest are FM only.

The walkie-talkie features the 32 bits DP32G030 (2) ARM processor working at 48MHz and 8 KB of RAM, an open radio FM chip and the radio chip, BK4819 , which can operate in the FM frequency range of 18 MHz ~ 660 MHz, 840 MHz ~ 1300 MHz. By loading modified firmware, we can access these bands. However, it’s crucial to note that the electronics were not designed to transmit on all of these frequencies, only those allocated for amateur radio. Therefore, transmitting outside of these frequencies could eventually damage the walkie-talkie, rendering it unusable. Additionally, the power output in these extra bands will be very low, making them useful only for listening purposes.

NOTE: For more hardware details we can take a look at walkie component list. and here some datasheets.

We can see the schema here:

It seems to be two K5(8)-K6 versions, but both models are exactly the same in terms of electronics and aesthetics.

K5(8)	K6

An interesting aspect is that this walkie-talkie allows battery charging from the charging base and through the USB-C connector, although its use is only recommended in emergencies. Furthermore, this model supports receiving NOAA alerts, but unfortunately, this service is only available in the USA.

Operation modes:

The non- PMR446 walkie-talkies allow operation in two different modes: channel or VFO (Variable Frequency Oscillator).

• Channel: When we press the arrow keys, they will navigate between the channels previously memorized. If we initiate a scan, it will be performed on the channels memorized in one of the available channel lists.
• VFO: When we press the arrow keys, they will adjust the configured “step” on the current frequency. If we initiate a scan, it will be performed on the current band.

An important aspect when using walkie-talkies is that communication is half-duplex, not full-duplex, so we must speak “in turns.”

Light indicator:

• Green: Receiving signal.
• Red: Transmitting signal.
• Blue: Battery charging via USB.
• Flashing Blue: Battery nearly charged via USB.

NOTE: The LED may illuminate in green, but we may not hear any audio. This can occur if we have configured an input code/subtone , causing the green light to indicate incoming signal, but we won’t hear anything because the code/subtone is incorrect. Another possibility is that this happens because we have DTMF decoding activated.

Tones and codes:

Tones and codes are a way of filtering incoming communications. It’s crucial to understand that they are only input filters for the walkie-talkie; they are NOT encryption systems and do not provide any confidentiality to the communication. With that said, they are useful in channels with high activity where users may interfere with each other.

If a pair of walkie-talkies configure a tone or code for reception, these two devices will only hear audio between themselves. Other walkie-talkies will continue to hear the audio since they do not have an input filter, thus receiving any signal from the channel. However, those who configured the tone/code will only hear each other.

• R-DCS: Digital reception code.
• R-CTCS: Same as the digital code but using analog subtones.
• T-DCS: Digital transmission code.
• T-CTCS: Same as the digital code but using analog subtones.

The codes can be different for TX (transmission) and RX (reception), so the transmitting walkie-talkie must use the code configured for reception on the other device.

Tones/codes prevent both undesired input communications and certain interferences that can cause noise on our frequency. The source of noise will not be able to generate the code or tone, so we will stop hearing it.

Digital codes are denoted with the suffix N and I, where N indicates the code is positive and I indicates it is negative. Practically, whether it’s positive or negative doesn’t matter. The management software CPS refers to negative codes as DCS-Reverse.

Modulation kinds:

There are other modulation techniques yet most modern analog models use FM due to its greater resistance to interference and noise. Another aspect we should be aware of is that frequencies can be expressed in cycles per second (Hz: Hertz) or wavelength (m: meters).

Repeaters:

Repeaters are an effective way to enable communication between systems when direct communication is not possible due to terrain or distance limitations. Essentially, they consist of a radio system with two antennas: one that listens on a frequency and another that retransmits what it receives, but on a different frequency.

Communication data is always provided from the perspective of the repeater.

Input frequency: The frequency at which the repeater listens. Fx-A in the image above.
Output frequency: The frequency at which the repeater re-transmits. Fx-B in the image above.
Offset: The difference between the input frequency/output frequency.

The offset is very useful because it allows walkie-talkies to listen to the repeater’s transmit frequency, and when we press the PTT (Push-To-Talk) button, it automatically applies the indicated offset, changing to the frequency +/- offset automatically, thereby transmitting on the repeater’s receive frequency.

For example, a repeater could have the following configuration parameters:

Input frequency: 145.000 Khz
Output frequency: 145.600 Khz
Offset: -600 Khz

The walkie-talkie should be configured as follows:

Frequency: 145.600 Khz
SFT-D: -
OFFSET: 000.600 Khz

What is happening is that when:

• We transmit a signal: The offset is automatically applied, shifting from 145.600 kHz -> 145.000 kHz, matching the repeater’s input frequency.
• We receive a signal: We listen on the frequency 145.600 kHz.

To access some repeaters, it is necessary to send them a 1750Hz tone, which we can do by pressing and holding SideKey1.
If we want to see which repeaters are near our area, we can always use applications like this one .

Reverse mode:

It may happen that two users are using a repeater to communicate, but one of them is not transmitting with enough power to reach the repeater, so this last one can only listen.

However, if the two walkie-talkies are close to each other, one of them could switch to reverse mode. What this does is that from that moment on, that walkie-talkie will listen on the repeater’s input frequency and transmit on its output frequency. This is usually used momentarily to agree with the partner on a frequency through which they can communicate directly without using the repeater. It should be used for the minimum necessary time because by transmitting on the repeater’s output frequency, we will overlap its signal for X kilometers around, potentially affecting other users.

To activate it, we must do it using the key combination: F+8(R).

Functions:

In the manual, you can find all the functionalities. I leave the link to both the official website and a copy on AlfaExploit .

To access the options, you need to press the M(A) button and navigate using the arrows. You can also access the options quickly if you know their ID. For example, if you know that the TDR option is 17, you can press M(A)+17.

If we enter the extended menu, we will be able to see the extra configuration parameters, to do this, we start by pressing:

SideKey1 + PTT + Power On

Buttons and functions:

All keyboard buttons have a special function that is activated by pressing the F key in combination:

Display indicators:

Symbol	Function
	Indicates the strength of the incoming or outgoing signal.
	Indicates the signal emission power: H(High)/M(Medium)/L(Low) TXP(13).
	Indicates the configuration of a code/subtone R_DCS(4), R_CTCS(5), T_DCS(6), T_CTCS(7).
	Indicates that the menu voice is activated VOICE(21).
	Indicates that we are working with a narrow bandwidth W/N(10).
	Indicates that the VOX(VOX:15) function is activated.
	Indicates whether the offset of the repeater channel is positive or negative SFT-D(8).
	Indicates that DTMF decoding is enabled D-DCD(43).
	Indicates that dual-band monitoring is enabled TDR(17).
	Indicates that the keyboard is locked.
	Indicates the battery charge level.
	Indicates that the battery is low.
	Indicates the channel on the display that we are operating on.
	Indicates that scrambling is activated SCR(11).
	Indicates that reverse mode (F+8(R)) is activated.
	Indicates if the channel is included in any scan list. The first diamond indicates it’s in scanlist1, the second diamond in scanlist2, and both diamonds in both scan lists.
	Indicates if Cross-Band is enabled WX(18).
	Indicates that the walkie is receiving a signal on the indicated channel.
	Indicates that the walkie is transmitting a signal on the indicated channel.
	Indicates that the battery is charging.
	Indicates that AM reception is activated AM(48).
	Indicates that NOAA channel scanning NOAA_S(49) is active. It will only appear if we are in NOAA mode(F+5(NOAA)).
	If we are on one channel but a signal comes in on another because we have enabled dual watch TDR(17), this symbol will indicate that the signal is coming in on the other channel.

DTMF calls:

The basic idea is to have a set of walkie-talkies all on the same frequency and be able to call one of them or a group of them using DTMF codes. Each walkie-talkie must have a unique identifier called an ANI-ID(35), which can only be configured using PC software.

If we transmit on the channel without setting the ANI-ID, nobody who has D-DCD(43) activated will hear us. The green light will come on because there’s radio signal, but no sound will be heard. However, if we set an ANI-ID that matches one of the walkie-talkies, it will immediately hear the audio without having to “pick up”.

The configuration parameters D-RSP(49) only apply to the receiving walkie-talkie:

• NULL: If the receiving walkie-talkie receives its ANI-ID(35), audio will be outputed through speakers. We could say it’s a phone with automatic answer.
• RING: It behaves exactly the same as with NULL, but additionally, it plays a ringing tone that will only stop when the receiver makes a transmission.
• REPLY: It behaves exactly the same as with NULL, but the receiving walkie-talkie also responds. This way, the transmitting walkie-talkie knows that the other side is active and will be able to hear the audio.
• BOTH: It behaves exactly the same as with NULL, but additionally, it plays a ringing tone and responds to the sender.

If transmission stops on the channel, the call will remain auto-picked up for the time configured in D-HOLD(40). To cancel a call, you’ll need to use one of the functions activated by the F key. However, if you want to delete a character in DTMF dialing mode, you must press SideKey1.

Calls can be made in various ways:

• Manual: Pressing the PTT, the ANI-ID of the walkie we want to call, * and our ANI-ID. For example, if our ID is 666 and we want to call 100, it would be: 100 * 666. But in my tests, only the receiver of the call could hear the audio, even with REPLY activated.
• Automatically: Pressing *, the ANI-ID of the walkie we want to call, and the PTT. In this mode, our ANI-ID is also sent, but it’s done automatically.

To call a group, you need to define the Local code character from the PC. Assuming it is #, calling 12# would be calling 120-129, with 1## calling 100-199, and ### calling 000-999, all possible users. But when calling a group, the REPLY function won’t work; the transmitter will speak blindly.

We must keep in mind that this is still an open channel. Anyone can receive and anyone can transmit on our frequency once a call is auto-accepted. That means if a colleague calls a walkie, it opens communications. If, at that moment, a third party unrelated to the group transmits on that frequency, the two “friendly” walkies will hear the third one, and of course, this third party has always been able to hear the audio from the “friendly” walkies.

I leave a demonstrative video with DTMF contacts configured and the D-RSP(49) set to BOTH. On the left, we have the K5(8), and on the right, the K6.

Depending on whether the walkie-talkie is the caller or receiver of the call, the display lines will show specific information.

NOTE: If two devices are configured with the same ANI-ID(35), both will respond to the call. Upon answering the call, both devices behave as if the D-DCD(43) configuration had not been set, allowing them to speak and listen, as well the initiator of the call as the two receivers.

Scrambling:

Conversations can be “encrypted” using scrambling SCR(11), which is essentially a code used to encrypt the signal. A walkie-talkie that does not have it configured will hear a distorted version of the audio.
We can observe the effect on the following video:

We must remember that encrypting any communication is illegal, at least in Spain, so we must be very careful with this option. If we want to be safe and ensure that it is never activated by mistake, we can access the extended menu and disable the possibility of activation through:

SideKey1 + PTT + Power On
SCREN: OFF

As we can see, the SCR option appears in the menu, but when activated, it does nothing. We can see that the letters SCR do not appear to the right below the frequency:

Air copy:

Clone all the configuration from one walkie to another, that is, make a clone. The steps are as follows:

• Both walkies: Press the PTT+SideKey2 buttons while starting up.
• Both walkies: Enter the frequency for the clone or leave it at the default.
• Receiver: Press Exit(D).
• Transmitter: Press M(A).

I leave a video showing how it works:

If the process encounters any error, we will see the counter E: increase on reception. In that case, we should restart the process.

Frequency scanner:

This walkie-talkie has a very interesting feature called Frequency Scanner: FC, which allows us to determine the frequency and the tone/code that another walkie-talkie is using. To activate this function, simply press F+4(FC) and wait for the other walkie-talkie to transmit a signal. Then, we can save the configuration in a memory slot as a channel by pressing M(A). This is very useful when working with inexperienced people in the world of radio who may not know what parameters are configured on their radio.

Another related functionality with FC is the Tone/Code scanner. If we know the frequency on which the counterpart is transmitting but are unaware of its tone/code, we can press F+*(Scan), and it will automatically detect the tone/code. Finally, we can save the configuration in a memory slot as a channel by pressing M(A).

Remote kill:

It’s possible to disable a walkie-talkie by sending it a sequence of DTMF tones(Kill code), known as remote kill. If the lost walkie-talkie is later located, it can be re-enabled using another sequence of DTMF tones(Revive code). However, for this to work, the active channel must have the D-DCD(43) option enabled.

The configuration to enable this function and set the codes can only be done from the PC .

Common setting: Permit remote kill
DTMF setting -> Local code: 666
DTMF setting -> Kill code: 66066
DTMF setting -> Revive code: 66166

To kill the walkie-talkie 666 we must call: ANI-ID(Local code)*Kill code, in this case 666*66066
To revive it: ANI-ID(Local code)*Revive code, in this case 666*66166

I leave a video showing how it works:

NOTE If multiple walkie-talkies have the same kill code, they will both be blocked. If the one sending the kill code has the same kill code, it does NOT self-block.

Frequency unlock:

This walkie-talkie allows transmitting on various bands (not all), but I don’t recommend it as we can irreversibly damage the equipment, and the signal power outside the amateur radio range will be poor.

Remember the supported frequency bands:

FM:            F1 50∽76 MHz
FM:            F2 108∽135.9975 MHz
FM:            F3 136∽173.9975 MHz
FM:            F4 174∽349.9975 MHz
FM:            F5 350∽399.9975 MHz
FM:            F6 400∽469.9975 MHz
FM:            F7 470∽599.9975 MHz
AM:            F2 108∽135.9975 MHz

To perform the configuration, we need to access the extended menu.

SideKey1 + PTT + Power On

We must take into account some aspects:

• By default, we can listen on all bands. The only exception is F5, which is controlled through the option 350EN.
• The rest of the options control transmission on the different bands.
• F-LOCK enables typical ranges according to geographical region.
• XXXTX enables additional bands when F-LOCK is OFF.

F-LOCK - Assigns the allowed bands for transmission.
    FCC (144-148, 420-450)
    CE (144-146, 430-440)
    GB (144-148, 430-440)
    430 (137-174, 400-430)
    438 (137-174, 400-438)
    OFF - Enables the bands: F3 (136∽173.9975 MHz) and F6 (400∽469.9975 MHz) with the possibility of expansion through 200TX, 350TX, and 500TX.

200TX - Enables TX on 200MHz F4.
350TX - Enables TX on 350MHz F5.
500TX - Enables TX on 500MHz F7.

350EN - Enables RX on 350MHz F5.

In my case, I’m going to enable only the amateur radio frequencies, the corresponding configuration options are:

F-LOCK: OFF
Tx 200 - OFF
Tx 350 - OFF
Tx 500 - OFF
350 En - ON

As you can see, with this configuration, we can listen to all bands but only transmit on the amateur radio bands:

Keep in mind that despite unlocking the frequencies, they will always be FM; we can never transmit in AM. Also, the transmission power outside the amateur radio band will be very poor, as the electronics were not designed for other ranges.

Mono installation:

In FreeBSD there seems to be a driver for the cable , but it doesn’t work very well; it’s detected as:

dmesg:
uchcom0: CH340 detected

lsusb:
Bus /dev/usb Device /dev/ugen0.3: ID 1a86:7523 QinHeng Electronics CH340 serial converter

According to FreeBSD, the driver is supported , and there’s a developed driver .

The comments in the source code don’t inspire much confidence, to say the least:

head -n 66 /sys/dev/usb/serial/uchcom.c|tail -n 4
/*
 * Driver for WinChipHead CH341/340, the worst USB-serial chip in the
 * world.
 */

When the cable is connected it appears two new devices:

/dev/cuaU0
/dev/ttyU0

It can be mapped inside Wine environment but none of them work:

HKEY_LOCAL_MACHINE\Software\Wine\Ports
New -> StringValue
Entry name: COM5
Entry value: /dev/cuaU0
Entry name: COM6
Entry value: /dev/ttyU0

Finally I decided to use a Bhyve virtual machine with a USB controller card delegated by passthru to a Linux machine were we will run Wine32.

Install the hardware extended kernel:

Reboot and you should be running the new kernel:

Linux ubuntu-cloud 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Check that you can manually load the required kernel module used to manage the USB cable:

When cable is connected we should see the following message in dmesg:

[   61.867011] usb 1-1: ch341-uart converter now attached to ttyUSB0

And a new device under /dev:

crw-rw---- 1 root dialout 188, 0 Feb 23 23:08 /dev/ttyUSB0

Let’s proceed with the installation of Wine32; the 64-bit version won’t work for running this software:

Create a 32bits wineprefix:

Create new wineprefix
Architecture: 32
Name: wineprefix32
/home/ubuntu/.local/share/wineprefixes/wineprefix32

We’ll need to install wine-mono within the Wine system on the Linux system:

Install it:

Proceed with installation:

It seems like it didn’t install anything, but if we click OK and enter again, we’ll see that it’s installed:

We install all the fonts to avoid any issues:

We install the Windows driver for the cable:
https://en.qsfj.com/support/downloads/3268 : UV-K5(8) Firmware

Click on the left button:

We can see which port is correct within Wine:

lrwxrwxrwx 1 ubuntu ubuntu 12 Feb 23 18:03 /home/ubuntu/.local/share/wineprefixes/wineprefix32/dosdevices/com33 -> /dev/ttyUSB0

The correct port is COM33.

NOTE: If we are conducting tests and reinstalls, we must ensure that there are no conflicts in the SSH known_hosts file, or else X11 forwarding will not work.

Updater:

Download the updater software:
https://en.qsfj.com/support/downloads/3268 : UV-K5(8) Firmware

The zip file contains several EXE files and some other files:

• CP210x_USB.exe: USB cable driver.
• AnonymPSUpdater_Setup_EN.exe: Updater software.
• K6_V3.00.15.bin: Firmware image.
• Firmware Upgration Instruction Video.mp4: Instructional video on how to update the firmware.
• UV-K5(8) UV-K6 Firmware Upgration Instruction.docx: Written instructions on how to update the firmware.

Install the updater software:

Start the software:

Install it:

In this Facebook group, the actual Quansheng team assures it, indicating that if it’s a model with the ability to configure menu text in two languages, we should use the firmware for the K5(8); if it doesn’t allow changing the language of the text, use the firmware for the K5.

 1. If your menu is pure English menu, you need to use UV-K5 firmware V2.01.31;
 2. If your menu is Chinese&English selectable menu, you need to use UV-K58/UV-K6 firmware V3.00.15.

Although I haven’t seen this menu in either the K5(8) or the K6, if we try to load the K5(8) firmware version on a any of them, the updater will inform us of the problem.

If you provide them with an email, they will send you the latest firmware version themselves. As of today, February 24, 2024, the provided versions are:

k5_v2.01.33_publish.bin
k6_v3.00.17_publish.bin

Start the software:

We press the PTT button and, without releasing it, turn on the walkie-talkie (the screen will remain blank and the flashlight will be on: flashing mode), connect the cable to the walkie-talkie, specify the COM33 port, and connect.

We click on the three dots and select the firmware file:

Now we can proceed with the update by clicking on “Update”. Before performing any update, we will check the battery level of the walkie:

NOTE: If the Update button is not available, it’s because we haven’t booted the walkie-talkie in firmware update mode.

For convenience, I’ve set up an alias to easily run the software:

alias quanshengUpdate='ssh -vYC ubuntu@192.168.69.5 "WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/wineprefix32 wine ~/.local/share/wineprefixes/wineprefix32/drive_c/Program\ Files/Anonym/Portable\ Radio\ Update\ Tools/V1.1.12/Updater.exe"'

CPS:

We download the management software:
https://en.qsfj.com/support/downloads/3268 : UV-K5(8) Programming Software-Neutral

The zip file contains several EXE files and some other files:

• CP210x_USB.exe: USB cable driver.
• PSCPS.exe: Management software.
• 20230522_144349.mp4: Instructional video on how to use the management software.

Serial port configuration:
Start it and configure the COM port, Settings -> COM Setting: COM33

Read data from radio:
We can read the walkie-talkie configuration by clicking on Read in button.

Base info:
In the Base info section, we can query firmware version.

Function key:
In the Function key section, we can configure the SideKeys.

Common setting:
In the Common setting section, we can configure various aspects of the radio. I’ll indicate their equivalent from the firmware menu. If there’s no equivalent in the menu and it’s an option only configurable from the PC, I’ll provide a brief description.

DTMF setting:
In the DTMF setting section, we can configure DTMF tone related parameters.

DTMF contacts:
In the DTMF contacts section, we can configure our DTMF contacts.

MR channel:
In the MR channel section, we can configure parameters related to the channels. From the main menu, we can edit, reorder, and delete channels. Double-clicking on a channel will also allow us to edit it.

The Frequency step option will only be available for the AM airband: 108∽135.9975 MHz. If we try to configure it for another band, the following error will appear:

NOTE: In channel mode, the step parameter doesn’t seem to make sense to me either, neither in AM nor in FM.

VFO channel:
In the VFO channel section, we can configure parameters related to the bands. If we look closely, we can see the same band listed twice. The first entry indicates the starting frequency: A, and the second indicates the ending frequency of the band: B.

If we set a TX freq-A different from RX freq-A, we are configuring an offset in that band for transmission.
Exactly, if we have RX freq-A: 136.00000 MHz and TX freq-A: 137.00000 MHz, we have an offset of +1.00000 MHz.
Whenever we are between the frequencies RX freq-A and RX freq-B, when transmitting a signal, we will exit on the current frequency +/- the offset. For example, if we are on 136.12500 MHz, we would transmit on 137.12500 MHz.
The parameter TX freq-B doesn’t seem to have any utility.

Scan list:
In the Scan list section, we can configure parameters related to scanning lists. From here, we can edit them, and we can also set one as the default. When we initiate scanning in channel mode, this will be the list used.

In list editing, we can define priority channels, which are channels scanned more frequently than non-priority channels. This is useful for scanning a large number of channels without overlooking reception on a priority channel while the radio is scanning non-priority ones.
For example, if we have a list with channels 1, 2, 4, and 5, with priorities set for 1 and 2, all channels will be scanned, but channels 1 and 2 will be scanned more frequently. This ensures that if there is activity on channels 1 or 2 while scanning channels 3 and 4, it won’t be missed.

Frequency:
In the Frequency section, we can view and edit the saved radio stations. To edit a station, simply double-click on the current frequency.

CPS password:
You can configure a password in CPS so that it prompts for it every time you try to read or load the configuration into the walkie.

Setting -> Password set...

Now, every time you want to read or write the configuration to the radio, it will ask for the password.

For greater convenience, I have set up an alias to run the software more easily.

alias quanshengCPS='ssh -vYC ubuntu@192.168.69.5 "WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/wineprefix32 wine ~/UV-K5\(8\)\ Programming\ Software-Neutral/cps_V1.0.40_免安装版/PSCPS.exe"'

CHIRP:

Chirp is another widely used configuration software that supports a large number of devices. We’ll install it on the Linux system we’ve used in the previous steps.

The version of Chirp included in Ubuntu 22.04 as of today, February 24, 2024, does not support Quansheng devices, so we will install it manually.

ii  chirp                                1:20200227+py3+20200213-3               all          Configuration tool for amateur radios

Install pip:

Install chirp from regular user:

Start the software:

Connect with the radio:
Connect with the radio: Radio -> Download from radio

Channel list:
It will display the channels. In my opinion, the interface leaves much to be desired as it is very complicated to understand what each field is. It would have been much simpler to map a column for each option in the walkie’s menu as CPS does. Despite its lack of intuitiveness, I will try to explain what each parameter does:

NOTE: Skip column seems to be a bug, as for skipping a channel from scanning we only have to not assign it as scanlist member. To configure the scanlists we must enable extrafields(explained below).

Tone Mode option can take one of the following values:

• None: No tone/code is assigned for either input or output.
• Tone: The output tone configured in the Tone column is assigned.
• TSQL: Both the output and input tones get configured with the ToneSquelch column value.
• DTCS: Both the output and input codes get configured with the DTCS column value.
• Cross: This mode should be assigned when configuring mixed settings, meaning not only codes or tones but the ability to choose between them for input and output. This field depends on another column: Cross Mode.

The Cross Mode column determines whether codes or tones will be used, with the first field indicating transmission and the second field reception:

• Tone -> Tone: The output tone configured in the Tone column and the input tone configured in the ToneSquelch column are assigned.
• Tone -> DTCS: The output tone configured in the Tone column and the input code configured in the RX_DTCS column are assigned.
• DTCS -> Tone: The output code configured in the DTCS column and the input tone configured in the ToneSquelch column are assigned.
• -> Tone: The output tone/code is not assigned, but the input tone configured in the ToneSquelch column is assigned.
• -> DTCS: The output tone/code is not assigned, but the input code configured in the RX_DTCS column is assigned.
• DTCS ->: The input tone/code is not assigned, but the output code configured in the DTCS column is assigned.
• DTCS -> DTCS: The output code configured in the DTCS column and the input code configured in the RX_DTCS column are assigned.

NOTE: It seems like the option Tone -> is missing, probably due to a glitch in Chirp. I assume that over time they will fix these kind of issues, considering that the support for Quansheng radios is still experimental.

Some modes are more restrictive than others. For example, if we configure only digital code as output, it doesn’t make sense to have a tone set for input. The software detects these restrictions, but not very accurately. Sometimes you have to click on more fields, even if you’re not changing anything, to apply these restrictions.

Band list:
Similarly to how we did with CPS , from CHIRP it’s also possible to define the start and end of each band.:

FM:            F1 50∽76 MHz
FM:            F2 108∽135.9975 MHz
FM:            F3 136∽173.9975 MHz
FM:            F4 174∽349.9975 MHz
FM:            F5 350∽399.9975 MHz
FM:            F6 400∽469.9975 MHz
FM:            F7 470∽599.9975 MHz
AM:            F2 108∽135.9975 MHz

To modify the parameters, we must scroll all the way down the channel list:

By modifying these parameters, we will alter the frequency limits when scanning in a band and the default parameters in the bands such as the tones/codes , bandwidth, transmission power, and other parameters. Of course, we can always modify these parameters on the fly from the walkie menu.

Settings:
In the Settings tab, we can find all other configuration settings.

Basic Settings:

Programmable keys: SideKeys configuration.

DTMF Settings:

DTMF Contacts: DTMF contact list.

Scan Lists: From this section, we can only assign the default scan list, enable/disable scan priority, and configure the two priority channels of each list. To edit the lists, we will do it from the Memories tab, having previously enabled the extra fields: View -> Show extra fields, explained below.

Unlock Settings: We can unlock transmission on frequencies outside the amateur radio range in the same way as we did from the extended menu . We can also see the option KILLED Device was disabled (via DTMF), this option only shows us if the walkie-talkie was disabled via remote kill , it does not allow to either lock or unlock the walkie-talkie.

FM Radio: It allows you to edit the stored radio channels.

Driver information: Displays the firmware version. The second parameter allows you to configure channels on frequencies outside the ’normal’ range if you have loaded special firmware that allows a wider frequency range. Without this option, channel editing will be restricted to ’normal’ frequency ranges.

Extra fields:
In the Memories section, additional parameters can be displayed if we enable them.

View -> Show extra fields

Actually, these parameters can also be accessed without enabling the mentioned menu. We should do:

Right click on the channel -> Properties -> Extra Tab

It seems that Chirp is quite buggy as of today, at least with this walkie model. For example, in channel 20, there’s only an analog tone configured for output, but in Properties, we see digital tones and more.

Backup configuration/calibration files:

The walkie comes calibrated and configured in a specific way, and this information is stored in the EEPROM, which has unique content for each walkie. So, it’s advisable to make a backup if we plan to experiment with exotic firmware in the near future.

First, we download the software k5prog-win

Execute it:

Configure serial port and speed 38400-K5/K6:

Read Configuration	Save Configuration

Read Calibration	Save Calibration

We download the files and keep them safe:

Tips:

Some basic recommendations are:

• Never transmit without the antenna, as the walkie-talkie may get damaged.
• The antenna must be appropriate for the frequency range in use; otherwise, it can also cause damage.
• Do not use the walkie-talkie while it’s charging.
• Only charge the battery when it’s fully discharged; otherwise, the battery memory may deteriorate.
• Use the USB-C charging port only for emergencies.
• Walkie-talkies cannot be used for commercial purposes or on PMR446 frequencies; a business license is required at least in Spain.
• Depending on the antenna length, optimal performance will vary across frequencies, as it corresponds to the wavelength of each frequency. The default antenna that comes with the Quansheng is designed for amateur radio frequencies, but using an antenna specifically tuned to the frequencies you plan to use will likely yield better results.
• We can see the frequencies of an antenna inside the thread of the antenna.
• If the CPS encounters any communication issues with the radio, we must ensure that the connector is inserted fully into the radio. We can try disconnecting and reconnecting the cable, unplugging the CPS from the COM port and reconnecting it. Sometimes, connecting the cable and then turning on the walkie seems to work better, all very random.

Resources:

• Wiki: https://github.com/ludwich66/Quansheng_UV-K5_Wiki/wiki
• Telegram EN: https://t.me/quansheng_uvk5_en
• Telegram ES: https://t.me/QuanShengES
• NewHamsInfo: https://newhams.info/
• HamRadioSchool: https://www.hamradioschool.com/all-articles
• URE forum: https://www.ure.es/foros/
• Online SDRs: https://www.receiverbook.de/map
• Signal Wiki: https://www.sigidwiki.com/wiki/Database
• Wave lengths: https://en.wikipedia.org/wiki/Amateur_radio_frequency_allocations
• HW MOD additional bands: http://www.hamskey.com/2024/02/introduction-to-uv-k5-hf-fullband.html
• MOD HW additional channels: https://www.universirius.com/en_gb/preppers/quansheng-uv-k5-manuale-del-firmware-ijv_v3/#IJV_V3-VX3
• MOD HW ESP32: https://github.com/kamilsss655/ESPRI
• Yes, DOOM can run on it: https://www.youtube.com/watch?v=5XH777ffqmk