Gpsd错误的时间

时间:2016-03-29 15:39:22

标签: synchronization embedded timing gpsd ntpd

每个人都是Ehilà!

我遇到了这个问题:

我正在使用GPSD,使用我工作的公司的旧GPS-Sirf / NMEA模块为ntp(现在在我的笔记本电脑上)提供服务。

让我忘记Ntpd ..一旦我启动gpsd,虽然日期和时间在 gpsmon 中是正确的,如果我运行 ntpshmmon 我有一个负时间(标记为“Real”的列中的大约-69年(以秒为单位),我认为它是我的SHM的时钟信息(而de row“Clock”实际上是收到的信息)

如果我更换模块并使用U-blox,那一切都没问题,SHM时钟恢复为+ 46年。 有没有办法用NTP管理GPS信息交换?或者在不确切知道GPS模块的情况下配置GPS?

很抱歉,如果我的问题是某种轻松的仙女......我希望有人遇到同样的问题并且可以发现线索......

THX! :)

FL

1 个答案:

答案 0 :(得分:1)

第一条规则是:不要恐慌

尝试将tinker panic 0插入/etc/ntp.conf

ntpd的反应取决于系统时钟和参考时间之间的差异。

  

对于微小的偏移量,ntpd会像往常一样调整本地时钟;对于较小和较大的偏移量,ntpd将暂停一段时间的参考时间。在后一种情况下,操作系统的时钟将继续,最后的校正在新的参考时间被拒绝时有效。一段时间后,小的偏移(显着小于一秒)将被回转(缓慢调整),而较大的偏移将导致时钟步进(重新设置)。巨大的抵消被拒绝,ntpd将自行终止,相信一定有一些非常奇怪的事情发生。 (Citation

将恐慌设置为零会使ntpd不受大偏移带来的奇怪想法的影响。

我们使用的是

# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift

# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

tinker panic 0

# Specify one or more NTP servers.
server 127.127.28.0 minpoll 4 maxpoll 4
fudge 127.127.28.0 time1 0.420 refid GPS
server 127.127.28.1 minpoll 4 maxpoll 4 prefer
fudge 127.127.28.1 refid GPS1

# Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
# on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
# more information.
server 0.ubuntu.pool.ntp.org
server 1.ubuntu.pool.ntp.org
server 2.ubuntu.pool.ntp.org
server 3.ubuntu.pool.ntp.org

# Use Ubuntu's ntp server as a fallback.
server ntp.ubuntu.com

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines.  Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient