CHIRP

It didn't work, I think the equipment broke, any direct backup of a UV 13 pro device?

Is there any way to do a factory format?

Sander van der Wel wrote in #note-3:

That's weird. I have attached the default image for the UV-13Pro.

Let us know if it helped.

Do know know if this is from a V1 or V2 model?

Jim Unroe wrote in #note-7:

Sander van der Wel wrote in #note-3:

That's weird. I have attached the default image for the UV-13Pro.

Let us know if it helped.

Do know know if this is from a V1 or V2 model?

My device is v2, I had the problem when loading in chirp and it gave me an error, when trying to load the chirp backup it was no longer possible to use the device

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

Sander van der Wel and Jim Unroe this driver had a problem on the first day it was released - should we be removing it from the build until we investigate further?

here the same problem, block to 666.500

Has anyone tried using OEM software to upload a known-working image? There's one in #9793 https://chirp.danplanet.com/attachments/10214 ... That would be my first step towards recovery.

Dan Smith wrote in #note-13:

Has anyone tried using OEM software to upload a known-working image? There's one in #9793 https://chirp.danplanet.com/attachments/10214 ... That would be my first step towards recovery.

I tried it with the software (P15UV CPS) and without results, I also tried to update the firmware with the same software

What does "without results" mean? It wouldn't upload, or it did upload and the radio is still inoperable?

Can you attach the broken image of your radio here so that the people that wrote the driver can have a look? I don't think we've seen that yet and it might provide some clues.

Okay, thanks for the image. Your english is fine, I just wanted to make sure we are clear.

To be honest, if the OEM software uploads a known-good image successfully and the radio is still not operational, that makes me suspect that the problem is some mode or behavior of the radio that could be caused by the OEM software just the same, given the right combination of inputs.

That said, I think we probably need to drop the UV-13Pro support from the public builds ASAP until we get a handle on what the problem is here.

Dan Smith I have no clue what's going on. Also not able to reproduce the problem. So it's probably best to drop support until we figure out what is happening.

I've ordered one for myself so we can properly debug this. Might take a week of two to arrive at my home.

Sander van der Wel wrote in #note-19:

I've ordered one for myself so we can properly debug this. Might take a week of two to arrive at my home.

Which vendor did you order it from? It is a V2? I have a V1 still in its factory state that I bought from the Cutesliving store on AliExpress.

It's a UV-13 Pro V2 from Factory Direct Collected Store. I will dump the rom chip before doing anything with it. This way I can always go back to the original state.

I linked it, but #11174 is another example of this it seems. I put a warning on the download page for the build, but for anyone who has already grabbed it they won't likely see it in time.

Cristofer Fuentealba wrote in #note-23:

I try to clone but those values ​​do not change, I attach an image where I think the error is.
I hope to be helpful

That's interesting...

Ok I just remembered how to dig out the firmware versions. Hold bottom function button while turning on radio. Doh.

The UV-13 pro V1 is V06.01,014
The UV-13 pro V2 is V06.01.013

I did purchase the V1 almost a year after I purchased the V2s which I bought roughly just as people on the internet started talking about this radio. At that time those who were posting Youtube videos were actually reviewing the V1 version and I happened to get the V2.

Kevin Omura wrote in #note-28:

Ok I just remembered how to dig out the firmware versions. Hold bottom function button while turning on radio. Doh.

The UV-13 pro V1 is V06.01,014
The UV-13 pro V2 is V06.01.013

I did purchase the V1 almost a year after I purchased the V2s which I bought roughly just as people on the internet started talking about this radio. At that time those who were posting Youtube videos were actually reviewing the V1 version and I happened to get the V2.

Do you have the CPS software for both radios? You could help by providing a backup of both (working) radios made with cps.

Kevin Omura wrote in #note-30:

Hi, yes just created them. Is this what you are after? If not let me know.

Is the V2 data from a radio without problems?

Sander van der Wel wrote in #note-31:

Kevin Omura wrote in #note-30:

Hi, yes just created them. Is this what you are after? If not let me know.

Is the V2 data from a radio without problems?

No, neither of my V2 radios will connect to CHIRP without the corrupt memory error.

Only the V1 radio will connect to CHIRP without errors with the UV-13Pro, UV17 and UV17 Pro GPS settings.

On the FB group that John moderates someone I have been chatting with has a UV-13Pro V1 with the same V06.01.014 firmware and it is also coming back with the corrupt memory error.

Kevin Omura wrote in #note-32:

Sander van der Wel wrote in #note-31:

Kevin Omura wrote in #note-30:

Hi, yes just created them. Is this what you are after? If not let me know.

Is the V2 data from a radio without problems?

No, neither of my V2 radios will connect to CHIRP without the corrupt memory error.

Only the V1 radio will connect to CHIRP without errors with the UV-13Pro, UV17. The UV17Pro and UV17Pro GPS settings come back with 'Error reading data from radio: not amount of data we want" which is the same error message I was getting with previous versions that worked on the UV17 setting.

On the FB group that John moderates someone I have been chatting with has a UV-13Pro V1 with the same V06.01.014 firmware and it is also coming back with the corrupt memory error.

That is weird, the V1 has a firmware version newer than the V2?!?

Since my UV-13Pro (sold as a V2) has the V06.01.014 firmware (so it is a V1??) I have pushed successfully the UV13Pro_V1_working.data but the device is still locked to 666.55 ==> not really a success!

Do you think it can be useful to update the firmware with the V06.01.013?

Kevin Omura wrote in #note-35:

Rot Ulet wrote in #note-34:

That is weird, the V1 has a firmware version newer than the V2?!?

Since my UV-13Pro (sold as a V2) has the V06.01.014 firmware (so it is a V1??) I have pushed successfully the UV13Pro_V1_working.data but the device is still locked to 666.55 ==> not really a success!

Do you think it can be useful to update the firmware with the V06.01.013?

Yes what I was calling my V2 with the SMA-F antenna connector has older firmware then my V1 with the SMA-M connector. And now to add more confusion to the mix. I have been chatting with another UV-13pro owner on FB who has a UV-13Pro that has V2 on his label and with the SMA-M connector and a dot with V2.

I had assumed both of what I called V2 radios with the SMA-F antennas were different but I did not know until today about the dot on the label which indicates version. We had assumed that the V1 radios were SMA-M connectors and my SMA-F radios were an updated version. But I just checked and one of what I had thought was a V2 radio has a white ball with V1 noted. This is the label on the far right, the centre radio with no sticker we also called a V2 radio since it was also an SMA-F connector.

The radio on the far left is the V1 which has the newer V06.01.14 firmware and was purchased Sept 2023. The two 'V2' radios I purchased in June of 2022.

Rot Ulet wrote in #note-38:

FYI mine has got a SMA-M connector. V2.

I have a V1 (written in a small white dot, behind the battery).
Antenna connector on the body of the radio is SMA-M.
Firmware version: V06.01.014

Where can be found the V06.01.014 firmware (to force flash it)? I can not find it anywhere, even the V06.01.013 is not on the baofeng website!

Does anyone know if there is an opensource firmware for this device?
Has anyone tried this https://whosmatt.github.io/uvmod/index.html?

those MODs is only for Quansheng, i so interesting in Firm 014 for UV13

Rot Ulet wrote in #note-40:

Where can be found the V06.01.014 firmware (to force flash it)? I can not find it anywhere, even the V06.01.013 is not on the baofeng website!

Does anyone know if there is an opensource firmware for this device?
Has anyone tried this https://whosmatt.github.io/uvmod/index.html?

Good queston. I just read the link on github but uvmod as James states is only for the Quansheng and other UV-K series radios.

I did find a link to opengd77 however I'm not sure if that will work with the UV-13. One quick question Rot, did you try a factory reset? Granted I can't find any hints as to how to do it. Tried the standard button configuration on my UV-13 as well as both top and button + pwr, top + pwr, bottom + menu + pwr and nothing pops up on screen saying 'factory'.

If anyone out there knows of the proper way to dump the firmware from a UV-13 and what software is required I'd be happy to dump both my working and non working with CHIRP radios for analysis. Also willing to sacrifice my unlabeled UV-13 in the quest for knowledge....

Rot Ulet wrote in #note-40:

Where can be found the V06.01.014 firmware (to force flash it)? I can not find it anywhere, even the V06.01.013 is not on the baofeng website!

Does anyone know if there is an opensource firmware for this device?
Has anyone tried this https://whosmatt.github.io/uvmod/index.html?

Hi, was just going back through the files uploaded to this thread and was reading the CHIRP debug log, so somehow the "Baofeng_UV-13Pro_20240214.img" file was deleted? Sorry I am going to ask some newbie questions as I've never put my copies of CHIRP into Developer mode. I did go into my drive to see if I had a copy of this file by following your path. "Program Files (x86)\CHIRP\Baofeng_UV-13Pro_20240214.img" but not there. Is this something I can dump from my working UV-13pro for you in developer mode? If so if you can give me a quick walk through I can try and dump it.

Kevin Omura wrote in #note-42:

I did find a link to opengd77 however I'm not sure if that will work with the UV-13. One quick question Rot, did you try a factory reset? Granted I can't find any hints as to how to do it. Tried the standard button configuration on my UV-13 as well as both top and button + pwr, top + pwr, bottom + menu + pwr and nothing pops up on screen saying 'factory'.

In the menu, the last entry is for reset but it is not (maybe) a real reset!

If anyone out there knows of the proper way to dump the firmware from a UV-13 and what software is required I'd be happy to dump both my working and non working with CHIRP radios for analysis. Also willing to sacrifice my unlabeled UV-13 in the quest for knowledge....

I am close to try to flash with the GM30 firmware (https://www.radioddity.com/pages/radioddity-download#FeaturedImage-6c76fd3b-f77a-40fd-b30f-fb5c88203521) but I still hoping to retrieve a valid 06.01.014 firmware from this forum...

FYI, just downloading the new version of chirp-next-20240216, which has the UV-13Pro option removed.

I did however run my UV-13pros with the UV17 basic setup which has worked for my V1 previously.

The UV-13pro (old "V2") running the V06.01.13 firmware still generates the "Error communicating with radio Radio memory is corrupted. Fix this by uploading a backup image to the radio".

The V1 radio running V06.01.14 firmware runs and populated the spreadsheet but again without the gaps I leave between memory slots.

Looks like they just removed the UV-13pro option.

The UV-13 had to be removed for now.

We are trying to figure out exactly what the problem is. And we are trying to fix it.

I ordered a UV-13Pro V2 to do this. It’s been sent, but it might take a couple of days.

It might help to get a precise description of the problem, like:

• what is the exact behavior of the radio when the VFO problem occurs?
• is the radio still useable?
• can you still communicate with it through CPS software or CHIRP?
• what happens if you upload a backup with CPS?
• I could provide one of you with a driver that gives me some more debug information

Rot Ulet wrote in #note-44:

Kevin Omura wrote in #note-42:

I did find a link to opengd77 however I'm not sure if that will work with the UV-13. One quick question Rot, did you try a factory reset? Granted I can't find any hints as to how to do it. Tried the standard button configuration on my UV-13 as well as both top and button + pwr, top + pwr, bottom + menu + pwr and nothing pops up on screen saying 'factory'.

In the menu, the last entry is for reset but it is not (maybe) a real reset!

Hi, I think that just resets some of the user configured things such as squelch and display. What I think of with a factory reset is the radio reloading firmware stored in rom. The way you factory reset a cell phone which wipes everything and reloads the original factory configuration.

If anyone out there knows of the proper way to dump the firmware from a UV-13 and what software is required I'd be happy to dump both my working and non working with CHIRP radios for analysis. Also willing to sacrifice my unlabeled UV-13 in the quest for knowledge....

I am close to try to flash with the GM30 firmware (https://www.radioddity.com/pages/radioddity-download#FeaturedImage-6c76fd3b-f77a-40fd-b30f-fb5c88203521) but I still hoping to retrieve a valid 06.01.014 firmware from this forum...

I looked at that link, the GM30 is a GMRS radio though. Would that make a difference?

Kevin Omura wrote in #note-48:

Rot Ulet wrote in #note-44:

Kevin Omura wrote in #note-42:

I did find a link to opengd77 however I'm not sure if that will work with the UV-13. One quick question Rot, did you try a factory reset? Granted I can't find any hints as to how to do it. Tried the standard button configuration on my UV-13 as well as both top and button + pwr, top + pwr, bottom + menu + pwr and nothing pops up on screen saying 'factory'.

In the menu, the last entry is for reset but it is not (maybe) a real reset!

Hi, I think that just resets some of the user configured things such as squelch and display. What I think of with a factory reset is the radio reloading firmware stored in rom. The way you factory reset a cell phone which wipes everything and reloads the original factory configuration.

If anyone out there knows of the proper way to dump the firmware from a UV-13 and what software is required I'd be happy to dump both my working and non working with CHIRP radios for analysis. Also willing to sacrifice my unlabeled UV-13 in the quest for knowledge....

I am close to try to flash with the GM30 firmware (https://www.radioddity.com/pages/radioddity-download#FeaturedImage-6c76fd3b-f77a-40fd-b30f-fb5c88203521) but I still hoping to retrieve a valid 06.01.014 firmware from this forum...

I looked at that link, the GM30 is a GMRS radio though. Would that make a difference?

I loaded the GM-30 firmware and the problem continues

Sander van der Wel wrote in #note-47:

The UV-13 had to be removed for now.

We are trying to figure out exactly what the problem is. And we are trying to fix it.

I ordered a UV-13Pro V2 to do this. It’s been sent, but it might take a couple of days.

It might help to get a precise description of the problem, like:

• what is the exact behavior of the radio when the VFO problem occurs?
• is the radio still useable?
• can you still communicate with it through CPS software or CHIRP?
• what happens if you upload a backup with CPS?
• I could provide one of you with a driver that gives me some more debug information

Hi Sander, thanks for the update!

I have not encountered the VFO issue, out of curiousity I put both radios into VFO mode and attempted to enter 666.500 which both radios rejected. Was the radio that failed with that entry running a modified firmware as my radios are running the stock firmware and neither allow me to enter that frequency.

The only issue I have had is with the older firmware version of the UV-13 with older V06.01.13 firmware. When connecting and attempting to download the radio I get the "Error communicating with radio Radio memory is corrupted. Fix this by uploading a backup image to the radio" message. I power off radio and unhook it, then power back on and everything seems to be running normally.

On the newer V1 UV-13 with the V06.01.14 firmware when I go to download the radio it works normally and populates the frequency spreadsheet. However what I do notice and this also happened with previous versions of CHIRP that I used with the UV-17 basic module is that any gaps I had between memory locations where removed and it did not appear to be any way to access them. That concerned me in that I wondered if by uploading this table back into my radio it could create a problem. With all my other radios any time I leave a gap eg leave memory location 100-110 blank the spreadsheet leaves those slots open and they can then be populated. However with every build of CHIRP that actually communicated with my working UV-13 Pro the table would always remove the blank rows so would only show 99-111 with no blank spots in between.

Because of that I don't recall ever uploading any spreadsheets modified in CHIRP back to my working radio as I was concerned that this could cause a problem with its internal memory.

If you like I can try your driver in the hope that we can pull more data on the issue.

Sander van der Wel wrote in #note-47:

The UV-13 had to be removed for now.

We are trying to figure out exactly what the problem is. And we are trying to fix it.

I ordered a UV-13Pro V2 to do this. It’s been sent, but it might take a couple of days.

It might help to get a precise description of the problem, like:

• what is the exact behavior of the radio when the VFO problem occurs?
• is the radio still useable?
• can you still communicate with it through CPS software or CHIRP?
• what happens if you upload a backup with CPS?
• I could provide one of you with a driver that gives me some more debug information

Hi, I have uv-13 pro V1 and I was flashed V06.01.13 without any problem (when I bought, its version was V06.01.14). There was no visual or functional change. I was using it with chirp by selecting uv-17. But with the latest version of chirp-next, I selected uv-13 pro and it blocked on 666.500 and vfo mode.

I did almost everything, I flashed original firmware, flashed gm-30 firmware, reset on the menu, loaded old recoveries, factory image files with older versions of chirp and with OEM CPS software. I did theese with mac and pc. Nothing changed.

The radio is still usable. It can communicate with oem cps and chirp. The menu is working, fm broadcast and flashlight completely working. Also I tried to change vfo A and vfo B frequencies with oem cps software and 666.500mhz not changed but ctcss, offset, and hi-low power setting has changed. I think it is not dead.

But the radio is not transmitting, shows battery is empty. I can’t change frequency. When I try changing to memory mode it says “no channel”.

When I upload a backup with chirp or cps nothing changes.

Sander van der Wel wrote in #note-47:

The UV-13 had to be removed for now.

We are trying to figure out exactly what the problem is. And we are trying to fix it.

I ordered a UV-13Pro V2 to do this. It’s been sent, but it might take a couple of days.

It might help to get a precise description of the problem, like:

• what is the exact behavior of the radio when the VFO problem occurs?
• is the radio still useable?
• can you still communicate with it through CPS software or CHIRP?
• what happens if you upload a backup with CPS?
• I could provide one of you with a driver that gives me some more debug information

Can the radio still be used?
The UV 13 Pro v2 equipment can no longer be used, the FM frequencies do work.
Can you still contact him through CPS or CHIRP software? Yeah.
What happens if you upload a backup with CPS? They charge normally but the device continues on the frequency 666.50000 and without recognizing the battery. Is it possible to load a security image from another computer with similar characteristics to chirp?

Turna Tarik wrote in #note-51:

Hi, I have uv-13 pro V1 and I was flashed V06.01.13 without any problem (when I bought, its version was V06.01.14). There was no visual or functional change. I was using it with chirp by selecting uv-17. But with the latest version of chirp-next, I selected uv-13 pro and it blocked on 666.500 and vfo mode.

Are you saying that your radio was working in chirp before version 20240213 but on/after that, the problem showed up? If so, I wonder if b7b16848 actually broke something? I'd also wonder if using the version before that (20240211) would allow restoring something given a known-good image?

Turna Tarik wrote in #note-51:

Hi, I have uv-13 pro V1 and I was flashed V06.01.13 without any problem (when I bought, its version was V06.01.14). There was no visual or functional change. I was using it with chirp by selecting uv-17. But with the latest version of chirp-next, I selected uv-13 pro and it blocked on 666.500 and vfo mode.

I did almost everything, I flashed original firmware, flashed gm-30 firmware, reset on the menu, loaded old recoveries, factory image files with older versions of chirp and with OEM CPS software. I did theese with mac and pc. Nothing changed.

The radio is still usable. It can communicate with oem cps and chirp. The menu is working, fm broadcast and flashlight completely working. Also I tried to change vfo A and vfo B frequencies with oem cps software and 666.500mhz not changed but ctcss, offset, and hi-low power setting has changed. I think it is not dead.

But the radio is not transmitting, shows battery is empty. I can’t change frequency. When I try changing to memory mode it says “no channel”.

When I upload a backup with chirp or cps nothing changes.

I have exactly the same behavior but I did not try to flash any other firmwares. Sometime when I launch a scan it changes the channel to 000.00 (even a 143.xx) but it does not receive anything and if a touch any button the 666.50 came back. I also try to set the frequency via CPS for VFOA and VFOB: after the upload the frequencies are displayed but not usable and if a touch any button the 666.50 came back.

Dan Smith wrote in #note-53:

Turna Tarik wrote in #note-51:

Hi, I have uv-13 pro V1 and I was flashed V06.01.13 without any problem (when I bought, its version was V06.01.14). There was no visual or functional change. I was using it with chirp by selecting uv-17. But with the latest version of chirp-next, I selected uv-13 pro and it blocked on 666.500 and vfo mode.

Are you saying that your radio was working in chirp before version 20240213 but on/after that, the problem showed up? If so, I wonder if b7b16848 actually broke something? I'd also wonder if using the version before that (20240211) would allow restoring something given a known-good image?

Yes, I was using chirp before version 20240213 without any problem by selecting uv-17. I used older versions with pc and mac, there was no problem.

I tried older versions of chirp and restored with known good images but this didn’t solve the problem. Nothing changed.

Yes, I was using chirp before version 20240213 without any problem by selecting uv-17. I used older versions with pc and mac, there was no problem.

I tried older versions of chirp and restored with known good images but this didn’t solve the problem. Nothing changed.

Okay, bummer that it didn't solve the problem, but that information may help lead to the issue. Sounds like perhaps reverting that change may also be prudent. Sander van der Wel?

I think we need to be really careful with that "full backup" driver. If I'm reading it correctly, it will also store the full backup in the .img. If you then try to use upload with that (or even regular chirp but with an image captured with that), it will write the wrong chunks of data to the indexed blocks, right?

Dan Smith wrote in #note-58:

I think we need to be really careful with that "full backup" driver. If I'm reading it correctly, it will also store the full backup in the .img. If you then try to use upload with that (or even regular chirp but with an image captured with that), it will write the wrong chunks of data to the indexed blocks, right?

Ehm... it will store the data in the file. Raises an error that the backup was made. And it will never return the data to the rest of CHIRP. (or am I missing something?) We can remove this after someone grabs the full backups.

Ah, yep, okay I didn't see that, good. Also that you changed the model so it won't create an image that would be loadable with the regular driver.

So, yep, seems okay, we just need to be cautious of such things, but glad you were already thinking that :)

Dan Smith wrote in #note-56:

Okay, bummer that it didn't solve the problem, but that information may help lead to the issue. Sounds like perhaps reverting that change may also be prudent. Sander van der Wel?

Better be safe than sorry and revert the change.

Hi Sander attached is the file from the 'working' UV-13Pro. I say 'working' because it just gave me the corrupt memory error for the first time. I had some problems trying to attach a file called Dump Stack as it would not allow me to attach it even though the account I'm using has admin access on this laptop. I opened the text file and pasted it to the file attached. This is the .01.014 firmware.

Am about to run the UV-13Pro that originally did not work. Running the older firmware.

Can you send the backup.bin file?

Kevin Omura wrote in #note-64:

Ok try this, it's showing that it's a Firefox document so not sure if it is correct but time stamp is. This will be from the non working UV-13Pro with FW .01.013

Yes!! that's what I need. :-)

Sander van der Wel wrote in #note-65:

Kevin Omura wrote in #note-64:

Ok try this, it's showing that it's a Firefox document so not sure if it is correct but time stamp is. This will be from the non working UV-13Pro with FW .01.013

Yes!! that's what I need. :-)

Ok working on the V1 radio again. Just crashed out CHIRP and have to restart and reload. Or did that file contain both radios?

Kevin Omura wrote in #note-66:

Ok working on the V1 radio again. Just crashed out CHIRP and have to restart and reload. Or did that file contain both radios?

No that file only contains 1 radio. Just delete the file and do it again with the other radio. That way you're certain that the new file is from the other radio.

Kevin Omura wrote in #note-68:

Ok, this should hopefully be the backup for the V1 radio that was working. This is the UV-13Pro with the V06.06.014 and black dot with V1 on the blue label.

Thank you!! I looks like the first one you sent is working and the second one is not working... But anyways.. I have a working and a non working backup now. :-) Time to do some investigation.

Sander van der Wel wrote in #note-69:

Kevin Omura wrote in #note-68:

Ok, this should hopefully be the backup for the V1 radio that was working. This is the UV-13Pro with the V06.06.014 and black dot with V1 on the blue label.

Thank you!! I looks like the first one you sent is working and the second one is not working... But anyways.. I have a working and a non working backup now. :-) Time to do some investigation.

Ok thanks! If you need me to rerun the V1 radio let me know and I will try it again. Fingers crossed that you can find the problem.

Kevin Omura wrote in #note-70:

Ok thanks! If you need me to rerun the V1 radio let me know and I will try it again. Fingers crossed that you can find the problem.

I do see a clear difference between the backups. One does indeed work properly with CHIRP, the other one gives the error. So that's great!! Just to be sure, your radios are working just fine?

Sander van der Wel wrote in #note-71:

Kevin Omura wrote in #note-70:

Ok thanks! If you need me to rerun the V1 radio let me know and I will try it again. Fingers crossed that you can find the problem.

I do see a clear difference between the backups. One does indeed work properly with CHIRP, the other one gives the error. So that's great!! Just to be sure, your radios are working just fine?

Hi Sander, yes the radios are working just fine. I did test VFO mode and even attempted to imput 666.500 which the radios rejected (both versions) but other non restricted frequencies will load fine. I never did upload any data to my working radio though, just did the downloads and backups.

One interesting note, I did download the latest version of CHIRP which replaced the version with the UV-13Pro module. Then when you asked for the backups I decided to uninstall that version and reinstall the UV-13Pro version figuring it would give the most useful results.

After doing this my V1 radio now gives me the corrupt memory error message. Radio still works just fine, no corruption of memories that I can find and no settings changed. Tested transmit and it is fine as well. The most odd thing is that I never uploaded anything to this radio. Only downloads so I find that very odd since nothing should have been changed or modified. I do have several 'clean' laptops that I can install the 'bad' version of CHIRP onto or can hold them back in case you need me to do more testing with a clean install on a Windows machine that has never had CHIRP installed.

I do have another laptop running Windows 10 that I can test, just thought of it now in case this is some weird quirk with Windows.

Granted the problem seems to be with different samples of the UV-13 Pro, I wonder if this is a hardware issue since what I initially called V1 (has the V1 ball on label) has the SMA-M connector and V06.01.014 FW.

The two UV-13 Pros that always failed connections were what I had called V2 after chatting with Jason have SMA-F antenna connections which could potentially mean a different main board or slightly different chips? It also has the older V06.01.013 FW.

Sorry to be so long winded, just hoping that something I said might be a clue to why this is so problematic. Good luck and thanks for looking into this!

And being curious I just ordered another UV-13 Pro from Banggood which is supposed to be a V2 from the seller I purchased the working radio from, though my ad showed the radio as a V1, so will be interesting to see what FW and what antenna connection this V2 radio has.

https://www.banggood.com/BaoFeng-UV-13-PRO-V2-Powerful-Dual-Band-Walkie-Talkie-Type-C-Charger-16KM-Long-Range-UV13-Pro-Transceiver-Ham-Two-Way-Radio-p-1986558.html?rmmds=myorder&cur_warehouse=CN&ID=223

More full backup images are welcome!!

Dimk Dimk wrote in #note-75:

Let me know if I can provide any more information that will help to solve the problem.

Would you be able to make a full backup with the backup driver discussed earlier?

I am also looking for a full backup of an untouched V2?

Would you be able to make a full backup with the backup driver discussed earlier?
could you please explain how I can add uv17fullbackup.py driver to Chirp application?

I am also looking for a full backup of an untouched V2?
another UV13PRO V2 with factory defaults on the way to me, will do backups next days

Dimk Dimk wrote in #note-77:

Would you be able to make a full backup with the backup driver discussed earlier?
could you please explain how I can add uv17fullbackup.py driver to Chirp application?

You can load it via the file->load module in CHIRP

Dimk Dimk wrote in #note-79:

Thanks for help! Backup finished with curious error message (pic attached)

That error message is supposed to be there. :-) Thank you!!

Sander van der Wel wrote in #note-81:

Sander van der Wel wrote in #note-80:

Dimk Dimk wrote in #note-79:

Thanks for help! Backup finished with curious error message (pic attached)

That error message is supposed to be there. :-) Thank you!!

Dimk Dimk wrote in #note-79:

Sander van der Wel wrote in #note-78:

Dimk Dimk wrote in #note-77:

Would you be able to make a full backup with the backup driver discussed earlier?
could you please explain how I can add uv17fullbackup.py driver to Chirp application?

You can load it via the file->load module in CHIRP

Thanks for help! Backup finished with curious error message (pic attached)

I have written a possible repair for a broken radio. Since I don't own a broken radio, is there someone who is willing to try it? This is completely at your own risk...

See the attached module.

My v13-pro v2 is working! I am running tests in case some errors persist. many thanks for everything

repair test.py working fine !! thanks :-)

Cristofer Fuentealba wrote in #note-82:

Sander van der Wel wrote in #note-81:

Sander van der Wel wrote in #note-80:

Dimk Dimk wrote in #note-79:

Thanks for help! Backup finished with curious error message (pic attached)

That error message is supposed to be there. :-) Thank you!!

Dimk Dimk wrote in #note-79:

Sander van der Wel wrote in #note-78:

Dimk Dimk wrote in #note-77:

Would you be able to make a full backup with the backup driver discussed earlier?
could you please explain how I can add uv17fullbackup.py driver to Chirp application?

You can load it via the file->load module in CHIRP

Thanks for help! Backup finished with curious error message (pic attached)

I have written a possible repair for a broken radio. Since I don't own a broken radio, is there someone who is willing to try it? This is completely at your own risk...

See the attached module.

My v13-pro v2 is working! I am running tests in case some errors persist. many thanks for everything

It works like a charm, radio is completely functional now! Many thanks!

Awesome progress everyone. Major kudos to Sander van der Wel for fixing the issue, but lots of thanks to all the users here providing reports, backups, feedback, testing, and of course, patience!

Dan Smith wrote in #note-85:

Awesome progress everyone. Major kudos to Sander van der Wel for fixing the issue, but lots of thanks to all the users here providing reports, backups, feedback, testing, and of course, patience!

+1

Great news! I am eager to test it as soon I will be back from holiday!

Dan Smith wrote in #note-85:

Awesome progress everyone. Major kudos to Sander van der Wel for fixing the issue, but lots of thanks to all the users here providing reports, backups, feedback, testing, and of course, patience!

Yes, excellent news!

What version of chirp do you use to load the Uv13repairTest.py? With the latest version, I load the file with the help->load module from chirp issue, the module successfully but when I try to read from the radio with the module 'UV-13RepairTest', I obtain the follwing error:

[2024-02-18 09:49:52,024] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM5', 'name': 'COM5', 'description': 'Lien série sur Bluetooth standard (COM5)', 'hwid': 'BTHENUM\\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\\7&28448827&2&000000000000_00000000', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM6', 'name': 'COM6', 'description': 'Lien série sur Bluetooth standard (COM6)', 'hwid': 'BTHENUM\\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0002\\7&28448827&2&FC58FACBCCA6_C00000000', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': 'Microsoft', 'product': None, 'interface': None}, {'device': 'COM7', 'name': 'COM7', 'description': 'USB-SERIAL CH340 (COM7)', 'hwid': 'USB VID:PID=1A86:7523 SER= LOCATION=1-3', 'vid': 6790, 'pid': 29987, 'serial_number': '', 'location': '1-3', 'manufacturer': 'wch.cn', 'product': None, 'interface': None}]
[2024-02-18 09:50:27,425] chirp.wxui.clone - DEBUG: Using port 'COM7'
[2024-02-18 09:50:27,425] chirp.wxui.clone - DEBUG: Selected <class 'chirp.loaded.loaded-10649-__6odgjs.UV13RepairTest'>
[2024-02-18 09:50:27,441] chirp.wxui.clone - DEBUG: Prompt pre_download disabled for radio
[2024-02-18 09:50:27,441] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x16e21c53e20, open=True>(port='COM7', baudrate=57600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2024-02-18 09:50:29,063] chirp.wxui.clone - ERROR: Failed to clone: Error reading data from radio: not the amount of data we want.
Traceback (most recent call last):
  File "chirp\wxui\clone.py", line 75, in run
  File "chirp\drivers\baofeng_uv17Pro.py", line 1016, in sync_in
  File "C:\Users\gaetan\AppData\Local\Temp\loaded-10649-__6odgjs.py", line 60, in _download
    _start_communication(radio)
  File "C:\Users\gaetan\AppData\Local\Temp\loaded-10649-__6odgjs.py", line 194, in _start_communication
    _sendmagic(radio, magic[0], magic[1])
  File "C:\Users\gaetan\AppData\Local\Temp\loaded-10649-__6odgjs.py", line 38, in _sendmagic
    baofeng_common._rawrecv(radio, response_len)
  File "chirp\drivers\baofeng_common.py", line 55, in _rawrecv
chirp.errors.RadioError: Error reading data from radio: not the amount of data we want.
[2024-02-18 09:50:36,326] chirp.wxui.clone - WARNING: Stopping clone thread

Can you detail me the whole process please?

Rot Ulet wrote in #note-89:

Can you detail me the whole process please?

I think you are right. I just tested it. It doesn't work with the latest version of chirp. But it does work with the 20240216 version.

Easiest way to use the module is to use the "Load Module from issue", functionality in "help". I'll see if I can figure out what happened in between version 20240216 and 20240217.

I have succeed in apply the repair script (20240217repairTest.py) to the radio with the chirp next-20240217. The radio reboot fine but I can not receive any sound.

I tried with the FM mode: the radio can scan for FM frequencies and stop on 'good' station but no sound.

I switch to VFO mode on 446.00625 frequency PMR 1 with another radio emitting on this same frequency: no sound but the radio show that something is received (antenna symbol with full bars). I have disabled CTCSS (still no sound) and also try a scan (menu 31 on this radio): the scan stop on the good CTCSS but no sound even if the radio show the antenna symbol with full bars.

Any ideas?

Rot Ulet wrote in #note-95:

I have succeed in apply the repair script (20240217repairTest.py) to the radio with the chirp next-20240217. The radio reboot fine but I can not receive any sound.

I tried with the FM mode: the radio can scan for FM frequencies and stop on 'good' station but no sound.

I switch to VFO mode on 446.00625 frequency PMR 1 with another radio emitting on this same frequency: no sound but the radio show that something is received (antenna symbol with full bars). I have disabled CTCSS (still no sound) and also try a scan (menu 31 on this radio): the scan stop on the good CTCSS but no sound even if the radio show the antenna symbol with full bars.

Any ideas?

My bad! The radio can emit sound when the usb cable is still connected!!! I unplugged the radio and make successful tries!!

Many thanks to the CHIRP team!

My bad! The radio can emit sound when the usb cable is still connected!!! I unplugged the radio and make successful tries!!

I was about to ask if you had removed the cable after programming. I have done this myself many many times :)

Ok. I've tried Repair module, and all come back. If i try to load again "my list", it switches to 666.50000 freq. So i've "repair" it again

Daniel Personale wrote in #note-98:

Ok. I've tried Repair module, and all come back. If i try to load again "my list", it switches to 666.50000 freq. So i've "repair" it again

I am not sure if I understand you right. Does the radio get repaired by the repair module? And then if you try to use chirp again for your radio, the problem comes back?

Daniel Personale Are you using the most recent release? Your debug log from the other bug you opened shows you're running 0213. You'll need to upgrade to the latest to fix the problem and prevent it from happening again.

Sander van der Wel wrote in #note-99:

Daniel Personale wrote in #note-98:

Ok. I've tried Repair module, and all come back. If i try to load again "my list", it switches to 666.50000 freq. So i've "repair" it again

I am not sure if I understand you right. Does the radio get repaired by the repair module? And then if you try to use chirp again for your radio, the problem comes back?

Exactly. The problem comes back if i write the memory again after repair.

Daniel Personale wrote in #note-102:

Exactly. The problem comes back if i write the memory again after repair.

I think you are using an old version of CHIRP. Which version are you using? In te last version, we removed support for the UV13Pro. Because of the problems.

Although I do think it might still work when you choose the UV17.

Sander van der Wel wrote in #note-103:

Daniel Personale wrote in #note-102:

Exactly. The problem comes back if i write the memory again after repair.

I think you are using an old version of CHIRP. Which version are you using? In te last version, we removed support for the UV13Pro. Because of the problems.

Although I do think it might still work when you choose the UV17.

The latest version of next 20240220 seems to have fixed the compressed memory slots that I found on all previous versions of CHIRP Next when using the UV-17 module. Therefore I wonder if this might solve the memory corruption issue.

The only downside is that only my V06.01.013 FW radios work while the V06.01.014 radio errors out when connecting. I also have a V2 radio on order from Banggood that shows leaving China for Canada today so maybe by next week I will have it to test and see what version of firmware it has.

Kevin Omura Thanks. I am going to have a look at them and see if I can identify the problem, and maybe write a driver to fix it. I also received a UV13Pro V2 myself today for some proper testing.

Kevin Omura The compressed channels is a setting in CHIRP, under View -> "hide empty memories". I think your problem with the radio that refuses to read, might be gone if you overwrite it with a backup from your other radio.

Kevin Omura I noticed the same behaviour with my radio. While trying to figure out the problem, I downloaded the contents of the radio with the CPS software. And now I cannot trigger the problem anymore, radio seems to work just fine.

Edit: managed to get the problem back by switching between VFO and channel mode. :-)

Sander van der Wel wrote in #note-110:

Kevin Omura I noticed the same behaviour with my radio. While trying to figure out the problem, I downloaded the contents of the radio with the CPS software. And now I cannot trigger the problem anymore, radio seems to work just fine.

Edit: managed to get the problem back by switching between VFO and channel mode. :-)

Interesting, I tried uploading the backup file I downloaded from the working UV-13 to the error UV-13 using P15UV CPS just now. Get the same communication error when trying to download from CHIRP. But if I upload the working CHIRP file and then immediately go to download from radio the radio will not generate the error. Unplug it and plug it back in and the error returns. I can live with this work around. Now really curious how the V2 radio works and what firmware it has.

Kevin Omura wrote in #note-106:

Sander van der Wel wrote in #note-103:

Daniel Personale wrote in #note-102:

Exactly. The problem comes back if i write the memory again after repair.

I think you are using an old version of CHIRP. Which version are you using? In te last version, we removed support for the UV13Pro. Because of the problems.

Although I do think it might still work when you choose the UV17.

The latest version of next 20240220 seems to have fixed the compressed memory slots that I found on all previous versions of CHIRP Next when using the UV-17 module. Therefore I wonder if this might solve the memory corruption issue.

The only downside is that only my V06.01.013 FW radios work while the V06.01.014 radio errors out when connecting. I also have a V2 radio on order from Banggood that shows leaving China for Canada today so maybe by next week I will have it to test and see what version of firmware it has.

I've tried now using the last version of Chirp using UV17 module. My is 13ProV2 with 013 firmware. When i try to read from radio: "Unexpected error communicating with radio".
Now i try with a clean img file.

Out of curiosity I went back to an older installation of CHIRP next on a laptop that I have not updated to later versions. I then tried downloading before uploading from the V06.01.013 and the V06.01.014 radios. Both worked perfectly. This was CHIRP next-20240122 on Python 3.10.8 wxPython 4.2.0 msw (phoenix) wxWidgets 3.2.0

Checked VFO mode and it works fine, then reattached radios to CHIRP and read from radio still works without errors.

I have several laptops I use for testing so I will leave that laptop untouched and back at that version of CHIRP.

I have found the cause of the problem.

The UV13Pro has more memory available for configuration than the UV17, so sometimes things get stored in a location where the UV17 driver never looks for data. I am working on an update.

Sander van der Wel wrote in #note-115:

I have found the cause of the problem.

The UV13Pro has more memory available for configuration than the UV17, so sometimes things get stored in a location where the UV17 driver never looks for data. I am working on an update.

Amazing. Ty

Sander van der Wel wrote in #note-117:

I have attached a new version of the driver. This driver should properly support the UV13Pro (and probably other related models too).

It would be appreciated if some of you can test this driver before I submit it to be integrated into CHIRP.

Please try this module with these instructions: LoadingTestModulesJU

Hi Sandor, just to verify I loaded this new driver and get the 'Error reading data from radio not the amount of data we want'.

The module shows up in CHIRP as UV-13Pro under model, checked to make sure it was the correct module as your file is tagged as baofeng_uv17.py. This is with the UV13 with FW V.06.01.013. Also of note when it errors out the radio stays stuck on Program.... on display. Shutting down this radio and unplugging from the computer restores radio to working condition. Tested VFO mode and it is working, TX working, etc.

Also connected the UV-13 with V06.01.014 FW with identical error and radio display stays locked on Program.... turning off the radio restores it to working condition.

Let me know if I should try anything else.

Thanks!

I tried it on a factory reset UV 13 Pro v2. In the high preset numbers (I tried 400-404) instead of showing black blocks, some of the preset names are truncated.

Kevin Omura wrote in #note-118:

Hi Sandor, just to verify I loaded this new driver and get the 'Error reading data from radio not the amount of data we want'.

The module shows up in CHIRP as UV-13Pro under model, checked to make sure it was the correct module as your file is tagged as baofeng_uv17.py. This is with the UV13 with FW V.06.01.013. Also of note when it errors out the radio stays stuck on Program.... on display. Shutting down this radio and unplugging from the computer restores radio to working condition. Tested VFO mode and it is working, TX working, etc.

Also connected the UV-13 with V06.01.014 FW with identical error and radio display stays locked on Program.... turning off the radio restores it to working condition.

Let me know if I should try anything else.

That's really weird... Is this happening with the other people as well? It sounds like you didn't insert the cable far enough into the radio...

Sander van der Wel wrote in #note-120:

Kevin Omura wrote in #note-118:

Hi Sandor, just to verify I loaded this new driver and get the 'Error reading data from radio not the amount of data we want'.

The module shows up in CHIRP as UV-13Pro under model, checked to make sure it was the correct module as your file is tagged as baofeng_uv17.py. This is with the UV13 with FW V.06.01.013. Also of note when it errors out the radio stays stuck on Program.... on display. Shutting down this radio and unplugging from the computer restores radio to working condition. Tested VFO mode and it is working, TX working, etc.

Also connected the UV-13 with V06.01.014 FW with identical error and radio display stays locked on Program.... turning off the radio restores it to working condition.

Let me know if I should try anything else.

That's really weird... Is this happening with the other people as well? It sounds like you didn't insert the cable far enough into the radio...

It was, ok I figured it out. It must be pilot error on my part. I had switched USB ports and somehow I must have accidentally selected the incorrect port. I switched back to the port I normally use, selected it and everything works perfectly so my fault.

Sorry,

Sander van der Wel wrote in #note-117:

I have attached a new version of the driver. This driver should properly support the UV13Pro (and probably other related models too).

It would be appreciated if some of you can test this driver before I submit it to be integrated into CHIRP.

Please try this module with these instructions: LoadingTestModules

No problem here, seems to work as expected.
UV-13 Pro v2.

No more "tricks" for stations names. But, still problem in Power-on Message.

Sander van der Wel wrote in #note-124:

I have updated the driver to check if the model memory, matches the model. Is there someone with a UV13Pro V1 or both radios that can test this driver? The driver is attached to this post.

I did a quick test using my UV-13Pro V1. Both download and upload cloning was performed. No issues were encountered. After uploading an image to the radio and downloading back to CHIRP, the before and after images were identical.

Where can we download latest firmware 014 or 015 ?

Sander van der Wel wrote in #note-124:

I have updated the driver to check if the model memory, matches the model. Is there someone with a UV13Pro V1 or both radios that can test this driver? The driver is attached to this post.

Hi, sorry for the delayed reply. I downloaded 02240224 and tried it out on the .013 and .014 FW UV-13 Pros. Downloads and uploads worked fine, checked VFO mode also good, did not run into any issues.