Well damn, I wish I'd had that coffee before shooting my mouth off.
I was not out to shoot Cambridge, but that is how the post reads. I
love the Cambridge 302, this is a really nice unit. I replaced another
brand expensive European flight computer earlier this year with this
unit and would do so again in a heartbeat. I really like the netto
vario, simple operation of the logger, the great integration with
WinPilot Pro, and this unit has been rock solid (Including in a
unbelievably hot cockpit with ground temperatures well over 100F where
both of my iPAQ PDAs wedged themselves and refuse to reset and the
Cambridge 302 works just fine - and because of this I'm in the
process of installing a 303 nav display to back up the PDA.).

Yes Marc you are correct, I talked more with Cambridge staff today and
I need to correct my claim that this is a problem with all units. This
problem may occur if you start to fill the memory in the 302,
apparently only some 302s. In my case I've flown around 6,000 km with
my 302 since installing it earlier this year, that's a lot of hours
and I'm running with the default 4 second sample rate, a lot of
samples. Apparently if there is a problem the symptoms start with
seeing intermittent "Cannot ... FAT" errors on the utility software
when trying to connect to the 302 to download log files. Indeed I'd
been seeing this for a few weeks intermittently and had always blamed
my iPAQ PDA's. This problem can continue and become more frequent as
it did in my case. Anyhow the workaround of clearing memory in the 302
is easy, and can be done when intermittent FAT errors occur (meaning
you should be able to download any log files before clearing memory).
And Cambridge is working on a permanent fix.

Darryl Ramm
DG-303 Acro 6DX