Hi all,
I was fortunate to fly on both August 1st and 2nd and on
down-loading the flight logs, those from August 2nd registered the date
as August 1. This occurred not only in the IGC file number (i.e. 881XXXX
instead of 882XXXX) but also in the summary statistics in SeeYou.
The really peculiar thing was that the same problem occurred with files
from two independent GPS logger systems (one an iPAC 5550 with an Emtac
bluetooth GPS and the other a Garmin Map 76S). As yet I haven't had
the opportunity to check with the Flarm record. Both systems had
correct calender date and UTC offset entered, which were unchanged when
re-checked. It was almost as if the logger failed to recognise that
the day flips over at 23-59-59 to 00-00-00 as the file numbers were
sequenced 1 and 2 (last digit in file number).
Did anyone else encounter such a problem or can anyone offer an
explanation? This is not the only time such a glitch has occurred - one
happened at an almost identical time last year with a different Garmin
Map76S. The only common factor between the two events was that both
were high altitude wave flights (20,000 feet plus) with low cockpit
temperatures. Is this a symptom of the unit possibly being outside
the prescribed operating temperature range?
Thanks in anticipation.
Geoff V
_______________________________________________ Aus-soaring mailing list [email protected] To check or change subscription details, visit: http://lists.internode.on.net/mailman/listinfo/aus-soaring
