Here I am

8.4AN GPS has wrong time

Attention: TDR Forum Junkies
To the point: Click this link and check out the Front Page News story(ies) where we are tracking the introduction of the 2025 Ram HD trucks.

Thanks, TDR Staff

G56 with adjustable pedals

Buying a "New" 2018 Ram 3500 CTD

Status
Not open for further replies.
Yesterday I received a notice that my 8.4AN was going to receive an OTA update. Today when I got in the truck the time was wrong. I went into the menu and it was set to sync with GPS. I set the clock manually and several hours later tried to switch it back to GPS sync. The time advanced about 4-1/2 hours. I checked and the GPS was showing multiple satellites. I don't understand how it can be receiving satellites and have the wrong time. It has my location correct so it should be able to figure out how to set the time right relative to GPS time.

Al
 
As a former IT project manager, first action, do a reset. Ignition either in accessory or truck running, press both knobs at the same time til it resets. Updates skilter it sometimes.

EDIT: Or try what Bruce recommends next post first.

Cheers, Ron
 
Last edited:
How far off is the time from your local time? Often times the GPS uses GMT (Greenwich Mean Time) or UTC (Universal Time Coordinate). It is up to the user to identify the correct time zone and daylight saving time if the program doesn't automatically perform that function. The reset as Ron mentioned should fix the hic-up. If not, check deep into your settings.
We used GMT as one of the settings entered into the the astral navigation system in our aircraft long before GPS was thought of. GMT, GHA, SHA, DEC and other data from the Astronomical Almanac, aka Star Book...
 
Last edited:
Thanks all.

I looked for a gps time offset setting and couldn’t find one. The offset was not an integral number of hours, or even half hours. I didn’t take the time to figure out the exact offset it was using. I will check it today and reset if it is still off. My only thought was that perhaps it has to receive a full almanac after an update and that takes several hours iirc.
 
Yesterday I received a notice that my 8.4AN was going to receive an OTA update. Today when I got in the truck the time was wrong. I went into the menu and it was set to sync with GPS. I set the clock manually and several hours later tried to switch it back to GPS sync. The time advanced about 4-1/2 hours. I checked and the GPS was showing multiple satellites. I don't understand how it can be receiving satellites and have the wrong time. It has my location correct so it should be able to figure out how to set the time right relative to GPS time.

Al

I'd bet your update didn't happen.....The OTA update failed on my truck twice so I did it manually. Look under "system information" and see if it has the new software version #18-45-01

Sam
 
I'd bet your update didn't happen.....The OTA update failed on my truck twice so I did it manually. Look under "system information" and see if it has the new software version #18-45-01

Sam
This is the most likely event. I have experienced updates that have had to be manually completed. The OTA may have lost signal and data. Also, the update processing may take a very long time and the data get corrupted during the installation process. Technology at its finest...:rolleyes:
 
Thanks all.

I looked for a gps time offset setting and couldn’t find one. The offset was not an integral number of hours, or even half hours. I didn’t take the time to figure out the exact offset it was using. I will check it today and reset if it is still off. My only thought was that perhaps it has to receive a full almanac after an update and that takes several hours iirc.
Check your current truck display time and compare it to your current time zone time. As a troubleshooting tool here is link to compare the difference of UTC (GMT) and your local time zone. https://greenwichmeantime.com/time-zone/usa/time-zones/
 
Last edited:
I am in EST zone which is 5.0 hours from GMT/UTC. GPS time is 18 seconds ahead of UTC due to “leap seconds”. So if the nav was not making the time zone correction the time synced to GPS should be 5 hours and 28 seconds ahead. I’ll go check and see what it is. If anyone knows where a menu option is to set the time zone, please tell me where it is. I couldn’t find it.

If it is still wrong, I’ll tty the reset.
 
OK. Local time 11:24. GPS time should be 16:24. When I sync to GPS it sets the time to 1900, which makes no sense. I tried the reset. It reset but no change.
The OTA update apparently failed. I have version 17.11.17. How do I force it manually?

Thanks
 
I am in EST zone which is 5.0 hours from GMT/UTC. GPS time is 18 seconds ahead of UTC due to “leap seconds”. So if the nav was not making the time zone correction the time synced to GPS should be 5 hours and 28 seconds ahead. I’ll go check and see what it is. If anyone knows where a menu option is to set the time zone, please tell me where it is. I couldn’t find it.

If it is still wrong, I’ll tty the reset.
I reviewed the 8.4 manual and notice the software program is supposed to update the time for your time zone so you won't find the setting; just the manual set and GPS link set. So this points strongly to update error or incomplete processing.
As far as leap seconds, they are already accounted for in the broadcast time signal - or receiver software:

Atomic Time vs. Universal Time
2 components are used to determine UTC (Coordinated Universal Time):

  1. International Atomic Time (TAI): A time scale that combines the output of some 200 highly precise atomic clocks worldwide, and provides the exact speed for our clocks to tick.
  2. Universal Time (UT1), also known as Astronomical Time, refers to the Earth's rotation around its own axis, which determines the length of a day.
Before the difference between UTC and UT1 reaches 0.9 seconds, a leap second is added to UTC and to clocks worldwide. By adding an additional second to the time count, our clocks are effectively stopped for that second to give Earth the opportunity to catch up.

Upcoming leap seconds are announced by the International Earth Rotation and Reference Systems Service (IERS) in Paris, France.

The Science Behind Leap Seconds
Atomic Time Too Accurate
The reason we have to add a second now and then is that the velocity of Earth's rotation around its own axis does not match the speed of atomic time. On average, it is a tiny bit too slow—and it is gradually slowing down, although very slightly.

Atomic clocks, however, tick away at pretty much the same speed over millions of years. Compared to the Earth's rotation, atomic clocks are simply too consistent.

How Often Are Leap Seconds Added?
Before the first leap second was added in 1972, UTC was 10 seconds behind Atomic Time. So far, a total of 27 leap seconds have been added. This means that the Earth has slowed down an additional 27 seconds compared to atomic time since then.

However, this does NOT mean that the days are 27 seconds longer nowadays. The only difference is that the days a leap second was added had 86,401 seconds instead of the usual 86,400 seconds.

Last Leap Second in December 2016
The last leap second was added on December 31, 2016, at 23:59:60 UTC. The difference between UTC and International Atomic Time (TAI) increased from the 36 seconds to the current 37 seconds.

Next Leap Second
Based on current predictions, the next leap second should be added on June 30, 2020. However, since the speed of the Earth's rotation is subject to unpredictable short-term variations, the date may still change. Once it is officially announced, we will publish it in our Time Zone News.
And, to overload to the "Way" TMI (too much information) factor: :eek:

Timekeeping [edit]
Leap seconds[edit]
While most clocks derive their time from Coordinated Universal Time (UTC), the atomic clocks on the satellites are set to GPS time (GPST; see the page of United States Naval Observatory). The difference is that GPS time is not corrected to match the rotation of the Earth, so it does not contain leap seconds or other corrections that are periodically added to UTC. GPS time was set to match UTC in 1980, but has since diverged. The lack of corrections means that GPS time remains at a constant offset with International Atomic Time (TAI) (TAI − GPS = 19 seconds). Periodic corrections are performed to the on-board clocks to keep them synchronized with ground clocks.[148]

The GPS navigation message includes the difference between GPS time and UTC. As of January 2017,[update] GPS time is 18 seconds ahead of UTC because of the leap second added to UTC on December 31, 2016.[149] Receivers subtract this offset from GPS time to calculate UTC and specific timezone values. New GPS units may not show the correct UTC time until after receiving the UTC offset message. The GPS-UTC offset field can accommodate 255 leap seconds (eight bits).​
 
Last edited:
Thanks, everyone.

I started a download of the update and left it running at the house while we went out for errands and dinner. When we came out of the restaurant, the time (which I had set manually) was wrong. I went into the setup and clicked on sync to GPS and the time became correct. I guess it healed itself. When we got back to the house and I shut the truck off I got the update pending message again. I told it to update now so we'll see what happens.
 
Not it didn't heal itself, it needed the OTA.

What you have experienced is the millennium bug of the GPS System.

It's called week rollover.

https://en.m.wikipedia.org/wiki/GPS_Week_Number_Rollover

November 3th 2019 was the crucial moment.
Yep. The April 2019 update for week number rollover is the very last update of anything my old TomTom will be getting. It has old maps and is officially obsolete for any future update and is now declared a paperweight. No loss here as it unexpectedly and unceremoniously lead us onto many mountain goat paths in its heyday while we were towing the travel trailer. I like the 12 inch in the Ram a LOT better...when it works. Still awaiting the Uconnect update in the "last quarter" of 2019 (for the past year) :mad:o_O:rolleyes:
 
I updated manually to 17-43 back in Sept. It keep failing to do 18.45 OTA, so I just manually did it this evening. BTW way, I have done the last two with the push button in "run" without the motor running as they state you should do. Snoking

IMG_20191115_184549.jpg
 
Last edited:
Status
Not open for further replies.
Back
Top