Project

General

Profile

Actions

Bug #168

closed

can't communicate with Baofeng UV-3R+

Added by Antoine Beaupré over 12 years ago. Updated about 10 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-3R+
Platform:
Windows
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:

Radio did not ACK first command

I get this in the terminal where i started chirp:

User selected Baofeng UV-3R on port /dev/ttyUSB0
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/wouxun.py", line 967, in sync_in
    self._mmap = uv3r_download(self)
  File "/home/anarcat/dist/chirp-daily-20120507/chirp/wouxun.py", line 877, in uv3r_download
    uv3r_prep(radio)
  File "/home/anarcat/dist/chirp-daily-20120507/chirp/wouxun.py", line 872, in uv3r_prep
    raise e
RadioError: Radio did not ACK first command
------
Clone failed: Radio did not ACK first command
Clone thread ended
--- Exception Dialog: Radio did not ACK first command ---
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-3R+ 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-3R.

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.

This is similar to #167, but I open a different issue because the error message is different. I also wonder if the protocol for the UV-3R+ is different from the UV-3R radio...


Files

IMG_0016.cleaned.JPG (1.18 MB) IMG_0016.cleaned.JPG Pushing the connector into the UV-3R against the table. x Smurf, 08/15/2012 06:45 PM

Related issues 1 (0 open1 closed)

Related to New Model #239: UV3R+Rejected07/10/2012

Actions
Actions #1

Updated by Antoine Beaupré over 12 years ago

I have tried to applied a similar method than recommended in #167, to no avail. I have tried:

  1. putting the radio in memory mode, in VHF or UHF mode (before or after switching to memory mode)
  2. putting the radio in menu mode
  3. locking the radio
  4. having the function key "raised" (hilighted)
  5. with the light on...

maybe it's a combination of the above... don't know, but so far i always end up with "Radio did not ACK first command".

good thing is that it's easier to program that radio than the uv5r. ;)

Actions #2

Updated by Jonathan Andrews over 12 years ago

UV3R+ Seems to have different internals/firmware to the UV3R, I can confirm that UV3R+ also gives me "Radio did not ACK first command
" when I try to read as "UV3R". UVD1P and UV5R both work with chirp and the same cable.

Actions #3

Updated by x Smurf about 12 years ago

I actually got this working just fine, but you need to push the connector in hard, real hard. What I do is put the connector in and push it down onto the desk (see attached picture).

Actions #4

Updated by x Smurf about 12 years ago

Just to be clear, you have to hold the radio this way during the whole read/write procedure.

Actions #5

Updated by Jonathan Andrews about 12 years ago

Yep, me bad ... thanks for the info, radio does work...

Weird thing is when I tried it last I also used the windows code to talk to the radio with no problems, then re-booted into linux and used chirp with UV5R, then with the 3R+ .... ho hum .... guess i'm not brutal enough with my cables.

Actions #6

Updated by Antoine Beaupré about 10 years ago

this issue can be closed: i confirm that pushing the radio hard against the desk works, thanks x Smurf! :)

Actions #7

Updated by Dan Smith about 10 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF