On Apr 30, 6:53*pm, wrote:
Downloaded two ways.
For my flight on Sunday 27th,used SeeYou to a laptop. That failed up front, rejected instantly by OLC. So I sent a help message and Hannes, one of the nice people at OLC, removed what he called all the spikes in the B records and it *scored satisfactorily.
Having had a problem with that method, for my flight on Monday I downloaded via a PDA using the Cambridge utility program, to a Compact Flash card and hence to the OLC. (This was the method I used all last year with zero problems.) That upload appeared to work normally, but it came up with a red V and an automatically generated note saying there appears to be a problem with the logger, please contact agent or manufacturer.
Since this forum has routinely been so helpful sharing experiences I thought that I would ask here first before taking the 302 out of the panel.







On Tuesday, April 30, 2013 10:54:56 AM UTC-6, wrote:
My 302 worked last year, but for the first flights this year has a problem with OLC. *Nothing was touched on the instrument in the meantime.

OLC reports that the 'b' records in the log are inconsistent and are described as having spikes. *The OLC help team kindly restored one of the two logs I have so far submitted, but can't expect them to do it regularly.

Any suggestions? *Anybody been through this already? *Or is my 302 destined for a trip to Cambridge?

Thanks, Howard (HL).

You may have the dreaded 302 rollover bug. Paul Remde's website has
the cure
John Cochrane