Project

General

Profile

Actions

Bug #11980

open

Baofeng P15UV incorrectly listed as UV-17Pro

Added by Chris Hemmah 6 days ago. Updated 2 days ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/14/2025
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Baofeng P15UV
Platform:
Linux
Debug Log:
I read the instructions above:
Yes

Description

NOT A SOFTWARE BUG: In multiple places in bug reports and documentation the Baofeng P15UV is incorrectly listed as a clone of the Baofeng UV-17Pro. It is not, it is a clone of the Baofeng UV-13Pro, and this is the driver that should be used.


Files

config.txt (1.3 KB) config.txt Chris Hemmah, 05/14/2025 09:09 AM
Baofeng_UV-13Pro_20250514_modded.img (36.2 KB) Baofeng_UV-13Pro_20250514_modded.img Chris Hemmah, 05/14/2025 09:09 AM
linux_system_info.txt (646 Bytes) linux_system_info.txt Chris Hemmah, 05/14/2025 09:09 AM
13prodebug.log (323 KB) 13prodebug.log Chris Hemmah, 05/17/2025 08:59 PM
17prodebug.log (15.7 KB) 17prodebug.log Chris Hemmah, 05/17/2025 08:59 PM
1000106618.jpg (534 KB) 1000106618.jpg Chris Hemmah, 05/17/2025 09:21 PM
1000106619.jpg (833 KB) 1000106619.jpg Chris Hemmah, 05/17/2025 09:21 PM
Actions #2

Updated by Dan Smith 6 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Massimo Nespolo 3 days ago

I have the P15UV, Chirps dialogs correctly with it by choosing UV-17Pro. If I choose UV-13Pro I get an error message saying '"No response from radio". It is not a cable program, because if I switch to UV-17Pro without touching the cable, it works.
Therefore, the correct alias seems to be UV-17Pro, not UV-13Pro. At least on Windows....

Actions #4

Updated by Dan Smith 3 days ago

Platform (windows or linux) definitely does not matter for this.

I'm inclined to switch it back to what Massimo originally reported since there have been no complaints about it in the last three months.

Chris can you please include a proper debug log so we can look at the exchange with the radio?

Actions #5

Updated by Dan Smith 3 days ago

Also, I note you have "modded" in your filename. Has the radio been changed in some physical way or had different firmware loaded?

Actions #6

Updated by Dan Smith 3 days ago

  • Status changed from Closed to Incomplete
Actions #7

Updated by Chris Hemmah 2 days ago

Dan Smith wrote in #note-4:

Platform (windows or linux) definitely does not matter for this.

I'm inclined to switch it back to what Massimo originally reported since there have been no complaints about it in the last three months.

Chris can you please include a proper debug log so we can look at the exchange with the radio?

It is not a common radio so I am not surprised. I can turn on debugging and interact with the radio with both drivers happily. The modded in the file name is simply the difference between the original downloaded config and my modded config with my preferred settings. The UV-17Pro and UV-13Pro are significantly different radios, even looking at the menu and functions it is obvious the P15UV is a clone of the UV-13Pro. I will upload the debug as soon as possible.

Actions #8

Updated by Dan Smith 2 days ago

The UV-13Pro (UV-17 based) and UV-17Pro are very different internally and it doesn't make any sense that one radio would respond to both drivers. If you can upload logs to show that I'd be very interested in seeing them.

If not, I'll switch it back to the way it was.

Actions #10

Updated by Chris Hemmah 2 days ago

Dan Smith wrote in #note-8:

The UV-13Pro (UV-17 based) and UV-17Pro are very different internally and it doesn't make any sense that one radio would respond to both drivers. If you can upload logs to show that I'd be very interested in seeing them.

If not, I'll switch it back to the way it was.

Uploaded as requested. Let me know if you need more or something different. I only opened this because I went down a rabbit hole until I found an obscure post linking the P15UV and UV-13Pro. This radio is a UV-13Pro clone.

Actions #11

Updated by Dan Smith 2 days ago

Sorry, when you said "interact with both happily" I thought you meant you were able to interact with the radio using either driver. There must be multiple radios out there with different internals using the same model.

Can you post a picture of the front of your radio and the FCC tag please? Massimo, if you could do the same, that would be helpful.

If Baofeng is really selling two different radios under the same name then we'll have to figure out something else.

Updated by Chris Hemmah 2 days ago

Dan Smith wrote in #note-11:

Sorry, when you said "interact with both happily" I thought you meant you were able to interact with the radio using either driver. There must be multiple radios out there with different internals using the same model.

Can you post a picture of the front of your radio and the FCC tag please? Massimo, if you could do the same, that would be helpful.

If Baofeng is really selling two different radios under the same name then we'll have to figure out something else.

As requested

Actions

Also available in: Atom PDF