Bug #10226: Quansheng TG-UV2+ not programming - CHIRP

Actions

Copy link

Bug #10226

open

Quansheng TG-UV2+ not programming

Added by Alexander Astafyev almost 2 years ago. Updated about 1 year ago.

Status:

In Progress

Priority:

Normal

Assignee:

Ran Katz

Category:

Target version:

Start date:

01/05/2023

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Quansheng TG-UV2+

Platform:

Windows

Debug Log:

I read the instructions above:

Description

An error "Unsupported model" occurs when trying to read or write channels on Quansheng TG-UV2+. At the same time, the radio station works with the native program.

Files

Download all files

debug.log (35.7 KB) debug.log		Alexander Astafyev, 01/05/2023 06:44 PM
Screenshot_2.jpg (93.4 KB) Screenshot_2.jpg		Alexander Astafyev, 01/06/2023 11:01 AM
tg_uv2p_fix_8591_v2 - patched 2023.py (23.2 KB) tg_uv2p_fix_8591_v2 - patched 2023.py		Alex Young, 08/29/2023 05:11 AM
tg_uv2p_fixed.py (26.9 KB) tg_uv2p_fixed.py		Alex Young, 08/29/2023 05:47 AM
tg_uv2p.py (27.3 KB) tg_uv2p.py		Ran Katz, 09/03/2023 12:15 AM
Screenshot 2023-09-03 102630.png (27.6 KB) Screenshot 2023-09-03 102630.png		Alex Young, 09/03/2023 12:31 AM

Actions

Copy link

Updated by Ran Katz almost 2 years ago

Hi,
Have you managed to work with this radio and chirp before? (on a different chirp version?)
It seems from the log file that your radio does not respond to the "identity" command,
what version of the native program are you using?

Actions

Copy link

Updated by Alexander Astafyev almost 2 years ago

File Screenshot_2.jpg Screenshot_2.jpg added

Ran Katz wrote in #note-1:

Hi,
Have you managed to work with this radio and chirp before? (on a different chirp version?)
It seems from the log file that your radio does not respond to the "identity" command,
what version of the native program are you using?

Hi,
No, I received this radio recently and it does not connect with any version of Chirp.
At the same time, other radios (version without plus) work well. The radio works with the TG-UV-D1.72 application

Actions

Copy link

Updated by Alex Young about 1 year ago

File tg_uv2p_fix_8591_v2 - patched 2023.py tg_uv2p_fix_8591_v2 - patched 2023.py added

I have a newer revision TG-UV2+ and it does not work with CHIRP, giving an "Unsupported model" error.
I analyzed the exchange with the factory program and found a difference for the IDENT request.

Factory TG-UV-D1.72.exe:

[29/08/2023 04:06:17] Written data (COM3)   
    02 50 6e 4f 47 64 41 4d                           .PnOGdAM          
[29/08/2023 04:06:17] Read data (COM3)  
    06                                                .                 
[29/08/2023 04:06:18] Written data (COM3)   
    4d 02                                             M.                
[29/08/2023 04:06:18] Read data (COM3)  
    50 35 35 35 35 f4 00 00                           P5555ô..         
[29/08/2023 04:06:18] Written data (COM3)   
    06                                                .                 
[29/08/2023 04:06:18] Read data (COM3)  
    06                                                .

CHIRP Legacy/Next:

[29/08/2023 04:59:31] Written data (COM3)   
    02 50 6e 4f 47 64 41 4d                           .PnOGdAM          
[29/08/2023 04:59:31] Read data (COM3)  
    06                                                .                 
[29/08/2023 04:59:31] Written data (COM3)   
    40 02                                             @.                
[29/08/2023 04:59:34] - Close port COM3

So the ident request command differs by one character. I did an experiment by patched tg_uv2p_fix_8591_v2.py module and tested it with CHIRP Legacy - my radio works without problems.

Actions

Copy link

Updated by Alex Young about 1 year ago

File tg_uv2p_fixed.py tg_uv2p_fixed.py added

I have fixed and tested the UV2+ driver as a CHIRP Daily module - the problem is finally resolved and the port exchange works exactly like the factory program. I hope Dan kindly fixes the driver in an upcoming build version.

Actions

Copy link

Updated by Dan Smith about 1 year ago

Alex, I can't include your change directly because it will break the regular TG-UV2 driver. Maybe @Ran Katz could integrate your change into a "try the old one, then try the new one" routine so it will work for both? If not, I can try and do it blindly, but I'll need someone with an old and new one to validate any change.

Actions

Copy link

Updated by Ran Katz about 1 year ago

Assignee set to Ran Katz

Dan, Alex,
I will look into this over the upcoming weekend.

Ran

p.s. looking into the original code I based the driver on (see here: https://chirp.danplanet.com/attachments/1585, line 359) , it seems the 0x40 is a typo / copy error as it is 0x4d in the original...

Actions

Copy link