Bug #1707
closedBaofeng UV-6 Cloning Problem
100%
Description
I'm trying to Download data fro from a pair of new Baofeng UV-6 radios and every time I try to clone it comes back with Error Radio refused to clone. I have a USB to serial cable with a genuine FTDI chip. I have checked that I selected all the right info on the Download pop up page. Port: Com 4 Vendor: Baofeng Model UV-6 I'm running on Windows 7 64bit. The current driver installed by Windows is a FTDI version 2.8.28.0. Radios cable and communication work perfectly with factory Baofeng UV-6 software but not with Chirp. Is this a new Bug or I'm missing something?
Files
Updated by Jim Unroe over 10 years ago
- Status changed from New to Feedback
After the "Ident" is received, your radios are no longer returning the expected "Ack" value. In "bug_#1441":http://chirp.danplanet.com/issues/1441 Daniel had a similar issue with a BF-888A. He later reported that when channel 16 was selected, the clone operation was successful. You might try setting your radio to each of the channels one-by-one to see if that makes a difference.
Jim KC9HI
Updated by Arnold Schwarzenegger over 10 years ago
I have the same problem. I get the message: "Radio refused clone". I tried all 128 different channels, but none of them reacts. I also used another cable, but get the same message. I use Linux mint 16 and USB port:/dev/ttyUSB0.
I own several Baofeng radio's and they all work fine with both CHIRP and my Linux version.....except the UV-6
Can someone please help?
Legendae
Updated by Luis Vicente over 10 years ago
Ditto. I have checked cloning radio with all 128 channels by unplugging the USB and restarting radio and Chirp before Avery channel and got the same radio refused clone everytime. All my other Baofeng radios also work fine with the Baofeng software and Chrip.
Updated by Jim Unroe over 10 years ago
Would either of you have access to a 32-bit Windows computer where you could use PortMon to capture the download from your radio using the factory software? If you can, attach it here so I can take a look at it.
Jim KC9HI
Updated by Luis Vicente over 10 years ago
The only 32 BIT SYSTEM I have is Windows XP and it does not let me capture with PortMon using the USB to serial cable.
Updated by Jim Unroe over 10 years ago
Luis,
Are you sure? I use my 32-bit Windows XP laptop (sitting right here next to me) log the serial port communications between a radio and programming software. I used it to capture the original serial port data that I used to develop the original UV-6 support.
Jim KC9HI
Updated by Carlos Marquez about 10 years ago
- File BF_UV6.LOG BF_UV6.LOG added
Jim,
I hope this log file helps.
Updated by Jim Unroe about 10 years ago
Carlos,
Close. Portmon needs to be switched to HEX and then grab the log.
Jim KC9HI
Updated by Carlos Marquez about 10 years ago
- File UV-6.hex.0829.LOG UV-6.hex.0829.LOG added
Try this log. I uploaded from the radio twice, toggling between HEX/ASC. It looks the same to me but I don't know what I'm looking at.
Updated by Carlos Marquez about 10 years ago
- File UV-6.ASC.0829.LOG UV-6.ASC.0829.LOG added
Updated by Carlos Marquez about 10 years ago
- File Chirp.HEX.0829.LOG Chirp.HEX.0829.LOG added
Just in case.
Updated by Jim Unroe about 10 years ago
Carlos,
It looks like our friends at Baofeng have changed the value of the string that is sent to the radio to start the cloning operation.
I need your help in testing/confirmation that this fixes the download process.
To help me test this, download the attached uv5r.py and launch chirp.
- enable developer mode: help -> check enable developer functions
- load this module: file -> load module, point to the uv5r.py you downloaded
- download from radio
If the download is successful, then save the download to a .img file and attach it to this issue. I will have to do some additional research before submitting a patch.
If you close chirp, you will have to repeat step 2 again to use this modified candidate.
Jim KC9HI
Updated by Carlos Marquez about 10 years ago
Jim,
Problem with module in Ubuntu CHIRP daily-20140717, "unable to load module:invalid syntax (uv5r.py, line1)". I'll try XP daily build tomorrow.
Updated by Carlos Marquez about 10 years ago
Jim,
Same problem. I tried both files in CHIRP daily-20140827 (XP) with same result. FYI, I use XP at work/day and Ubuntu or W8 at home/night.
Updated by Carlos Marquez about 10 years ago
- File UV-6.140903.img UV-6.140903.img added
Jim,
I was downloading the wrong link? It worked fine when I downloaded from the right page.
Updated by Jim Unroe about 10 years ago
Carlos,
Thanks for the .img file.
Apparently what you have is an older radio. It's aux memory is similar to a UV-5R with pre-BFB291 firmware. So some of the memory locations in the Aux block are different from the UV-6 that is already supported. So whatever you do, don't make any changes on the Settings->Other menu.
I'm going to have to think about this some.
Jim KC9HI
Updated by Jim Unroe about 10 years ago
- Status changed from Feedback to In Progress
- Assignee set to Jim Unroe
- Target version set to 0.4.1
- % Done changed from 0 to 100
- Chirp Version changed from 0.4.0 to daily
- Platform changed from Windows to All
Patch submitted
Updated by Brian Evans about 10 years ago
I just purchased a UV-6 and have the same issue. I have no issues using the system and cable with my BF-F8+ and BF-888S. I have used the Baofeng software and it does connect without issues. I tried upgrading to the latest Daily (9/8/2014) and it still doesn't work.
Updated by Jim Unroe about 10 years ago
Carlos,
This change has been added to the latest CHIRP daily build. Does it work for you?
Jim
Updated by Shawn Esler about 10 years ago
Jim,
I also have the UV-6 and downloaded the lastest daily (09/13/14) and when I try to download from the radio, it reads "Radio does not respond." Any suggestions?
Updated by Jim Unroe about 10 years ago
Do you have it working with the Baofeng software? If you do, do you have access to a 32-bit Windows where you can capture a download from the radio using PortMon?
Updated by S C about 10 years ago
- File Portmon.log Portmon.log added
I also have a UV-6 which shows a "Radio refused clone" error when trying to read it with Chirp. The Baofeng UV6UV7 software does work, and I captured a read with Portmon and attached the log file. It also appears that someone posted a similar log file in bug #1617.
Updated by S C about 10 years ago
And just an update for whatever it's worth, I realized that the "Radio refused clone" message appeared while using a daily build from 09-03-14 to try to read the UV-6. The latest build (09-13-14) now produces a "Radio does not respond" error instead.
Updated by Jim Unroe about 10 years ago
That isn't a log of the full download from the radio to the Baofeng software. Also, I need it switched to hex. Thanks for providing though. This is what I need to research the difference between your radio and the radio that was used for the initial CHIRP support.
Updated by Carlos Marquez about 10 years ago
- File UV6_20140915.LOG UV6_20140915.LOG added
Thanks Jim,
Great stuff. Worked both in Ubuntu and XP.
Updated by Carlos Marquez about 10 years ago
- File UV6_20140915.img UV6_20140915.img added
Updated by Carlos Marquez about 10 years ago
I have only downloaded from radio. Haven't tried uploading yet.
Updated by Jim Unroe about 10 years ago
Thanks Carlos. Now if I can just figure out what Baofeng did to make S C's UV-6 different.
Updated by Wren S about 10 years ago
Wren S wrote:
I've got 3 UV-6's which work fine in the baofeng software but "Radio did not respond" in CHIRP.
Forgot to mention portmon won't run in my windows 7 box, and your developer update .py file doesn't help.
Updated by Jim Unroe about 10 years ago
Wren,
Sorry, The debug.log doesn't help me. It confirms that neither of the current "init" strings are accepted by your radios to begin cloning. I don't have a way of determining what your radios require without a port scan of the OEM software doing its "dance" with your radios.
I don't know if it will help, but would you email me a copy of your OEM programming software? uv-6 [at] kc9hi [dot] net
Or you can try this free serial port analyzer (limited to 5 sessions per day and 23 minutes per session)
http://freeserialanalyzer.com/
Jim KC9HI
Updated by S C about 10 years ago
Ok I hope I did this right. I ran the freeserialanalyzer software and told it to monitor "Console" and "Data" views. I then started the Baofeng software (it froze a couple of times before working, fyi, just in case that activity shows up in this log) and then performed a successful read of the radio. I then wrote that data right back to the radio, followed by saving the freeserialanalyzer file which is attached here. I still have Portmon too so if there's a certain way I need to configure it when I capture a UV-6/Baofeng software read/write, let me know.
Updated by Jim Unroe about 10 years ago
Actually the file you attached just saved the configuration of the software when you did the capture. What you need to do is right-click in the "send" window and save it as an "html" file. I need the one for "send" but you can attach the one for the "receive" as well.
Jim
Updated by S C about 10 years ago
- File capture.PNG capture.PNG added
- File Writes.htm Writes.htm added
Jim Unroe wrote:
Actually the file you attached just saved the configuration of the software when you did the capture. What you need to do is right-click in the "send" window and save it as an "html" file. I need the one for "send" but you can attach the one for the "receive" as well.
Jim
By "send" do you mean "writes"? I think I got it for ya.
Updated by Jim Unroe about 10 years ago
S C,
Yes. This is what I am looking for. Actually, both the Reads and Writes file would be nice. But this looks like it is from CHIRP. Would you get me a set from the OEM software?
Thanks,
Jim
Updated by S C about 10 years ago
- File OEM Reads (download from UV-6).htm OEM Reads (download from UV-6).htm added
- File OEM Writes (download from UV-6).htm OEM Writes (download from UV-6).htm added
- File OEM Reads (upload to UV-6).htm OEM Reads (upload to UV-6).htm added
- File OEM Writes (upload to UV-6).htm OEM Writes (upload to UV-6).htm added
Jim Unroe wrote:
S C,
Yes. This is what I am looking for. Actually, both the Reads and Writes file would be nice. But this looks like it is from CHIRP. Would you get me a set from the OEM software?
Thanks,
Jim
Alright, I have captured both the "reads" and "writes" windows twice, once while downloading the programming from the radio and again while uploading programming to the radio. These four files, plus the last one that you said looks like it's from CHIRP, are all in fact from the OEM Baofeng software.
Updated by S C about 10 years ago
- File CHIRP Reads (failed download from UV-6).htm CHIRP Reads (failed download from UV-6).htm added
- File CHIRP Writes (failed download from UV-6).htm CHIRP Writes (failed download from UV-6).htm added
And for good measure, here are captures of "reads"/"writes" while using CHRIP daily build 20140913. This is of course, a failed attempt to download the programming from the radio which resulted in the usual "Radio did not respond" error message. I have not at any point been able to successfully download anything from the UV-6 using CHIRP, let alone upload anything.
Updated by Jim Unroe about 10 years ago
S C,
You've got the right idea. but all 6 files are empty.
Jim KC9HI
Updated by S C about 10 years ago
Jim Unroe wrote:
S C,
You've got the right idea. but all 6 files are empty.
Jim KC9HI
Dang, ok I must not be doing something right with the "freeserialanalyzer" software. What steps do I need to take exactly to export the correct files?
Updated by Jim Unroe about 10 years ago
S C,
You did it with the original Writes.htm file. Download using the OEM software while capturing with the "freeserialanalyzer" software. After the download is complete, you should see the captured "reads" and "writes" in the corresponding windows. Right-click each window and choose to save it as an html file.
Jim
Updated by S C about 10 years ago
- File capture.PNG capture.PNG added
- File basic-complete.PNG basic-complete.PNG added
Jim Unroe wrote:
S C,
You did it with the original Writes.htm file. Download using the OEM software while capturing with the "freeserialanalyzer" software. After the download is complete, you should see the captured "reads" and "writes" in the corresponding windows. Right-click each window and choose to save it as an html file.
Jim
Ok so for whatever reason the "reads/writes" export will only spit out the useless small file, just like the last six. In the analyzer software I tried using a different output method "Request View" rather than "Data View" that I had been using previously, and this exports one file of captured data. I exported the "Complete" tab as seen in the screenshot. This created a much larger file which hopefully contains the data you need. This site only allows a max of 5MB file attachments so I posted the files to the UV-5R facebook group and tagged you in the post. One file is for a download and one for an upload to/from the UV-6 with the OEM software. Hopefully this is useful?
Updated by Jim Unroe about 10 years ago
Sean,
I've bad news and good news.
The bad news is that these files are huge. They contain a huge amount of "noise". That, and the fact that my browser is very sluggish because of the file size, makes them virtually impossible to use.
The good news is that I trudged through the first part of it anyway. I can see that the problem that CHIRP is having with these radios is the same problem that Carlos is having with his UV-8 radios.
This doesn't seem like there is going to be an easy fix for this. I'm going to need to consult some of the "experts" in the developer mailing list to see if they can help me solve this.
Jim
Updated by Gary Ball almost 10 years ago
I am really having an issue trying to program my UV-6... I keep getting the refuse to clone on CHIRP and I cannot get the Baofeng software to install. I can't get it to run the set up...
Has anyone else run into this and resolved it, if so will you please help me out?
Updated by Baofeng CHIRP over 9 years ago
Luis Vicente wrote:
I'm trying to Download data fro from a pair of new Baofeng UV-6 radios and every time I try to clone it comes back with Error Radio refused to clone. I have a USB to serial cable with a genuine FTDI chip. I have checked that I selected all the right info on the Download pop up page. Port: Com 4 Vendor: Baofeng Model UV-6 I'm running on Windows 7 64bit. The current driver installed by Windows is a FTDI version 2.8.28.0. Radios cable and communication work perfectly with factory Baofeng UV-6 software but not with Chirp. Is this a new Bug or I'm missing something?
h1. Baofeng UV-6 Cloning Problem
*UNABLE TO CONNECT THE RADIO TO THE CHIRP software, com error !!!!
Is any action being TAKEN WITH THIS ISSUE? Is the developer taking action? it seems like a MICROSOFT action plan :-).
*
Updated by Freddie Ruddick over 9 years ago
Hi all,
Been following this for a while, as I'm having the same issue. Jim, any progress with the developers?
If it helps in any way, I have a UV-6 which has the same issue; which I'd be willing to lend to a dev.
Cheers,
Freddie
Updated by Matt Schmohl over 8 years ago
- File UV-6 Chirp fail 1.mon UV-6 Chirp fail 1.mon added
- File UV-6 Chirp fail 1.txt UV-6 Chirp fail 1.txt added
- File Baofeng UV-6 Stock 1.mon Baofeng UV-6 Stock 1.mon added
- File Baofeng UV-6 Stock 1.txt Baofeng UV-6 Stock 1.txt added
- File debug.log debug.log added
I just picked up a lot of these radios and am very disappointed they are not working with chirp (which is an awesome program for the radios it works with). Hopefully the attached log files are of some help in this matter. I'm running Windows 7 x64, CHIRP daily-20160517 using prolific usb cables, Driver version: 3.2.0.0. I hope this issue is resolved soon because the Baofeng software sucks REALLY bad.
Updated by Robert Morris over 8 years ago
It appears I just spent several weeks waiting for my new electronic brick to arrive from China. Since I'm using Mac OS X, the software that ships with the Baofeng UV-6 is useless. CHIRP is my only hope. Please fix this bug!
To be certain, I've programmed my Baofeng UV-5R (purchased mid 2014) many times with CHIRP. So, it's not the cable.
Updated by Marcus van Dam over 8 years ago
- File uv5r.py.diff uv5r.py.diff added
- File uv5r.py uv5r.py added
Looking at the dumps of Matt, your issue seems to be similar to mine.
Where the radio returns 12 bytes in the ident response and CHIRP only expects 8 bytes.
With some help of Jim (on the mailing list), I've managed to get this radio to correctly complete a dump, at the expense of killing compatibility with other Baofeng radios.
You can find the diff and new uv5r.py file attached.
Jim was working on a more permanent solution to the problem.
Updated by Jim Unroe over 8 years ago
Marcus,
Would you provide the 12 byte reply from your UV-6.
Thanks,
Jim KC9HI
Updated by Jim Unroe over 8 years ago
- File uv5r.py added
Please give this a driver try. To use it...
1 save the attached file to where you keep your *.img files
2 click "Help" in the menu bar and enable "Enable developer functions"
3 click "File" in the menu bar
4 click "Load module" in the drop-down menu
5 locate and load the file saved in step 1
See if you can download from and upload to your UV-6.
Note: Loading this driver is only temporary. It does not change your CHIRP install. You must load this driver after loading CHIRP and before trying to clone from/to a UV-6 with a 12 byte ident.
If it works, please attach a debug.log file and the saved image. Then I will submit a patch.
If it does not work, please attach a debug.log file.
Jim KC9HI
Updated by Marcus van Dam over 8 years ago
Hi Jim,
I have tested your module, and it is cloning like a charm. I haven't tried programming yet.
The following debug output was generated related to the magic and ident:
INFO: Sending Magic: 000: 50 bb ff 20 12 08 23 00 P.....#. INFO: Ident: 000: aa 01 01 36 01 74 01 04 ...6.t.. INFO: Extra: 000: 00 05 20 dd 00 00 00 00 ........ INFO: Radio Version is ' Ver UV6S83 '
I see no further errors regarding the cloning.
The full 12 byte ident string is:
AA 01 01 36 01 74 01 04 00 05 20 DD
// Marcus
Updated by Jim Unroe about 8 years ago
- Status changed from In Progress to Resolved
This was addressed in the CHIRP-2016013 build.
Jim KC9HI