charlie foxtrot wrote:
Hi All,

Yep, one of the b-records in my flight was corrupt, look at the log
time, shown with first 6 digits behind the B

in line 1 time is 21:12:32
in line 2 time is 22:36:00
in line 3 time is 21:12:40, look at the excerpt of Your IGC file below!

B2112323234199N10530479WA0334303580000022015000
B2236003402499N10530538WV0336003583000022015208
B2112403234260N10530608WA0338003602000020015000

The OLC did an administrative validation of my flight - THANK YOU OLC!

I received an e-mail suggesting to open the B-record in notepad, and
deleting the bogus line. Has anybody else tried this?

Chris 'CF'

Interesting. I've had 2 club members run into the same problem with
the OLC recently. Exact same scenario. Here are the relevant portions
of the latest file. Again, it's just one record out of order and,
interestingly enough, flagged as a "bad fix".

B 170222 4059430N 07500769W A 715 679
B 172206 5904629N 07500719W V 708 681
B 170230 4059510N 07500708W A 700 672

Even more intriguing, in all three files I've looked at, the longitude
and altitude portion of the fix suggests that the record is actually a
good fix but that the recording is what's screwed up (if you look these
values all fit "in sequence" just fine, but the time stamp and
lattitude are courrupted). I'm not familiar with the low-level coding
in this sort of firmware, but if I didn't know better I'd say there's a
very subtle bug in the logging module rather than a receiver problem.


BTW, I just import the file into Excel which provides a simple parser
at file open. Then, I have some macros to add values such as time
between fixes, instantaneous (fix to fix) rate of climb, and rolling
average rate of climb (last 6 fixes). Most of the problem show up
immediately with this approach.

P3