GPS week rollover issue

[Jonathan Foster]

I just came across this interesting page: https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know

On April 6th of this year the GPS week will roll over and on some older instruments it could mess up the date. How many of our soaring instruments might have this problem?

Jonathan

[kinsell]

On 2/6/19 10:00 AM, Jonathan Foster wrote:
> I just came across this interesting page: https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>
> On April 6th of this year the GPS week will roll over and on some older instruments it could mess up the date. How many of our soaring instruments might have this problem?
>
> Jonathan
>
There's some potential for problems, but some of the firmware has been
hacked to delay the actual appearance of the problem for years in the
future. I doubt there's going to be a big ripple of problems in April.

[Tim Newport-Peace[_4_]]

At 17:00 06 February 2019, Jonathan Foster wrote:
>I just came across this interesting page:
>https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>
>On April 6th of this year the GPS week will roll over and on some older
>instruments it could mess up the date. How many of our soaring
instruments
>might have this problem?
>
>Jonathan
>
Any of them, but the older instrument the more likely it is to have a
problem.

The date is transmitted by the satellite as a day oy the week and a week
number. there are 11 bits available for the week number (0-1023) and a
rollover occurs every 1024 weeks (an Epoch) or 19 years 8 months approx.

As the GPS engine in the instrument does not receive the Epoch number from
a satellite, it relies on a Battery Maintained Real Time Clock on the GPS
Engine module. If the battery fails or is allowed to become discharged,
Epoch 0 may be assumed, which it probably isn't. Epoch 0 started 6th Jan
1980 originally, but some recorders may have a different date set to fix
previous rollover problems.

The RTC battery should hold up for six months or so, but as the battery
becomes older, the capacity may decrease, reducing the figure. The best
advice seems to be to connect your instrument just before 6th April to
allow the GPS Engine battery to charge. And pray. If you Recorder has the
right date after 6th April 2019 all is well and good, but never allow the
RTC battery to become discharged.

If you have the wrong date after 6th April, it is a Return-to-Manufacturer
repair.

Good Luck!

[Jonathan Foster]

Tim, thanks for that explanation. Is this what happened to the Cambridge instruments that needed an update to keep working several years ago?

On Wednesday, February 6, 2019 at 10:45:04 AM UTC-7, Tim Newport-Peace wrote:
> At 17:00 06 February 2019, Jonathan Foster wrote:
> >I just came across this interesting page:
> >https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
> >
> >On April 6th of this year the GPS week will roll over and on some older
> >instruments it could mess up the date. How many of our soaring
> instruments
> >might have this problem?
> >
> >Jonathan
> >
> Any of them, but the older instrument the more likely it is to have a
> problem.
>
> The date is transmitted by the satellite as a day oy the week and a week
> number. there are 11 bits available for the week number (0-1023) and a
> rollover occurs every 1024 weeks (an Epoch) or 19 years 8 months approx.
>
> As the GPS engine in the instrument does not receive the Epoch number from
> a satellite, it relies on a Battery Maintained Real Time Clock on the GPS
> Engine module. If the battery fails or is allowed to become discharged,
> Epoch 0 may be assumed, which it probably isn't. Epoch 0 started 6th Jan
> 1980 originally, but some recorders may have a different date set to fix
> previous rollover problems.
>
> The RTC battery should hold up for six months or so, but as the battery
> becomes older, the capacity may decrease, reducing the figure. The best
> advice seems to be to connect your instrument just before 6th April to
> allow the GPS Engine battery to charge. And pray. If you Recorder has the
> right date after 6th April 2019 all is well and good, but never allow the
> RTC battery to become discharged.
>
> If you have the wrong date after 6th April, it is a Return-to-Manufacturer
> repair.
>
> Good Luck!

[Dan Marotta]

My old Cambridge gps had to be sent back to be reset.Â* What about the
ClearNav or PowerFlarm portable?

On 2/6/2019 10:56 AM, Jonathan Foster wrote:
> Tim, thanks for that explanation. Is this what happened to the Cambridge instruments that needed an update to keep working several years ago?
>
> On Wednesday, February 6, 2019 at 10:45:04 AM UTC-7, Tim Newport-Peace wrote:
>> At 17:00 06 February 2019, Jonathan Foster wrote:
>>> I just came across this interesting page:
>>> https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>>>
>>> On April 6th of this year the GPS week will roll over and on some older
>>> instruments it could mess up the date. How many of our soaring
>> instruments
>>> might have this problem?
>>>
>>> Jonathan
>>>
>> Any of them, but the older instrument the more likely it is to have a
>> problem.
>>
>> The date is transmitted by the satellite as a day oy the week and a week
>> number. there are 11 bits available for the week number (0-1023) and a
>> rollover occurs every 1024 weeks (an Epoch) or 19 years 8 months approx.
>>
>> As the GPS engine in the instrument does not receive the Epoch number from
>> a satellite, it relies on a Battery Maintained Real Time Clock on the GPS
>> Engine module. If the battery fails or is allowed to become discharged,
>> Epoch 0 may be assumed, which it probably isn't. Epoch 0 started 6th Jan
>> 1980 originally, but some recorders may have a different date set to fix
>> previous rollover problems.
>>
>> The RTC battery should hold up for six months or so, but as the battery
>> becomes older, the capacity may decrease, reducing the figure. The best
>> advice seems to be to connect your instrument just before 6th April to
>> allow the GPS Engine battery to charge. And pray. If you Recorder has the
>> right date after 6th April 2019 all is well and good, but never allow the
>> RTC battery to become discharged.
>>
>> If you have the wrong date after 6th April, it is a Return-to-Manufacturer
>> repair.
>>
>> Good Luck!

--
Dan, 5J

[Tim Newport-Peace[_4_]]

A number of Legacy Cambridges had problems. They use the Garmin GPS25
Engine and lets face it, the batteries are very old now. I believe that CAI
replaced the GPS Engine, which includes the RTC Battery.

ClearNav are more recent by far, so are unlikely to be affected.

I'm not sure about Flarm, why not ask them?

Tim.

At 18:40 06 February 2019, Dan Marotta wrote:
>My old Cambridge gps had to be sent back to be reset.Â* What about the
>ClearNav or PowerFlarm portable?
>
>On 2/6/2019 10:56 AM, Jonathan Foster wrote:
>> Tim, thanks for that explanation. Is this what happened to the
Cambridge
>instruments that needed an update to keep working several years ago?
>>
>> On Wednesday, February 6, 2019 at 10:45:04 AM UTC-7, Tim Newport-Peace
>wrote:
>>> At 17:00 06 February 2019, Jonathan Foster wrote:
>>>> I just came across this interesting page:
>>>>
>https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>>>>
>>>> On April 6th of this year the GPS week will roll over and on some
older
>>>> instruments it could mess up the date. How many of our soaring
>>> instruments
>>>> might have this problem?
>>>>
>>>> Jonathan
>>>>
>>> Any of them, but the older instrument the more likely it is to have a
>>> problem.
>>>
>>> The date is transmitted by the satellite as a day oy the week and a
week
>>> number. there are 11 bits available for the week number (0-1023) and a
>>> rollover occurs every 1024 weeks (an Epoch) or 19 years 8 months
approx.
>>>
>>> As the GPS engine in the instrument does not receive the Epoch number
>from
>>> a satellite, it relies on a Battery Maintained Real Time Clock on the
>GPS
>>> Engine module. If the battery fails or is allowed to become
discharged,
>>> Epoch 0 may be assumed, which it probably isn't. Epoch 0 started 6th
Jan
>>> 1980 originally, but some recorders may have a different date set to
fix
>>> previous rollover problems.
>>>
>>> The RTC battery should hold up for six months or so, but as the
battery
>>> becomes older, the capacity may decrease, reducing the figure. The
best
>>> advice seems to be to connect your instrument just before 6th April to
>>> allow the GPS Engine battery to charge. And pray. If you Recorder has
>the
>>> right date after 6th April 2019 all is well and good, but never allow
>the
>>> RTC battery to become discharged.
>>>
>>> If you have the wrong date after 6th April, it is a
>Return-to-Manufacturer
>>> repair.
>>>
>>> Good Luck!
>
>--
>Dan, 5J
>

[Tango Eight]

I'll post information pertinent to ClearNav products here and on the CN user forum as soon as I have the official story.

-Evan

On Wednesday, February 6, 2019 at 5:15:04 PM UTC-5, Tim Newport-Peace wrote:
> A number of Legacy Cambridges had problems. They use the Garmin GPS25
> Engine and lets face it, the batteries are very old now. I believe that CAI
> replaced the GPS Engine, which includes the RTC Battery.
>
> ClearNav are more recent by far, so are unlikely to be affected.
>
> I'm not sure about Flarm, why not ask them?
>
> Tim.
>
> At 18:40 06 February 2019, Dan Marotta wrote:
> >My old Cambridge gps had to be sent back to be reset.Â* What about the
> >ClearNav or PowerFlarm portable?
> >
> >On 2/6/2019 10:56 AM, Jonathan Foster wrote:
> >> Tim, thanks for that explanation. Is this what happened to the
> Cambridge
> >instruments that needed an update to keep working several years ago?
> >>
> >> On Wednesday, February 6, 2019 at 10:45:04 AM UTC-7, Tim Newport-Peace
> >wrote:
> >>> At 17:00 06 February 2019, Jonathan Foster wrote:
> >>>> I just came across this interesting page:
> >>>>
> >https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
> >>>>
> >>>> On April 6th of this year the GPS week will roll over and on some
> older
> >>>> instruments it could mess up the date. How many of our soaring
> >>> instruments
> >>>> might have this problem?
> >>>>
> >>>> Jonathan
> >>>>
> >>> Any of them, but the older instrument the more likely it is to have a
> >>> problem.
> >>>
> >>> The date is transmitted by the satellite as a day oy the week and a
> week
> >>> number. there are 11 bits available for the week number (0-1023) and a
> >>> rollover occurs every 1024 weeks (an Epoch) or 19 years 8 months
> approx.
> >>>
> >>> As the GPS engine in the instrument does not receive the Epoch number
> >from
> >>> a satellite, it relies on a Battery Maintained Real Time Clock on the
> >GPS
> >>> Engine module. If the battery fails or is allowed to become
> discharged,
> >>> Epoch 0 may be assumed, which it probably isn't. Epoch 0 started 6th
> Jan
> >>> 1980 originally, but some recorders may have a different date set to
> fix
> >>> previous rollover problems.
> >>>
> >>> The RTC battery should hold up for six months or so, but as the
> battery
> >>> becomes older, the capacity may decrease, reducing the figure. The
> best
> >>> advice seems to be to connect your instrument just before 6th April to
> >>> allow the GPS Engine battery to charge. And pray. If you Recorder has
> >the
> >>> right date after 6th April 2019 all is well and good, but never allow
> >the
> >>> RTC battery to become discharged.
> >>>
> >>> If you have the wrong date after 6th April, it is a
> >Return-to-Manufacturer
> >>> repair.
> >>>
> >>> Good Luck!
> >
> >--
> >Dan, 5J
> >

[Andy Blackburn[_3_]]

Our very own Y2K bug. To be fair, they designed it before 2000 made us all worry about such things, but still, maybe they could've allocated an extra hex character.

9B

[Bruce Hoult]

On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster wrote:
> I just came across this interesting page: https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>
> On April 6th of this year the GPS week will roll over and on some older instruments it could mess up the date. How many of our soaring instruments might have this problem?

I'm guessing that will be the final end of my 1994 Cambridge Model 10. (It's already had the battery replaced, of course)

[Tim Newport-Peace[_4_]]

At 02:12 07 February 2019, Andy Blackburn wrote:
>Our very own Y2K bug. To be fair, they designed it before 2000 made us
all
>worry about such things, but still, maybe they could've allocated an
extra
>hex character.
>
>9B
>
It is just transmissions on the L1 frequency that have this limitation.
Transmissions on L2 & L5 do not, but GPS Engines in Flight Recorders use
L1,
presumably on cost grounds.

[Dan Daly[_2_]]

I asked the Canadian dealer, Solaire Canada. He asked FLARM Technology. He just got back: "We have confirmed with the manufacturer of our GPS receiver modules (u-blox) that they handle the GPS week rollover event on April 6th 2019 correctly. We thus do not expect any issues on that date. This applies to all Classic and PowerFLARM devices, as well as OEM devices using a u-blox GPS receiver." So, no worries for PowerFLARMs and rollover.
Cheers

[Tango Eight]

All ClearNav products are expected to handle the GPS Epoch rollover with no issues.

best regards,
Evan Ludeman for ClearNav Instruments

[Dan Daly[_2_]]

On Thursday, February 7, 2019 at 11:58:29 AM UTC-5, Tango Eight wrote:
> All ClearNav products are expected to handle the GPS Epoch rollover with no issues.
>
> best regards,
> Evan Ludeman for ClearNav Instruments

Thanks Evan!

[Steve Leonard[_2_]]

On Wednesday, February 6, 2019 at 8:57:31 PM UTC-6, Bruce Hoult wrote:

> I'm guessing that will be the final end of my 1994 Cambridge Model 10. (It's already had the battery replaced, of course)

Nah, Bruce. I bet if your GPS battery is still good, it will survive this one the same way it survived the first one. The problems didn't show up immediately on the first roll-over. They showed up when the old GPS batteries started to age out. At least, that is what I remember. May need to replace my memory battery. :-)

At least, that is my current gamble. Just mailed 4 Model 20s to Gary to get that GPS battery replaced!

Steve Leonard

[kinsell]

On 2/6/19 7:57 PM, Bruce Hoult wrote:
> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster wrote:
>> I just came across this interesting page: https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know
>>
>> On April 6th of this year the GPS week will roll over and on some older instruments it could mess up the date. How many of our soaring instruments might have this problem?
>
> I'm guessing that will be the final end of my 1994 Cambridge Model 10. (It's already had the battery replaced, of course)
>

I've got a 1996 era Garmin backpacker gps still holding the correct
date. Internal battery was replaced under warranty about 22 years ago.

I'd be surprised if it suddenly got the wrong date on April 6, but
really doesn't matter anyway. Lots of old Volksloggers got hit with the
date problem, maybe they'd be more subject to failure if any of them are
still in use.

[Tim Newport-Peace[_4_]]

At 03:16 09 February 2019, kinsell wrote:
>On 2/6/19 7:57 PM, Bruce Hoult wrote:
>> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
>wrote:
>>> I just came across this interesting page:
>https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
rollover-what-you-need-know
>>>
>>> On April 6th of this year the GPS week will roll over and on some
older
>instruments it could mess up the date. How many of our soaring
instruments
>might have this problem?
>>
>> I'm guessing that will be the final end of my 1994 Cambridge Model 10.
>(It's already had the battery replaced, of course)
>>
>
>I've got a 1996 era Garmin backpacker gps still holding the correct
>date. Internal battery was replaced under warranty about 22 years ago.
>
>I'd be surprised if it suddenly got the wrong date on April 6, but
>really doesn't matter anyway. Lots of old Volksloggers got hit with the
>date problem, maybe they'd be more subject to failure if any of them are
>still in use.
>
Most of the Volksloggers were made with the Garmin GPS25 Engine, same as
legacy Cambridge.

[Tim Newport-Peace[_4_]]

At 03:16 09 February 2019, kinsell wrote:
>On 2/6/19 7:57 PM, Bruce Hoult wrote:
>> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
>wrote:
>>> I just came across this interesting page:
>https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
rollover-what-you-need-know
>>>
>>> On April 6th of this year the GPS week will roll over and on some
older
>instruments it could mess up the date. How many of our soaring
instruments
>might have this problem?
>>
>> I'm guessing that will be the final end of my 1994 Cambridge Model 10.
>(It's already had the battery replaced, of course)
>>
>
>I've got a 1996 era Garmin backpacker gps still holding the correct
>date. Internal battery was replaced under warranty about 22 years ago.
>
>I'd be surprised if it suddenly got the wrong date on April 6, but
>really doesn't matter anyway. Lots of old Volksloggers got hit with the
>date problem, maybe they'd be more subject to failure if any of them are
>still in use.
>
Most of the Volksloggers were made with the Garmin GPS25 Engine, same as
legacy Cambridge.

[JS[_5_]]

On Saturday, February 9, 2019 at 7:45:06 AM UTC-8, Tim Newport-Peace wrote:
> At 03:16 09 February 2019, kinsell wrote:
> >On 2/6/19 7:57 PM, Bruce Hoult wrote:
> >> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
> >wrote:
> >>> I just came across this interesting page:
> >https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
> rollover-what-you-need-know
> >>>
> >>> On April 6th of this year the GPS week will roll over and on some
> older
> >instruments it could mess up the date. How many of our soaring
> instruments
> >might have this problem?
> >>
> >> I'm guessing that will be the final end of my 1994 Cambridge Model 10.
> >(It's already had the battery replaced, of course)
> >>
> >
> >I've got a 1996 era Garmin backpacker gps still holding the correct
> >date. Internal battery was replaced under warranty about 22 years ago.
> >
> >I'd be surprised if it suddenly got the wrong date on April 6, but
> >really doesn't matter anyway. Lots of old Volksloggers got hit with the
> >date problem, maybe they'd be more subject to failure if any of them are
> >still in use.
> >
> Most of the Volksloggers were made with the Garmin GPS25 Engine, same as
> legacy Cambridge.

One rollover problem the Volkslogger doesn't have is due to the robust chassis.
It makes a good wheel chock.
Jim

[kinsell]

On 2/9/19 8:33 AM, Tim Newport-Peace wrote:
> At 03:16 09 February 2019, kinsell wrote:
>> On 2/6/19 7:57 PM, Bruce Hoult wrote:
>>> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
>> wrote:
>>>> I just came across this interesting page:
>> https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
> rollover-what-you-need-know
>>>>
>>>> On April 6th of this year the GPS week will roll over and on some
> older
>> instruments it could mess up the date. How many of our soaring
> instruments
>> might have this problem?
>>>
>>> I'm guessing that will be the final end of my 1994 Cambridge Model 10.
>> (It's already had the battery replaced, of course)
>>>
>>
>> I've got a 1996 era Garmin backpacker gps still holding the correct
>> date. Internal battery was replaced under warranty about 22 years ago.
>>
>> I'd be surprised if it suddenly got the wrong date on April 6, but
>> really doesn't matter anyway. Lots of old Volksloggers got hit with the
>> date problem, maybe they'd be more subject to failure if any of them are
>> still in use.
>>
> Most of the Volksloggers were made with the Garmin GPS25 Engine, same as
> legacy Cambridge.
>
>

But not all GPS25's were the same, depends on what firmware was loaded.
Here's a more comprehensive article, at the very end it talks about some
1999 related failures that got kicked down the road many years based on
firmware.

https://www.gps.gov/governance/advisory/meetings/2017-11/powers.pdf

In the unlikely event you're able to update firmware in a GPS engine,
that should be done prior to April.

-Dave

[kinsell]

On 2/9/19 9:31 AM, JS wrote:
> On Saturday, February 9, 2019 at 7:45:06 AM UTC-8, Tim Newport-Peace wrote:
>> At 03:16 09 February 2019, kinsell wrote:
>>> On 2/6/19 7:57 PM, Bruce Hoult wrote:
>>>> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
>>> wrote:
>>>>> I just came across this interesting page:
>>> https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
>> rollover-what-you-need-know
>>>>>
>>>>> On April 6th of this year the GPS week will roll over and on some
>> older
>>> instruments it could mess up the date. How many of our soaring
>> instruments
>>> might have this problem?
>>>>
>>>> I'm guessing that will be the final end of my 1994 Cambridge Model 10.
>>> (It's already had the battery replaced, of course)
>>>>
>>>
>>> I've got a 1996 era Garmin backpacker gps still holding the correct
>>> date. Internal battery was replaced under warranty about 22 years ago.
>>>
>>> I'd be surprised if it suddenly got the wrong date on April 6, but
>>> really doesn't matter anyway. Lots of old Volksloggers got hit with the
>>> date problem, maybe they'd be more subject to failure if any of them are
>>> still in use.
>>>
>> Most of the Volksloggers were made with the Garmin GPS25 Engine, same as
>> legacy Cambridge.
>
> One rollover problem the Volkslogger doesn't have is due to the robust chassis.
> It makes a good wheel chock.
> Jim
>

At least the Volksloggers put out actual IGC files. The Models 10, 20,
and 25 should have been relegated to wheel chock duty long before the
Volksloggers.

[Dan Marotta]

This raises a question with me.Â* I've often heard that Cambridge started
the whole GPS flight logging thing.Â* If that is true, why did FAI come
up with a different file structure?Â* If it is true, why not simply use
the Cambridge file?Â* Is it not "secure" enough?



On 2/10/2019 7:34 AM, kinsell wrote:
> On 2/9/19 9:31 AM, JS wrote:
>> On Saturday, February 9, 2019 at 7:45:06 AM UTC-8, Tim Newport-Peace
>> wrote:
>>> At 03:16 09 February 2019, kinsell wrote:
>>>> On 2/6/19 7:57 PM, Bruce Hoult wrote:
>>>>> On Wednesday, February 6, 2019 at 9:00:44 AM UTC-8, Jonathan Foster
>>>> wrote:
>>>>>> I just came across this interesting page:
>>>> https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-
>>> rollover-what-you-need-know
>>>>>>
>>>>>> On April 6th of this year the GPS week will roll over and on some
>>> older
>>>> instruments it could mess up the date. How many of our soaring
>>> instruments
>>>> might have this problem?
>>>>>
>>>>> I'm guessing that will be the final end of my 1994 Cambridge Model
>>>>> 10.
>>>> (It's already had the battery replaced, of course)
>>>>>
>>>>
>>>> I've got a 1996 era Garmin backpacker gps still holding the correct
>>>> date.Â* Internal battery was replaced under warranty about 22 years
>>>> ago.
>>>>
>>>> I'd be surprised if it suddenly got the wrong date on April 6, but
>>>> really doesn't matter anyway.Â* Lots of old Volksloggers got hit
>>>> with the
>>>> date problem, maybe they'd be more subject to failure if any of
>>>> them are
>>>> still in use.
>>>>
>>> Most of the Volksloggers were made with the Garmin GPS25 Engine,
>>> same as
>>> legacy Cambridge.
>>
>> One rollover problem the Volkslogger doesn't have is due to the
>> robust chassis.
>> It makes a good wheel chock.
>> Jim
>>
>
> At least the Volksloggers put out actual IGC files.Â* The Models 10,
> 20, and 25 should have been relegated to wheel chock duty long before
> the Volksloggers.

--
Dan, 5J

[Martin Gregorie[_6_]]

On Sun, 10 Feb 2019 09:32:19 -0700, Dan Marotta wrote:

> This raises a question with me.Â* I've often heard that Cambridge started
> the whole GPS flight logging thing.Â* If that is true, why did FAI come
> up with a different file structure?Â* If it is true, why not simply use
> the Cambridge file?Â* Is it not "secure" enough?
>
Did the Cambridge file include baro height as well as GPS?
What about the task, pilot, glider and other stuff in the header, i.e.
A,C and H records?

FWIW, now that the use of finish rings and variable barrel size
turnpoints is becoming common in some countries the IGC 'C' records
(which list the start and end of a task as well as the turnpoints) really
need extending to allow the logger to record the type and size of all the
items that define a task, especially where variable barren sizes are used
in a handicapped event.


--
Martin | martin at
Gregorie | gregorie dot org

[Tim Newport-Peace[_4_]]

At 17:14 10 February 2019, Martin Gregorie wrote:
>On Sun, 10 Feb 2019 09:32:19 -0700, Dan Marotta wrote:
>
>> This raises a question with me.Â* I've often heard that Cambridge
started
>> the whole GPS flight logging thing.Â* If that is true, why did FAI come
>> up with a different file structure?Â* If it is true, why not simply use
>> the Cambridge file?Â* Is it not "secure" enough?

Bob Fletcher (General Manager of Cambridge Aero Instrument) and Hans
Trautenberg came up with it in 1993-4.

>>
>Did the Cambridge file include baro height as well as GPS?
>What about the task, pilot, glider and other stuff in the header, i.e.
>A,C and H records?

Of course.
>
>FWIW, now that the use of finish rings and variable barrel size
>turnpoints is becoming common in some countries the IGC 'C' records
>(which list the start and end of a task as well as the turnpoints) really

>need extending to allow the logger to record the type and size of all the

>items that define a task, especially where variable barren sizes are used

>in a handicapped event.
>

No, not really. The C-records are for defining Tasks in accordance with The
Sporting Code, which defines barrel radii and are not variable.

[Dan Marotta]

Thanks.Â* Way more complex than needed for my flying - completed my
diamonds with camera and barograph.Â* Now I just fly for fun and use
OLC/Skylines to extract the data for my logs.

On 2/10/2019 10:14 AM, Martin Gregorie wrote:
> On Sun, 10 Feb 2019 09:32:19 -0700, Dan Marotta wrote:
>
>> This raises a question with me.Â* I've often heard that Cambridge started
>> the whole GPS flight logging thing.Â* If that is true, why did FAI come
>> up with a different file structure?Â* If it is true, why not simply use
>> the Cambridge file?Â* Is it not "secure" enough?
>>
> Did the Cambridge file include baro height as well as GPS?
> What about the task, pilot, glider and other stuff in the header, i.e.
> A,C and H records?
>
> FWIW, now that the use of finish rings and variable barrel size
> turnpoints is becoming common in some countries the IGC 'C' records
> (which list the start and end of a task as well as the turnpoints) really
> need extending to allow the logger to record the type and size of all the
> items that define a task, especially where variable barren sizes are used
> in a handicapped event.
>
>

--
Dan, 5J

[Charlie M. (UH & 002 owner/pilot)]

No real clue on GPS engine rollover, but I have dealt with other date issues.

Yes, I did most of my badges with a camera and a Replogle. Due to processing errors, I started doing my own film processing. I also developed other badge flights for our club until a club member (who was a pro photographer and could dump in a film load for almost nothing), sorta, "been there, done that".