Bug #10085
closedSupport for alternate 'identification string' on some Abbree AR-63 devices
100%
Description
As discussed on the page for Issue #9903 , my Abbree AR-63 radio provides a different "identification string" than currently expected, resulting in the error "Radio returned unknown identification string."
Jim suggested (based on the same debug.log file attached to this issue) that:
50 33 32 30 37 33 02 ff <-- this is what my AR-63 replies with (and what CHIRP is expecting) 50 33 32 30 37 33 03 ff <-- this is what your AR-63 replies with
Files
Updated by Jim Unroe over 1 year ago
- Status changed from New to In Progress
- Target version set to chirp-legacy
I'm working on it. Stay tuned.
Jim KC9HI
Updated by Jim Unroe over 1 year ago
Luke,
The attached proposed driver module adds support for radio models that been seen with multiple ID strings. It works with my Abbree AR-63. Test it on your AR-63. If that works (fingers crossed), then I will have to test it with a few of the other radio models that this driver supports to make sure my changes didn't break the support for any of them.
Thank you for your help.
Jim KC9HI
Updated by Luke Stein over 1 year ago
Jim Unroe wrote:
The attached proposed driver module adds support for radio models that been seen with multiple ID strings. It works with my Abbree AR-63. Test it on your AR-63. If that works (fingers crossed), then I will have to test it with a few of the other radio models that this driver supports to make sure my changes didn't break the support for any of them.
No, thank you! Your attached proposed driver appears to work successfully for both "Download from Radio" and "Upload to Radio" for me (using the 2022-10-12 daily build).
Updated by Jim Unroe over 1 year ago
Luke Stein wrote:
Jim Unroe wrote:
The attached proposed driver module adds support for radio models that been seen with multiple ID strings. It works with my Abbree AR-63. Test it on your AR-63. If that works (fingers crossed), then I will have to test it with a few of the other radio models that this driver supports to make sure my changes didn't break the support for any of them.
No, thank you! Your attached proposed driver appears to work successfully for both "Download from Radio" and "Upload to Radio" for me (using the 2022-10-12 daily build).
That is good news. Let me dig out some of the other radios to get them tested, and if that goes well, then I can create a formal patch submit it to be included in CHIRP.
Jim KC9HI
Updated by Jim Unroe over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Patch submitted. Support will be in the next CHIRP daily build following acceptance.
Jim KC9HI
Updated by Anonymous over 1 year ago
- Status changed from Resolved to Closed
Applied in changeset commit:57cdcdf59345.