CHIRP

Jim Unroe wrote:

The UV-5RTP already is supported. As shown on the CHIRP Supported Radio Models list on the CHIRP home page...

Baofeng/Pofung

• UV-5RTP (use BF-F8HP)

Jim KC9HI

Agreed. I've used the BF-F8HP profile on several UV-5RTP radios with no problem.

Jim Unroe wrote:

The UV-5RTP already is supported. As shown on the CHIRP Supported Radio Models list on the CHIRP home page...

Baofeng/Pofung

• UV-5RTP (use BF-F8HP)

Jim KC9HI

I am using the cable that shipped with the radio, newest build version of Chirp, Windows 10 with updates, and the BF-F8HP profile and I have no transmit function on the radio after programming. I tried it with the UV-5R setting and same results. I have 20 of these radios and so far I have had the same problem on everyone I touched. I was able to roll back to the stock setting and it transmits just fine. I've used a BF8-F8HP and UV-82HP as the source for the cloning with no changes. Any ideas? I get the firmware is different error message.

One thing that you should not be doing is directly uploading an image from another radio into any of these radios. CHIRP used to be able to protect the user from making this mistake by refusing to upload an image that was created from a radio with a different firmware version. Lately these radios have been reporting the same firmware version to CHIRP no matter what the real internal firmware version it. This makes it impossible for CHIRP to protect you from cross-loading memory areas that can cause erratic and/or undesired behavior.

The preferred method is to download from the working destination radio to create a tab that is compatible with it. Then you would "import" the "source image" into this tab to update the channels. Change any global settings as needed and then upload back to the same radio. This prevents the cross-loading of memory areas that are different between the radios that could cause problems that are similar to what you are experiencing. It also works between radios of various vendors and models.

Another popular, quick-and-dirty method is to download from the destination radio to create a tab that is compatible with it. Then download from the source radio (or load an "image" that was previously saved from the source radio) to create a second tab. Copy-and-paste the channels from the tab from the source radio to the tab for the destination radio.

Jim KC9HI

I didn't make that clear. My apologies. I downloaded the source radio then cut and pasted it on to the previously downloaded destination radio. Same result. I built a "clean" tab and it also did it. Finally, I downloaded the destination radio, then did a manual entry of each channel. No changes. It seems ANY change from the original trigger the no tx response.

Then roll back to stock, attach that image to this issue. The make the minimal amount of changes needed to cause the not TX conditions (copy-and-paste 1 channel, 2 channels, just whatever the minimum it takes) and add that image to the issue with a note of what was changed.

Jim KC9HI