文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > 自然科学 > 生物学 > u-blox7-V14_ReceiverDescriptionProtocolSpec_Public
侵权投诉

u-blox7-V14_ReceiverDescriptionProtocolSpec_Public

ublox 软件编程手册

u-blox7-V14_ReceiverDescriptionProtocolSpec_Public

6.3 iTOW Timestamps

All the main UBX-NAV messages (and some other messages) contain an iTOW field which indicates the GPStime at which the navigation epoch occurred. Messages with the same iTOW value can be assumed to havecome from the same navigation solution.

Note that iTOW values may not be valid (i.e. they may have been generated with insufficient conversion data)and therefore it is not recommended to use the iTOW field for any other purpose. If reliable absolute timeinformation is required, users are recommended to use the UBX-NAV-TIMEUTC, UBX-NAV-TIMEGPS,UBX-NAV-PVT or UBX-NAV-SOL messages, which contain additional fields that indicate the validity and

u-blox7-V14_ReceiverDescriptionProtocolSpec_Public

accuracy of the calculated times.The original designers of GPS chose to express time/date as an integer week number (starting withthe first full week in January 1980) and a time of week (often abbreviated to TOW) expressed in

seconds. Manipulating time/date in this form is far easier for digital systems than the more

"conventional" year/month/day, hour/minute/second representation. Consequently, most GPS/GNSSreceivers use this representation internally, only converting to a more "conventional forms" at

external interfaces. The iTOW field is the most obvious externally visible consequence of this

internal representation.

6.4 UTC Representation

UTC time is used in many NMEA and UBX messages. In NMEA messages it is always reported rounded to thenearest hundredth of a second. Consequently, it is normally reported with two decimal places (e.g. 124923.

52). What is more, although compatibility mode (selected using UBX-CFG-NMEA) requires three decimalplaces, rounding to the nearest hundredth of a second remains, so the extra digit is always 0.

UTC time is is also reported within some UBX messages, such as UBX-NAV-TIMEUTC and UBX-NAV-PVT. Inthese messages date and time are separated into seven distinct integer fields. Six of these (year, month, day,hour, min and sec) have fairly obvious meanings and are all guaranteed to match the corresponding values inNMEA messages generated by the same navigation epoch. This facilitates simple synchronisation betweenassociated UBX and NMEA messages.

The seventh field is called nano and it contains the number of nanoseconds by which the rest of the time anddate fields need to be corrected to get the precise time. So, for example, the UTC time 12:49:23.521 would bereported as: hour: 12, min: 49, sec: 23, nano: 521000000.

It is however important to note that the first six fields are the result of rounding to the nearest hundredth of asecond. Consequently the nano value can range from -5000000 (i.e. -5 ms) to +994999999 (i.e. nearly 995ms).

When the nano field is negative, the number of seconds (and maybe minutes, hours, days, months or evenyears) will have been rounded up. Therefore, some or all of them will need to be adjusted in order to get thecorrect time and date. Thus in an extreme example, the UTC time 23:59:59.9993 on 31st December 2011would be reported as: year: 2012, month: 1, day: 1, hour: 0, min: 0, sec: 0, nano: -700000.

Of course, if a resolution of one hundredth of a second is adequate, negative nano values can simply berounded up to 0 and effectively ignored.

6.5 Leap Seconds

Occasionally it is decided (by one of the international time keeping bodies) that, due to the slightly uneven spinrate of the Earth, UTC has moved sufficiently out of alignment with mean solar time (i.e. the Sun no longerappears directly overhead at 0 longitude at midday). A "leap second" is therefore announced to bring UTCback into close alignment. This normally involves adding an extra second to the last minute of the year, but it

上一页第23页

你可能喜欢

热门文档

相关文档

  • GPS模块协议u-blox5_Protocol_Specifications(GPS.G5-X...

    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 ...

  • LD420EUB-SDA1_Final

    Receiver Signal (B-) FIRST LVDS Receiver Signal ...V IN _ MAX V IN _ MIN Description LVDS ...9-7. Appropriate Condition for Public Display - ...

  • GWF-7M01_Spec_V10

    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 ...

  • 9-Real_Time_Transport_Protocol

    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 ...

  • ATK-NEO-6M 高性能GPS模块用户手册

    (串口)方式,输出的 GPS 定位数据采用 NMEA-0183 协议(默认) ,控制协议为 UBX 协议(该协议的详细介绍请看 u-blox6_ReceiverDescriptionProtocolSpec_GPS.G6-SW...

  • GPS用户手册_V2.0

    (该协议的详细介绍请看 u-blox6_ReceiverDescriptionProtocolSpec_GPS.G6-SW-...(2) 定位状态,A=有效定位,V=无效定位 (3) 纬度 ddmm.mmmmm(度分) (4)...

  • LD470DXS-SCA1规格书

    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 ...

  • LD420WXN-SAA1_Ver_0.0_080129_Pre

    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 ...

  • L G_LD550DUS-SEB1-低亮高清超窄边

    ‘H’ Description SECOND LVDS Receiver Signal (A...3. (N<M) ※ G to G Spec is average of ...9-7. Appropriate Condition for Public Display - ...

  • YG-309M-A SPEC_V1.1说明书标准书

    Wangcs YG-309M-A DESCRIPTION : CSR8605 (ROM )Module REV : 1.0 CHECKED...LTD Receiver Performance (Temperature 25°C) Issue Date :2013-05-08 17--...

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email