CHIRP

Rob Zak wrote in #note-1:

Cam Cornelius wrote:

Hello,

Marcus Dudley has been developing an amazing firmware for the Tidradio TD-H3. The FW is new from the ground up and currently only works with his basic programmer. Currently he is not interested in a pluging for CHIRP, but the community is. This is a fairly new firmware (still in release candidate mode), but very polished and robust with much better features and flexibility than Tidradio's stock firmware. The FB group for this firmware already has almost 8 thousand members in under 4 months.

He has published the file format and serial protocol on his website here: https://nicsure.co.uk/h3h8/forumdisplay.php?fid=8

The facebook group is here: https://www.facebook.com/groups/456942886822492

I'm not a programmer, but just wanted to make you aware. Any traction on this would be greatly appreciated.

Thank you,
Cam Cornelius
K1CAM

I am NOT a programmer! Using ChatGPT I cam up with a SHELL for a driver. I'm sure someone smarter than me can use this to make it work. It was created by using the links posted by Cam and the example.py from CHIRP.

I too want to see a working driver, so I'm only trying to give it a kick start.

Thanks, Rob. Unfortunately the module isn't loading in the latest CHIRP-Next.I get an "Invalid or unsupported module file" error.

EDIT: Just saw your note...thanks for the head start!

Rob, thanks for the effort, but that GPT-generated "driver" doesn't even resemble a CHIRP driver. The template driver in the CHIRP tree (which does nothing other than load) is much closer. If you don't mind, I'd please ask you to delete it from the attachments here because people will try it, and will contact the team and open other bugs complaining that the one in this bug does not work. I appreciate the intent, but since it's not really a better start than the template driver, it will only serve to confuse users and cause extra paperwork for the team. Thanks for understanding.

Dan Smith wrote in #note-4:

Rob, thanks for the effort, but that GPT-generated "driver" doesn't even resemble a CHIRP driver. The template driver in the CHIRP tree (which does nothing other than load) is much closer. If you don't mind, I'd please ask you to delete it from the attachments here because people will try it, and will contact the team and open other bugs complaining that the one in this bug does not work. I appreciate the intent, but since it's not really a better start than the template driver, it will only serve to confuse users and cause extra paperwork for the team. Thanks for understanding.

Dan, I can appreciate where you're coming from with the comment. I can't figure out how to delete it, or I would happily comply. I realize it won't load, I tried to be clear this doesn't work. I thought the read/write commands were correct, as well as the data structure. I'm sorry. Let me know how to remove and I surely will.

No worries, I just removed it.

Nope, none of that stuff did anything to actually talk to the radio. It was pretty typical gen-AI hallucination about all the details that were too obscure to find on google :)

Thanks anyway!

Dan Smith wrote in #note-7:

No worries, I just removed it.

Nope, none of that stuff did anything to actually talk to the radio. It was pretty typical gen-AI hallucination about all the details that were too obscure to find on google :)

Thanks anyway!

Thanks Dan, again, apologies for the distraction. Perhaps you'd be willing to take a look at creating a functional driver? Thank you.

Agreed. Any help with a driver would be appreciated, Dan.

Thanks and looking forward,
Cam

On Mon, Nov 4, 2024 at 9:10 AM Rob Zak redmine@chirpmyradio.com wrote: