CHIRP

If the radio is in 'Normal Mode' don't you want download with CHIRP using the TD-H3 selection? Using the TD-H3-HAM selection sets CHIRP to use only the ham frequency ranges (144-148 MHz and 420-450 MHz) so trying to add FRS/GMRS frequencies would be 'out-of-supported-range'. The TD-H3 selection supports 135-174 MHz and 400-520 MHz, which should be what you want.

You have to use the TD-H3-Ham setting as far as I know.The other TD-H3 don' seem to connect to the radio.

Richard Dubey wrote in #note-2:

You have to use the TD-H3-Ham setting as far as I know.The other TD-H3 don' seem to connect to the radio.

Then according to the driver, the radio must be in "ham" mode, not "normal" mode.

I will try this again when I get home. But I'm pretty sure I accessed the radio when it was in GMRS, HAM and NORMAL mode all with the TD-H3-Ham setting selected in CHIRP. Pretty sure the other TD-H3 settings never worked (wouldn't connect to the radio) for me no matter the radio settings. I will re-verify later today.

I think the original authors of this driver shouldn't have registered the base driver, only the ham/gmrs variants. I just didn't know how these radios behaved when I reviewed it.

Jim, I developed something new for the K5 driver variants that allows proper detection of variants like these so the user only has to choose one from the list and it will pick the right one. If you can hold off for a bit, let me try to get that working for this driver (I have one to test with). If so, it'll be a better user experience I think.

Rich, if you can just use this tweak for the moment, please do and give me a few days to try this, okay?

Jim, Dan

I'm fine for now. I've got all the FRS and GMRS channels as well as the Connecticut Repeaters in my area. I tested a couple repeaters and everything seems to be fine. I most likely won't be adding too much for a little bit, still getting used to the HT thing. I've generally been more of a HF guy so this is new to me. I really appreciate how quickly you resolved this and if I can help any more let me know.

73
Rich
W1SPS
WSAE654

Dan,

I was lucky to have just received a TD-H3. I just never got around to open the box. Without it I would have had no way of knowing what was going on.

I was going to ask Richard the firmware version installed in his radio. Mine is 231228. My plan was to upgrade to the latest firmware version (240427) to see if that changed anything. The 'ident_mode' as currently programmed for the Ham, GMRS and Normal modes all match those used for the TD-H8. I don't have an 'H8' so I was going to contact you to see if you had one for testing.

How do you check the firmware?

Richard Dubey wrote in #note-10:

How do you check the firmware?

Tap the blue button and then tap the v key as many times as it takes to get to the Version menu.

Dan,

After updating my TD-H3 to the latest firmware from Tidradio, the existing CHIRP support works 100%. The firmware that shipped with my TD-H3 (sold and setup as a GMRS model) is "broken" when set to 'Normal' mode (which is the more required for full-band TX/RX support).

Richard,

The problem is the radio's firmware. I would expect that the firmware version in your radio is the same as mine or at least an older version prior to fixing the cloning issue when the radio is set to 'Normal' mode.

Okay, well, I still want to do the detection thing, even for people with updated firmware. I'll check what I've got on mine as well.

Are you saying there really are three separate versions of the radio, normal, ham, and GMRS?

Not three separate radios, you might say 3 different modes. Shut the radio off then push PTT and the top right keypad button (with the little key on it) and turn the radio on. There will be three selections Ham, GMRS and Normal. I will check the the Version when I get home later today.

73
Rich
W1SPS
WSAE654

Dan Smith wrote in #note-13:

Okay, well, I still want to do the detection thing, even for people with updated firmware. I'll check what I've got on mine as well.

Sure. Go ahead. I have worked with/used other drivers that do this. Unfortunately they bring issues with them that would be nice if steps could be taken to eliminate all or at least some of them.

I am currently working on a radio that will be supported by this driver. I will pause work on it for now and pick it back up when you have finished.

Are you saying there really are three separate versions of the radio, normal, ham, and GMRS?

Yes. Like radios from other vendors, these radios are configured at the factory, packaged and sold as different version. My TD-H3 was packaged and sold as a GMRS version with appropriate FCC ID. It is only because the hidden menu that allows the mode (Ham, GMRS and Normal) to be selected. I have radios from other vendors that the hidden menu and others that requires a special software program to switch between the various modes (US Ham, EU Ham, PMR, FreeNet, etc.).

Ok the Firmware on my TD-H3 is HAM_240229

Rich

My first testing with test driver and TD-H3 downloading...

TD-H3 Mode 1 (Ham): downloaded but failed identified (TD- H8 -Ham)
TD-H3 Mode 2 (GMNRS): downloaded but failed identified (TD- H8 -GMRS)
TD-H3 Mode 3 (Normal): downloaded and passed identification (TD-H3)

Hmm, that's odd, this works for me on the H3 and H8 in all three modes each. Can you grab debug logs? And to be clear, without the detect patch (and code as it is in master) you can download them all if you choose them manually?

Ah, I bet I know what's going on, I bet your system is sorting the classes differently from mine, lemme try to fix that.

My first testing with test driver and TD-H3 uploading...

All seems to work 100%. Images upload to radio when the radio's mode matches the image's mode. When the radio's mode does not match the image's a "Model mismatch!" error is presented.

Dan Smith wrote in #note-22:

Okay, yeah, glad you found that. Weird that mine sorts 100% the favorable way and yours doesn't, but who knows. Maybe because it gets done in a different order when loading. Anyway, give this one a shot instead please :)

The second one works great. Double checked uploading again. All as expected.

This would be super great to add to RT95. People with RT95_VOX radio fails download when they choose RT95. Instead of trying RT95_VOX like the prompt tells them, they contact Retevis or file a bug saying that it doesn't work.

Okay cool, I'll get this pushed up then as I found a typo in the UI while I was doing it that needs fixing.

And yep, I think there are probably lots of other radios where this strategy would be beneficial.

So actually, I might have lost track of the original issue here. Jim, your problem was needing a firmware update and then you're good, right? What about Rich? Seems like he has a newer firmware than both of us and still has a problem?

Ah I guess there's something newer than what Rich is running, so perhaps that's what he needs to do?

Dan Smith wrote in #note-25:

So actually, I might have lost track of the original issue here. Jim, your problem was needing a firmware update and then you're good, right? What about Rich? Seems like he has a newer firmware than both of us and still has a problem?

I am thinking that Rich had the same issue. The radio when set to Normal mode was responding with the Ham response. So it couldn't be read with the TD-H3 menu pick. It instead has to be read with the TD-H3-Ham pick which limited the valid bands to only ham frequencies. The firmware update noted that OEM CPS had the same issue.

The firmware update corrected the response when the radio was was in Normal mode. So this ticket was actually 'not a bug' for CHIRP.

Okay, so I don't see that you listed what version you upgraded to, but I'm guessing it's newer than 2402xx?

Anyway, I'm going to say I'm "fixing" this bug with the detection patch. It's a loose definition of "fixing" as in "making it detect the correct radio (when the firmware is right)" :)

Dan Smith wrote in #note-28:

Okay, so I don't see that you listed what version you upgraded to, but I'm guessing it's newer than 2402xx?

It was most recent firmware available: 240427 (released the same day as the most recent CHIRP-next build). I mentioned it in note-9.

Ah, sorry I missed it. Okay cool, well, I'll merge this as tested and hopefully Rich can apply that update and be fixed as well.

My radio is pretty new, I got it only a week and a half ago.

Lol, sorry folks. I'm a little confused. The last fix I tried allowed me to address the radio with TD-H3 (when radio was set to "Normal" mode). This worked and allowed me to set up FRS, GMRS and some Ham Repeaters. All of which loaded back to the radio and function.

So you want me to try CHIRP with the "Detect-o-matic" fix loaded? And If so what would you like me to do?

Rich

Richard Dubey wrote in #note-31:

My radio is pretty new, I got it only a week and a half ago.

Mine was brand new, too. I received it on 4/23 and only opened the package and turned it on to help you.

Lol, sorry folks. I'm a little confused. The last fix I tried allowed me to address the radio with TD-H3 (when radio was set to "Normal" mode). This worked and allowed me to set up FRS, GMRS and some Ham Repeaters. All of which loaded back to the radio and function.

While doing research for this issue, it was discovered that the 'fix' I provided was just a workaround for a bug in the firmware.

Your radio with 240229 (February 29, 2024) firmware just like mine with 231228 (December 28, 2023) firmware, when configured for Normal mode are/were replying to CHIRP as if it was in Ham mode. That is why you could only get it to work in Ham mode.

With this bug, your radio won't work with the factory TD-H3 'Normal' mode software. Try it. You will have to use the TD-H3 (Ham) software to program your radio when set in Normal mode because of the firmware bug. And like CHIRP, this 'Ham' software will be limited programming only ham frequencies.

The 'fix' is to update your firmware to at least a version that fixes the firmware bug. I was able to come with firmware versions 240229, 240401 and 240427. I opted to install the latest TD-H3 firmware available which was released April 27th (240427).

So you want me to try CHIRP with the "Detect-o-matic" fix loaded? And If so what would you like me to do?

Yes. But it will only work after you update your radio's firmware. Once you update your radio's firmware, the currently available CHIRP-next will work (as will the factory software). The 'Detect-o-matic' is more of an added convenience than it is a 'fix' (CHIRP can't fix a firmware bug).

Rich

Jim

Ok, I will update the firmware to (April 27th (240427) when I get home today.
Rich

Richard Dubey wrote in #note-33:

Ok, I will update the firmware to (April 27th (240427) when I get home today.
Rich

My recommendation would be to not upgrade to today's CHIRP-next build right away.

• The first thing that you should do would be to make sure you have a current CHIRP image saved from your radio in Normal mode using my original workaround.
• Next would be to update your radio's firmware to the latest that is available from the Tidradio downloads page. Unfortunately you will have to create an account and log in before you can make any downloads. You can download any of the TD-H3 versions available. The only difference is the CPS that is provided with the ZIP file: Ham, GMRS or unlocked. The firmware is the same. The firmware uploader and instructions for using it are included in the 1.H3 Firmware Upgrade folder that is contained in the ZIP file.
• After you have upgraded the firmware, make sure that the Normal mode is still selected. Then use you current CHIRP-next (not the one from today) to download from your radio using the TD-H3 model selection. This should now work without need loading the workaround that I provided. I don't know if updating the firmware removed the programming or not. If it does, then upload the image that you made before you started.
• Once you've updated the firmware and are sure that you channels and settings are correct, you can then upgrade to the latest CHIRP-next that was released today. It will include the new 'Detect-o-matic' feature.