Simchaev Arthur-BAS071 wrote:
Thank you Mike . I set flag3 to 1 and now I see PPSFREQ & PPSTIME(but don't see
PPSSIGNAL as you mentioned )
Perhaps because you are now only using the type 20 nmea driver?
From the first post in this thread you were using the type 20
nmea driver for the time and
Of Mike George
Sent: Sunday, April 06, 2014 6:03 PM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] PPS problem
Arthur:
I am also using GPIO PPS and I saw what you describe when using different
options for NMEA flag3.
It sounds like you have flag 3 set to 0 in your NMEA config.
It default
ssage-
From: questions-bounces+bas071=motorolasolutions@lists.ntp.org
[mailto:questions-bounces+bas071=motorolasolutions@lists.ntp.org] On Behalf
Of David Lord
Sent: Thursday, April 03, 2014 1:48 PM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] PPS problem
Simchaev Arthur-B
Simchaev Arthur-BAS071 wrote:
Hi David
I have the following system :
uname -a
Linux am335x-evm 3.2.0-4.08 #5 Wed Mar 12 15:07:28 IST 2014 armv7l GNU/Linux
And pps is existed in the kernel , when I run ppstest /dev/pps0 , I see the pps clock
grown . Also ntpd shows that the server is PPS "o".
] On Behalf
Of David Lord
Sent: Thursday, April 03, 2014 1:48 PM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] PPS problem
Simchaev Arthur-BAS071 wrote:
> Hi Guys
> Thank you to your assistance . Seems is working now .
> I see that NMEA chosen as PPS peer server :
>
> re
Martin Burnicki wrote:
> Dowd, Greg wrote:
>> Why not? You really want to as the network entries will
>> do iburst and get selected before your refclock does
>> and force some clock stepping before settling down.
>> I usually use maxpoll 4 as well. The decreased jitter
>> in the local sign
> Why not? You really want to as the network entries
> will do iburst and get selected before your refclock
> does and force some clock stepping before settling down.
> I usually use maxpoll 4 as well. The decreased jitter
> in the local signal makes higher poll rates both valid
> and useful.
Dowd, Greg wrote:
Why not? You really want to as the network entries will do iburst
and get selected before your refclock does and force some clock
stepping before settling down. I usually use maxpoll 4 as well. The
decreased jitter in the local signal makes higher poll rates both
valid and us
Why not? You really want to as the network entries will do iburst and get
selected before your refclock does and force some clock stepping before
settling down. I usually use maxpoll 4 as well. The decreased jitter in the
local signal makes higher poll rates both valid and useful.
On Apr 2,
Simchaev Arthur-BAS071 wrote:
Hi Guys
Thank you to your assistance . Seems is working now .
I see that NMEA chosen as PPS peer server :
remote refid st t when poll reach delay offset jitter
==
oGPS_N
ednesday, April 02, 2014 11:25 PM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] PPS problem
David Lord wrote:
.
> I currently use a "Sure" gps, ntp-dev-4.2.7p433 on NetBSD-6
>
> I have a few significant differences in my ntp.conf
>
> #
&
David Lord wrote:
.
I currently use a "Sure" gps, ntp-dev-4.2.7p433 on NetBSD-6
I have a few significant differences in my ntp.conf
#
tos orphan 10
A few more comments
tos orphan 10 # is to replace your three lines:
server 127.127.1.0 #lo server
fudge 127.127.1.0 stra
William Unruh wrote:> BlackLists wrote:
>> Simchaev Arthur-BAS071 wrote:
>>> server 127.127.1.0 #lo server
>>> fudge 127.127.1.0 stratum 7
>>> restrict 127.127.1.0 noquery nomodify notrap
>>
>> I'd start by getting rid of those three lines.
>>
>> I'd recommend orphan mode instead;
>> tos cohort 1
On 2014-04-02, E-Mail Sent to this address will be added to the BlackLists
wrote:
> Simchaev Arthur-BAS071 wrote:
>> server 127.127.1.0 #lo server
>> fudge 127.127.1.0 stratum 7
>> restrict 127.127.1.0 noquery nomodify notrap
>
> I'd start by getting rid of those three lines.
>
> I'd recommend o
Simchaev Arthur-BAS071 wrote:
> server 127.127.1.0 #lo server
> fudge 127.127.1.0 stratum 7
> restrict 127.127.1.0 noquery nomodify notrap
I'd start by getting rid of those three lines.
I'd recommend orphan mode instead;
tos cohort 1 orphan 11
(Available in newer version of NTP
including th
Arthur,
What OS are you using specifically?
Also, you shouldn't put "iburst" in the server line for a local refclock... I
don't even know if that is valid, hopefully NTP
ignores it.
Jason
___
questions mailing list
questions@lists.ntp.org
http://lis
Simchaev Arthur-BAS071 wrote:
Hi .
Could you please help me with the following problem ?
Our board supports PPS & NTP . I connect & define the Garmin GPS(GPS16x-HVS) as
the NMEA reference clock . Unfortunately when I add the atom reference clock to ntp in
order to receive pps , after sometime
Hi .
Could you please help me with the following problem ?
Our board supports PPS & NTP . I connect & define the Garmin GPS(GPS16x-HVS)
as the NMEA reference clock . Unfortunately when I add the atom reference
clock to ntp in order to receive pps , after sometime NMEA & ATOM(pps) clocks
marked
Hi,
My name is Andrei Bogdan Rus and I am from Romania. I have a problem and I
don't know how to solve it. Mabey you can help me.
I am using a Trimble Palisade NTP Synchronization Sit. The computer used,
runs Linux Fedora Core 6. When I configured the sistem to work with the gps
receiver, ev
19 matches
Mail list logo
