CHIRP

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....

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?

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

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.

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.

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.

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.

Massimo can you please provide the information requested above?

From the look of Chris' label the current state of things is correct. If you have the same label but require a different driver, we need to know and do something about it.

Dan Smith wrote in #note-13:

Massimo can you please provide the information requested above?

From the look of Chris' label the current state of things is correct. If you have the same label but require a different driver, we need to know and do something about it.

Massimo, can you please show what you have? I solved this through alot of research, I'd rather not have others have to do this rabbit hole diving. I don't want this subject to die on the vine. I'd love to see your radio and debug logs myself, obviously ours are somehow different. I've now programmed two P15UVs the same way ordered at different times.

Massimo Nespolo wrote in #note-3:

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....

See above notes

Chris Hemmah wrote in #note-15:

Massimo Nespolo wrote in #note-3:

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....

See above notes

Massimo, we can see the notes from before. What we are looking for is what I provided. Debug logs of both drivers connecting, and a picture of the back of the radio. Can you provide that? I am very curious to see your results.