CHIRP

Jim Unroe wrote:

Be sure the 2-pin plug is fully inserted. Attach a debug.log file.

Jim KC9HI

Plugs are fully inserted and programming cable tested a lot of times with many other transcievers.
While trying to read "NKTECH UV-82 Plus" as some other radio, sometimes transmiting turns on for about 1-2 sec.
Its not use to attach debug.log file as there is no useful information. CHIRP always tells "Radio did not respond".

Alexey UR5FFM

Do you have the factory software?

If yes, does the factory software work to program this radio?

If yes, which factory software did you use?

No, don't and can not to find it. :-(
Still looking. If I find, shall check and inform.
There is possibility that radio is malfunction, but I don't think so...

If there is nothing in the debug.log, then the radio is not responding back to CHIRP. Reasons for this could be...

• cable not working (you have already ruled that out)
• radio is "listening" for a different "magic" string to start the cloning process (likely)
• something wrong with the radios communications (not likely)

To determine the "magic" string, the serial communication of a working factory programming software will have to be captured.

Jim

I find factory software which compatible with that radio and it works fine!
It is same as Baofeng CT-3.
Here is the link to download: https://drive.google.com/open?id=0B8BGmr-vYNsbNHpsLU83dEpCZ28

Jim Unroe wrote:

To determine the "magic" string, the serial communication of a working factory programming software will have to be captured.

If you can explaine how to capture "magic" string, I can try to do it to help CHIRP became more powerful.

Thank you for detailed manual!

The problem is follow, UV3_VIP saves config file as *.dat, but not *.img, like other Baofeng's software.
That *.dat file size much bigger, then *.img. Its around 35KB, instead of 6KB as *.img has.
Trying to open as different Baofengs and some Kenwoods, but only ERROR in the settings I see.
Is it use to show debug.log or need to open settings file some other way?

The factory software and the CHIRP software collect and use the settings information differently. The data files are not interchangeable and are not expected to be. It is very rare for them to be the same (the UV-B5/UV-B6 are the only radio models that I know of where they are the same - only the extension is different).

You were not supposed to try to look at any settings.

uv5r(custom_to_get_image).py - for grabbing an image only

My instructions were...

If successful, attach the image to this issue and do nothing else.

Please attach the image so I can look at it to determine the next step should be.

Jim

I need you to attempt a download from your radio using CHIRP and the special driver module.

If the download is successful, save the tab that was created to an *.img file and attach that file to this issue so I will be able to download it and study it. Do nothing else.

If the download is unsuccessful, attach the debug.log file to this issue. If it doesn't work, I need to be able to understand why because we must have the *.img file.

Jim

Jim Unroe wrote:

I need you to attempt a download from your radio using CHIRP and the special driver module.

I do not find any new files.
May be you forgot to attach it.

There is no new file. I haven't see the results from the "uv5r(custom_to_get_image).py" file from post #8.

Jim