FlyWithCe recorder woes

Ladies and Gentlemen:

I've had a recurring technical issue with my FlyWithCE flight recorder
purchased a couple of weeks ago, and wanted to see if others had had
the same experience and could offer a possible cause or solution.

Last Saturday and this Saturday, I flew flights of just under 500KM
and just under 600KM, respectively. The latter was good enough for
diamond goal and return and distance, but of course the EW died on the
way out there also. Both were out of Jean, NV (GMT+7). Upon
downloading the flights, I was surprised to find that both flights
were cleanly split into two separate logs each, at exactly Zulu
changeover (1700 local). It gets more interesting... all data post-
Zulu changeover seems to have been stamped with the date previous to
the one I flew!

Here are the examples. The first flight was taken on 20 June.

http://www.onlinecontest.org/olc-2.0...htId=109146687

And here's the second section of that flight, incorrectly stamped 19
June:

http://www.onlinecontest.org/olc-2.0...htId=109355395

Here is the first section of my 27 June flight:

http://www.onlinecontest.org/olc-2.0...htId=627288331

And the second section, incorrectly dated 26 June:

http://www.onlinecontest.org/olc-2.0...htId=627122754

Both flights, I had a fresh set of batteries, and the logger was kept
cool, shaded by the Kestrel's turtle deck. It received and excellent
signal all day, and the actual position of the aircraft doesn't seem
to have been corrupted at all.

Has anyone else had these issues? Is there any way of telling if it's
a hardware (logger) or software (downloading software) issue? I've
corresponded with Uros at FlyWithCE, and he's working towards a
solution but hasn't found the particular reason for this yet.

The logger is an excellent idea, and could really get large groups of
normal pilots (me) out there flying distance. I also understand that,
as a new product, there are bound to be bugs. I just wish the bugs
allowed the distance to be counted as LONGER than actual!

I guess it's also possible that Uros has created a time machine. If
so, maybe it will take me back to the 1980s.

http://www.hulu.com/watch/8729/napol...e-time-machine

Mark
OZ

U¿ytkownik Ferstlesque napisa³:

Last Saturday and this Saturday, I flew flights of just under 500KM
and just under 600KM, respectively. The latter was good enough for
diamond goal and return and distance, but of course the EW died on the
way out there also.
EW? EW is a certified logger. FlyWithCE is a recording device which is
not certified, so can't be used to claim any FAI badge/diamond.

--
Wojtu¶.net

On Jun 28, 1:20*pm, Wojciech Scigala wrote:
U¿ytkownik Ferstlesque napisa³:

Last Saturday and this Saturday, I flew flights of just under 500KM
and just under 600KM, respectively. The latter was good enough for
diamond goal and return and distance, but of course the EW died on the
way out there also.

EW? EW is a certified logger. FlyWithCE is a recording device which is
not certified, so can't be used to claim any FAI badge/diamond.

--
Wojtu¶.net

He never said he wanted to use this logger for a badge leg claim.

I had some problems discovering this bug. First I had to create
appropriate recording which this is very late here – it is 2 AM at
midnight UTC here. I overslept twice waiting for the UTC midnight.
After I created the recording it was easy – the mistake was small and
I already released the update. Logbook version 1.15 fixes this
problem.

Bug was fixed in 8 days and it would be sooner if I would not have to
wait until UTC midnight. :-)

Best regards

Uros