CHIRP

I just received 2x Retevis RA79 HTs, which are re-packaged and re-branded Quansheng UV-K5. Chrip reads from the devices just fine using the Retevis RA79 device profile, but it won't allow me to update the profile with my local repeater Chirp CSV file details (see attached screenshot with errors reported, and debug log), when trying to do a cut-and-paste from the CSV to the IMG. I even tried reducing it just to the 14 local VHF repeaters to see if there were some bad entries, and restarting in Developer mode, none of which worked -- cut-and-paste from CSV always failed with the image in the screenshot so long as the device was identified as a Retevis RA79 on the initial read.

The combo that ended up working for me was to read from the HTs telling Chirp the devices were Quansheng UV-K5. It then worked just fine when I tried to cut-and-paste from the CSV, and similarly the write-back to the device completed successfully and the radios are programmed as expected.

So I'm not sure how Chirp "maps" re-branded devices to the same drivers, but whatever it is doing for the RA79 is not quite working properly. I should, of course, note that I've flashed my RA79s with Egzumer 0.22 (which I think is what 80% of people with UV-K5s do).

Also attached is the IMG file for the RA79 (Chirp named it Quansheng_UV-K5, even when I selected that it was a Retevis RA79). This is the img file that I was able to successfully update and write back.