[chirp_users] New stable version, power in csv

[chirp.cordless at xoxy.net]

> Date: Thu, 7 Nov 2013 14:22:38 -0500
> From: "John LaMartina" <JohnLa at usa.net>
> 
> What type radio are you trying to program?

Yaesu FT-60s and an FT-8800.
Maybe more units for my CERT group if I can get them onboard with
Chirp, but that's what I have cables for.

> Date: Thu, 7 Nov 2013 11:24:15 -0800
> From: Tom Hayward <esarfl at gmail.com>
> 
> There was some talk recently of releasing 0.4.0. No time table.

OK, thanks. It would be welcome. Just sayin' ...

>> Second: I can readily see how to set the power level for a memory
>> when a .img file is loaded, and save and reload that.
>> 
>> But I like to build my memory images from a collection of spreadsheets,
>> kind of mix-n-match. Exporting to csv, it looks like the power level is lost,
>> and so I infer I also can't build a csv with power level info and import it.
>> 
>> Am I missing something, or could that be added, or is there another
>> workflow that would address this issue?
> 
> We can't think of a good way to do this. Maybe you have an idea.
> Here's an example:
> 
> Export from a 5W handheld set to high power. Import to a 50W mobile.
> Do you set the imported channel on the mobile to low power, because
> that is the closest option to 5W?
> 
> We haven't been able to solve this ambiguity, so we just don't
> import/export power.

I understand the issue. My suggestion: Don't let the perfect be the enemy
of the good. Right now your struggle with the general case is preventing
me from automating the repeated programming of the same radio in the
specific case.

So specifically, first approach: Export the power level to csv. When importing
from csv, put up a dialogue, once per file import, that asks whether to import 
the power level in the csv or substitute a user selectable default.

The user is alerted to the issue, but at least can control it.
In my case, I might decide it's worth the trouble to prepare two spreadsheets,
one for FT-60, one for FT-8800. More effort, but better than the status quo.

Or I might then put the power levels I want for the FT-8800 in the spreadsheet,
and when importing to an FT-60, default all to high. In my experience, less than
5W is rarely usable, I often can't reach the whole group on simplex at 50W with
my FT8800! And I can barely reach our local CERT repeater on 446 with my HT at 5W.
So in this case, I have what I want even though there's some kludging going on.

That's not solving the general case, but nobody will be blindsided that there's a
name/Watt translation done by the importation that they may need to clean up.
Which is no worse than what exists now.


If you want a first crack at the general case: It's no secret what absolute
power level (watts) hi/med/lo means for a given radio and band.
That's three values for FT-60 and arguably eight, depending on
how the data structure is organized, for FT-8800.

Export the numerical watts to csv and do the best approximation on import.
I'd build this on top of the first implementation, and allow exporting as either
name or watts, and still allow a default substitution on import.

But bottom line, as long as the user isn't surprised that a translation is
being performed, and there's some reasonable control of that to cover
the important cases (same radio, or mobile -> HT) then you have improved
usability and no reason for complaint by users, I think. The obsessive user
can either maintain separate spreadsheets per radio, or be alerted that they
need to do a "power level cleanup" pass on the .img after importing.

You say you've been thinking about this, and what I've suggested isn't
rocket surgery. So perhaps I'm missing something. I'm happy to
continue the discussion.

Thanks and regards,

-dan