Project

General

Profile

Actions

Bug #6757

closed

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

Added by Pablo Escobar about 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
04/27/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
WLN KD-C1, Retevis RT22
Platform:
All
Debug Log:
I read the instructions above:

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":https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/retevis_rt22.py#L137 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!..

Files

chirp.log (3.2 KB) chirp.log Pablo Escobar, 04/27/2019 08:08 AM
retevis_rt22_test.py (19.4 KB) retevis_rt22_test.py Jim Unroe, 04/27/2019 10:03 AM
chirp_failed_to_read_block_100.log (5.29 KB) chirp_failed_to_read_block_100.log Pablo Escobar, 04/27/2019 10:26 AM
chirp_failed_to_read.log (5.03 KB) chirp_failed_to_read.log Pablo Escobar, 04/27/2019 10:26 AM
debug.log (46.9 KB) debug.log Jan NL, 04/11/2020 11:05 AM

Related issues

Is duplicate of Bug #6747: Retevis RT22 New firmware "Radio Identification Failed"Feedback04/26/2019

Actions
Actions #1

Updated by Jim Unroe about 5 years ago

  • Status changed from New to Feedback

Would you include the full debug.log file?

Actions #2

Updated by Pablo Escobar about 5 years ago

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

Actions #3

Updated by Jim Unroe about 5 years ago

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

Actions #4

Updated by Pablo Escobar about 5 years 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.

Actions #5

Updated by Jim Unroe about 5 years 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

Actions #6

Updated by Pablo Escobar about 5 years 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

Actions #7

Updated by Jim Unroe about 5 years 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

Actions #8

Updated by Pablo Escobar about 5 years 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.

Actions #9

Updated by Heath Petty almost 5 years ago

I am also hitting this issue with a black model. I tried the rt21 driver, since it identifies as a P3207, but changed the initial string in the enter programming mode function to match the string in the rt22 driver:

def _rt21_enter_programming_mode(radio):
    serial = radio.pipe

    try:
        #serial.write("PRMZUNE")
        serial.write("PROGRGS")
        ack = serial.read(1)
    except:
        raise errors.RadioError("Error communicating with radio")

This read something from the radio, but it did not read the right thing because chirp threw an error:

RadioError: Failed to read block at 0100

Forging ahead, I added a frequency in channel 1, and wrote it to the radio. The write succeeded, but it changed the voice to chinese.

I don't mind hacking on this, but I'm not sure how to figure out what I need to tweak to get it to talk to this radio. Anyone have any clues?

Actions #10

Updated by Heath Petty almost 5 years ago

After some hacking around, I have it kind of working. The issue I'm still seeing is that the settings tab is not being populated after I read the config from the radio. Everything else is good.

To get the radio to a good state, I had to use the programming software here on a windows 10 virtual machine (it will also work just fine on a regular windows machine):

http://www.uv3r.com/images/RT22-programming-software.zip

Once I re did the settings (and put it back into english). I did a serial dump of a download operation. Everything seemed the same as before, just a different id. I made the following change to the chirp/drivers/retevis_rt22.py file:

I changed the line that read:

_fileid = ["P32073", "P3" + "\x00\x00\x00" + "3"]

to read:

_fileid = ["P32073", "P3" + "\x00\x00\x00" + "3", "P3207!"]
Actions #11

Updated by Jim Unroe almost 5 years ago

Retevis is sending me a current RT22 for use in troubleshooting.

Jim KC9HI

Actions #12

Updated by T B over 4 years ago

I have newer versions of the WLN KD-C1 and HESENATE HT-U222. Both identify as P3207!. The test driver (retevis_rt22_test.py) was successful in reading and writing to both radios. Thanks for your help as these are great little UHF radios! Please let me know if I can help with any further testing.

Actions #13

Updated by T B over 4 years ago

Writing to the HESENATE HT-U222 failed setting the radio ID. Trying to read from the updated radio would give the following:
DEBUG: Incorrect model ID, got this:

000: 04 00 05 02 ff ff f8 ff ........

I modified the test driver to the following so chirp can read the updated radio with the empty ID field:

_fileid = ["P32073", "P3" + "\x00\x00\x00" + "3", "P3207!", ""]

Actions #14

Updated by Bryan Murdock over 4 years ago

Hi, I just got a new WLN KD-C1 radio and I too am getting the "Radio identification failed" error when I attempt to download from radio. I'm running CHIRP daily-20190718. I'm new to debugging chirp problems, but if there is anything I can do to help please let me know.

Actions #15

Updated by Bryan Murdock over 4 years ago

Here is the debug log that I got:

[2019-08-08 22:29:36,552] chirp.logger - DEBUG: log level=10
[2019-08-08 22:29:36,552] chirp.logger - DEBUG: CHIRP daily-20190718 on Linux malo 5.2.5-arch1-1-ARCH #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019 x86_64 (Python 2.7.16)
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,725] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,726] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-08-08 22:29:36,727] chirp.ui.reporting - DEBUG: Checking for updates
[2019-08-08 22:29:36,855] chirp.ui.reporting - DEBUG: Server reports version daily-20190718 is latest
[2019-08-08 22:29:43,432] chirp.ui.mainapp - DEBUG: User selected WLN KD-C1 on port /dev/ttyUSB1
[2019-08-08 22:29:43,436] chirp.ui.clone - DEBUG: Clone thread started
[2019-08-08 22:29:43,437] chirp.drivers.retevis_rt22 - DEBUG: download
[2019-08-08 22:29:43,487] chirp.drivers.retevis_rt22 - DEBUG: Incorrect model ID, got this:

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

[2019-08-08 22:29:43,489] chirp.ui.reporting - DEBUG: Reporting exception
[2019-08-08 22:29:43,489] chirp.ui.common - ERROR: -- Exception: --
[2019-08-08 22:29:43,491] chirp.ui.common - ERROR: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/chirp/ui/clone.py", line 256, in run
    self.__radio.sync_in()
  File "/usr/lib/python2.7/site-packages/chirp/drivers/retevis_rt22.py", line 331, in sync_in
    data = do_download(self)
  File "/usr/lib/python2.7/site-packages/chirp/drivers/retevis_rt22.py", line 230, in do_download
    _rt22_enter_programming_mode(radio)
  File "/usr/lib/python2.7/site-packages/chirp/drivers/retevis_rt22.py", line 139, in _rt22_enter_programming_mode
    raise errors.RadioError("Radio identification failed.")
RadioError: Radio identification failed.

[2019-08-08 22:29:43,492] chirp.ui.common - ERROR: ----------------
[2019-08-08 22:29:43,492] chirp.ui.clone - ERROR: Clone failed: Radio identification failed.
[2019-08-08 22:29:43,780] chirp.ui.clone - DEBUG: Clone thread ended
[2019-08-08 22:29:43,781] chirp.ui.reporting - DEBUG: Reporting model usage: WLN_KD-C1,download,True
[2019-08-08 22:29:43,784] chirp.ui.reporting - DEBUG: Reporting exception
[2019-08-08 22:29:43,785] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio identification failed. ---
[2019-08-08 22:29:43,787] chirp.ui.inputdialog - ERROR: None

[2019-08-08 22:29:43,787] chirp.ui.inputdialog - ERROR: ----------------------------

Actions #16

Updated by Peter Goodricke over 4 years ago

Ive just got 2 new WLN KD-C1 and have connected a Saleae and between
Send P R O G S 2
Receive 6 P 3 2 0 7 ! 0XF8 0XFF

and its rejected by CHIRP
The progam as suppied from
genuine software provided by WLN at http://www.kai-li.com/uploads/KD-C1_SETUP%201.2.rar
Send PROGS PROGS
Receive 6 P3207!0XF80XFF

Actions #17

Updated by Jan NL about 4 years ago

I have two new WLN KD-C1 that have the "Radio identification failed" issue.

Version is CHIRP daily-20200409 on Ubuntu Linux.

Cable, software and connections are confirmed to be working on a KD-C1 that I already had.

Model number of the working version is the same as of the non-working (all three KD-C1, not KD-C1 plus)

Tried the suggestion above and loaded the driver.
This does not work as the Chirp interface turns red and becomes unresponsive.

Log file is attached.
Both non-working porto's have the same behavior.

Greetings from The Netherlands, Jan

A bad session goes like this:

[2020-04-11 19:51:03,529] chirp.ui.mainapp - DEBUG: User selected WLN KD-C1 on port /dev/ttyUSB0
[2020-04-11 19:51:03,546] chirp.ui.clone - DEBUG: Clone thread started
[2020-04-11 19:51:03,547] chirp.drivers.retevis_rt22 - DEBUG: download
[2020-04-11 19:51:03,599] chirp.drivers.retevis_rt22 - DEBUG: Incorrect model ID, got this:

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

[2020-04-11 19:51:03,600] chirp.ui.reporting - DEBUG: Reporting exception
[2020-04-11 19:51:03,600] chirp.ui.common - ERROR: -- Exception: --
[2020-04-11 19:51:03,601] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/retevis_rt22.py", line 331, in sync_in
data = do_download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/retevis_rt22.py", line 230, in do_download
_rt22_enter_programming_mode(radio)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/retevis_rt22.py", line 139, in _rt22_enter_programming_mode
raise errors.RadioError("Radio identification failed.")
RadioError: Radio identification failed.

[2020-04-11 19:51:03,601] chirp.ui.common - ERROR: ----------------
[2020-04-11 19:51:03,601] chirp.ui.clone - ERROR: Clone failed: Radio identification failed.
[2020-04-11 19:51:03,602] chirp.ui.clone - DEBUG: Clone thread ended
[2020-04-11 19:51:03,603] chirp.ui.reporting - DEBUG: Reporting model usage: WLN_KD-C1,download,True
[2020-04-11 19:51:03,604] chirp.ui.reporting - DEBUG: Reporting exception
[2020-04-11 19:51:03,604] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio identification failed. ---
[2020-04-11 19:51:03,604] chirp.ui.inputdialog - ERROR: None

A good session goes like this:

[2020-04-11 19:53:04,226] chirp.ui.mainapp - DEBUG: User selected WLN KD-C1 on port /dev/ttyUSB0
[2020-04-11 19:53:04,241] chirp.ui.clone - DEBUG: Clone thread started
[2020-04-11 19:53:04,242] chirp.drivers.retevis_rt22 - DEBUG: download
[2020-04-11 19:53:04,306] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0000...
[2020-04-11 19:53:04,412] chirp.drivers.retevis_rt22 - DEBUG: Address: 0000
[2020-04-11 19:53:04,412] chirp.drivers.retevis_rt22 - DEBUG: 000: ff ff ff ff ff ff ff ff ........
008: ff ff ff ff 00 ff 00 00 ........
016: 25 06 60 44 25 06 60 44 %.D%.D
024: ff ff ff ff 00 ef 0d 00 ........
032: 75 18 60 44 75 18 60 44 u.Du.D
040: ff ff ff ff 00 ef 1a 00 ........
048: 25 31 60 44 25 31 60 44 %1D%1D
056: ff ff ff ff 00 ef 27 00 ......'.

[2020-04-11 19:53:04,412] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0040...
[2020-04-11 19:53:04,519] chirp.drivers.retevis_rt22 - DEBUG: Address: 0040
[2020-04-11 19:53:04,519] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 43 60 44 75 43 60 44 uCDuCD
008: ff ff ff ff 00 ef 34 00 ......4.
016: 25 56 60 44 25 56 60 44 %VD%VD
024: ff ff ff ff 00 ef 41 00 ......A.
032: 75 68 60 44 75 68 60 44 uhDuhD
040: ff ff ff ff 00 ef 4e 00 ......N.
048: 25 81 60 44 25 81 60 44 %.D%.D
056: ff ff ff ff 00 ef 5b 00 ......[.

[2020-04-11 19:53:04,519] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0080...
[2020-04-11 19:53:04,625] chirp.drivers.retevis_rt22 - DEBUG: Address: 0080
[2020-04-11 19:53:04,625] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 93 60 44 75 93 60 44 u.Du.D
008: ff ff ff ff 00 ef 68 00 ......h.
016: 25 06 61 44 25 06 61 44 %.aD%.aD
024: ff ff ff ff 00 ef 75 00 ......u.
032: 75 18 61 44 75 18 61 44 u.aDu.aD
040: ff ff ff ff 00 ef 82 00 ........
048: 25 31 61 44 25 31 61 44 %1aD%1aD
056: ff ff ff ff 00 ef 8f 00 ........

[2020-04-11 19:53:04,625] chirp.drivers.retevis_rt22 - DEBUG: Reading block 00c0...
[2020-04-11 19:53:04,732] chirp.drivers.retevis_rt22 - DEBUG: Address: 00c0
[2020-04-11 19:53:04,732] chirp.drivers.retevis_rt22 - DEBUG: 000: 25 06 60 44 25 06 10 44 %.D%..D
008: 29 28 29 28 00 ef 9c 00 )()(....
016: 75 93 60 44 75 93 10 44 u.
Du..D
024: ec 29 ec 29 00 ef a9 00 .).)....
032: 75 93 60 44 75 93 10 44 u.Du..D
040: 56 03 56 03 00 ef b6 00 V.V.....
048: 75 93 60 44 75 93 60 44 u.
Du.`D
056: 55 04 55 04 00 ef c3 00 U.U.....

[2020-04-11 19:53:04,732] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0100...
[2020-04-11 19:53:04,838] chirp.drivers.retevis_rt22 - DEBUG: Address: 0100
[2020-04-11 19:53:04,838] chirp.drivers.retevis_rt22 - DEBUG: 000: 00 00 32 43 00 00 32 43 ..2C..2C
008: ff ff ff ff 00 ff d0 00 ........
016: 00 00 00 00 00 00 00 00 ........
024: 00 00 00 00 00 00 00 00 ........
032: 00 00 00 00 00 00 00 00 ........
040: 00 00 00 00 00 00 00 02 ........
048: 04 02 02 03 04 01 01 06 ........
056: 04 00 05 02 ff ff 00 02 ........

[2020-04-11 19:53:04,838] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0140...
[2020-04-11 19:53:04,944] chirp.drivers.retevis_rt22 - DEBUG: Address: 0140
[2020-04-11 19:53:04,944] chirp.drivers.retevis_rt22 - DEBUG: 000: 04 02 02 03 04 01 01 06 ........
008: 04 00 05 02 ff ff 00 02 ........
016: 01 c1 07 00 85 b5 19 84 ........
024: 65 00 11 00 00 01 16 00 e.......
032: 04 02 02 03 04 01 01 06 ........
040: 04 00 05 02 ff ff 00 02 ........
048: 04 02 02 03 04 01 01 06 ........
056: 04 00 05 02 ff ff ff ff ........

[2020-04-11 19:53:04,945] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0180...
[2020-04-11 19:53:05,050] chirp.drivers.retevis_rt22 - DEBUG: Address: 0180
[2020-04-11 19:53:05,050] chirp.drivers.retevis_rt22 - DEBUG: 000: 04 02 02 03 04 01 01 06 ........
008: 04 00 05 02 ff ff ff ff ........
016: 01 c1 07 00 85 b5 19 84 ........
024: 65 00 11 00 00 01 16 00 e.......
032: 04 02 02 03 04 01 01 06 ........
040: 04 00 05 02 ff ff ff ff ........
048: 04 02 02 03 04 01 01 06 ........
056: 04 00 05 02 ff ff ff ff ........

[2020-04-11 19:53:05,051] chirp.drivers.retevis_rt22 - DEBUG: Reading block 01c0...
[2020-04-11 19:53:05,157] chirp.drivers.retevis_rt22 - DEBUG: Address: 01c0
[2020-04-11 19:53:05,157] chirp.drivers.retevis_rt22 - DEBUG: 000: 04 02 02 03 04 01 01 06 ........
008: 04 00 05 02 ff ff ff ff ........
016: 01 c1 07 00 85 b5 19 84 ........
024: 65 00 11 00 00 01 16 00 e.......
032: 04 02 02 03 04 01 01 06 ........
040: 04 00 05 02 ff ff ff ff ........
048: 04 02 02 03 04 01 01 06 ........
056: 04 00 05 02 ff ff ff ff ........

[2020-04-11 19:53:05,157] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0200...
[2020-04-11 19:53:05,264] chirp.drivers.retevis_rt22 - DEBUG: Address: 0200
[2020-04-11 19:53:05,264] chirp.drivers.retevis_rt22 - DEBUG: 000: ff ff ff ff ff ff ff ff ........
008: ff ff ff ff 00 ff 00 00 ........
016: 25 06 60 44 25 06 60 44 %.D%.D
024: ff ff ff ff 00 ef 0d 00 ........
032: 75 18 60 44 75 18 60 44 u.Du.D
040: ff ff ff ff 00 ef 1a 00 ........
048: 25 31 60 44 25 31 60 44 %1D%1D
056: ff ff ff ff 00 ef 27 00 ......'.

[2020-04-11 19:53:05,264] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0240...
[2020-04-11 19:53:05,371] chirp.drivers.retevis_rt22 - DEBUG: Address: 0240
[2020-04-11 19:53:05,371] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 43 60 44 75 43 60 44 uCDuCD
008: ff ff ff ff 00 ef 34 00 ......4.
016: 25 56 60 44 25 56 60 44 %VD%VD
024: ff ff ff ff 00 ef 41 00 ......A.
032: 75 68 60 44 75 68 60 44 uhDuhD
040: ff ff ff ff 00 ef 4e 00 ......N.
048: 25 81 60 44 25 81 60 44 %.D%.D
056: ff ff ff ff 00 ef 5b 00 ......[.

[2020-04-11 19:53:05,371] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0280...
[2020-04-11 19:53:05,478] chirp.drivers.retevis_rt22 - DEBUG: Address: 0280
[2020-04-11 19:53:05,478] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 93 60 44 75 93 60 44 u.Du.D
008: ff ff ff ff 00 ef 68 00 ......h.
016: 25 06 61 44 25 06 61 44 %.aD%.aD
024: ff ff ff ff 00 ef 75 00 ......u.
032: 75 18 61 44 75 18 61 44 u.aDu.aD
040: ff ff ff ff 00 ef 82 00 ........
048: 25 31 61 44 25 31 61 44 %1aD%1aD
056: ff ff ff ff 00 ef 8f 00 ........

[2020-04-11 19:53:05,478] chirp.drivers.retevis_rt22 - DEBUG: Reading block 02c0...
[2020-04-11 19:53:05,585] chirp.drivers.retevis_rt22 - DEBUG: Address: 02c0
[2020-04-11 19:53:05,585] chirp.drivers.retevis_rt22 - DEBUG: 000: 25 06 60 44 25 06 10 44 %.D%..D
008: 29 28 29 28 00 ef 9c 00 )()(....
016: 75 93 60 44 75 93 10 44 u.
Du..D
024: ec 29 ec 29 00 ef a9 00 .).)....
032: 75 93 60 44 75 93 10 44 u.Du..D
040: 56 03 56 03 00 ef b6 00 V.V.....
048: 75 93 60 44 75 93 60 44 u.
Du.`D
056: 55 04 55 04 00 ef c3 00 U.U.....

[2020-04-11 19:53:05,585] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0300...
[2020-04-11 19:53:05,692] chirp.drivers.retevis_rt22 - DEBUG: Address: 0300
[2020-04-11 19:53:05,692] chirp.drivers.retevis_rt22 - DEBUG: 000: ff ff ff ff ff ff ff ff ........
008: ff ff ff ff 00 ff 00 00 ........
016: 25 06 60 44 25 06 60 44 %.D%.D
024: ff ff ff ff 00 ef 0d 00 ........
032: 75 18 60 44 75 18 60 44 u.Du.D
040: ff ff ff ff 00 ef 1a 00 ........
048: 25 31 60 44 25 31 60 44 %1D%1D
056: ff ff ff ff 00 ef 27 00 ......'.

[2020-04-11 19:53:05,692] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0340...
[2020-04-11 19:53:05,800] chirp.drivers.retevis_rt22 - DEBUG: Address: 0340
[2020-04-11 19:53:05,800] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 43 60 44 75 43 60 44 uCDuCD
008: ff ff ff ff 00 ef 34 00 ......4.
016: 25 56 60 44 25 56 60 44 %VD%VD
024: ff ff ff ff 00 ef 41 00 ......A.
032: 75 68 60 44 75 68 60 44 uhDuhD
040: ff ff ff ff 00 ef 4e 00 ......N.
048: 25 81 60 44 25 81 60 44 %.D%.D
056: ff ff ff ff 00 ef 5b 00 ......[.

[2020-04-11 19:53:05,800] chirp.drivers.retevis_rt22 - DEBUG: Reading block 0380...
[2020-04-11 19:53:05,908] chirp.drivers.retevis_rt22 - DEBUG: Address: 0380
[2020-04-11 19:53:05,908] chirp.drivers.retevis_rt22 - DEBUG: 000: 75 93 60 44 75 93 60 44 u.Du.D
008: ff ff ff ff 00 ef 68 00 ......h.
016: 25 06 61 44 25 06 61 44 %.aD%.aD
024: ff ff ff ff 00 ef 75 00 ......u.
032: 75 18 61 44 75 18 61 44 u.aDu.aD
040: ff ff ff ff 00 ef 82 00 ........
048: 25 31 61 44 25 31 61 44 %1aD%1aD
056: ff ff ff ff 00 ef 8f 00 ........

[2020-04-11 19:53:05,908] chirp.drivers.retevis_rt22 - DEBUG: Reading block 03c0...
[2020-04-11 19:53:06,016] chirp.drivers.retevis_rt22 - DEBUG: Address: 03c0
[2020-04-11 19:53:06,016] chirp.drivers.retevis_rt22 - DEBUG: 000: 25 06 60 44 25 06 10 44 %.D%..D
008: 29 28 29 28 00 ef 9c 00 )()(....
016: 75 93 60 44 75 93 10 44 u.
Du..D
024: ec 29 ec 29 00 ef a9 00 .).)....
032: 75 93 60 44 75 93 10 44 u.Du..D
040: 56 03 56 03 00 ef b6 00 V.V.....
048: 75 93 60 44 75 93 60 44 u.
Du.`D
056: 55 04 55 04 00 ef c3 00 U.U.....

[2020-04-11 19:53:06,031] chirp.ui.clone - DEBUG: Clone thread ended
[2020-04-11 19:53:06,031] chirp.ui.reporting - DEBUG: Reporting model usage: WLN_KD-C1,download,False
[2020-04-11 19:53:06,033] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1800000-2000000 160 Meter Band simplex , 1800000-2000000 160 Meter Band simplex mode: CW ]
[2020-04-11 19:53:06,034] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1800000-1810000 Digimodes simplex , 1800000-1810000 Digital Modes simplex ]
[2020-04-11 19:53:06,036] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1999000-2000000 Beacons simplex mode: CW , 1999000-2000000 Beacons simplex ]
[2020-04-11 19:53:06,036] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [3500000-4000000 80 Meter Band simplex , 3500000-4000000 80 Meter Band simplex ]
[2020-04-11 19:53:06,038] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [7000000-7300000 40 Meter Band simplex , 7000000-7300000 40 Meter Band simplex ]
[2020-04-11 19:53:06,039] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10100000-10150000 30 Meter Band simplex , 10100000-10150000 30 Meter Band simplex ]
[2020-04-11 19:53:06,040] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10130000-10140000 All narrow band digimodes simplex , 10130000-10140000 RTTY simplex mode: RTTY ]
[2020-04-11 19:53:06,040] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10140000-10150000 All modes, digimodes, no phone simplex , 10140000-10150000 Packet simplex ]
[2020-04-11 19:53:06,040] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [14000000-14350000 20 Meter Band simplex , 14000000-14350000 20 Meter Band simplex ]
[2020-04-11 19:53:06,042] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [18068000-18168000 17 Meter Band simplex , 18068000-18168000 17 Meter Band simplex ]
[2020-04-11 19:53:06,043] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [21000000-21450000 15 Meter Band simplex , 21000000-21450000 15 Meter Band simplex ]
[2020-04-11 19:53:06,044] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [24890000-24990000 12 Meter Band simplex , 24890000-24990000 12 Meter Band simplex ]
[2020-04-11 19:53:06,045] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [28000000-28070000 CW simplex mode: CW , 28000000-28070000 CW simplex mode: CW ]
[2020-04-11 19:53:06,045] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [28150000-28190000 All narrow band modes, digimodes simplex , 28150000-28190000 CW simplex mode: CW ]
[2020-04-11 19:53:06,046] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [29000000-29200000 All modes, AM preferred simplex mode: AM , 29000000-29200000 AM simplex mode: AM ]
[2020-04-11 19:53:06,047] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [29300000-29510000 Satellite downlink simplex , 29300000-29510000 Satellite Downlinks simplex ]
[2020-04-11 19:53:06,047] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1800000-2000000 160 Meter Band simplex , 1800000-2000000 160 Meter Band simplex mode: CW ]
[2020-04-11 19:53:06,048] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1800000-1810000 Digimodes simplex , 1800000-1810000 Digital Modes simplex ]
[2020-04-11 19:53:06,048] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [1999000-2000000 Beacons simplex mode: CW , 1999000-2000000 Beacons simplex ]
[2020-04-11 19:53:06,048] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [3500000-4000000 80 Meter Band simplex , 3500000-4000000 80 Meter Band simplex ]
[2020-04-11 19:53:06,049] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [7000000-7300000 40 Meter Band simplex , 7000000-7300000 40 Meter Band simplex ]
[2020-04-11 19:53:06,049] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10100000-10150000 30 Meter Band simplex , 10100000-10150000 30 Meter Band simplex ]
[2020-04-11 19:53:06,049] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10130000-10140000 All narrow band digimodes simplex , 10130000-10140000 RTTY simplex mode: RTTY ]
[2020-04-11 19:53:06,049] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [10140000-10150000 All modes, digimodes, no phone simplex , 10140000-10150000 Packet simplex ]
[2020-04-11 19:53:06,050] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [14000000-14350000 20 Meter Band simplex , 14000000-14350000 20 Meter Band simplex ]
[2020-04-11 19:53:06,050] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [18068000-18168000 17 Meter Band simplex , 18068000-18168000 17 Meter Band simplex ]
[2020-04-11 19:53:06,050] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [21000000-21450000 15 Meter Band simplex , 21000000-21450000 15 Meter Band simplex ]
[2020-04-11 19:53:06,051] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [24890000-24990000 12 Meter Band simplex , 24890000-24990000 12 Meter Band simplex ]
[2020-04-11 19:53:06,051] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [28000000-28070000 CW simplex mode: CW , 28000000-28070000 CW simplex mode: CW ]
[2020-04-11 19:53:06,051] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [28150000-28190000 All narrow band modes, digimodes simplex , 28150000-28190000 CW simplex mode: CW ]
[2020-04-11 19:53:06,051] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [29000000-29200000 All modes, AM preferred simplex mode: AM , 29000000-29200000 AM simplex mode: AM ]
[2020-04-11 19:53:06,052] chirp.ui.bandplans - WARNING: Bandplan North American Band Plan has duplicates [29300000-29510000 Satellite downlink simplex , 29300000-29510000 Satellite Downlinks simplex ]
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Code supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Rx Code supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Pol supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Mode supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Offset supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Name supported: False
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Tune Step supported: False
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Name supported: False
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: ToneSql supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Cross Mode supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Comment supported: False
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Code supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Rx Code supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: DTCS Pol supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Mode supported: True
[2020-04-11 19:53:06,079] chirp.ui.memedit - INFO: Offset supported: True
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: Name supported: False
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: Tune Step supported: False
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: Name supported: False
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: ToneSql supported: True
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: Cross Mode supported: True
[2020-04-11 19:53:06,080] chirp.ui.memedit - INFO: Comment supported: False
[2020-04-11 19:53:06,086] chirp.drivers.retevis_rt22 - DEBUG: bitpos 1
[2020-04-11 19:53:06,086] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,086] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,087] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,087] chirp.drivers.retevis_rt22 - DEBUG: bitpos 2
[2020-04-11 19:53:06,087] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,087] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,087] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: bitpos 4
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: bitpos 8
[2020-04-11 19:53:06,088] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,089] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,089] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,089] chirp.drivers.retevis_rt22 - DEBUG: bitpos 16
[2020-04-11 19:53:06,089] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,090] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,090] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,090] chirp.drivers.retevis_rt22 - DEBUG: bitpos 32
[2020-04-11 19:53:06,090] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,091] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,091] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,091] chirp.drivers.retevis_rt22 - DEBUG: bitpos 64
[2020-04-11 19:53:06,092] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,092] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,092] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,093] chirp.drivers.retevis_rt22 - DEBUG: bitpos 128
[2020-04-11 19:53:06,093] chirp.drivers.retevis_rt22 - DEBUG: bytepos 0
[2020-04-11 19:53:06,093] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,094] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,094] chirp.drivers.retevis_rt22 - DEBUG: bitpos 1
[2020-04-11 19:53:06,094] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,095] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,095] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,095] chirp.drivers.retevis_rt22 - DEBUG: bitpos 2
[2020-04-11 19:53:06,096] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,096] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,096] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,097] chirp.drivers.retevis_rt22 - DEBUG: bitpos 4
[2020-04-11 19:53:06,097] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,097] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,097] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,098] chirp.drivers.retevis_rt22 - DEBUG: bitpos 8
[2020-04-11 19:53:06,098] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,098] chirp.drivers.retevis_rt22 - DEBUG: Got TX DTCS (10281) RX DTCS (10281)
[2020-04-11 19:53:06,099] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,099] chirp.drivers.retevis_rt22 - DEBUG: bitpos 16
[2020-04-11 19:53:06,099] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,100] chirp.drivers.retevis_rt22 - DEBUG: Got TX DTCS (10732) RX DTCS (10732)
[2020-04-11 19:53:06,100] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,100] chirp.drivers.retevis_rt22 - DEBUG: bitpos 32
[2020-04-11 19:53:06,100] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,100] chirp.drivers.retevis_rt22 - DEBUG: Got TX Tone (854) RX Tone (854)
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: bitpos 64
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: Got TX Tone (1109) RX Tone (1109)
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,101] chirp.drivers.retevis_rt22 - DEBUG: bitpos 128
[2020-04-11 19:53:06,102] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,102] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,102] chirp.drivers.retevis_rt22 - DEBUG: mem.skip
[2020-04-11 19:53:06,103] chirp.drivers.retevis_rt22 - DEBUG: bitpos 128
[2020-04-11 19:53:06,103] chirp.drivers.retevis_rt22 - DEBUG: bytepos 1
[2020-04-11 19:53:06,103] chirp.drivers.retevis_rt22 - DEBUG: Got TX (65535) RX (65535)
[2020-04-11 19:53:06,103] chirp.drivers.retevis_rt22 - DEBUG: mem.skip

Actions #18

Updated by Jan NL about 4 years ago

I managed to program both the radios with software I found here:
http://web1.foxhollow.ca/WLN/

You will need a driver for the programming cable that I found here:
http://www.wch.cn/download/CH341SER_EXE.html

Both are "unofficial" sites, so use at own risk.

Actions #19

Updated by Bernhard Hailer almost 4 years ago

Turns out there is an issue with Retevis RT22 variants (the WLN KD-C1 is one of them).
This ticket duplicates #6747. Please follow and post there. Thanks!

Actions #20

Updated by Bernhard Hailer over 3 years ago

  • Status changed from Feedback to Closed
  • Assignee deleted (Jim Unroe)
  • Model affected changed from WLN KD-C1 to WLN KD-C1, Retevis RT22

This ticket duplicates #6747. Please follow and post there. Thanks!

Actions

Also available in: Atom PDF