ublox 软件编程手册

When the receiver first starts, it has no information about how these clock ticks relate to other time systems; itcan only count time in 1 millisecond steps. However, as the receiver derives information from the satellites it istracking or from aiding messages, it estimates the time that each of these 1kHz clock ticks takes place in thetime-base of the relevant GNSS system. In previous versions of the firmware for u-blox receivers this was alwaysthe GPS time-base, but in the latest firmware it could be GPS or GLONASS and in the future it could also beother GNSS systems (such as Galileo, Compass.... etc). This estimate of GNSS time based on the local 1kHzclock is called receiver local time.
As receiver local time is a mapping of the local 1kHz reference onto a GNSS time-base, it may experienceoccasional discontinuities, especially when the receiver first starts up and the information it has about thetime-base is changing. Indeed after a cold start receiver local time will indicate the length of time that thereceiver has been running. However, when the receiver obtains some credible timing information from asatellite or aiding message, it will jump to an estimate of GNSS time.
6.2 Navigation Epochs
Each navigation solution is triggered by the tick of the 1kHz clock nearest to the desired navigation solutiontime. This tick is referred to as a navigation epoch. If the navigation solution attempt is successful, one of theresults is an accurate measurement of time in the time-base of the chosen GNSS system, called GNSS systemtime. The difference between the calculated GNSS system time and receiver local time is called the clock bias(and the clock drift is the rate at which this bias is changing).
In practice the receiver's local oscillator will not be as stable as the atomic clocks to which GNSS systems arereferenced and consequently clock bias will tend to accumulate. However, when selecting the next navigationepoch, the receiver will always try to use the 1kHz clock tick which it estimates to be closest to the desired fixperiod as measured in GNSS system time. Consequently the number of 1kHz clock ticks between fixes will
occasionally vary (so when producing one fix per second, there will normally be 1000 clock ticks between fixes,but sometimes, to correct drift away from GNSS system time, there will be 999 or 1001).
The GNSS system time calculated in the navigation solution is always converted to a time in both the GPS andUTC time-bases for output.
Clearly when the receiver has chosen to use the GPS time-base for its GNSS system time, conversion to GPStime requires no work at all, but conversion to UTC requires knowledge of the number of leap seconds sinceGPS time started (and other minor correction terms). The relevant GPS to UTC conversion parameters aretransmitted periodically (every 12.5 minutes) by GPS satellites, but can also be supplied to the receiver via theUBX-AID-HUI aiding message. By contrast when the receiver has chosen to use the GLONASS time-base as itsGNSS system time, conversion to GPS time is more difficult as it requires knowledge of the difference betweenthe two time-bases, but conversion to UTC is easier (as GLONASS time is closely linked to UTC).
Where insufficient information is available for the receiver to perform any of these time-base conversionsprecisely, pre-defined default offsets are used. Consequently plausible times are nearly always generated, butthey may be wrong by a few seconds (especially shortly after receiver start). Depending on the configuration ofthe receiver, such "invalid" times may well be output, but with flags indicating their state (e.g. the "valid" flagsin UBX-NAV-PVT

).Future u-blox receivers are likely to employ multiple GNSS system times and/or receiver local times
(in order to support multiple GNSS systems in parallel), so users should not rely on UBX messages
that report GNSS system time or receiver local time being supported in future. It is therefore
recommended to give preference to those messages that report UTC time.
135 NMEA, UBX Protocol Specification, u-blox 5 GNSS Receiver GPS.G5-X-07036-E Public Release Table of Contents Page ix Receiver Description Overview ...
Receiver Signal (B-) FIRST LVDS Receiver Signal ...V IN _ MAX V IN _ MIN Description LVDS ...9-7. Appropriate Condition for Public Display - ...
4. Product Description 4.1. Block Diagram MT7601 VCC(3.3V) SMPS 3.3V...Receiver RF Front End External antenna 2.412~2.4835GHz LED XTAL 40MHz ...
Source description V=2 P SC PT=SDES=202 SSRC/CSRC 1 SDES items ... ...(s) Receiver Report Receiver Report SSRC SSRC report block(s) 1 report ...
(串口)方式,输出的 GPS 定位数据采用 NMEA-0183 协议(默认) ,控制协议为 UBX 协议(该协议的详细介绍请看 u-blox6_ReceiverDescriptionProtocolSpec_GPS.G6-SW...
(该协议的详细介绍请看 u-blox6_ReceiverDescriptionProtocolSpec_GPS.G6-SW-...(2) 定位状态,A=有效定位,V=无效定位 (3) 纬度 ddmm.mmmmm(度分) (4)...
PUBLIC DISPLAY ITEM Page 1 2 3 4 5 6 6 8 ...Ground LVDS Receiver Signal(-) LVDS Receiver Signal...V IN _ MAX V IN _ MIN Description LVDS ...
PUBLIC DISPLAY ITEM Page 1 2 3 4 5 6 6 8 ...General Description The LC420WXN is a Color Active...Receiver Clock Signal(-) LVDS Receiver Clock ...
‘H’ Description SECOND LVDS Receiver Signal (A...3. (N<M) ※ G to G Spec is average of ...9-7. Appropriate Condition for Public Display - ...
Wangcs YG-309M-A DESCRIPTION : CSR8605 (ROM )Module REV : 1.0 CHECKED...LTD Receiver Performance (Temperature 25°C) Issue Date :2013-05-08 17--...
热门文档