Project

General

Profile

Actions

Bug #8215

closed

Chirp não consegue ligar ao Baofeng GT-5TP (firmware N82301) com cabo CH340

Added by Sérgio Barroso over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/29/2020
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng GT-5TP
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Boa tarde.
Instalei a última versão do CHIRP e tentei ligar o meu rádio Baofeng GT-5TP (firmware N82301) com cabo CH340 que comprei.
Segundo a vossa página devo escolher o BAOFENG UV-2HP como rádio compatível com o meu.
No entanto, continua a aparecer o erro que não consegue ligar ao rádio.
Quando olho para o rádio verifico que ele muda, momentaneamente, o ecran preenchendo todos os espaços do visor.
Já tentei ligar ao software de fábrica mas também indica que não consegue comunicar com o rádio.
Podem ajudar?
Obrigado.

Good afternoon.
I installed the latest version of CHIRP and tried to connect my radio Baofeng GT-5TP (firmware N82301) with CH340 cable that I bought.
According to your page I must choose BAOFENG UV-2HP as a radio compatible with mine.
However, the error still fails to connect to the radio.
When I look at the radio I notice that it changes, momentarily, the screen filling all the spaces of the display.
I have already tried to connect to the factory software but it also indicates that it cannot communicate with the radio.
Can you help?
Thank you.


Files

debug.log (27.9 KB) debug.log Sérgio Barroso, 08/29/2020 08:29 AM
erro.png (93.4 KB) erro.png Sérgio Barroso, 08/29/2020 08:29 AM
Actions #1

Updated by Bernhard Hailer over 3 years ago

  • Description updated (diff)
  • Model affected changed from (All models) to Baofeng GT-5TP
Actions #2

Updated by Bernhard Hailer over 3 years ago

  • Status changed from New to Feedback

Seu rádio não responde às tentativas de Chirp de falar com ele.
Parece um problema de cabo / driver / conector. Por favor, consulte estes artigos Wiki:
CableGuide
CableGuide FTDI OEM Cables
Notas do Windows: Se você estiver usando um cabo genérico com um chip Prolific, provavelmente precisará fazer o downgrade do driver para a versão 3.2.0.0.
Ele pode ser encontrado em http://www.miklor.com/COM/UV_Drivers.php

Your radio doesn't respond to Chirp's attempts to talk with it.
This looks like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php

Actions #3

Updated by Jim Unroe over 3 years ago

Hi Sérgio,

According to the debug.log file, the radio does not respond to either of the 2 requests to initiate cloning. I downloaded the factory programming software and determined that CHIRP does send the correct request to initiate the cloning process on the GT-5TP when the UV-82HP model is selected. Since CHIRP does not get a reply from the radio, I would suspect that there is a problem with the connection between the 2-pin plug and the socket of the radio.

Does the radio work with the factory programming software? Trying the factory programming software would confirm if it is a CHIRP issue or a cable issue.

Jim KC9HI

Actions #4

Updated by Sérgio Barroso over 3 years ago

Hello.
It had already been tested with the factory software and also returns the message that it cannot communicate with the radio.
The cable I have has the CH340 driver.
I tried to install the cable with the Profilic 3.2.0.0 drive but the system did not recognize the cable.

Actions #5

Updated by Jim Unroe over 3 years ago

Sérgio Barroso wrote:

Hello.
It had already been tested with the factory software and also returns the message that it cannot communicate with the radio.
The cable I have has the CH340 driver.
I tried to install the cable with the Profilic 3.2.0.0 drive but the system did not recognize the cable.

Then this is clearly not a CHIRP issue. If you leave the cable unplugged from the radio you will likely get the exact same error messages.

You do not want to install the Prolific v3.2.0.0 device driver for a programming cable with a WCH USB-to-Serial chip. It is only for Prolific type chips.

I would look at the following.

  1. Device driver - Look at Device Manager to see if the device driver is installed correctly and working. The latest version of the CH340/CH341 device driver is 3.5. You can download the latest latest WCH driver from the "chip vendor's downloads page":http://www.wch-ic.com/search?q=CH340&t=downloads.

  2. Connection to radio - Make sure the 2-pin plug is fully inserted into the socket of the radio. I don't know about the GT-5 series, but the GT-3 series has a ridge that goes around the top of the socket and contacts the plastic of the plug's shell and interferes with the plug being fully inserted. On my UV-82 radios, the metal pins of the plug would stick on the metal ring of the socket and fool me into thinking the plug was fully inserted when it wasn't. I eventually learned the technique for getting the plug fully inserted.

  3. Defective programming cable - Try the programming cable with a different radio or borrow a working programming cable from someone else to determine if the programming cable itself is the problem.

Good luck,
Jim KC9HI

Actions #6

Updated by Bernhard Hailer over 3 years ago

  • Status changed from Feedback to Closed

No more traffic on this ticket.

Actions

Also available in: Atom PDF