Anyone else having issues with the GPS time not auto updating for daylight savings???

Yes, I noticed that too. I guess the GPS software does not recognize the changes to daylight savings time mandated by congress in 2007 moving the time change from April to March. I turned off the auto correction and reset my time zone, and the correct time showed up. I wonder if in April the GPS will catch up and I can turn auto correction back on. Hmmm.

Yup, even though they provided the V2.0 update last year, they seem to have failed to take into account the new DST starting date.

I noticed even after I said stop autocorrecting the time, it kept setting it back.

Did it correct accurately in the fall for those who had the units installed?

If it did then perhaps the satellites did not send out a correction signal . . .

Did it correct accurately in the fall for those who had the units installed?

 

If it did then perhaps the satellites did not send out a correction signal . . .

If they're grabbing satellite time stamps, they don't send out an offset, they send out GMT, i.e. no offset, it's up to the device to know how much to offset from it, it's why DST is such a pain, it's not even consistent in the US.

I noticed even after I said stop autocorrecting the time, it kept setting it back.

I have noticed this as well, any fix for it?

+1 I can't get the correct time to display no matter how I approach it.. I thought about going to -5 time zone instead of my normal -6 timeszone for the time being.

im EST so first i set it not auto correct time and it worked but as soo nas i shut the car off, even with my corrected time, it reverted back to an hour too slow. Si i set the time zone from EAST to Atlantic which is an hour faster and it works

Yeah, there were a lot of hotfixes available for WinCE/WinMo devices after 2007 to apply the DST fix (Google search get a lot of hits). Seems Pioneer forgot to apply MS' patch to the WinCE 5 image they gave us.

Let's see now: unit goes on sale in '08, but is missing an '07 patch and the iGo 8 fix for correct timezone location for some of us (No, Pioneer, I DON'T live in Boise)... Seems they did all their testing in a single geographic location outside the US to me.

God I wish their engineering department had an external Bugzilla so we could submit bugs for tracking.

+1 for this problem also

In DATA.ZIP, config folder, timezone.ini file. There are instructions on when daylight/standard time starts Down to millisecond, too...

In DATA.ZIP, config folder, timezone.ini file. There are instructions on when daylight/standard time starts Down to millisecond, too...

so wtf do i need to change on this??

;name, bias, daylightbias,standardbias, daylight year, month, dayofweek, day, hour, minute, second, millisecond, standard year, month, dayofweek, day, hour, minute, second, millisecond

;See TIME_ZONE_INFORMATION for what's what

timezone = "GMT-5 Eastern US", 300, -60, 0, 0, 3, 0, 2, 2, 0, 0, 0, 0, 11, 0, 1, 2, 0, 0, 0

glad to see I am not the only one and Boris, I like you tag line about Chicago!

In DATA.ZIP, config folder, timezone.ini file. There are instructions on when daylight/standard time starts Down to millisecond, too...

 

so wtf do i need to change on this??

 

;name, bias, daylightbias,standardbias, daylight year, month, dayofweek, day, hour, minute, second, millisecond, standard year, month, dayofweek, day, hour, minute, second, millisecond

;See TIME_ZONE_INFORMATION for what's what

 

timezone = "GMT-5 Eastern US", 300, -60, 0, 0, 3, 0, 2, 2, 0, 0, 0, 0, 11, 0, 1, 2, 0, 0, 0

I'll check on other forums if anyone has information about this...

Please let us know how to fix this.

I noticed even after I said stop autocorrecting the time, it kept setting it back.

 

I have noticed this as well, any fix for it?

I've got the same issue! Anybody got a fix?

Ok, so my f90Bt is showing the wrong time as well. If I try to set auto correct off, and change the time, it wil lshowe the correct time for a few, then revert back. I'm guessing the satellite signal is overriding? Kinda of like a PC on the network getting its' time information from the network it's on. hopefully because it was the weekend, they did not change the time and they will today.

Brian

I've got the same issue! Anybody got a fix?

Yes.. change your timezone, then in a few weeks when it gets to what it thinks your regions DST changeover is, swap it back.

It has all the appearances of them not having the OS patched for the US's recent change in DST dates, this should have been a no brainer for Pioneer, but then this is also a US only issue, the rest of the world doesn't muck with DST "just because they can"

Thats is what I did...changed the time zone. Which is fine for now, just kind of silly that you have a clock/radio/nav that you can not change the time.

Just add it to the list of strange quirks that have to be worked out on this forums because of poor original product design.

Good thing they left these units open for change either by accident or on purpose.

I just noticed this today as well. I wonder if installing this patch from Microsoft in test mode will fix us up:

http://www.microsoft.com/downloads/details.aspx?FamilyId=0D6FC192-3142-4473-B435-B514E4B360A5&displaylang=en

I agree this was short-sighted on Pioneer's part not to include a fix for this in their last update. The above update has been available from Microsoft since 2/15/2008.

Ah yes what an awesome bug.

Glad to see someone called support and it's still same old clueless bs

Fix action is prob live with it or tough luck.

What a blunder think this will cause some isues with returns and sales ah yeah I think it will.

This isn't a problem with WIN CE 5. I booted in safe mode, went to control panel and changed the time zone to GMT -6 and it set it to the correct time.

This could be a bug in the iGo software, they might not have accounted for it when they programmed the parser for the GPS timestamp.

In DATA.ZIP, config folder, timezone.ini file. There are instructions on when daylight/standard time starts Down to millisecond, too...

 

so wtf do i need to change on this??

 

;name, bias, daylightbias,standardbias, daylight year, month, dayofweek, day, hour, minute, second, millisecond, standard year, month, dayofweek, day, hour, minute, second, millisecond

;See TIME_ZONE_INFORMATION for what's what

 

timezone = "GMT-5 Eastern US", 300, -60, 0, 0, 3, 0, 2, 2, 0, 0, 0, 0, 11, 0, 1, 2, 0, 0, 0

The format of that line should work like this. ( a lot of educated guessing involved here, no actual reference material )

timezone = "GMT-5 Eastern US", MINUTE_DIFF_FROM_GMT, MINUTE_DIFF_WHEN_DST, 0, 0, START_MONTH_OF_YEAR, 0, START_WEEK_OF_MONTH, START_DAY_OF_WEEK, 0, 0, 0, 0, END_MONTH_OF_YEAR, 0, END_WEEK_OF_MONTH, END_DAY_OF_WEEK, 0, 0, 0

I have no idea what the 0's would represent, perhaps specific to some crazy timezones, but this should fit all USA timezones.

In 2006, BEGIN as April 2 and END was October 29.

In 2007, March 11 and November 4.

In 2008, March 9 and November 2.

In 2009, March 8 and November 1. (This is why it didn't work. they didn't build in that each year is different than the last, most people don't realize that this new DST is NOT STATIC year to year!)

So, to fix this for 2009, you can change this timezone.ini file to read: (for Easter Standard Time, for instance)

timezone = "GMT-5 Eastern US", 300, -60, 0, 0, 3, 0, 2, 1, 0, 0, 0, 0, 11, 0, 1, 1, 0, 0, 0

I researched this while at work and haven't been out to my car to test yet, but that's the only way the CSV line/string format makes sense.

The old DST was not static in dates either - it was always the first Sunday in April to the Last Sunday in October. Now it is the Second Sunday in March to the First Sunday in November . . .

Has anyone called Pioneer?