Bug #10085

Support for alternate 'identification string' on some Abbree AR-63 devices

Added by Luke Stein about 1 month ago. Updated about 1 month ago.

Status:Closed Start date:10/18/2022
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:Abbree AR-63

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

debug.log (33.9 kB) Luke Stein, 10/18/2022 05:47 pm

retevis_rt21_multiple_id_string_support.py (62.4 kB) Jim Unroe, 10/18/2022 06:10 pm

Associated revisions

Revision 3784:57cdcdf59345
Added by Jim Unroe about 1 month ago

[AR-63] Add support for multiple "identification strings"

It was discovered that not all Abbree AR-63 radios respond with the
same "identification string" (aka fingerprint).

This patch updates the retevis_rt21.py driver module to add multiple
fingerprint support.

fixes #10085

History

Updated by Jim Unroe about 1 month ago

  • Status changed from New to In Progress
  • Target version set to chirp-daily

I'm working on it. Stay tuned.

Jim KC9HI

Updated by Jim Unroe about 1 month 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 about 1 month 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 about 1 month 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 about 1 month 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 about 1 month ago

  • Status changed from Resolved to Closed

Applied in changeset 57cdcdf59345.

Also available in: Atom PDF