Project

General

Profile

Actions

Bug #167

closed

can't communicate with Baofeng UV-5R

Added by Antoine Beaupré almost 12 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/09/2012
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
Baofeng UV-5R
Platform:
Linux
Debug Log:
I read the instructions above:

Description

h2. 1. What is the behavior you are seeing?

The radio doesn't respond to chirp, the error is:

An error has occured

Radio did not respond

I get this in the terminal where i started chirp:

Clone thread started
''
-- Exception: --
Traceback (most recent call last):
  File "/home/anarcat/dist/chirp-daily-20120507/chirpui/clone.py", line 223, in run
    self.__radio.sync_in()
  File "/home/anarcat/dist/chirp-daily-20120507/chirp/uv5r.py", line 223, in sync_in
    self._mmap = _do_download(self)
  File "/home/anarcat/dist/chirp-daily-20120507/chirp/uv5r.py", line 138, in _do_download
    data = _do_ident(radio)
  File "/home/anarcat/dist/chirp-daily-20120507/chirp/uv5r.py", line 121, in _do_ident
    raise errors.RadioError("Radio did not respond")
RadioError: Radio did not respond
------
Clone failed: Radio did not respond
Clone thread ended
--- Exception Dialog: Radio did not respond ---
Traceback (most recent call last):
  File "./chirpw", line 68, in 
    langs += os.getenv("LANG").split(":")
AttributeError: 'NoneType' object has no attribute 'split'
----------------------------

I did not find a debug.log, looking at the source i assume this is the same.

h2. 2. What is the behavior you were expecting?

I was expecting a nice filling up of the tab with the radio data, so i can flash it back. :)

h2. 3. Can you reproduce the problem all the time?

Yes.

h2. 4. What are the steps required to reproduce the problem?

Connect a Baofeng UV-5R radio to a Debian Wheezy laptop using a "Kenwood/Wouxun cable".

Power up the radio.

Choose "Download from Radio" in the Radio menu, with port /dev/ttyUSB0, Vendor Baofeng et Model UV-5R.

h2. 5. Is this specific to a certain radio model (driver) or something that you can reproduce with another radio?

I am happy to say chirp looks fine with my Wouxun KG-UVD1P.

Actions #1

Updated by Antoine Beaupré almost 12 years ago

Correction: this applies to today's most recent daily.

Actions #2

Updated by Simon Mouradian almost 12 years ago

This bug applied to me also. Running ubuntu 12.04 and chirp daily 20120517. Note that I must run chirpw with sudo before I get this, otherwise I get permission denied. I am new to this so I may be doing something completely wrong.

Actions #3

Updated by Simon Mouradian almost 12 years ago

It turns out this is not an issue with chirp. the uv-5r requires that:
a) You push the cable well into place (more force than you would think)
b) Move to mode A
c) Switch to memory mode.

Antoine, if you try with the above in mind things should work for you. I was successful using chirp daily 20120517 in linux.

Actions #4

Updated by Antoine Beaupré almost 12 years ago

This actually works, thanks!

Not sure if moving to mode A is really necessary, but i think that being just in memory mode is enough.

Thanks very much for your great software, this ticket can be closed (unless docs need to be updated somewhere?).

Actions #5

Updated by Dan Smith almost 12 years ago

  • Status changed from New to Rejected

Hmm, I've not noticed this behavior, but I'll check it out locally and see if that's the case for me as well.

Thanks to all!

Actions #6

Updated by Antoine Beaupré over 9 years ago

i really think the instructions for this radio should be updated to at least include the fact that the radio needs to be in memory mode. being in an idle channel is not sufficient.

i can also note that by pushing the adapter too hard in the socket, i actually broke the internal mike, because for some reason one of my baofeng now thinks there's always a mike present. this is similar to what is described here: http://forums.qrz.com/showthread.php?426980-Baofeng-UV-5RE-Plus-internal-microphone

Actions #7

Updated by Jim Unroe over 9 years ago

  • Chirp Version changed from 0.2.2 to 0.4.0

I have never had to make sure that I have the radio in any particular mode (A display, B display, VFO or MR) before downloading or uploading. It doesn't matter.

Jim KC9HI

Actions #8

Updated by Bill Hopkins about 7 years ago

Same issue, Baofeng UV-B6 radio will not Acknowledge the Chirp attempt to communicate.
Using the Daily build of Chirp and running Linux Mint 17.3

I have no problem with Chirp connecting with the radio, when using the Baofeng UV-B5 ver 1.09 Windows programming software.

Bill VE3WAH

Actions #9

Updated by Jim Unroe about 7 years ago

Not the same issue. This is a totally different radio. Open a new issue. Include a debug log and a serial port capture if possible.

Jim

Actions #10

Updated by Bill Hopkins about 7 years ago

Sorry guys, my mistake. My Baofeng is a newer model than the model this thread, is for.
I will post the issue with my Baofeng UV-B6, in a new thread.

Actions

Also available in: Atom PDF