I've made two flights since experiencing the problem.Â* Since then, I've
turned on my CN devices 20 or so minutes before takeoff and have not
seen a repeat of the problem.

On 5/30/2019 6:46 AM, Tango Eight wrote:
Hi Henry,

There will be no issue with Winscore.

What's going on he

1. UTC and GPS time are not the same. The current offset is 18 seconds.

2. When the GPS starts up, it starts with an offset programmed in firmware. This offset is less than 18 seconds.

3. After GPS lock, the GPS receiver gets the current offset from the system, typically about 5 minutes after GPS lock. It applies the new offset immediately, and the jump causes one out of sequence B record if the flight recorder is recording. It doesn't start recording until you are flying.

4. OLC picks up the out of sequence B record if it exists.

Since the offset change is 2 or 3 seconds, it can be masked by setting the igc file fix interval to 4 seconds. You can avoid the jump altogether by powering up 5 minutes before flying.

If you get a bad OLC result, you can fix it by downloading your flight again at either 4 or 10 second interval and resubmitting.

best regards,
Evan Ludeman


On Thursday, May 30, 2019 at 8:01:58 AM UTC-4, wrote:
Well, here I am in Cordele with R5S starting on Monday and got the OLC time error message after submitting my ClearNav II log for yesterday’s flight.
So, downloaded CN vario version and got the same error message. For thrills I loaded a flight on 5/15/19 and although OLC advised late, accepted the flight into the system. I have changed nothing nor updated either unit since 5/15 so why then, not now?
I will look at and change the interval to 4 secs and try again ( as mentioned by T8 in this thread).
Questions and request...
Will I have issues with scoring during the contest (winscore)?
I would appreciate if someone would post an update summary of do and don’t and ideas in a simple to grasp way that even an airline pilot might follow.
Many thanks.
R

--
Dan, 5J