<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Thanks, I was hoping I'd get suggestions for a better procedure than I was planning to use, and that will be how I'll do it as well.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I typically use 3 different models depending on activity. For example if I am going on a multi day AT Ski trip I'll probably take a KG-816 with a Frankenstiened AAA cell pack that uses a combination of dummy and rechargeable Li-Ion cells so I can still get the full transmit power from 8.4V if required, but also get full lumens from my headlamps or can use my Avalanche Beacon for backup batteries. But if there is a need for FRS, then it would be a simlar configured UVD1P, also with a Frankensteined 14500 Li-Ion AA cell pack. The odd time if I may need the ability to do seat of the pants telemetry, I'll carry the UV6D due to the 2.5kHz frequency stepping ability. This method will enable me to work effectively with all of them until there is a CHIRP for Android! Thanks very much.</div>
<div class="gmail_extra"><div><div dir="ltr"><div><br></div><div><font face="comic sans ms, sans-serif">Regards,</font></div><font face="comic sans ms, sans-serif">John Kellas<br></font></div></div>
<br><br><div class="gmail_quote">On Mon, Jan 6, 2014 at 11:48 AM, Tom Hayward <span dir="ltr"><<a href="mailto:esarfl@gmail.com" target="_blank">esarfl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Jan 6, 2014 at 10:32 AM, John Kellas <<a href="mailto:sales@mparam.com">sales@mparam.com</a>> wrote:<br>
> Thanks for the head's up. As I cannot upload a .csv file to the radio, I<br>
> have to export it first to a format that can, that's the step I was<br>
> wondering if I could get around: EG: storing metadata in a file format that<br>
> can directly program the radio as well. Sounds like for the time being the<br>
> best method is to work with a native .CSV file for any updates, and then<br>
> export it as a .chirp file for upload to the radio,<br>
<br>
</div>The only format that will upload to the radio is that radio's .img<br>
file (they differ for every model). .chirp or .csv must first be<br>
imported into a .img before upload.<br>
<br>
Here's how I do it:<br>
<br>
I have a master csv file with the set of channels I like to program in<br>
my radios. Actually, I have a few master files. One has ham stuff and<br>
another has commercial channels for SAR. These are CSV files I save in<br>
the stock_config directory in the chirp folder. By doing this, they<br>
are listed in the File > Open Stock Config menu in Chirp.<br>
<br>
When I need to program a radio, I "Download from Radio", then "Open<br>
Stock Config". This leaves me with the radio img open in one tab and<br>
my master CSV open in another tab. I copy channels in the CSV tab,<br>
then paste them in the img tab. Then from the img tab, I "Upload from<br>
Radio" and the radio is programmed.<br>
<div class="HOEnZb"><div class="h5"><br>
Tom KD7LXL<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
</div></div></blockquote></div><br></div></div>