Bug #11258
closedRadtel RT-470 10W NEW PCB / V2.00 Firmware ERROR: Failed to clone: Radio returned unknown identification string
100%
Description
Extremely similar to issue 11164, but with firmware 2.00
Files
Updated by Jim Unroe about 2 months ago
- File mml_jc8810_RT470_fw200.py mml_jc8810_RT470_fw200.py added
- Assignee set to Jim Unroe
- Target version set to chirp-py3
The attached test driver add the fingerprint for RT-470 radios with PCB V2 using firmware v2.00. Instructions to use it are here: LoadingTestModules
Let me know how it goes.
Another option would be to either upgrade your firmware to v2.11a which is already supported or, better yet, upgrade to firmware v2.13a and then do me a favor by copying the menu list provided in #11164 and editing it to note any differences between it and your radio with fw v2.13a so I can finish that ticket.
Updated by Charles Gallo about 1 month ago
Unfortunately,. I flashed to 2.11a last night, so no longer have access - will do 2.13 later today
Updated by Jim Unroe about 1 month ago
Charles Gallo wrote in #note-2:
Unfortunately,. I flashed to 2.11a last night, so no longer have access - will do 2.13 later today
Before you upgraded, did the test driver module for v2.00 work? Add the debug log for v2.11a so its fingerprint can be added, too.
There is currently no support for 2.13a so you will have to use the test driver module attached to ticket #11164. I am waiting to get a reply that contains updated menu list. Usually each firmware update has changed the available settings and/or added new settings. Now is the time to identify them and update CHIRP accordingly.
Updated by Charles Gallo about 1 month ago
As I said, unfortunately, I flashed to 2.11A before I got a chance to test
The good news - the code from #11164 worked perfectly with 2.13a here - AND I went through the menu, and I saw no changes. The one thing I can't 100% confirm is the defaults for the buttons (the sets are right) as I had changed my buttons
I think you are good to go menu wise
Updated by Jim Unroe about 1 month ago
Charles Gallo wrote in #note-4:
As I said, unfortunately, I flashed to 2.11A before I got a chance to test
The good news - the code from #11164 worked perfectly with 2.13a here - AND I went through the menu, and I saw no changes. The one thing I can't 100% confirm is the defaults for the buttons (the sets are right) as I had changed my buttons
I think you are good to go menu wise
Thank you for the testing and followup. I will try to patches submitted for both tickets.
Updated by Anonymous about 1 month ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|ff0d17630e965331e3c32f7850705190dab6d3ba.