There's no benefit to .chirp over .csv. Just use .csv.

Thanks for the head's up. As I cannot upload a .csv file to the radio, I have to export it first to a format that can, that's the step I was wondering if I could get around: EG: storing metadata in a file format that can directly program the radio as well. Sounds like for the time being the best method is to work with a native .CSV file for any updates, and then export it as a .chirp file for upload to the radio,

Regards, John Kellas

On Mon, Jan 6, 2014 at 11:21 AM, Tom Hayward esarfl@gmail.com wrote:

On Mon, Jan 6, 2014 at 9:51 AM, John Kellas sales@mparam.com wrote:

...

I see when working in a .csv file I can use the comment field. That field does not export over to the .chirp file. Is there a way to add a comments field to the .chirp or .img files?

There's no benefit to .chirp over .csv. Just use .csv.

.img files are a direct data dump from the radio. They can only store fields supported by the radio. If your radio doesn't have a built in comment field (I'm not aware of any that do), then there's no way to store a comment in the .img file.

Dan has proposed a new file format that would store the img data plus some additional metadata. This is a long way from fruition.

Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

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.

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.

Regards, John Kellas

On Mon, Jan 6, 2014 at 11:48 AM, Tom Hayward esarfl@gmail.com wrote:

On Mon, Jan 6, 2014 at 10:32 AM, John Kellas sales@mparam.com wrote:

...

Thanks for the head's up. As I cannot upload a .csv file to the radio, I have to export it first to a format that can, that's the step I was wondering if I could get around: EG: storing metadata in a file format

that

...

can directly program the radio as well. Sounds like for the time being

the

...

best method is to work with a native .CSV file for any updates, and then export it as a .chirp file for upload to the radio,

The only format that will upload to the radio is that radio's .img file (they differ for every model). .chirp or .csv must first be imported into a .img before upload.

Here's how I do it:

I have a master csv file with the set of channels I like to program in my radios. Actually, I have a few master files. One has ham stuff and another has commercial channels for SAR. These are CSV files I save in the stock_config directory in the chirp folder. By doing this, they are listed in the File > Open Stock Config menu in Chirp.

When I need to program a radio, I "Download from Radio", then "Open Stock Config". This leaves me with the radio img open in one tab and my master CSV open in another tab. I copy channels in the CSV tab, then paste them in the img tab. Then from the img tab, I "Upload from Radio" and the radio is programmed.

Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users