Bug #6101

Zastone X6 not able to be programmed

Added by Ean Wallander 8 months ago. Updated 7 months ago.

Status:New Start date:09/10/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:Windows
Model affected:(All models)

Description

Hello
I am trying to program 2 brand new Zastone X6's. Both of them give the same error when I am trying to download from radio. The error is "Radio returned unknown identification string". I have programmed a X6 in the past about a month ago with no problems. I have tested the cable from the computer to the radios with other radios to verify it works. Because I was able to program an X6 before and now I can't, I am wondering if the problem was in updating CHIRP. Any help would be appreciated. Thanks

debug.log (38.6 kB) Ean Wallander, 09/10/2018 02:35 pm

program_defect_KD-C1.py (19.1 kB) J A, 10/15/2018 04:26 am

History

Updated by J A 8 months ago

I just got 2 WLN KD-C1 (same as X6 rt22 etc etc) and one of them returned "Radio returned unknown identification string".
Did some logging and the ID string started with P3xxx3 but the xxx was spaces (or something else).
So I tested a modified retevis_rt22.py in development mode and it worked.

Replaced
ident.startswith("P32073")
with
ident.startswith("P3")

Updated by Ean Wallander 8 months ago

Thank you for your response. I am new to this and can not seem to figure out how to change the ID string. Would I have to be in development mode to do this?

Updated by J A 8 months ago

Ean Wallander wrote:

Thank you for your response. I am new to this and can not seem to figure out how to change the ID string. Would I have to be in development mode to do this?

You can edit retevis_rt22.py directly as a quick workaround, but I don't know the consequences (warning :) ). But it worked for me :)

Updated by Ean Wallander 8 months ago

I have tried to figure out what you are saying to do, but am unable to follow. Could you please give even more simple directions and hopefully I can walk myself through it. Thank you very much for your time and expertise.

Updated by Giuseppe Ravasio 8 months ago

Same problem here.
Olved with J A patch.

I hope that the change will be merged to the chirp repo

Updated by J A 7 months ago

Attached file loaded in development mode worked for me. Proceed at your own risk.

Also available in: Atom PDF