Project

General

Profile

Actions

Bug #11164

closed

Radtel RT-470 10W NEW PCB / V2.13A Firmware ERROR: Failed to clone: Radio returned unknown identification string

Added by Simon Roma 10 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/13/2024
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Radtel RT-470
Platform:
Windows
I read the instructions above:
Yes

Description

I have a device Radtel RT-470 10W NEW PCB / V2.13A Firmware and when I try to connect I get:
ERROR: Failed to clone: Radio returned unknown identification string.
I browsed through other reports for this model but it didn't help in my case


Files

chirp_debug-2qonhqn4.txt (886 Bytes) chirp_debug-2qonhqn4.txt Simon Roma, 02/14/2024 12:44 PM
chirp_debug-0c8brvr5.txt (2.55 KB) chirp_debug-0c8brvr5.txt Simon Roma, 02/14/2024 12:48 PM
chirp_debug-fobebq12.txt (2.43 KB) chirp_debug-fobebq12.txt Simon Roma, 02/14/2024 10:01 PM
mml_jc8810_rt470_fw213a.py (49.1 KB) mml_jc8810_rt470_fw213a.py Jim Unroe, 02/15/2024 05:18 AM
HI-8811 Menu List (00-56) - FW V2.00.txt (3.47 KB) HI-8811 Menu List (00-56) - FW V2.00.txt Jim Unroe, 02/15/2024 05:23 AM
Actions #1

Updated by Jim Unroe 10 months ago

Please make an attempt to get another debug log file. For some reason the attached debug log does not show a valid identification string.

Actions #4

Updated by Jim Unroe 10 months ago

Still not looking like a valid identification string.

Every valid identification string up to this point regardless of if it is PCB1 or PCB2 is 8 bytes long and starts with "00 00 00". What CHIRP expects for an RT-470 with NEW PCB / V2.11A Firmware is:

00 00 00 2C 00 20 D8 04

What the debug log shows for the received identification string from your radio is:

[2024-02-13 20:20:16,099] chirp.drivers.mml_jc8810 - DEBUG: 000: 38 ec 78 06 c8 72         8.x..r..

These 6 bytes do not resemble any of the (21) 8-byte identification strings that CHIRP currently knows about.

One thing that I noticed last night experimenting with my Hiroyasu HI-8811 (a relabeled RT-470L) with NEW PCB and firmware 2.00A is that the first time that CHIRP would ask the radio to go into clone mode, it sent an identification string that CHIRP doesn't know about, yet. But if I immediately made a second attempt, the second request returned an identification string that CHIRP did recognize and the download completed successfully. So would you try to download after the first one fails? If it fails attach the new debug log with containing the back-to-back failures. Thanks.

Also, does the Radtel factory programming software work with your radio?

Actions #5

Updated by Simon Roma 10 months ago

Yes, the radio works fine with the manufacturer's program. This log file should be good: DEBUG: 000: 00 00 00 36 00 20 dc 04 ...6....

Updated by Jim Unroe 10 months ago

Simon Roma wrote in #note-5:

Yes, the radio works fine with the manufacturer's program. This log file should be good: DEBUG: 000: 00 00 00 36 00 20 dc 04 ...6....

Awesome. Thanks.

I have attached a test module that should read from/write to your radio. How to use it: LoadingTestModules

I would appreciate if you would compare the menus in your radio to those in the attached Menu List and edit the list as needed to match your radio. This will hopefully uncover any changes made to the menus by the firmware that will also need to be accounted for in CHIRP besides the identification string. Thanks.

Actions #7

Updated by Simon Roma 10 months ago

Thank you, now it's OK, the connection was successful :). I will check the MENU and let you know. Thank you.

Actions #8

Updated by Jim Unroe 9 months ago

Simon Roma wrote in #note-7:

Thank you, now it's OK, the connection was successful :). I will check the MENU and let you know. Thank you.

Are you making any progress on the menu list? I would like to get this submitted so the ticket can be closed.

Actions #9

Updated by Anonymous 9 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF