Bug #6757

problem reading data from WLN KD-C1 - Radio identification failed - (white model)

Added by Pablo Escobar 22 days ago. Updated 22 days ago.

Status:Feedback Start date:04/27/2019
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:WLN KD-C1

Description

Hello,

I am using CHIRP daily-20190424 installed from ubuntu PPA repository to configure WLN KD-C1

When I try "radio >> download from radio" I get the error message "Radio identification failed". I could workaround the problem by commenting these lines and then I can read the device configuration

The walkie that presents the problem is branded as WLN and is white. I have another pair branded as RADTEL (black color) that work perfectly fine without any workaround.

When I generate a debug log I get this:

[2019-04-27 11:14:23,374] chirp.drivers.retevis_rt22 - DEBUG: Incorrect model ID, got this:

000: 50 33 32 30 37 21 f8 ff   P3207!..

chirp.log (3.2 kB) Pablo Escobar, 04/27/2019 08:08 am

retevis_rt22_test.py (19.4 kB) Jim Unroe, 04/27/2019 10:03 am

chirp_failed_to_read_block_100.log (5.3 kB) Pablo Escobar, 04/27/2019 10:26 am

chirp_failed_to_read.log (5 kB) Pablo Escobar, 04/27/2019 10:26 am

History

Updated by Jim Unroe 22 days ago

  • Status changed from New to Feedback

Would you include the full debug.log file?

Updated by Pablo Escobar 22 days ago

I attach the full log file. thanks for looking into it.

Updated by Jim Unroe 22 days ago

  • File retevis_rt22_test.py added
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • Platform changed from Linux to All

Pablo,

Give this test driver a try...

1. save test driver to a convenient location
2. enable "Enable Developer Functions" in the Help menu
3. choose "Load Driver" in the File menu
4. locate and load the driver saved in step 1

Now try to download from and upload to your radio.

Note: Use of this test driver does not permanently change your CHIRP installation in any way. After you close CHIRP you will have to load this test driver again to access your radio.

Jim KC9HI

Updated by Pablo Escobar 22 days ago

I have tried your driver and I could download the first time. After this I tried to upload without doing any change and I got an error (sorry I didn't take note of this error)

After the error I can no longer download. I always get an error "failed to read block" with the new driver and also with the original driver. I attach a log file for driver

Is it safe to dump the firmware from my other walkie and copy it to this device to restore it to its original state? or how should I proceed? I did a quick test and the walkie seems to work fine.

Updated by Jim Unroe 22 days ago

Pablo Escobar wrote:

I have tried your driver and I could download the first time. After this I tried to upload without doing any change and I got an error (sorry I didn't take note of this error)

After the error I can no longer download. I always get an error "failed to read block" with the new driver and also with the original driver. I attach a log file for driver

Is it safe to dump the firmware from my other walkie and copy it to this device to restore it to its original state? or how should I proceed? I did a quick test and the walkie seems to work fine.

You can't dump the firmware for these radios using CHIRP. The firmware is not upgrade-able.

Is is safe to upload the image file from your other radio into this one? I don't know. I take it you didn't save the first successful download from this radio, right?

The only way to return this radio to its original state would be to upload the successful down from this radio. Uploading an image from another radio changes it to the state of the other radio.

I would try unplugging programming cable from computer (unplug from radio first) and plug it in again. Or you might even try rebooting computer.

In any case, this new issue is unrelated to the "Radio identification failed" problem the test driver addresses.

Jim KC9HI

Updated by Pablo Escobar 22 days ago

I have tried in windows virtual machine using the official software and I get similar problems. The software gets stuck and cannot complete to download (the download works fine with other walkies)

I tried to find if there is any way to reset the walkie to default settings but I couldn't find how to do it. I am out of ideas. It seems like the rom of the device is defective and I cannot read it? Maybe I could read it the first time just by chance?

I am going to contact the dealer

Updated by Jim Unroe 22 days ago

I tried to find if there is any way to reset the walkie to default settings but I couldn't find how to do it. I am out of ideas. It seems like the rom of the device is defective and I cannot read it? Maybe I could read it the first time just by chance?

Probably whatever prompted the change of the "radio identification" may have changed the timing slightly.

Jim

Updated by Pablo Escobar 22 days ago

Is there any workaround I could try to try to fix the timing issues?

Any similar case that is documented and I can read as reference?

Thanks in advance for any help or advice.

Also available in: Atom PDF