New Model #9903
closed"G63" TXQ-G63 / Talinfone-G63 / Jianpai-MDLG63 / Wurui-G63 / Abbree-AR63 - Mini UHF 16 Channel Radio
100%
Description
Anyone yet working on a CHIRP interface for these 'G63' models?
They all appear to use the same hardware with different name branding.
AKA:
Talinfone G63
Jianpai MDL-G63
TXQ G63
Wurui G63
Abbree AR-63
I am willing to do anything I can to help with this project!
YouTube:
https://www.youtube.com/watch?v=ui2zSmHkV70
https://www.youtube.com/watch?v=ZDLOvLyNtQs
Sources:
https://www.anyradios.com/product/talinfone-g63-automatic-wireless-copy-frequency-uhf-mini-walkie-talkie/
https://www.aliexpress.com/item/3256803943520072.html?gatewayAdapt=4itemAdapt
Files
Updated by Andy B over 2 years ago
Anyone??? Anyone?? Bueller? Bueller?
Radios are cheap, can drop ship one to a developer....
Updated by Jim Unroe over 2 years ago
- Status changed from New to Feedback
It looks similar to a typical 16-channel UHF radio, just in a different case. I just submitted a patch to add a pair of similar radios. Probably around a half-a-dozen models or more altogether.
Jim KC9HI
Updated by Matthew Davies over 2 years ago
The programming app you have for download is older than mine. Mine's 2022.6.6 and it does not require a password and it's all in English. It's made for the G63 but it works on the similar models. Look around for it.
Updated by Jim Unroe about 2 years ago
- File retevis_rt21_ar-63_#1.py retevis_rt21_ar-63_#1.py added
- Status changed from Feedback to In Progress
- Assignee set to Jim Unroe
- Target version set to chirp-legacy
Please test the attached custom driver module to see if it works for your radio.
Vendor: Abbree
Model: AR-63
Here is how you use the custom driver module.
save the custom driver module to a convenient location (DO NOT RIGHT-CLICK THE LINK. Left-click the link and then on the page that loads, left-click the download link near the top left corner.)¶
click Help¶
enable Enable Developer Functions¶
click File¶
click Load Module¶
locate and load custom driver module that was saved in step 1¶
The CHIRP background will now be red to indicate it is running with a externally loaded driver module. You can now test the custom driver module.
Note: The test driver module does not permanently change your CHIRP installation in any way. Every time you load CHIRP you must load this driver module to have access to its fixes or added features.
Jim KC9HI
Updated by Jim Unroe about 2 years ago
- File Abbree_AR-63.img Abbree_AR-63.img added
Add CHIRP Radio Images (*.img) file.
Jim KC9HI
Updated by Jim Unroe about 2 years 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 2 years ago
- Status changed from Resolved to Closed
Applied in changeset commit:9228bc6753c0.
Updated by Luke Stein about 2 years ago
Thank you to Jim for your work on this. I just tried the 10/12 Chirp build with my Abbree AR-63 (selecting Vendor "Abbree" and Model "AR-63") and received
An error has occurred
Radio returned unknown identification string
Not sure if there's any additional info I can help provide, if this is user error, or perhaps reflects variation across different versions of the radio.
All the best,
Luke
Updated by Jim Unroe about 2 years ago
Luke Stein wrote:
Thank you to Jim for your work on this. I just tried the 10/12 Chirp build with my Abbree AR-63 (selecting Vendor "Abbree" and Model "AR-63") and received
An error has occurred
Radio returned unknown identification stringNot sure if there's any additional info I can help provide, if this is user error, or perhaps reflects variation across different versions of the radio.
All the best,
Luke
Attach the debug.log file. Hopefully it shows what the "identification string" is so it can be added to the list.
The "How to report issues":https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues page explains how to located the debug.log file.
Jim KC9HI
Updated by Luke Stein about 2 years ago
Thank you Jim, and sorry for the incomplete but report. I'm hoping that the fourth line of this excerpt gets us there. Please let me know!
[2022-10-18 11:34:58,711] chirp.ui.mainapp - DEBUG: User selected Abbree AR-63 on port /dev/cu.usbserial-142330 [2022-10-18 11:34:58,723] chirp.ui.clone - DEBUG: Clone thread started [2022-10-18 11:34:58,724] chirp.drivers.retevis_rt21 - DEBUG: download [2022-10-18 11:34:58,743] chirp.drivers.retevis_rt21 - DEBUG: 000: 50 33 32 30 37 33 03 ff P32073.. [2022-10-18 11:34:58,745] chirp.ui.reporting - DEBUG: Reporting exception [2022-10-18 11:34:58,745] chirp.ui.common - ERROR: -- Exception: -- [2022-10-18 11:34:58,746] chirp.ui.common - ERROR: Traceback (most recent call last): File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/clone.py", line 255, in run self.__radio.sync_in() File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 701, in sync_in data = do_download(self) File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 588, in do_download _enter_programming_mode(radio) File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 510, in _enter_programming_mode raise errors.RadioError("Radio returned unknown identification string") RadioError: Radio returned unknown identification string [2022-10-18 11:34:58,746] chirp.ui.common - ERROR: ---------------- [2022-10-18 11:34:58,746] chirp.ui.clone - ERROR: Clone failed: Radio returned unknown identification string [2022-10-18 11:34:58,752] chirp.ui.clone - DEBUG: Clone thread ended [2022-10-18 11:34:58,760] chirp.ui.reporting - DEBUG: Reporting model usage: Abbree_AR-63,download,True [2022-10-18 11:34:58,761] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio returned unknown identification string --- [2022-10-18 11:34:58,761] chirp.ui.reporting - DEBUG: Reporting exception [2022-10-18 11:34:58,762] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "/Applications/CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw", line 79, inos.putenv("LANG", langs[0]) IndexError: list index out of range
Updated by Luke Stein about 2 years ago
Thank you Jim, and sorry for the incomplete but report. I'm hoping that the fourth line of this excerpt gets us there. Please let me know!
[2022-10-18 11:34:58,711] chirp.ui.mainapp - DEBUG: User selected Abbree AR-63 on port /dev/cu.usbserial-142330 [2022-10-18 11:34:58,723] chirp.ui.clone - DEBUG: Clone thread started [2022-10-18 11:34:58,724] chirp.drivers.retevis_rt21 - DEBUG: download [2022-10-18 11:34:58,743] chirp.drivers.retevis_rt21 - DEBUG: 000: 50 33 32 30 37 33 03 ff P32073.. [2022-10-18 11:34:58,745] chirp.ui.reporting - DEBUG: Reporting exception [2022-10-18 11:34:58,745] chirp.ui.common - ERROR: -- Exception: -- [2022-10-18 11:34:58,746] chirp.ui.common - ERROR: Traceback (most recent call last): File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/clone.py", line 255, in run self.__radio.sync_in() File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 701, in sync_in data = do_download(self) File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 588, in do_download _enter_programming_mode(radio) File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/retevis_rt21.py", line 510, in _enter_programming_mode raise errors.RadioError("Radio returned unknown identification string") RadioError: Radio returned unknown identification string [2022-10-18 11:34:58,746] chirp.ui.common - ERROR: ---------------- [2022-10-18 11:34:58,746] chirp.ui.clone - ERROR: Clone failed: Radio returned unknown identification string [2022-10-18 11:34:58,752] chirp.ui.clone - DEBUG: Clone thread ended [2022-10-18 11:34:58,760] chirp.ui.reporting - DEBUG: Reporting model usage: Abbree_AR-63,download,True [2022-10-18 11:34:58,761] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio returned unknown identification string --- [2022-10-18 11:34:58,761] chirp.ui.reporting - DEBUG: Reporting exception [2022-10-18 11:34:58,762] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "/Applications/CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw", line 79, inos.putenv("LANG", langs[0]) IndexError: list index out of range
Updated by Jim Unroe about 2 years ago
Luke Stein wrote:
Thank you Jim, and sorry for the incomplete but report. I'm hoping that the fourth line of this excerpt gets us there. Please let me know!
Yes. Thanks for attaching the debug.log file. This is exactly what I was hoping to see. The 7th character of the identification string is different as shown below.
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
I'm not sure, yet, how I want to go about supporting this difference. So in the mean time, would you do the following.
Since this issue is closed, would you open a new issue? Just say something about "add support for additional 'identification string' found for the Abbree AR-63" and attach the same debug.log file as the one that you added to this issue.¶
After you have added the new issue, once I have developed what I consider a "permanent" fix, I will attach to your newly opened issue. I will need you to test it and provide feedback.¶
While you are waiting for me to add what I eventually develop as a "permanent" fix to your newly opened issue, I have provided a "hack" of the current driver that should allow you to program your radio. Just follow the instruction in note-4 above substituting the filename for this driver.¶
Jim KC9HI
Updated by Luke Stein about 2 years ago
Jim Unroe wrote:
Since this issue is closed, would you open a new issue? Just say something about "add support for additional 'identification string' found for the Abbree AR-63" and attach the same debug.log file as the one that you added to this issue.¶
After you have added the new issue, once I have developed what I consider a "permanent" fix, I will attach to your newly opened issue. I will need you to test it and provide feedback.¶
While you are waiting for me to add what I eventually develop as a "permanent" fix to your newly opened issue, I have provided a "hack" of the current driver that should allow you to program your radio. Just follow the instruction in note-4 above substituting the filename for this driver.¶
Thanks, Jim! Just documenting here for completeness: Opened Issue #10085 , and the "hacked" driver you provided seems to both read from and write to my radio just fine. Thanks! I'm set up to watch the old and new issues and will test a new version when you are ready.