anastrophe wrote: does anyone know what time it is?
Does Anybody Really Know What Time It Is?
OOOHH I DO MR CARTER!!!!!!!!
Since the establishment of Coordinated Universal Time in 1972, 22 leap seconds have been added to keep atomic time in synch with the rotation of the Earth. When the Global Positioning System (GPS) started in 1980, it was synchronized with UTC. However, GPS time does not add leap seconds, and as a result GPS time is now 13 seconds ahead of UTC. So, if you’re getting your time from a GPS satellite, is it correct?
Before you answer, consider this: the frequency or rate of UTC is computed by the International Bureau of Weights and Measures (BIPM) located near Paris, France. The BIPM uses a weighted average from approximately 250 atomic clocks located in about 50 national laboratories to construct a time scale called International Atomic Time (TAI in French) (Figure 1). TAI time is a uniform and stable scale, which does not keep in step with the slightly irregular rotation of the Earth. Therefore TAI time is many seconds off from UTC time.
In fact, as of January 1, 2000, it was 32 seconds ahead, and that’s because of an additional 10-second drift that occurred from when UTC was introduced in the late 1950s and the introduction of leap seconds. Based upon this confusing array of seemingly inconsistent time bases, how can embedded and communications systems know what time it really is?
Why UTC?
During the past 37 years, two conflicting demands on standard time have developed.
On one hand, science, communications systems, and electronic navigation systems have needed and exploited the extreme stabilities offered by atomic clocks. On the other hand, astronomy and celestial navigation still need time related to earth position, no matter how erratic it might be relative to atomic clocks.
To achieve a workable compromise between these two opposing demands, the Internal Radio Consultative Committee (CCIR) created a compromise time scale called Coordinated Universal Time (UTC), which became effective January 1, 1972 (Figure 2).
On that date, the difference between TAI and UTC was 10 seconds. The rate of UTC is exactly the same as TAI. In fact, the “ticks†that mark the beginning of each second of TAI and UTC are precisely synchronous. However, the date of any given event on the UTC time scale must agree with its date on the UT1 scale to within 0.9 seconds. (UT1 is the true navigator’s time scale related to the earth’s actual angular position relative to the sun.)
Offsetting UTC from TAI by a precise, whole number of seconds accomplishes both requirements. In order to maintain the defined relationship between UT1 and UTC, a one-second correction, a leap second, is added to UTC as is required. However, since the earth continuously changes its rate of rotation, this time offset cannot be permanent. In order to keep UTC within 0.9 seconds of UT1, the Bureau International de l’Heure (BIH) occasionally adds (or deletes) a second to (or from) the UTC scale, and every standard time system in the world follows suit.
Since the earth’s rotation rate is not perfectly predictable, scientists cannot forecast the need for a leap second more than a few months in advance. Leap seconds will be needed as long as the UTC time scale is used to keep UTC approximately in step with the sun. Otherwise, our clocks would gradually show the sun rising later and later until, after thousands of years, our clocks would indicate the sun was rising at noon.
But what about the time differential between GPS and UTC, and why should the discrepancy matter at all?
Understanding Time
In order to understand time, the concepts of date, interval and synchronization must be first understood. “Time†can mean either date or time interval (that is: duration). An example of “date†is November 15, 1996, 15:35:14 PST (Pacific Standard Time), where 15:35:14 indicates time of day in hours, minutes and seconds. An example of a “time†interval is the amount of time required to fly between two cities, say 3h:51m:12s. This latter example gives no indication of when (that is, the date) the flight occurred, only that it lasted 3 hours, 51 minutes, 12 seconds. Note that a notation of hours, minutes and seconds can indicate either time of day or duration.
Synchronization is the third important time concept. For example, it is not normally crucial for an orchestra to begin its concert at a precise hour, minute or second of the day, but it is essential that all members of the orchestra begin at the same instant and that they stay at the same tempo. A gasoline engine’s timing must be correct within a thousandth of a second or so, otherwise the sparks will not fire the fuel at just the right time to provide power to the pistons. Unseen by the casual user, many electronic navigation systems, computer networks and even television receivers require synchronization to transmit signals with an accuracy of a millionth of a second or better.
In addition to these uses of precise time synchronization, the National Institute of Standards and Technology (NIST) adds, “Precise time measurements are also essential for accurate navigation and the support of communications on earth and in space. Scientific organizations such as NASA depend on reliable and consistent time measurement for projects such as interplanetary space travel. Fractional disparities in times between a space probe and tracking stations on Earth can dramatically affect the positions of spacecraft. Precise time measurements are also essential to radio navigation systems like the Global Positioning System (GPS). By synchronizing the satellite clocks within nanoseconds of each other, it makes it possible for a receiver to know its position on earth within a few meters.â€
So what happens if you acquire your time from a GPS satellite and you need to be in synch with UTC time?
Bringing UTC and GPS Together
Every GPS satellite carries a cesium beam frequency standard. It is essential to the accuracy of the navigational solution that the time and frequency of these devices be controlled to the maximum extent possible. A one-nanosecond error in timing represents about one foot in navigational error. Both the U.S. Naval Observatory and the U.S. Air Force at Falcon AFB in Colorado, monitor each satellite daily. Corrections are uploaded to every satellite as a result of these measurements.
A user’s GPS receiver applies this correction-measured data to produce precise corrected outputs of time and frequency. The GPS satellite operates on a GPS time scale, which is a continuous time scale (like UT1). The satellite transmits information about the number of leap seconds that must be added to convert GPS time to UTC. It is important therefore to have a GPS receiver on the time and frequency generator that is receiving the signal to apply the correction automatically.
Why? If the purpose of a time code generator is to provide time information that is to be correlated with data collected at a different location, then both clocks must agree. Therefore setting the clocks automatically to a common time scale (probably UTC) is not only desirable but necessary.
A GPS synchronized time code generator gets precise time information from the Navstar/ GPS satellite system and can provide precision of better than ±100 nanoseconds relative to UTC, as maintained by the US Naval Observatory.
While processing satellite data normally, a timing GPS time generator will produce precise time and frequency outputs, regardless of the quality of the internal time base oscillator, because it is being continuously corrected from GPS data. If the generator is deprived of satellite data, however, the stability of the internal oscillator is the only factor that determines the amount of time error that will develop over time. This is where a company has to decide the degree of redundancy they need in their GPS time and frequency generator.
Redundancy in GPS Time and Frequency Generator
Generators can be equipped with a basic TCXO (temperature-compensated crystal oscillator), a high-stability oven oscillator or a Rubidium oscillator. Each will provide increasingly better stability in the absence of satellite data. All will provide the same time precision of 100 nanoseconds while processing satellite data.
In high quality time and frequency generators, as well as high-end network time-servers, the internal operation of a GPS receiver is extremely complex. However, the user will find it to be the simplest system for time and frequency purposes. The reason is that the GPS system is usually completely self-contained and makes all necessary corrections automatically.
So the answer to the question posed in the first paragraph (“If you are getting your time from a GPS satellite, is it correct?â€) is that the time is correct if you use a high quality time and frequency generator or network time-server that has the proper GPS receiver. And if you don’t want to think about itâ€and you shouldn’tâ€commercial off-the-shelf time and frequency generators, along with time-servers are available from timing experts like Symmetricom.
Symmetricom, Timing, Test
and Measurement Division
San Jose, CA.
978 927 8220.
[
www.symmttm.com].