<div dir="ltr">It looks as though it may have been addressed but never actually added in?<div><br></div><div><a href="http://chirp.danplanet.com/attachments/513/fix_kenwood.patch">http://chirp.danplanet.com/attachments/513/fix_kenwood.patch</a><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 8, 2015 at 12:39 PM, Tom Hayward <span dir="ltr"><<a href="mailto:tom@tomh.us" target="_blank">tom@tomh.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Apr 8, 2015 at 4:55 AM, Ryan Tourge <<a href="mailto:ryan.tourge@gmail.com">ryan.tourge@gmail.com</a>> wrote:<br>
> I made some changes to kenwood_live.py on my local system (mac) to allow<br>
> CHIRP to work with all the frequency steps the Kenwood 271/281/471 supports<br>
> (2.5 Khz was what I was interested in). It works great on my mac and linux<br>
> machines. For it to work on windows I would need to recompile from source<br>
> correct?<br>
<br>
</div></div>This is the use case the Load Module feature was designed to solve. To<br>
use it, turn on developer features, then go to File > Load Module, and<br>
choose your edited kenwood_live.py file every time you launch Chirp.<br>
<br>
The optimal long-term solution is to submit these changes for<br>
inclusion in Chirp, so that everyone can benefit from your work.<br>
<br>
Tom KD7LXL<br>
_______________________________________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br>
</blockquote></div><br></div>