CHIRP

TG UV 2 plus as i know is a newer model but do what have to do , as i see there is no interest at supporting this brand as baofeng . Sorry for the inconvenience

I found TG-UV2+ has shown up in the supported device list but I can't seem to find that working.
I can connect to the device with the Quansheng software, but Chirp gives me "Invalid response for address 0x0000"
Please let me know how I can help, would love to make this work. I'm new to HAM but I'm a developer

Ran Katz wrote:

Added Image file for proposed driver

Is this image for TG-UV2 or TG-UV2plus

Hao Xu wrote:

I found TG-UV2+ has shown up in the supported device list but I can't seem to find that working.
I can connect to the device with the Quansheng software, but Chirp gives me "Invalid response for address 0x0000"
Please let me know how I can help, would love to make this work. I'm new to HAM but I'm a developer

I don't know where you found it is a "supported device list". Neither the vendor "Quansheng" nor the model "TG-UV2" shows up in any CHIRP files. The only thing close in the CHIRP Supported Radio Models list on the home page is Wouxun KG-UV2D, which I would expect to be not compatible with a Quansheng radio. I would consider it safe to say that CHIRP does not support any Quansheng radio models.

Jim KC9HI

Jim Unroe wrote:

Hao Xu wrote:

I found TG-UV2+ has shown up in the supported device list but I can't seem to find that working.
I can connect to the device with the Quansheng software, but Chirp gives me "Invalid response for address 0x0000"
Please let me know how I can help, would love to make this work. I'm new to HAM but I'm a developer

I don't know where you found it is a "supported device list". Neither the vendor "Quansheng" nor the model "TG-UV2" shows up in any CHIRP files. The only thing close in the CHIRP Supported Radio Models list on the home page is Wouxun KG-UV2D, which I would expect to be not compatible with a Quansheng radio. I would consider it safe to say that CHIRP does not support any Quansheng radio models.

Jim KC9HI

It showed up in the build on 02/10 and 02/14, not on 02/09. So, I assume someone added the driver recently, but I can't seem to find that in the drivers
https://trac.chirp.danplanet.com/chirp_daily/daily-20220210/Model_Support.html

Hao Xu wrote:

It showed up in the build on 02/10 and 02/14, not on 02/09. So, I assume someone added the driver recently, but I can't seem to find that in the drivers
https://trac.chirp.danplanet.com/chirp_daily/daily-20220210/Model_Support.html

I need to correct that it is indeed in 02/09 build but it was not in 02/02. https://trac.chirp.danplanet.com/chirp_daily/daily-20220202/Model_Support.html

Hao Xu wrote:

Hao Xu wrote:

It showed up in the build on 02/10 and 02/14, not on 02/09. So, I assume someone added the driver recently, but I can't seem to find that in the drivers
https://trac.chirp.danplanet.com/chirp_daily/daily-20220210/Model_Support.html

I need to correct that it is indeed in 02/09 build but it was not in 02/02. https://trac.chirp.danplanet.com/chirp_daily/daily-20220202/Model_Support.html

I stand corrected. I was looking at the files from 18 January which did not yet include the tg_uv2p.py driver.

Jim KC9HI

yup, I found the "commit 8236e479d0fd":http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/rev/8236e479d0fd by Ran Katz. Looks like it is working for him somehow. I have 3 units (2 Chinese domestic version and 1 US imported version) and I got none of them working. I guess I need to setup an environment and debug a bit when I got a chance

Ran Katz wrote:

Hi Hao,
I managed to test the radio on a windows machine (so far everything I did was on a MAC...) and encountered communications issues - not exactly what you experience, but very basic ones (getting "garbage" back from the radio).
I managed to fix them by changing the com port to have 2 stop bits - apparently this was documented and set in the original C application I based my driver on, obviously I missed it , but the strange thing is that I didn't encounter any issues on the MAC while on windows (with the same CH340 cable) it fails.

Once fixed it works on my radio both on MAC and on windows, read and write.

So, I uploaded a fix candidate : tg_uv2p_fix_8591_v1.py
please download it and:

1. Open CHIRP
2. Enable the developer functions: Help->Enable Developer Functions
3. Load the new driver: File -> Load Module and select the attached driver
4. Try to download : Radio ->Download from radio , select the TG-UV2+FIX model
5. if download works please try uploading as well
6. Let me know how it went

Thanks!
Ran

Hi Ran,

You rock! This works!
I was about to sniff the official software today based on our email communication and saw this update you have here.
I was using my Windows machine all the time since I wasn't sure if Macs have proper drivers for the cable. Good thing is that we caught the bug early on.

Cheers,
Hao