On Nov 20, 11:54*am, Papa3 wrote:
On Nov 20, 8:45*am, T8 wrote:

On Nov 20, 8:06*am, Papa3 wrote:

On Nov 18, 4:03*pm, "noel.wade" wrote:
[snip]
Hi Evan,

You know me better than that *:-)

While you're right that a paper declaration is sometimes safer, there
are a number of situations where where an electronic declaration is
needed. * The problem I have with the EW is largely that I can't
always be sure that there is nothing in the declaration. * For
instance, I have a null (blank) declaration on the SD card that should
overwrite what's on the EW. * That should work... unless, I somehow
get the boot sequence wrong. * Or, I've decided to change the task at
the last minute, and I want to make sure I'm "official" in that both
FRs have the same task. * Or, I'm trying for a category of record that
requires an electronic declaration.

I guess my point is just that a *reliable declaration process in an FR
is a pretty important thing IMO.

While its nice to have electronic declarations that work reliably
almost everybody will be fine with paper and should be making paper
declarations even if they do an electronic one. The only situation
where that does not apply AFAIK is FAI world records. Right? Most of
us should carry paper forms and do a paper declaration (in addition
and after the electronic declaration is made) ...

BTW many of these usability issues are unneeded pain and is
unfortunately outside the IGC specs so vendors get to invent all sorts
of creative usability problems. e.g some of the EW ones mentioned
here, or the Volkslogger re-time stamping a declaration at power-on
(enough of a trap IMNSHO to warn people off the Volkslogger altogether
if you are doing badges/records) or the older Cambridge GPS (e.g.
Model 20) (not the C302) overwriting declarations in IGC files stored
on the recorder. Some of these are things that the vendors should have
just fixed in the products. BTW on the EW I suspect they tried to make
things automatic and the behavior configurable but ended up confusing
some people with the complexity of settings and sometimes unexpected
behavior.

Personally I like just making a declaration from SeeYou Mobile to the
flight recorder (C302 in my case).

Darryl