New Model #11507
closedBaofeng K6 and K61
100%
Description
K6 - https://www.baofengradio.com/products/k6
(They are also selling K61 but can't find the website but its the same firmware)
You can find their software here: (redacted)
Files
Updated by TERRENCE RODRIGUEZ 8 months ago
- File IMG_6878.jpeg IMG_6878.jpeg added
Sorry for that and yes I have tried both with Quansheng UV-K5 and no it doesn't work.
Updated by Jonathan Blaine 7 months ago
Confirming that there's only a K6-only Windows-only app that will program this radio. I found it via some deep internet searching on radioreference.com and simonthewizard.com. It's a Chinese app: just click the highlighted boxes to install.
Updated by Shaun Davis 6 months ago
Any ETA on when the K6 will be supported by Chirp?
Updated by TERRENCE RODRIGUEZ 6 months ago
Understood the instructions of the repeated Tickets.
Original question still stands, is there an update?
Terrence Rodriguez
Sent from my iPhone
On Oct 19, 2024, at 10:58 PM, Shaun Davis redmine@chirpmyradio.com wrote:
Updated by Dan Smith 6 months ago
No update. There's really no point in asking, as any updates that I know of would be posted here anyway. It's going to require a developer with the time and interest to work on it, but if/when that happens, it'll get posted here (honest).
However, I would like to see more detail than "it doesn't work" when trying the K5 driver. Can you please try it and then immediately use Help->Report or update a bug to send a debug log to this ticket? It's very possible that it's totally a different radio, but the debug log will help rule that out for sure.
Updated by Shaun Davis 6 months ago
I tried to do a "Download from radio" of my current Baofeng NA-K6 radio using the K5 Plus profile and it says:
{Error Communicating with Radio - Error Reading data from Radio: not the amount of data we want.}
Shaun Davis
Lexington NC
Updated by Dan Smith 6 months ago
Pictures of a message are not very useful. Please, per IssueInstructions and How_To_Report_Issues use the Help->Report or update a bug tool to send a debug log.
Also, the Baofeng K5-Plus is not the driver I'm asking to try. Please try the Quansheng UV-K5 driver and use the above tool to send a debug log.
Updated by TERRENCE RODRIGUEZ 6 months ago
- File config.txt config.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241020]
This was attempting to connect my “Baofeng K6” (as written on the back) via Quansheng K5 driver as they appear similar. I’ll put it in “Update” mode (which is accomplished when you hold the 2nd and 3rd ptt and power on the device) and try it again.
Updated by TERRENCE RODRIGUEZ 6 months ago
- File config.txt config.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241020]
This was the attempt in Update mode. It did not work but I assume that is more for changing firmware.
Updated by TERRENCE RODRIGUEZ 6 months ago
- File config.txt config.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241020]
This was attempting to connect my “Baofeng UV-K61” (as written on the back) via Quansheng K5 driver. It didn’t work as well. Hope this helps.
Updated by TERRENCE RODRIGUEZ 6 months ago
- File Screen Shot 2024-10-22 at 9.30.05 AM.png Screen Shot 2024-10-22 at 9.30.05 AM.png added
- File IMG_7846.jpg IMG_7846.jpg added
- File IMG_7847.jpeg IMG_7847.jpeg added
Here are additional images. Error message and pictures of back of radio for model #'s which differ from what the other users have noted in this thread but I'm sure it's the same radio, just a Baofeng thing.
Updated by Shaun Davis 6 months ago
Dan Smith wrote in #note-9:
Pictures of a message are not very useful. Please, per IssueInstructions and How_To_Report_Issues use the Help->Report or update a bug tool to send a debug log.
Also, the Baofeng K5-Plus is not the driver I'm asking to try. Please try the Quansheng UV-K5 driver and use the above tool to send a debug log.
I'm just going to send the radio back. If it can't be used with Chirp then it's useless to me and I'm not a troubleshooter... Beofeng should pay Chirp good money to help this software work with their radios instead of people having to do this as a service to the radio community. Take Care!
Updated by TERRENCE RODRIGUEZ 5 months ago
TERRENCE RODRIGUEZ wrote in #note-12:
[Uploaded from CHIRP next-20241020]
This was attempting to connect my “Baofeng UV-K61” (as written on the back) via Quansheng K5 driver. It didn’t work as well. Hope this helps.
@Daniel Fiechter Smith anything else I can do to support or are you still searching for a developer to help?
Updated by TERRENCE RODRIGUEZ 5 months ago
TERRENCE RODRIGUEZ wrote in #note-16:
TERRENCE RODRIGUEZ wrote in #note-12:
[Uploaded from CHIRP next-20241020]
This was attempting to connect my “Baofeng UV-K61” (as written on the back) via Quansheng K5 driver. It didn’t work as well. Hope this helps.
Dan Smith anything else I can do to support or are you still searching for a developer to help?
Updated by Steve Washburn about 1 month ago
New to Radio and Chirp, this unfortunately seems to apply to the K63 as well.
Updated by Jim Unroe about 1 month ago
Steve Washburn wrote in #note-19:
New to Radio and Chirp, this unfortunately seems to apply to the K63 as well.
I believe that this is likely to be true. However I don't have a K63 available for testing. So when I finally have a driver available to attach to this issue for testing, I will need someone with a K63 to validate it for the K63.
Updated by Jim Unroe about 1 month ago
I have just attached the first test driver module for the Baofeng K6 (and whatever similar variants Baofeng may have for it such as BF-K6, UV-K6, etc). It also works for my Baofeng K61. Hopefully it will also work for the Baofeng K63 but additional testing and work may be required.
You are embarking on alpha/beta testing. Don't forget to save your 1st successful download, unedited, to a native CHIRP Radio Images (*.ing) file to be kept in a safe place as a backup.
Please report any issues or successes with test driver against this ticket. DO NOT OPEN ANOTHER TICKET to report issues related to this test driver.
The instructions for how to use the attached driver module are located here: LoadingTestModules
As a reminder, this Issue Number: 11507
Updated by Michael Marquette about 1 month ago
I just tried the file on my K61, appears to have worked fine without any issues.
Updated by Octavio Gianatiempo about 1 month ago
- File config.txt config.txt added
- File Baofeng_K6_20250316.img Baofeng_K6_20250316.img added
- File macos_system_info.txt macos_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250314]
I tried the test driver witth a UV-K66 (S/N UVK66000955). When downloading the data from the radio, It recognised it and succesfully put it into programming mode. However, the data makes no sense (it appears to be 60606060 repeated).
Updated by Jim Unroe about 1 month ago
Octavio Gianatiempo wrote in #note-23:
[Uploaded from CHIRP next-20250314]
I tried the test driver witth a UV-K66 (S/N UVK66000955). When downloading the data from the radio, It recognised it and succesfully put it into programming mode. However, the data makes no sense (it appears to be 60606060 repeated).
Thank you for confirming that the UV-K66 is not supported by this driver. It will need a ticket of its own to accommodate its own separate development.
Updated by Jim Unroe about 1 month ago
Test driver #2
condenses the code by eliminating some redundancy. The update should not change anything from the end user's point of view. The driver still needs to be tested to make sure there are no unexpected surprises. Just as a reminder, here are the instructions for its use: LoadingTestModules
Updated by Michael Marquette 24 days ago
I used test driver #2 with two new K61 radios and had no issues, looks good.