<< I was able to read and write using Chirp with my UV-5X3 a few weeks ago

without any issues. Has something changed? >>

Dunno if they’ve changed anything, Bob, but I’d hold onto whatever build you used a couple weeks ago, just in case. The build that is failing for me is today’s… "chirp-daily-20161018.app”. I’ve also got a copy of build “chirp-daily-20161005” and that fails in exactly the same manner.

<< I had the same error message while trying to program the Btech UV-5001. Once I put the radio in VFO mode, I turned it off and back on again. I was able to read and program the radio. I have no idea why this worked, but it did. Good luck. >>

Thanks for the tip, Toby. Alas, toggling VFO mode didn’t work for me. Glad yours cleared up ok.

Jeff

<< I’ve had that happen with some of my other radios. My initial thought is to put all the planets back in alignment. - Unplug the cable and plug it back in - Power cycle the radio - Close and reopen CHIRP

Just a thought… >>

Aye, resetting everything and having it come up clean was my first thought as well, John. I’ve probably been through a dozen or more of those shut-everything-down, re-plug-everything, bring-each-component-up-individually-and-clean cycles. Alas, Chirp remains very unhappy with my UV-5X3.

Thanks for the suggestion.

Jeff

Hey Jim,

Thanks for the help. I loaded the file you attached, per your instructions. Same result/error.

When I click ‘File’ and then ‘Load Module’ and browse to the baofeng_common.py file there’s no message/confirmation upon opening the file. Just goes back to the blank Chirp screen. I assume that’s normal behavior.

Not sure what kind of file baofeng_common.py is (some sort of diagnostic?), but would the fact that my UV-5X3 is listed under ‘Btech’ rather than ‘Baofeng’ make any difference? i.e. is there a ‘btech_common.py' file?

Thanks again.

Jeff

On Oct 19, 2016, at 7:53 AM, Jim Unroe rock.unroe@gmail.com wrote:

Jeff,

1 save the attached file to where you keep you CHIRP Radio Images (*.img) files 2 click "Help" 3 enable "Enable Developer Functions" 4 click "File" 5 click "Load Module" 6 locate and load the file saved in step 1

Now try to read from your UV-5X3 and report back.

Jim

I just did an update of my chirp, (hg -v pull -u) Downloaded my tech uv-5x3, no problem on download or re upload. Using a home made cable with an FTDI chip.

make sure the cable is well seated in the radio and the volume is all the way up. Not sure why the volume makes a difference but it does. I suppose we can add then into the instruction window pop-up.

On Oct 19, 2016, at 9:36 AM, Jim Unroe rock.unroe@gmail.com wrote:

On Wed, Oct 19, 2016 at 8:46 AM, Jeff Hughes jeffreyhughes@earthlink.net wrote:

...

Hey Jim,

Thanks for the help. I loaded the file you attached, per your instructions. Same result/error.

When I click ‘File’ and then ‘Load Module’ and browse to the baofeng_common.py file there’s no message/confirmation upon opening the file. Just goes back to the blank Chirp screen. I assume that’s normal behavior.

Yes. This is normal.

...

Not sure what kind of file baofeng_common.py is (some sort of diagnostic?), but would the fact that my UV-5X3 is listed under ‘Btech’ rather than ‘Baofeng’ make any difference? i.e. is there a ‘btech_common.py' file?

The boafeng_common.py is used by the uv5x3.py driver for the download/upload support.

...

Thanks again.

Jeff

If your programming cable has an FTDI chip, are you running the latest driver from ftdichips.com? If your programming cable has a Prolific type chip, are you running one of the generic device drivers?

Jim _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to James Lee at jml@jmlzone.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Thank you, gentlemen. I’m now up and running with Chirp on my UV-5X3. I re-downloaded the driver. I’m using a Baeofeng / BTECH cable (drivers at www.ftdichip.com/Drivers/VCP.htm http://www.ftdichip.com/Drivers/VCP.htm). Immediately upon installation I pulled up a terminal window (this is on a Mac) and looked under /dev… no serial driver so I wasn’t optimistic. But as soon as I plugged in the cable it appeared. Voila! There came the progress bar as my radio cloned - something I hadn’t seen before - and then the page with all my channels presented itself. What a beautiful sight! Chirp is SO much easier than laboriously going through the radio’s rather arcane menu system.

Thanks again guys.

Jeff

On Oct 19, 2016, at 11:37 PM, Glenn glennervin@cableone.net wrote:

Is it not also important to be sure that the channel the radio is on is not receiving any traffic? Some folks remove their antenna during this to ensure no reception comes in. Glenn ----- Original Message ----- From: "jml" <jml@jmlzone.com mailto:jml@jmlzone.com> To: "Discussion of CHIRP" <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com> Sent: Wednesday, October 19, 2016 10:29 PM Subject: Re: [chirp_users] "Error Reading Data from Radio..."

I just did an update of my chirp, (hg -v pull -u) Downloaded my tech uv-5x3, no problem on download or re upload. Using a home made cable with an FTDI chip.

make sure the cable is well seated in the radio and the volume is all the way up. Not sure why the volume makes a difference but it does. I suppose we can add then into the instruction window pop-up.

...

On Oct 19, 2016, at 9:36 AM, Jim Unroe rock.unroe@gmail.com wrote:

On Wed, Oct 19, 2016 at 8:46 AM, Jeff Hughes jeffreyhughes@earthlink.net wrote:

...

Hey Jim,

Thanks for the help. I loaded the file you attached, per your instructions. Same result/error.

When I click ‘File’ and then ‘Load Module’ and browse to the baofeng_common.py file there’s no message/confirmation upon opening the file. Just goes back to the blank Chirp screen. I assume that’s normal behavior.

Yes. This is normal.

...

Not sure what kind of file baofeng_common.py is (some sort of diagnostic?), but would the fact that my UV-5X3 is listed under ‘Btech’ rather than ‘Baofeng’ make any difference? i.e. is there a ‘btech_common.py' file?

The boafeng_common.py is used by the uv5x3.py driver for the download/upload support.

...

Thanks again.

Jeff

If your programming cable has an FTDI chip, are you running the latest driver from ftdichips.com? If your programming cable has a Prolific type chip, are you running one of the generic device drivers?

Jim _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to James Lee at jml@jmlzone.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net mailto:glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com

---

chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jeff Hughes at jeffreyhughes@earthlink.net mailto:jeffreyhughes@earthlink.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com