Project

General

Profile

Actions

Bug #373

closed

UV-5R upload/download problem (Radio reported unknown vendor) + Temp Solution

Added by Lior Elazary over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
12/23/2012
Due date:
% Done:

0%

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

Description

After receiving the radio I was able to program it on linux (using the daily build) with no problem.
I tried to disable the TX on the radio ('settings/Other Settings') and changed the VHF limit to 30-300MHZ and UHF to 300-1000.
After uploading the data to the radio, I was able to enter frequencies in the these ranges on the radio (although it did not seem like it actually was receiving any signal), and it looks like the radio was still transmitting (I tested it on the FRS channel 7 (462.7125MHZ) on low power).

MY radio version is: BFB293 (120915N/B5R0001 when power+6)

Solution:
After starting CHIRP on the command line, I noticed the following

Ident:
000: aa 01 00 03 00 10 00 dd ........

Vendor is '\x01\x00\x03' (OK)
Version is '\x00\x10\x00' (OK)
Image is ' Ver BFB293 '
Radio is ' Ver BFB293 '
Clone thread ended

Is looks like the vendor is 01/00/03 but in the uv5r.py code line 176 (http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/uv5r.py#L176) its looking for a \x04 in the vendor. No problem, I changed the \x04 to \x03. Restarted CHIRP and everything works fine now. The TX checkbox still does not seem to work (I can TX).

I am not sure why the radio seemed to be sending the correct vendor before but now it wont, but it does seem to be working now with no problems (I can upload/download and change settings all day long).

Hope this helps.

Lior.

Actions #1

Updated by Lior Elazary over 11 years ago

Sorry, the issue was that after changing the no TX and freq ranges and uploading the the radio, I was not able to upload/download from the radio at all after that. I tried a factory reset and it still did not work. I kept getting 'Radio reported unknown vendor' message.

Actions #2

Updated by Dan Smith over 11 years ago

  • Status changed from New to In Progress
  • Assignee set to Dan Smith
  • Target version set to 0.3.0

Okay, I think that probably I need to remove the check for the 0x04 entirely. The original version had something that looked like a reasonable vendor in that field, so I checked for it. After version 291, it seems to be mostly garbage.

Actions #3

Updated by Dan Smith over 11 years ago

  • Status changed from In Progress to Closed

In r1771 I removed that bit entirely, so your radio should be identified by tomorrow's daily build. Please re-open this if not.

Thanks!

Actions

Also available in: Atom PDF