Project

General

Profile

Actions

Bug #3595

closed

BAOFENG GT-3WP

Added by Aaron Blackford about 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/22/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng GT-3WP
Platform:
All
Debug Log:
I read the instructions above:

Description

Why doesn't Chirp work with this radio? I thought they were basically a UV-82. Any ideas?

Actions #1

Updated by Jim Unroe about 8 years ago

  • Status changed from New to Feedback
  • Platform changed from Windows to All

Because the radio does not identify itself. Baofeng blanked out the 14 bytes of memory that identify the radio which doesn't not allow CHIRP to separate this radio from the rest of the Baofeng radios.

Jim KC9HI

Actions #2

Updated by Aaron Blackford about 8 years ago

So is there any way to trick the software to be able to program the radio? The factory software sucks.

Actions #3

Updated by Doug McComber about 8 years ago

Perhaps upon those 14 bytes returning as null or unknown, a routine that prompts the user for the model is called?

Actions #4

Updated by Gijs Hoskam over 7 years ago

Any idea if this will be solved in the future? Anyone know if there is a workaround for this issue?

Actions #5

Updated by Jim Unroe over 7 years ago

  • Status changed from Feedback to Resolved

Supported. See issue #3485

Actions #6

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Resolved to Closed
  • Priority changed from High to Normal
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from GT-3WP to Baofeng GT-3WP
Actions

Also available in: Atom PDF