New Model #2261
closedbf-a58
100%
Description
does anyone know when chirp will be able to program the BF-A58 from Baofeng? Or where I can find programming for it?
Files
Updated by Jim Unroe almost 10 years ago
- Status changed from New to Feedback
Justin,
I wouldn't be surprised if this isn't just a UV-82 or UV-5R in a different case. Baofeng is well known for this sort of repackaging. Try the both models and report back.
Jim KC9HI
Updated by Michael Walker over 9 years ago
I tried all the available models on the daily build and none of them worked even though it looked like a UV5R.
The Baofeng software did work though. http://www.409shop.com/shop_displaynews.php?id=292
Mike
Updated by Jim Unroe over 9 years ago
Michael or Justin,
Use the attached uv5r.py file just to see if it will read the data from your radios. Here's how you do it.
- save the uv5r.py file to where you normally save your CHIRP .img files
- click Help and enable "Enable Developer Functions"
- click File then click Load Module then load the uv5r.py file saved in step 1
Once the module is loaded, then download from the radio using the UV-5R model selection. If you are successful at downloading from your radio, then save the download to a .img file and attach it here so I can examine it.
Loading this driver does not alter your CHIRP installation. If you close CHIRP, then you will have to load the module again to do further testing.
Jim KC9HI
Updated by Emil Sandnabba over 9 years ago
Hello Jim,
I did just received my radio and now I'm having the same problem. :)
I tried your file with the the latest daily build without success. I did however get another error message:
"ERROR: Clone failed: Incorrect 'Model' selected."
Another note is that if I try to clone the radio with model "UV-B5" selected I get: "ERROR: Clone failed: Radio did not ack programming mode".
Don't know if that might help.
Any other things that I can try or help with?
Updated by Jim Unroe over 9 years ago
Emil,
Load CHIRP
Load module
Attempt download
Close CHIRP
Then get and attach the debug.log file.
"How to find the debug.log file":http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Jim KC9HI
Updated by Emil Sandnabba over 9 years ago
Ok, attaching the file.
I did also note that the radio rebooted after I got the "Incorrect 'Model' selected" dialog.
Hope that this helps.
Emil
Updated by Emil Sandnabba over 9 years ago
- File BF_A58.img BF_A58.img added
Aha! I added "BFT515" to the "BASETYPE_UV5R" array in the driver file, and now it seems to work. :)
I cloned the radio and saved the result with "Save as". Hope that this is the image you requested. Attaching it here.
Thanks!
Emil
Updated by Emil Sandnabba over 9 years ago
Sorry for spam, but here is the debug.log when the clone succeed.
The radio does also restart after the clone is done.
Thanks
Emil
Updated by Jim Unroe over 9 years ago
- Status changed from Feedback to In Progress
- Assignee set to Jim Unroe
- Target version set to 0.5.0
Emil,
Perfect. I'll work on getting a patch submitted this weekend.
Thanks for the help.
Jim KC9HI
Updated by Jim Unroe over 9 years ago
I just found out that the BF-A58 is a radio with 3 power levels so it needs to be moved from UV-5R class to the BF-F8HP class.
Jim KC9HI
Updated by Emil Sandnabba over 9 years ago
- File 20150702.log 20150702.log added
Hi again Jim,
Many thanks for your help. You are right about that the radios has 3 power levels.
I had to make some changes today however, but I can't get the latest daily builds to work.
I have tried both 20150702 and 20150623 with the same result. I'm just getting "ERROR: Radio did not respond" trying with both UV-5R and BF-F8HP.
I'm also getting some python tracebacks however that I suppose can be the problem.
I'm attaching the debug-log here (Started chirp with "python2 ./chirpw --log ./20150702.log -v").
The 20150607 version works fine with the UV-5R driver anyways.
Thanks.
Emil
Updated by Jim Unroe over 9 years ago
Emil,
There is nothing useful in this debug.log file. You must cause the error, then close CHIRP and finally grab the debug.log file.
A "Radio did not respond" error is usually an indication that the 2-pin plug is not fully engaged into the socket.
Jim KC9HI
Updated by Emil Sandnabba over 9 years ago
- File new_debug.log new_debug.log added
- File BF-A58-connector.jpg BF-A58-connector.jpg added
Oh, yeah you where right. I must have mixed the debug-logs in some way. My bad.
The radio is using a new motorola-like multi-pin programming cable, so I'm pretty sure that there are no connection problems.
I have also tried the following:
- Download from radio with 20150607. Works fine. Closing application
- Started 20150702, does not work.
- Started 20150607, still working.
But as I said last time, I think the Python tracebacks are the most interesting.
Thanks.
Emil
Updated by Jim Unroe over 9 years ago
Emil,
When it was discovered that the BF-A58 radio had three power levels instead of 2, it was mistakenly moved to the Intek KT-980HP model instead of the BF-F8HP model.
I will submit a patch to move it to the correct model.
Jim KC9HI
Updated by Jim Unroe over 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Emil,
The patch has been submitted. The next daily build should allow you to use the BF-F8HP model selection.
In the mean time, to get support for 3 power levels, you should be able to use the 20150702 daily build and choose the Vendor: Intek and Model: KT-980HP.
Jim KC9HI
Updated by Jim Unroe about 9 years ago
- Status changed from Resolved to Closed
fixed in CHIRP daily-20150814
Jim KC9HI
Updated by fred smith over 8 years ago
I have a Baofeng UV-82wp, which seems similar to the BF-A58. Firmware version number is nt5101. I want to use chirp, but this neither model appears on the list. I tried all the ones listed and get an error message (radio did not respond). ...any ideas?
Updated by Jim Unroe over 8 years ago
This radio does not report the firmware version that CHIRP requires to keep the user from cross-loading other Baofeng image files into this radio. Unfortunately CHIRP cannot accept an image with 14 hex 0xFF characters or the firmware version. Sorry.
Jim KC9HI