Hi Dan
Following is just my personal opinion: when you begin, just take some older Yeasu HT as basis, and copy it to FT4.py -file. This way you will get prototypes of needed procedures, so you can start modifying those. After you have managed to get data from radio to Chirp and back, then it might be a good time to ask from Chirp users and developers lists, whether there are others having those newer Yeasus. And then, it would be a good time to decide, into which family your new implementation would be stored.
I am also a new developer in Chirp (and also in Python). I have worked (and am still working) in embedded world, using mainly C as the programming tool, so my approach might be a bit skewed.
BR,
Kalle
Dan Clemmensen via chirp_devel kirjoitti 31.12.2018 klo 6:00:
I am a new Ham who foolishly purchased a radio not supported by CHIRP. (Yaesu FT-4XR). This HT and its modern siblings (FT-65, FT-75, FT-35...) do not use the same protocol as older Yaesu HTs (e.g. FT-60, Ft-70), nor do they use the same cable. They may not use the same memory map either, but the documentation makes it likely that the family's memory maps will be similar to each other but of different sizes. I have figured out the protocol but not the memory map. I now understand how to work on the map (Thanks, Al and Pavel!).
Looking at the "drivers" directory, it appears that each supported radio has its own .py file, but there is also shared code when a bunch of radios have similar protocols or memory maps. I see how to build a driver for my FT-4XR, but it is not clear how to structure this code to make it easy to add support for other members of the family.
I do not have a good name for the family. They all share the SCU-35 programming cable, and this cable is not used by any other radios, so one thought is to name the common module scu35.py, but that seems like a weird name. Any guidance will be appreciated. I could just create FT4.py and let others deal with other family members, but that seems selfish. Is there an existing family that I can use as a worked example of how to structure the code?
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers