Bug #11004
closedRadtel RT-470 "Radio returned unknown identification string"
Added by F Let 12 months ago. Updated 11 months ago.
100%
Description
Hi,
while attempting to read from a Radtel RT-470 (firmware V2.00 hardware 11-V02) from Chirp (next-20231209 on Python 3.8.10, Linux Mint 20.3 Cinnamon)
got the message "Radio returned unknown identification string".
All works fine with a Baofeng UV-5R, so the problem does not come from the hardware/cable/port authorization/etc.
This is kind of frustrating as RT-470 is listed as "supported".
NO debug.log in ~/.chirp -- which in itself might be a bug. Please don't trash the bug report for this reason. chirp.config attached.
Thanks for any help.
Best
Files
| Help_Open-debug-log.png (45.1 KB) Help_Open-debug-log.png | Jim Unroe, 12/11/2023 08:21 AM | ||
| mml_jc8810-pcb2.py (49.5 KB) mml_jc8810-pcb2.py | Jim Unroe, 12/13/2023 04:46 AM | ||
| RT-470 Menu List v1.25a (00-51).txt (3.08 KB) RT-470 Menu List v1.25a (00-51).txt | Jim Unroe, 12/13/2023 04:49 AM | ||
| Radtel_RT-470_20231213.img (44.9 KB) Radtel_RT-470_20231213.img | F Let, 12/13/2023 12:57 PM | ||
| RT-470 Menu List v2.11a (00-57).txt (3.36 KB) RT-470 Menu List v2.11a (00-57).txt | F Let, 12/13/2023 01:02 PM | ||
| mml_jc8810-pcb2.py (48.9 KB) mml_jc8810-pcb2.py | Jim Unroe, 12/13/2023 06:22 PM | ||
| chirp_debug-4hnhvwgo.txt (4.32 KB) chirp_debug-4hnhvwgo.txt | Mark Wiseley, 12/19/2023 06:52 AM | ||
| mml_jc8810-pcb2-213a.py (50.4 KB) mml_jc8810-pcb2-213a.py | Jim Unroe, 12/19/2023 11:08 AM | ||
| chirp_debug-n6gckp_c.txt (4.2 KB) chirp_debug-n6gckp_c.txt | Mark Wiseley, 12/19/2023 11:25 AM |
Updated by F Let 12 months ago
Jim Unroe wrote in #note-1:
This is apparently a radio having the new PCB which has a new identification string that is unknown to CHIRP. The debug log is needed to determine what the identification string is.
Indeed. However, Chirp does not dump a debug.log file... Searched the whole file system, nothing.
This is what's printed in the console:
ERROR: Failed to clone: Radio returned unknown identification string
Traceback (most recent call last):
File "/home/user/.local/lib/python3.8/site-packages/chirp/wxui/clone.py", line 69, in run
self._fn()
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 479, in sync_in
data = do_download(self)
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 350, in do_download
_enter_programming_mode(radio)
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 291, in _enter_programming_mode
raise errors.RadioError("Radio returned unknown identification string")
chirp.errors.RadioError: Radio returned unknown identification string
Updated by F Let 12 months ago
F Let wrote in #note-2:
Jim Unroe wrote in #note-1:
This is apparently a radio having the new PCB which has a new identification string that is unknown to CHIRP. The debug log is needed to determine what the identification string is.
Indeed. However, Chirp does not dump a debug.log file... Searched the whole file system, nothing.
This is what's printed in the console:
ERROR: Failed to clone: Radio returned unknown identification string
Traceback (most recent call last):
File "/home/user/.local/lib/python3.8/site-packages/chirp/wxui/clone.py", line 69, in run
self._fn()
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 479, in sync_in
data = do_download(self)
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 350, in do_download
_enter_programming_mode(radio)
File "/home/user/.local/lib/python3.8/site-packages/chirp/drivers/mml_jc8810.py", line 291, in _enter_programming_mode
raise errors.RadioError("Radio returned unknown identification string")
chirp.errors.RadioError: Radio returned unknown identification string
Printed the 'ident' variable in mml_jc8810.py ==> value is b'\x00\x00\x00(\x00 \xd4\x04'
Updated by Jim Unroe 12 months ago
F Let wrote in #note-2:
Jim Unroe wrote in #note-1:
This is apparently a radio having the new PCB which has a new identification string that is unknown to CHIRP. The debug log is needed to determine what the identification string is.
Indeed. However, Chirp does not dump a debug.log file... Searched the whole file system, nothing.
What happens when you click Help -> Open debug log ?
Updated by Jim Unroe 12 months ago
- File Help_Open-debug-log.png Help_Open-debug-log.png added
F Let wrote in #note-5:
Jim Unroe wrote in #note-4:
What happens when you click Help -> Open debug log ?
There's no such menu entry.
Then you must running a very old classic CHIRP and not the current CHIRP-next. The latest is 20231209. Classic CHIRP is no longer supported and any updated will be for CHIRP-next only. So update and attach the debug.log file. Without having a physical radio in my possession, this is the only way I will know what the radio's response is.
Updated by F Let 12 months ago
Tried with the latest Windows version of Chirp-next (Chirp-next-231209 on Python 3.10.08.
This is what's dumped in the "open debug log" window:
[2023-12-13 11:03:20,942] chirp.logger - DEBUG: CHIRP next-20231209 on Win32 (Unknown 10.0:19044) (Python 3.10.8)
[2023-12-13 11:03:20,996] chirp.wxui - DEBUG: Using locale: fr_FR (318)
[2023-12-13 11:03:20,996] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: fr_FR (de,el,en_US,es,fr,hu,it,ja_JP,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2023-12-13 11:03:20,996] chirp.wxui - DEBUG: Translation loaded=True for wxstd: fr_FR (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-12-13 11:03:21,227] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19044-SP0 // CHIRP/next-20231209 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-12-13 11:03:21,597] chirp.wxui.main - INFO: Server reports next-20231209 is latest
[2023-12-13 11:03:26,783] chirp.wxui.clone - DEBUG: Using port 'COM13'
[2023-12-13 11:03:26,783] chirp.wxui.clone - DEBUG: Selected
[2023-12-13 11:03:26,783] chirp.wxui.clone - DEBUG: Serial opened: Serial
[2023-12-13 11:03:26,783] chirp.drivers.mml_jc8810 - DEBUG: download
[2023-12-13 11:03:26,852] chirp.drivers.mml_jc8810 - DEBUG: 000: 00 00 00 2c 00 20 d8 04 ...,....
[2023-12-13 11:03:26,852] chirp.wxui.clone - ERROR: Failed to clone: Radio returned unknown identification string
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 69, in run
File "chirp\drivers\mml_jc8810.py", line 479, in sync_in
File "chirp\drivers\mml_jc8810.py", line 350, in do_download
File "chirp\drivers\mml_jc8810.py", line 291, in _enter_programming_mode
chirp.errors.RadioError: Radio returned unknown identification string
[2023-12-13 11:03:29,721] chirp.wxui.clone - WARNING: Stopping clone thread
Updated by Jim Unroe 12 months ago
- File mml_jc8810-pcb2.py mml_jc8810-pcb2.py added
- File RT-470 Menu List v1.25a (00-51).txt RT-470 Menu List v1.25a (00-51).txt added
F Let wrote in #note-7:
Tried with the latest Windows version of Chirp-next (Chirp-next-231209 on Python 3.10.08.
This is what's dumped in the "open debug log" window:
Perfect. This is what was needed.
Give the attached test driver module a try to see if it will read and write to your radio. Please save the fist successful download, unedited, to a native CHIRP Radio Images (*.ing) file and then attach it to this issue. Here are instructions for how to use the test driver module: LoadingTestModules
Also, would you make a copy of the attached RT-470 Menu List and update it based on your firmware version? It will be used to see if there are any settings that have been added, removed or changed.
Updated by F Let 12 months ago
- File Radtel_RT-470_20231213.img Radtel_RT-470_20231213.img added
- File RT-470 Menu List v2.11a (00-57).txt RT-470 Menu List v2.11a (00-57).txt added
The test module worked for downloading factory configuration, changing channel names and uploading the modified config back to the radio. Cheers!
Files attached as requested.
Updated by Jim Unroe 12 months ago
- File mml_jc8810-pcb2.py mml_jc8810-pcb2.py added
F Let wrote in #note-9:
The test module worked for downloading factory configuration, changing channel names and uploading the modified config back to the radio. Cheers!
Files attached as requested.
Thanks for the feedback and the updated Menu List. After reviewing the list it would appear that only the PF key support needs to be updated. The attached file has the PF key updates. Please load this test driver module and check that the PF key settings match with what is selected in the radio.
Updated by Mark Wiseley 11 months ago
- File chirp_debug-4hnhvwgo.txt chirp_debug-4hnhvwgo.txt added
Hey all, new to this forum, but I picked up a new 470x the other day and all was good, then updated it from 2.11 to the new 2.13a. Now I'm having the same issue with Chirp as this bug reported. I have gone to the developer mode and tried this test module, but still same issue. I will attach the debug log. Thanks in advance for any help, hoping to figure out how to get rid of the squelch tail on some frequencies! :)
Updated by Jim Unroe 11 months ago
Mark Wiseley wrote in #note-12:
Hey all, new to this forum, but I picked up a new 470x the other day and all was good, then updated it from 2.11 to the new 2.13a. Now I'm having the same issue with Chirp as this bug reported. I have gone to the developer mode and tried this test module, but still same issue. I will attach the debug log. Thanks in advance for any help, hoping to figure out how to get rid of the squelch tail on some frequencies! :)
This new identification string will have to be added.
Updated by Jim Unroe 11 months ago
Jim Unroe wrote in #note-13:
Mark Wiseley wrote in #note-12:
Hey all, new to this forum, but I picked up a new 470x the other day and all was good, then updated it from 2.11 to the new 2.13a. Now I'm having the same issue with Chirp as this bug reported. I have gone to the developer mode and tried this test module, but still same issue. I will attach the debug log. Thanks in advance for any help, hoping to figure out how to get rid of the squelch tail on some frequencies! :)
This new identification string will have to be added.
In the mean time would you download the RT-470 Menu List v2.11a (00-57).txt list that is attached to this issue, make a copy and update it for the v2.13a firmware? Thanks.
Updated by Mark Wiseley 11 months ago
Jim Unroe wrote in #note-14:
Jim Unroe wrote in #note-13:
Mark Wiseley wrote in #note-12:
Hey all, new to this forum, but I picked up a new 470x the other day and all was good, then updated it from 2.11 to the new 2.13a. Now I'm having the same issue with Chirp as this bug reported. I have gone to the developer mode and tried this test module, but still same issue. I will attach the debug log. Thanks in advance for any help, hoping to figure out how to get rid of the squelch tail on some frequencies! :)
This new identification string will have to be added.
In the mean time would you download the RT-470 Menu List v2.11a (00-57).txt list that is attached to this issue, make a copy and update it for the v2.13a firmware? Thanks.
I'm really sorry as I want to help, but I can't figure out how to update that menu list? I have searched all over trying to figure out how?
Updated by Jim Unroe 11 months ago
Mark Wiseley wrote in #note-15:
I'm really sorry as I want to help, but I can't figure out how to update that menu list? I have searched all over trying to figure out how?
It is a text file of the menus of the radio and their choices. You go through the radios menus one-by-one to see if any were move around to different menu numbers, any new menus were added or any previous menus were removed. Then you check to see that the choices have remained the same and update any choices when you find that they are differet.
Updated by Jim Unroe 11 months ago
- File mml_jc8810-pcb2-213a.py mml_jc8810-pcb2-213a.py added
The attached test driver module should include support for the v2.13a identification string. How to use it:LoadingTestModules
Updated by Mark Wiseley 11 months ago
- File chirp_debug-n6gckp_c.txt chirp_debug-n6gckp_c.txt added
Jim Unroe wrote in #note-17:
The attached test driver module should include support for the v2.13a identification string. How to use it:LoadingTestModules
Ok, I will work on that. I also tried that test module, but I get the same error. Uploaded new debug. Thanks again!
Updated by Jim Unroe 11 months ago
Mark Wiseley wrote in #note-18:
Jim Unroe wrote in #note-17:
The attached test driver module should include support for the v2.13a identification string. How to use it:LoadingTestModules
Ok, I will work on that. I also tried that test module, but I get the same error. Uploaded new debug. Thanks again!
My bad. You should have opened a different ticket for the RT-470X. This one is for the RT-470 so I added it to the RT-470 instead of RT-470X.
Updated by Mark Wiseley 11 months ago
Jim Unroe wrote in #note-19:
Mark Wiseley wrote in #note-18:
Jim Unroe wrote in #note-17:
The attached test driver module should include support for the v2.13a identification string. How to use it:LoadingTestModules
Ok, I will work on that. I also tried that test module, but I get the same error. Uploaded new debug. Thanks again!
My bad. You should have opened a different ticket for the RT-470X. This one is for the RT-470 so I added it to the RT-470 instead of RT-470X.
Shoot sorry. Would you like me to open up a new ticket?
Updated by Mark Wiseley 11 months ago
Mark Wiseley wrote in #note-20:
Jim Unroe wrote in #note-19:
Mark Wiseley wrote in #note-18:
Jim Unroe wrote in #note-17:
The attached test driver module should include support for the v2.13a identification string. How to use it:LoadingTestModules
Ok, I will work on that. I also tried that test module, but I get the same error. Uploaded new debug. Thanks again!
My bad. You should have opened a different ticket for the RT-470X. This one is for the RT-470 so I added it to the RT-470 instead of RT-470X.
Shoot sorry. Would you like me to open up a new ticket?
On a positive note, if I choose the 470 it does let me read the radio now. Not sure how different they are so I won't write anything back to the radio until I hear from you. Thanks again and sorry for the mixup.
Updated by Mark Wiseley 11 months ago
Updated by Anonymous 11 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|98682e9a04bc4d931d32f42d1f172132e6f9ced4.