[chirp_users] How to analyse the memory map for a new radio type?

Pavel Milanes Costa pavelmc at gmail.com
Sun Dec 30 12:22:17 PST 2018

Hi Dan,

There is no silver bullet, on the chirp's wiki search for /'developer', 
there is a frew simple guide for developers.

I will suggest this steps to you:

 1. Subscribe to the developers maillist chirp_devel at intrepid.danplanet.com
 2. Setup a dev environment (clone the chirp repo, dev wiki page has
    info about it)
 3. Search on similar radios from the same OEM (Yaesu) usually OEMs tend
    to make one simple protocol for many radios, and you then need to
    tweak only the mem part, that also tend to be reused also.
 4. Decide if you it worth creating a new drivers or reusing some of the
    actual code (Yaesu has a lots of reusable code)
 5. Start coding
 6. Don't hesitate to ask question on the dev list, may be you became
    the next Yaesu Guru for Chirp!
 7. Funny, I was called recently by a user the 'Chirp's Kenwood Guru'
    ;-) on the chirp's wiki (not a guru at all, just hard work)

Happy hacking and Holiday, HNY to all.

El 30/12/18 a las 13:26, Dan Clemmensen escribió:
> I am a new Ham, and I foolishly selected a radio that is not supported 
> by CHIRP. (Yaesu FT-4XR). I wish to add support for it and its recent 
> Yaesu siblings. I have successfully analysed the serial protocol and 
> I  can read and write the memory, but I don't know what to do next. Is 
> there a HOWTO somewhere? If not, I can attempt to create one, but some 
> guidance would be appreciated.
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to M.Sc. Pavel Milanes Costa at pavelmc at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20181230/67411779/attachment-0002.html 

More information about the chirp_users mailing list