CHIRP

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

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.

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.

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...

(I have created a PR but I would like Alex to test it first so I closed it for now)

@Alex Young,
can you test the attached driver with chirp-next (daily)?
Thanks!
Ran

Ran Katz,
I have the new patch working.