Project

General

Profile

Actions

Bug #3031

closed

Baofeng UV-5R to Baofeng GT-3 Mk 2

Added by Randy Tobler over 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/28/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
UV-5R and GT-3MK2
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I have updated my CHIRP to the up to date version. I have installed updated drivers for my USB. I have installed the uv5y.pr file. My GT3 Mk2 has all the channels uploaded. Both are BFB297 when turning on and pressing 3. But I still can not hear anything or transmit. Operating on Windows 10.

Actions #1

Updated by Randy Tobler over 8 years ago

Randy Tobler wrote:

I have updated my CHIRP to the up to date version. I have installed updated drivers for my USB. I have installed the uv5y.pr file. My GT3 Mk2 has all the channels uploaded. Both are BFB297 when turning on and pressing 3. But I still can not hear anything or transmit. Operating on Windows 10. I have tried to download 0.4.1 but I keep getting an "error opening file for writing" C:\program files (x86)\CHIRP_ctypes.pdy

Actions #2

Updated by Jim Unroe over 8 years ago

Randy,

CHIRP v0.4.0 was released in April of 2014
CHIRP v0.4.1 was released in August of 2014. It is v0.4.0 with a single backport that failed to do what it was intended to do. So for all practical purposes, v0.4.1 is the April 2014 v0.4.0.

Baofeng made a change to the memory layout of radios in the late summer/early fall of 2014 that made CHIRP Radio Image (*.img) files from prior radios incompatible with the new radios. The reverse is also true.

Baofeng Radios that use the "uv5r.py" driver (all but the BF-888s, UV-B5 and UV-B6) should be using a CHIRP daily build from July 2015 or after.

Recent CHIRP daily builds will prevent a an incompatible CHIRP Radio Image file from being uploaded into the radio. The CHIRP v0.4.x builds do not have this protection because 20 months ago it was not required.

You will have to recover the radio by uploading the "backup" image that you saved before uploading "foreign" image into your radio. If you did not save a "backup" image, then you will have to use a "factory" image saved from a radio having the exact same firmware version or have the image that you have "repaired".

Jim KC9HI

Actions #3

Updated by Bernhard Hailer about 4 years ago

  • Status changed from New to Closed
  • Priority changed from Urgent to Normal
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from UV5R and GT3MK2 to UV-5R and GT-3MK2

No more feedback by submitter.

Actions

Also available in: Atom PDF