I flew yesterday October 3, 2022 and recorded the flight on my Oudie. On download the Oudie assigned the date of 28/12/2009 to the flight.
Has anyone seen this before? Is there a fix for it?
Roy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T24gMTAvNC8yMDIyIDg6MTkgUE0sIFJveSBCLiB3cm90ZToNCj4gSSBmbGV3IHllc3RlcmRh eSAgT2N0b2JlciAzLCAyMDIyIGFuZCByZWNvcmRlZCB0aGUgZmxpZ2h0IG9uIG15IE91ZGll LiBPbiBkb3dubG9hZCB0aGUgT3VkaWUgYXNzaWduZWQgdGhlIGRhdGUgb2YgMjgvMTIvMjAw OSB0byB0aGUgZmxpZ2h0Lg0KPiBIYXMgYW55b25lIHNlZW4gdGhpcyBiZWZvcmU/ICBJcyB0 aGVyZSBhIGZpeCBmb3IgaXQ/DQo+IFJveQ0KU291bmRzIGxpa2UgYSBHUFMgcm9sbG92ZXIg ZXZlbnQsIEkgZ29vZ2xlZCAnR1BTIFJvbGxvdmVyIEF1Z3VzdCAyMDIyJyANCmFuZCBmb3Vu ZCB0aGlzOg0KDQoiTW9zdCByZWNlaXZlcnMgd2VyZSB1cGRhdGVkIHdpdGggc29mdHdhcmUg dG8gYWNjb3VudCBmb3IgdGhlIG5leHQgMjAgDQp5ZWFycy4gQnV0IG90aGVyIEdQUyByZWNl aXZlciBtYW51ZmFjdHVyZXJzIHNldCBhIGRlbGF5ZWQgZGF0ZSBmb3IgdGhlIA0Kcm9sbG92 ZXIgZGF0ZSB0byBvY2N1ciBvbiDigJMgU2VwdGVtYmVyIDE4dGgsIDIwMjIiDQoNCkkgZ3Vl c3MgT3VkaWUgY2hvc2Ugbm90IHRvIGhhbmRsZSByb2xsb3ZlciBldmVudHMgYnV0IGp1c3Qg cG9zdHBvbmVkIGEgDQpmZXcgeWVhcnMuICBJJ20gY2hlY2tpbmcgbXkgT3VkaWUgbm93LiAg VGhlIG9ubHkgc29sdXRpb24gaW4gdGhlIHBhc3QgaXMgDQpoYXJkd2FyZSByZXBsYWNlbWVu dCBvciBhIGZpcm13YXJlIHVwZGF0ZS4gIEkndmUgYmVlbiBsb29raW5nIGF0IHRoZSANCk5h dml0ZXIgc2l0ZSBidXQgbm90IGZpbmRpbmcgYW55dGhpbmcgeWV0Lg0KDQpEYXZlIExhaXRp bmVuDQo=

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tuesday, October 4, 2022 at 10:49:18 PM UTC-4, David Laitinen wrote:

On 10/4/2022 8:19 PM, Roy B. wrote:

I flew yesterday October 3, 2022 and recorded the flight on my Oudie. On download the Oudie assigned the date of 28/12/2009 to the flight.
Has anyone seen this before? Is there a fix for it?
Roy

Sounds like a GPS rollover event, I googled 'GPS Rollover August 2022'
and found this:

"Most receivers were updated with software to account for the next 20
years. But other GPS receiver manufacturers set a delayed date for the rollover date to occur on – September 18th, 2022"

I guess Oudie chose not to handle rollover events but just postponed a
few years. I'm checking my Oudie now. The only solution in the past is hardware replacement or a firmware update. I've been looking at the
Naviter site but not finding anything yet.

Dave Laitinen

Just checked mine and it shows the correct date and time. I have software version Y/OUDIE9.37.001.
Seems to work ok.

Uli
'AS'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T24gMTAvNC8yMDIyIDExOjE0IFBNLCBBUyB3cm90ZToNCj4gT24gVHVlc2RheSwgT2N0b2Jl ciA0LCAyMDIyIGF0IDEwOjQ5OjE4IFBNIFVUQy00LCBEYXZpZCBMYWl0aW5lbiB3cm90ZToN Cj4+IE9uIDEwLzQvMjAyMiA4OjE5IFBNLCBSb3kgQi4gd3JvdGU6DQo+Pj4gSSBmbGV3IHll c3RlcmRheSBPY3RvYmVyIDMsIDIwMjIgYW5kIHJlY29yZGVkIHRoZSBmbGlnaHQgb24gbXkg T3VkaWUuIE9uIGRvd25sb2FkIHRoZSBPdWRpZSBhc3NpZ25lZCB0aGUgZGF0ZSBvZiAyOC8x Mi8yMDA5IHRvIHRoZSBmbGlnaHQuDQo+Pj4gSGFzIGFueW9uZSBzZWVuIHRoaXMgYmVmb3Jl PyBJcyB0aGVyZSBhIGZpeCBmb3IgaXQ/DQo+Pj4gUm95DQo+PiBTb3VuZHMgbGlrZSBhIEdQ UyByb2xsb3ZlciBldmVudCwgSSBnb29nbGVkICdHUFMgUm9sbG92ZXIgQXVndXN0IDIwMjIn DQo+PiBhbmQgZm91bmQgdGhpczoNCj4+DQo+PiAiTW9zdCByZWNlaXZlcnMgd2VyZSB1cGRh dGVkIHdpdGggc29mdHdhcmUgdG8gYWNjb3VudCBmb3IgdGhlIG5leHQgMjANCj4+IHllYXJz LiBCdXQgb3RoZXIgR1BTIHJlY2VpdmVyIG1hbnVmYWN0dXJlcnMgc2V0IGEgZGVsYXllZCBk YXRlIGZvciB0aGUNCj4+IHJvbGxvdmVyIGRhdGUgdG8gb2NjdXIgb24g4oCTIFNlcHRlbWJl ciAxOHRoLCAyMDIyIg0KPj4NCj4+IEkgZ3Vlc3MgT3VkaWUgY2hvc2Ugbm90IHRvIGhhbmRs ZSByb2xsb3ZlciBldmVudHMgYnV0IGp1c3QgcG9zdHBvbmVkIGENCj4+IGZldyB5ZWFycy4g SSdtIGNoZWNraW5nIG15IE91ZGllIG5vdy4gVGhlIG9ubHkgc29sdXRpb24gaW4gdGhlIHBh c3QgaXMNCj4+IGhhcmR3YXJlIHJlcGxhY2VtZW50IG9yIGEgZmlybXdhcmUgdXBkYXRlLiBJ J3ZlIGJlZW4gbG9va2luZyBhdCB0aGUNCj4+IE5hdml0ZXIgc2l0ZSBidXQgbm90IGZpbmRp bmcgYW55dGhpbmcgeWV0Lg0KPj4NCj4+IERhdmUgTGFpdGluZW4NCj4gDQo+IA0KPiBKdXN0 IGNoZWNrZWQgbWluZSBhbmQgaXQgc2hvd3MgdGhlIGNvcnJlY3QgZGF0ZSBhbmQgdGltZS4g SSBoYXZlIHNvZnR3YXJlIHZlcnNpb24gWS9PVURJRTkuMzcuMDAxLg0KPiBTZWVtcyB0byB3 b3JrIG9rLg0KPiANCj4gVWxpDQo+ICdBUycNCkFuZCBJIGhhdmUganVzdCBjb21wbGV0ZWQg Y2hlY2tpbmcgbXkgT3VkaWUgMiBhbmQgdGhlIGRhdGUgaXMgY29ycmVjdC4NCg0KRGF2ZSBM YWl0aW5lbg0K

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 05/10/2022 03:49, David Laitinen wrote:

On 10/4/2022 8:19 PM, Roy B. wrote:

I flew yesterday  October 3, 2022 and recorded the flight on my Oudie.
On download the Oudie assigned the date of 28/12/2009 to the flight.
Has anyone seen this before?  Is there a fix for it?
Roy

Sounds like a GPS rollover event, I googled 'GPS Rollover August 2022'
and found this:

"Most receivers were updated with software to account for the next 20
years. But other GPS receiver manufacturers set a delayed date for the rollover date to occur on – September 18th, 2022"

I guess Oudie chose not to handle rollover events but just postponed a
few years.  I'm checking my Oudie now.  The only solution in the past is hardware replacement or a firmware update.  I've been looking at the
Naviter site but not finding anything yet.

Dave Laitinen

Rollover occurs every 1024 weeks or approximately every 19 year 8
months. A date of December 2009 looks odd as it is not wrong by a
multiple of 1024 weeks. Contact support@naviter.com, including the IGC file.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

My Oudie 2 also had a logger hiccup this summer
I reset it and fixed it by turning it on and letting the software load and lock on to the satellite grid.
Then I pushed the tiny reset button on the lower back and let it reboot up. Don't forget to shut down Oudie properly the procedure is:
Menu
Next
Exit
This method shuts off the software before you shut off the device.
Nick
T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Roy,

I suspect that the date issue was caused by taking-off before the logger had a good lock on GPS satellites. It records the date and time of the takeoff.

I have never heard of an Oudie having a GPS date rollover issue.

Best Regards,

Paul Remde
____________________________________________
On Wednesday, October 5, 2022 at 2:15:27 PM UTC-5, nickkennedy...@gmail.com wrote:

My Oudie 2 also had a logger hiccup this summer
I reset it and fixed it by turning it on and letting the software load and lock on to the satellite grid.
Then I pushed the tiny reset button on the lower back and let it reboot up. Don't forget to shut down Oudie properly the procedure is:
Menu
Next
Exit
This method shuts off the software before you shut off the device.
Nick
T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wednesday, October 5, 2022 at 3:35:19 PM UTC-7, pa...@remde.us wrote:

Hi Roy,

I suspect that the date issue was caused by taking-off before the logger had a good lock on GPS satellites. It records the date and time of the takeoff.

I have never heard of an Oudie having a GPS date rollover issue.

Best Regards,

Paul Remde
____________________________________________
On Wednesday, October 5, 2022 at 2:15:27 PM UTC-5, nickkennedy...@gmail.com wrote:

My Oudie 2 also had a logger hiccup this summer
I reset it and fixed it by turning it on and letting the software load and lock on to the satellite grid.
Then I pushed the tiny reset button on the lower back and let it reboot up. Don't forget to shut down Oudie properly the procedure is:
Menu
Next
Exit
This method shuts off the software before you shut off the device.
Nick
T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thanks Paul - I did turn it on very close to the start of the flight - and the mis-dated flight shows that it acquired position after the tow was completed.
Roy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Paul and all,

Satellites only send week number within the epoch, they do not send the
epoch number (on the band we use). The GPS engine has it's own battery
and stores epoch number, it also has a Real Time Clock, so under normal circumstances, a time jump of this magnitude should never happen.

When lock is achieved, the RTC is updated (time and week number within
the epoch but not the epoch number), and a small position jump can
sometimes be detected.

The fault may lie in the recorder's GPS Engine. Replacing the Engine is
a Workshop job.

But it is always worth trying another flight allowing GPS lock to occur
well before take-off, and reporting what happens.

I agree that this does not look like a rollover issue as the error is
not a multiple of 1024 weeks.

Tim.

On 05/10/2022 23:39, Roy B. wrote:

On Wednesday, October 5, 2022 at 3:35:19 PM UTC-7, pa...@remde.us wrote:

Hi Roy,

I suspect that the date issue was caused by taking-off before the logger had a good lock on GPS satellites. It records the date and time of the takeoff.

I have never heard of an Oudie having a GPS date rollover issue.

Best Regards,

Paul Remde
____________________________________________
On Wednesday, October 5, 2022 at 2:15:27 PM UTC-5, nickkennedy...@gmail.com wrote:

My Oudie 2 also had a logger hiccup this summer
I reset it and fixed it by turning it on and letting the software load and lock on to the satellite grid.
Then I pushed the tiny reset button on the lower back and let it reboot up. >>> Don't forget to shut down Oudie properly the procedure is:
Menu
Next
Exit
This method shuts off the software before you shut off the device.
Nick
T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

One thing to remember about GPS lock is if you travel a long distance,
or months have elapsed since the last use, it can take a "long time"
to get a 3D lock.

On the Oudie be sure to add the "GPS Status" NaxBox to your map page.
The box needs to say "3D" before you fly.

Good luck, John (OHM)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On the Oudie be sure to add the "GPS Status" NaxBox to your map page.
The box needs to say "3D" before you fly.

Thanks John - I did not know that.
I live, and I learn.
ROY

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)