[chirp_users] More baofeng woes (UV-B5) (Scott Martin)
scott at kc9qen.com
Sun May 31 14:54:16 PDT 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 05/31/2015 04:27 PM, Jim Unroe wrote:
> On Sun, May 31, 2015 at 1:33 PM, Richard Menedetter <ricsi at gmx.at> wro
>>>>> I picked up a UV-B5 and am unable to program it with chirp.
>>>> Yes ... sadly there is an open ticket for this for 4 months ...
>>>> unfixed as of yet.
>>>> New UV-B5 software is not recognized by Chirp.
>>>> There is a one line patch for Linux Chirp floating around that make
s it work.
>>>> Or you can use the Baofeng SW to download the image, rename it, use
chirp to edit it, rename it back
>>>> and use baofeng SW to upload it.
>>>> I hope this will be addressed by Chirp soon!
>>> Where is this one line patch?
>> It only works on Linux, as there the Python code is directly accessib
>> I was very much hoping that Chirp gets changed to work with the "new"
>> If you are using Linux I can search for the old message and send it t
>>> Jim KC9HI
>> CU, Ricsi
> If you got me the one line patch, I was planning to get it tested and
> then submit it to be added to CHIRP.
> Jim KC9HI
Thanks for your time all.
I've tried a python script 'uvr5.py' with a md5sum of
8259c589e7791536a0ea91cade6729b9 . It's a *nix box. I'm digging into the
hardware and starting to think this one's lost it's smoke. I'm charging
my camera battery now...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the chirp_users