Flight Log Not Complete

[[email protected][_2_]]

After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?

[kinsell]

On 9/4/20 9:05 PM, wrote:
> After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?
>

Well known problem, seen with both ClearNav and LX Nav gear. After
turning on the logger, wait a long time (like five minutes) after
getting the GPS locked notice before taking off. It takes the GPS
chipset forever to get the time completely right.

If it were ClearNav, you have the option of re-downloading the file with
a 4 second sampling time to work around the problem. Don't know that
you can do that with LX.

Dave

[Paul Remde]

Hi Terry,

I recommend updating the firmware in the LX9050 to the latest version. I think the date jump issue was fixed a while ago.

Best Regards,

Paul Remde
__________________________________

On Friday, September 4, 2020 at 10:05:07 PM UTC-5, wrote:
> After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?

[Dan Marotta]

Yes, and if you have another logger, use it!Â* I have had one fail and
simply downloaded the other one.Â* Does whatever vario you use with your
LX have a flight recorder?Â* OLC is not world record stuff, after all.

On 9/5/2020 6:37 AM, Paul Remde wrote:
> Hi Terry,
>
> I recommend updating the firmware in the LX9050 to the latest version. I think the date jump issue was fixed a while ago.
>
> Best Regards,
>
> Paul Remde
> __________________________________
>
> On Friday, September 4, 2020 at 10:05:07 PM UTC-5, wrote:
>> After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?

--
Dan, 5J

[Tango Eight]

On Saturday, September 5, 2020 at 10:29:54 AM UTC-4, Dan Marotta wrote:
> Yes, and if you have another logger, use it!Â* I have had one fail and
> simply downloaded the other one.Â* Does whatever vario you use with your
> LX have a flight recorder?Â* OLC is not world record stuff, after all..
>
> On 9/5/2020 6:37 AM, Paul Remde wrote:
> > Hi Terry,
> >
> > I recommend updating the firmware in the LX9050 to the latest version. I think the date jump issue was fixed a while ago.
> >
> > Best Regards,
> >
> > Paul Remde
> > __________________________________
> >
> > On Friday, September 4, 2020 at 10:05:07 PM UTC-5, wrote:
> >> After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?
>
> --
> Dan, 5J

OLC needs to quit making up requirements that go beyond igc.

T8

[Thomas Dixon]

On Friday, September 4, 2020 at 9:05:07 PM UTC-6, wrote:
> After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?


This happened to me with my ClearNav. I was turning off my instrument shortly after landing and then turning it back on later to download flight. The last roughly 20 minutes would be missing. I contacted Rex Williams and was told this would happen if I turned it off right after landing for some software reason the last few minutes would not record. I now wait until I am clear of the runway and back at the trailer then download and turn it off.. No longer have any missing flight track.
Boise. ID

[Frank Whiteley]

On Saturday, September 5, 2020 at 1:43:44 PM UTC-6, Thomas Dixon wrote:
> On Friday, September 4, 2020 at 9:05:07 PM UTC-6, wrote:
> > After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?
>
>
> This happened to me with my ClearNav. I was turning off my instrument shortly after landing and then turning it back on later to download flight. The last roughly 20 minutes would be missing. I contacted Rex Williams and was told this would happen if I turned it off right after landing for some software reason the last few minutes would not record. I now wait until I am clear of the runway and back at the trailer then download and turn it off. No longer have any missing flight track.
> Boise. ID

That's quite a buffer lag to write to storage, but it's exists to some extent in other loggers. Accident flight logs are sometimes missing the final moments due to power interruption before the buffer writes to storage.

Frank Whiteley

[Terry Edmonds]

On Saturday, September 5, 2020 at 7:37:47 AM UTC-5, Paul Remde wrote:
> Hi Terry,
>
> I recommend updating the firmware in the LX9050 to the latest version. I think the date jump issue was fixed a while ago.
>
> Best Regards,
>
> Paul Remde
> __________________________________
> On Friday, September 4, 2020 at 10:05:07 PM UTC-5, wrote:
> > After my glider flight today I downloaded my flight log from the LX9050 to an SD card as usual. When uploading for an OLC claim I get the message "A clock jump was found in the recording. The flight was shortened from there". Only the last 7 minutes of the flight is indicated. It was a 3 hour flight and the file size is the about the same for my other flights of similar duration. I won't know if this is a one time thing or if there is a bigger problem until I fly again. Has anyone else had this happen?

Paul; Today I updated the LX9050 firmware to the latest version 800. The previously installed version was 607. Do you believe the date jump fix was between those two versions? I flew a short 40 minute test flight and the log was good on it.

Terry

[[email protected]]

Check the logging interval. (He said the file was the correct size. The data is there.) By changing your logging interval from 1 second to 4 when you load the file onto the SD card from the 9050 the clock jump gets overlooked and you can get OLC to accept your flight. Act quickly!

Doug
W24

[Steve Bralla]

>
> OLC needs to quit making up requirements that go beyond igc.
>
> T8

True but maybe ClearNav needs to fix their problems.

[kinsell]

On 9/6/20 5:00 AM, wrote:
> Check the logging interval. (He said the file was the correct size. The data is there.) By changing your logging interval from 1 second to 4 when you load the file onto the SD card from the 9050 the clock jump gets overlooked and you can get OLC to accept your flight. Act quickly!
>
> Doug
> W24
>

Looking at the file now, it's got four second intervals and it still has
the CLOCKJUMP problem, easily seen well after takeoff. It went from
38 seconds to 37 seconds in the B records. Nasty problem. Of course he
still didn't get credit for the flight.

[Dan Marotta]

....So he had to sleep alone that night?Â* Sheesh...Â* It's beginning to
look like one's manhood hangs on the approval of OLC...

On 9/6/2020 10:02 PM, kinsell wrote:
> On 9/6/20 5:00 AM, wrote:
>> Check the logging interval. (He said the file was the correct size.
>> The data is there.)Â* By changing your logging interval from 1 second
>> to 4 when you load the file onto the SD card from the 9050 the clock
>> jump gets overlooked and you can get OLC to accept your flight. Act
>> quickly!
>>
>> Doug
>> W24
>>
>
> Looking at the file now, it's got four second intervals and it still
> has the CLOCKJUMP problem, easilyÂ* seen well after takeoff.Â* It went
> from 38 seconds to 37 seconds in the B records. Nasty problem.Â* Of
> course he still didn't get credit for the flight.

--
Dan, 5J

[kinsell]

Ummm, you were quite concerned about it when it was YOUR flight logs
that were corrupt. I guess it's no big deal unless it's YOUR flight log?


On 9/7/20 10:15 AM, Dan Marotta wrote:
> ...So he had to sleep alone that night?Â* Sheesh...Â* It's beginning to
> look like one's manhood hangs on the approval of OLC...
>
> On 9/6/2020 10:02 PM, kinsell wrote:
>> On 9/6/20 5:00 AM, wrote:
>>> Check the logging interval. (He said the file was the correct size.
>>> The data is there.)Â* By changing your logging interval from 1 second
>>> to 4 when you load the file onto the SD card from the 9050 the clock
>>> jump gets overlooked and you can get OLC to accept your flight. Act
>>> quickly!
>>>
>>> Doug
>>> W24
>>>
>>
>> Looking at the file now, it's got four second intervals and it still
>> has the CLOCKJUMP problem, easilyÂ* seen well after takeoff.Â* It went
>> from 38 seconds to 37 seconds in the B records. Nasty problem.Â* Of
>> course he still didn't get credit for the flight.
>

[Dan Marotta]

Touche'

On 9/7/2020 5:56 PM, kinsell wrote:
> Ummm, you were quite concerned about it when it was YOUR flight logs
> that were corrupt.Â* I guess it's no big deal unless it's YOUR flight log?
>
>
> On 9/7/20 10:15 AM, Dan Marotta wrote:
>> ...So he had to sleep alone that night? Sheesh...Â* It's beginning to
>> look like one's manhood hangs on the approval of OLC...
>>
>> On 9/6/2020 10:02 PM, kinsell wrote:
>>> On 9/6/20 5:00 AM, wrote:
>>>> Check the logging interval. (He said the file was the correct size.
>>>> The data is there.)Â* By changing your logging interval from 1
>>>> second to 4 when you load the file onto the SD card from the 9050
>>>> the clock jump gets overlooked and you can get OLC to accept your
>>>> flight. Act quickly!
>>>>
>>>> Doug
>>>> W24
>>>>
>>>
>>> Looking at the file now, it's got four second intervals and it still
>>> has the CLOCKJUMP problem, easilyÂ* seen well after takeoff.Â* It went
>>> from 38 seconds to 37 seconds in the B records. Nasty problem.Â* Of
>>> course he still didn't get credit for the flight.
>>
>

--
Dan, 5J