CHIRP

If it would help I would be willing to load my radio (UV-13Pro) for development. Or with some coaching I could probably do the data exports needed.

The OEM software is fine, but not as good as Chirp. Any development being done?

I am willing to Loan my uv13 pro or learn how to provide the output with a little coaching.

Hardware loan is hereby offered

I would suggest that you monitor issue #9237. I believe that the Radioddity GM-30 and Baofeng UV-13 Pro and UV-15R are very close cousins. That is what I am doing.

Jim KC9HI

GM13 USES SAME CHASSIS SAM AS RT95, TYT UV88, TIDRADIO H5 (GMRS). NOT SURE IF SOFTWARE IS SAME.
THE UV88 IS MUCH CLOSER TO THE GM30 AND THE RADIODITY RT85 IS DEAD RINGER. BUT THOSE SOFTWARE DOES NOT WORK WITH UV13PRO AS FAR AS I CAN TELL

This software works with UV-13 Pro - http://download.abbree.com/P15UV%20CPS.rar

Still Willing to load Radio or figure out how to extract data from it uv-13 Pro.

William BENHARBONE wrote:

communication between uv13pro and the http://download.abbree.com/P15UV%20CPS.rar software in radiotrace file

Sorry i can't open the link and i am really struggling to find a software to program my uv 13 pro v2, any help?

Jim Winicky wrote in #note-8:

Still Willing to load Radio or figure out how to extract data from it uv-13 Pro.

William BENHARBONE wrote in #note-9:

communication between uv13pro and the http://download.abbree.com/P15UV%20CPS.rar software in radiotrace file

Hi William. I did find 2 programs that allow programming of the radio. I uploaded a zip and rar file of each on my Dropbox. Hopefully this helps everyone when the abree link is down and while we still wait for chirp support.

https://drive.google.com/drive/folders/1FM9Qkyw1hG1hp80oJYLXwrPaqnGLLcS-

Cameron Moyer wrote in #note-13:

Jim Winicky wrote in #note-8:

Still Willing to load Radio or figure out how to extract data from it uv-13 Pro.

William BENHARBONE wrote in #note-9:

communication between uv13pro and the http://download.abbree.com/P15UV%20CPS.rar software in radiotrace file

Hi William. I did find 2 programs that allow programming of the radio. I uploaded a zip and rar file of each on my Google Drive. Hopefully this helps everyone when the abree link is down and while we still wait for chirp support.

https://drive.google.com/drive/folders/1FM9Qkyw1hG1hp80oJYLXwrPaqnGLLcS-

Linking GM-30 related work in https://chirp.danplanet.com/issues/9237

Has anyone been able to get the gm30ctl.py module for the Radioddity GM-30 to work with the UV-13 Pro v2? [[[https://chirp.danplanet.com/attachments/7883]]]

Thanks Aaron P Blankenships :) Big step :)

Freek Wolsink wrote in #note-18:

Thanks @AaronBlankenships :) Big step :)

Aaron Blankenship wrote in #note-17:

Abbree support has provided me with the UV-13 firmware V06.01.013 (attached) to support the TP-8Plus. Firmware can be flashed following the process […]

The GM-30 software refuses to work with my baofeng-branded unit, but I have a working copy of the software labelled P15UV.

• do you know if I can install this firmware on the baofeng UV-13 Pro (and not brick it)?

• Not sure what TP-8Plus is; is a Firmware upgrade likely to improve things for my radio?

• is a firmware upgrade to this binary beneficial

Richard Wonka wrote in #note-20:

• Not sure what TP-8Plus is; is a Firmware upgrade likely to improve things for my radio?

Ah… TP8plus is yet another label for the same thing it seems.

I wonder if a firmware upgrade will be worth it. Guess I’ll find out. For science.

I have the paper manual that came with Baofeng branded HT. On the first page it says that the manual applies to UV-13Pro, TP8, TP8Plus, TP8R, TP8S, TP8X and PT8Pro.

With the latest version of CHIRPNext, this is working if you use the Baofeng UV-17 radio. It reads and writes to the radio.

I was able to connect my uv13-pro v2 using uv-17 in chirp.
From 20240130 version, i can't connect it, appear a message and radio reboot

Okay, I'm not sure if that's what other people are seeing here or not, but your debug log shows what you'd expect from a almost-but-not-quite-the-same model. Chirp is expecting more memory than the radio is sending, which is why it fails.

Were you saying that it worked before the 0130 version? If not, then I think that's expected. If it used to work and doesn't now, then maybe there's something that can be done, but I don't see anything in the history since then that makes me think it could be related.

Dan Smith wrote in #note-28:

Okay, I'm not sure if that's what other people are seeing here or not, but your debug log shows what you'd expect from a almost-but-not-quite-the-same model. Chirp is expecting more memory than the radio is sending, which is why it fails.

Were you saying that it worked before the 0130 version? If not, then I think that's expected. If it used to work and doesn't now, then maybe there's something that can be done, but I don't see anything in the history since then that makes me think it could be related.

Yep, it worked before that version

I will have a look at this. Only difficult thing here is that I don't own this specific radio.

I think what happened here, is that an upload of an image got interrupted. This can cause the memory map of the radio to corrupt. This makes it impossible for Chirp to find the right memory blocks. You can fix this by writing a working image to the radio.

I see someone already posted a default CPS image. Try writing that image to you radio and let me know if you can use Chirp again to read the radio.

Sander van der Wel wrote in #note-33:

I think what happened here, is that an upload of an image got interrupted. This can cause the memory map of the radio to corrupt. This makes it impossible for Chirp to find the right memory blocks. You can fix this by writing a working image to the radio.

I see someone already posted a default CPS image. Try writing that image to you radio and let me know if you can use Chirp again to read the radio.

I can confirm. I just tried.
Writing a previously saved .img file via Chirp to the radio, works.
What happened to me is: I had used chirp to save my frequencies. Then I used the Baofeng program to edit the "character problems", and wrote with that software. From here, if I try to reconnect to the radio with chirp, the message from yesterday appears. So I think it's an incompatibility between one program and another.

I think that means we're interpreting this section incorrectly and probably need to fix something. At the least, I think we should be catching that error and warning the user with a more reasonable error message.

Does this mean we should mark the UV-13 Pro as identical to one of the UV-17 models, or perhaps subclass it so we have room to account for differences later?

I want to try to fix this problem as good as possible. Since bricking my radio just for testing this problem, is not my hobby, I created an emulator that will act like the radio for both CPS and Chirp. :-) Just finished the emulator for the UV17 kind of models. It does look like we can mark the UV-13 Pro as a subclass. But we need some verification by someone who owns the 13 Pro.

Sander, if you want to submit that to tools/ for posterity that's cool. I have an icom simulator that I use locally that I should put in there as well.

Cristofer Fuentealba wrote in #note-39:

I had problems creating a backup copy of my uv-13 pro, the memory was corrupted, I am using the latest version of chirp, does anyone have a backup copy of this device?

Assuming that you downloaded from your radio before making any changes, CHIRP automatically creates a 'backup' of all successful downloads. There should be one of your radio in its original state prior to you making any changes. You can easily access the saved backups by clicking Show image backup location in the Help menu.

Jim Unroe wrote in #note-40:

Cristofer Fuentealba wrote in #note-39:

I had problems creating a backup copy of my uv-13 pro, the memory was corrupted, I am using the latest version of chirp, does anyone have a backup copy of this device?

Assuming that you downloaded from your radio before making any changes, CHIRP automatically creates a 'backup' of all successful downloads. There should be one of your radio in its original state prior to you making any changes. You can easily access the saved backups by clicking Show image backup location in the Help menu.

Dear, it was not possible to use this copy because it is corrupt, thank you very much in advance

Can someone share a backup copy of the Baofeng UV-13 Pro device?

Jim Unroe wrote in #note-44:

Cristofer Fuentealba wrote in #note-42:

Can someone share a backup copy of the Baofeng UV-13 Pro device?

I located my Baofeng UV-13 Pro V1 (still in its factory state) and captured a CHIRP Radio Images (*.img) file it.

Thanks for sharing, the equipment doesn't work, I think it's broken

Jim Unroe wrote in #note-44:

Cristofer Fuentealba wrote in #note-42:

Can someone share a backup copy of the Baofeng UV-13 Pro device?

I located my Baofeng UV-13 Pro V1 (still in its factory state) and captured a CHIRP Radio Images (*.img) file it.

Hi, I used this image on my V2: the device reboot but is unable to read properly the battery nor to change channel (VFO mode, locked to 666.500) nor talk.

Does someone have a Baofeng UV-13 Pro V2 image please?

the same problem here, block vfo 666.500 , no channel, no batery, i had 014 firm upgrde to 013 and the same problem :-(

Bug #11167
There are already several of us with the same problem, I hope someone can help us solve it and not lose the equipment :(

This issue is closed, let's please keep new discussion about this bug on #11167 so it's all in one place. Thanks!