<div dir="ltr">Thanks Tom<div><br></div><div>Walt</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 10, 2016 at 12:51 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"><span class="">On Wed, Feb 10, 2016 at 12:01 PM, Walt Childson <<a href="mailto:wchildson@gmail.com">wchildson@gmail.com</a>> wrote:<br>
> There are some new columns in the Img file but those columns do not get<br>
> generated in CSV.<br>
><br>
> In general the IMG columns, the memory Properties column list, the CSV<br>
> columns and the WiKi column definitions are not in sync.<br>
><br>
> I especially would like to use the Power column.<br>
<br>
</span>Hi Walt,<br>
<br>
The differences you are seeing between CSV and .img files are due to<br>
the differences between radio models.<br>
<br>
Chirp .img files are the exact contents of a radio's memory as<br>
downloaded by Chirp. This means they will be different for every radio<br>
and will only support the features of that radio. Some radios support<br>
power settings per channel, some do not, so availability of this<br>
column will vary by radio model. Likewise, Dstar columns are only<br>
available for Dstar radios, etc.<br>
<br>
Chirp CSV is meant to be a least-common-denominator format. For the<br>
most part, it contains columns supported by all radios. Not all radios<br>
support power settings, and for those that do there is no standard*,<br>
so CSV does not support a power level column. Not all radios support<br>
"priority" scanning (and this means different things for different<br>
radios), so this is intentionally left out of Chirp CSV format.<br>
<br>
*When I say there is no standard for power levels, I mean that "low"<br>
and "high" mean completely different things on different radios. Low<br>
power can mean anything from 50 mW to 10 watts, depending on the<br>
radio. High power could mean anything from 5 watts to 100 watts or<br>
more. It gets even more complicated when you add in power levels like<br>
"Mid", "Medium", "L2", "L3", etc.<br>
<br>
Chirp's import/export/copy/paste features attempt to disambiguate<br>
these power levels by assigning a value in watts to each power level<br>
in every radio that supports power levels. If you copy a "high" power<br>
radio channel from a handheld and paste it into mobile, Chirp looks up<br>
what "high" means for that handheld--typically 5 watts--then attempts<br>
to find the closest power level to 5 watts on the mobile--probably<br>
"low" power. Since CSV format is not tied to a specific radio, there's<br>
no good baseline power levels to choose from, so it just isn't<br>
supported.<br>
<br>
Adding an unsupported column to a CSV file will not add support for<br>
that column in Chirp. You would also need to add the column in the<br>
Chirp code and write code for how to interpret that column. This code<br>
would be relatively simple to write if not for the problem I mentioned<br>
above--you would need to define how to disambiguate all the possible<br>
options.<br>
<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" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Walt Childson at <a href="mailto:wchildson@gmail.com">wchildson@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</blockquote></div><br></div>