[chirp_devel] Newbie working on New Model #4787

Dan Clemmensen
Sun Dec 30 20:00:48 PST 2018


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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20181230/082c681f/attachment-0001.html 


More information about the chirp_devel mailing list