Bug #1617

UV-6

Added by Александр Герман about 5 years ago. Updated almost 3 years ago.

Status:Closed Start date:05/07/2014
Priority:Normal Due date:
Assignee:- % Done:

0%

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

Description

does not read data from the radio

BF_UV6.LOG (4.3 MB) Carlos Marquez, 08/14/2014 02:19 pm

History

Updated by Jim Unroe about 5 years ago

This is most likely not a CHIRP issue. Check the miklor.com website to help resolve this. Most issues like this are caused by the programming cable not being fully plugged into the radio or the Prolific driver is not compatible with the chip in the programming cable. Please review these pages on the miklor.com website.

Common Error Messages
USB Cables and Drivers

Jim KC9HI

Updated by patraic emery about 5 years ago

Jim Unroe wrote:

This is most likely not a CHIRP issue. Check the miklor.com website to help resolve this. Most issues like this are caused by the programming cable not being fully plugged into the radio or the Prolific driver is not compatible with the chip in the programming cable. Please review these pages on the miklor.com website.

Common Error Messages
USB Cables and Drivers

Jim KC9HI

I too am having this issue but i am able to program my uv-5r and not my uv-6

Updated by Jim Unroe about 5 years ago

This wouldn't be the first time Baofeng changed something that caused the clone operation to stop working. We'll need more to go on than "it doesn't work".

Which CHIRP version are you using (look in Help->About)?
What is the error message you are getting?
If you leave the programming cable unplugged from the radio, do you get the same error?
Provide a debug.log (click the link below for instructions).

How To Report Issues: Getting your debug.log

Jim KC9HI

Updated by Александр Герман about 5 years ago

Jim Unroe wrote:

This wouldn't be the first time Baofeng changed something that caused the clone operation to stop working. We'll need more to go on than "it doesn't work".

Which CHIRP version are you using (look in Help->About)?
What is the error message you are getting?
If you leave the programming cable unplugged from the radio, do you get the same error?
Provide a debug.log (click the link below for instructions).

How To Report Issues: Getting your debug.log

Jim KC9HI

the original program UV6UV7 works well. and CHIRP daily-20140428 not work with a walkie-talkie.

Updated by Jim Unroe about 5 years ago

Please supply the requested debug.log
Jim KC9HI

Updated by Александр Герман about 5 years ago

Jim Unroe wrote:

Please supply the requested debug.log
Jim KC9HI

the program shows me a message on radio did not respond. where to get the debug.log file?

Updated by Jim Unroe about 5 years ago

I provided a link in a previous message that explains how to do this.
Jim

Updated by Александр Герман about 5 years ago

Jim Unroe wrote:

I provided a link in a previous message that explains how to do this.
Jim

I have not found the debug.log file. show the way to him.

Updated by Jim Unroe about 5 years ago

Here is the quoted text from the page that I posted previously that explains how to get the debug log.

Getting your debug log
If you are expecting something to happen (such as importing from a file, or setting a memory) and CHIRP appears to ignore the request, you probably should include your debug.log. If you are getting an error message, you should definitely include the log.

begin quoted text

The debug log is cleared every time you start chirp, so the procedure for getting a usable log is:

1. Start chirp
2. Reproduce the failure or bug
3. Close chirp
4. Copy and send the debug.log before starting chirp again

Here are some tips for getting to it on the various platforms:

Windows
Go to Start->Run and type "%APPDATA%\CHIRP". Your debug.log file will be in the folder that opens.

end quoted text

In the case of Windows Vista and above, you put the "%APPDATA%\CHIRP" in the search box that appears just above the Start button after it has been clicked.

Jim KC9HI

Updated by Александр Герман about 5 years ago

1. Start chirp
2. Reproduce the failure or bug
3. Close chirp
4. Copy and send the debug.log before starting chirp again

Here are some tips for getting to it on the various platforms:

Hallelujah))
Skipping existing stock config
User selected Baofeng UV-6 on port COM6
Clone thread started
Sending Magic: 000: 50 bb ff 20 12 08 23 00 P.....#.

Radio did not respond
-- Exception: --
Traceback (most recent call last):
File "chirpui\clone.pyo", line 227, in run
File "chirp\uv5r.pyo", line 616, in sync_in
File "chirp\uv5r.pyo", line 447, in _do_download
File "chirp\uv5r.pyo", line 443, in _ident_radio
RadioError: Radio did not respond
------
Ошибка загрузки Radio did not respond
Clone thread ended
--- Exception Dialog: Radio did not respond ---
Traceback (most recent call last):
File "chirpw", line 75, in <module>
AttributeError: 'NoneType' object has no attribute 'split'

Updated by Jim Unroe about 5 years ago

Do you have a 32-bit Windows computer available that you can use to capture the serial port data while using the UV6UV7 software?

Jim KC9HI

Updated by Александр Герман about 5 years ago

Jim Unroe wrote:

Do you have a 32-bit Windows computer available that you can use to capture the serial port data while using the UV6UV7 software?

Jim KC9HI

UV6UV7 software works all right, and CHIRP no.

Updated by Carlos Marquez almost 5 years ago

Jim,
I hope this log file helps.

Updated by Jim Unroe almost 3 years ago

  • Status changed from New to Resolved

The issue with the longer 12 byte reply was addressed in the CHIRP-2016013 build.

Jim KC9HI

Updated by Jim Unroe almost 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF