On 29/04/14 03:59, Brian Inglis wrote:
I understand that the NBFM
transmitter starts with phase modulation then integrates, multiplies,
and filters
the result to the FM carrier frequency
You are confusing carrier phase and audio phase.
(FM modulation is mathematically the same as frequency
On 29/04/2014 06:35, A C wrote:
[]
The original error messages were:
A timeout was reached (3 milliseconds) while waiting for the Network
Time Protocol Daemon service to connect.
followed by
The Network Time Protocol Daemon service failed to start due to the
following error:
The service
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 26/04/2014 05:05, Harlan Stenn wrote:
William Unruh writes:
[]
More recent ntpd combine server and client in one program.
Not sure when that was.
It's been the case for at least 20 years' time.
This is something that may be
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
For Rob, I would suggest that each TX have a GPS/PPS reference with sky
view, and that each PC was identical (e.g. all Raspberry Pi cards), and
then getting them synced to with 12 microseconds should be easy. I
Of course that is
A C wrote:
On 2014-04-28 22:23, David Taylor wrote:
On 29/04/2014 05:51, A C wrote:
[]
Followed the same instructions, no dice.
.. and what are the messages in the Windows Event Log(s)?
The original error messages were:
A timeout was reached (3 milliseconds) while waiting for the
Harlan Stenn wrote:
This is something that may be different in the upcoming rewrite.
Do you have a pointer to those plans?
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
Paul wrote:
We have thousands
of clients served from three S2 servers (so 0% need for refclock support).
There are three S1 servers on campus (not yet in production). All three
required building NTPd, one required a driver patch and one required
building a kernel.
It would be interesting to
Harlan Stenn wrote:
William Unruh writes:
Well, ntpd could include timepps.h into ntpd source and point to it,
instead of using the system one.
Is there only one version of that file that is compatible with the
places NTP will be built? What sort of bit-rot issues are there if we
include a
On 2014-04-29 00:47, David Woolley wrote:
On 29/04/14 03:59, Brian Inglis wrote:
I understand that the NBFM
transmitter starts with phase modulation then integrates, multiplies,
and filters
the result to the FM carrier frequency
You are confusing carrier phase and audio phase.
I omitted the
On 2014-04-29 00:47, David Woolley wrote:
On 29/04/14 03:59, Brian Inglis wrote:
I understand that the NBFM
transmitter starts with phase modulation then integrates, multiplies,
and filters
the result to the FM carrier frequency
You are confusing carrier phase and audio phase.
I omitted the
On Tue, Apr 29, 2014 at 12:12 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
I would find it annoying to have to tell someone Oh, but if you want to
pass on the time you need to uninstall what you have now and replace it
with the client/server version.
Clearly there was
On Tue, Apr 29, 2014 at 4:35 AM, Rob nom...@example.com wrote:
This solution provides a lean ntpd program that is fit for most users,
and it facilitates the easy addition of refclock drivers.
Sure or you just recognize that only one system in a million needs refclock
support and assume anyone
Ok, so on a whim I purged it completely from the system. Installed from
scratch and the same problem occurred, no starting up of the process. I
let the installation complete without letting it try to start the
service again. Then I simply performed a reinstall where it detected
the
On 29/04/2014 09:41, Rob wrote:
[]
Of course that is what we have.
E.g. on a prototype here at home:
ntpq -p
remote refid st t when poll reach delay offset jitter
==
oPPS(0) .PPS.
On 29/04/2014 14:40, Jason Rabel wrote:
Ok, so on a whim I purged it completely from the system. Installed from
scratch and the same problem occurred, no starting up of the process. I
let the installation complete without letting it try to start the
service again. Then I simply performed a
Jason Rabel wrote:
Ok, so on a whim I purged it completely from the system. Installed from
scratch and the same problem occurred, no starting up of the process. I
let the installation complete without letting it try to start the
service again. Then I simply performed a reinstall where it
As a follow up to this discussion which has been very helpful to me
wanted to say we are moving towards adding 4 internal time servers (NTP
Unix based.. non-x86 hdw) to the two Windows domain controllers that are
running NTP as well. All 6 will be synced externally and will serve all
our
On 29/04/2014 14:40, Paul wrote:
[]
Sure or you just recognize that only one system in a million needs refclock
support and assume anyone running a refclock needs to be smart enough to
build ntpd with the requisite driver.
However, many of my users who use PPS or other ref-clocks run Windows,
On Tue, Apr 29, 2014 at 10:12 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
However, many of my users who use PPS or other ref-clocks run Windows
The subject line is Attn LINUX distributors. And it's really about
timepps.h
___
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 29/04/2014 14:40, Paul wrote:
[]
Sure or you just recognize that only one system in a million needs refclock
support and assume anyone running a refclock needs to be smart enough to
build ntpd with the requisite driver.
However,
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
Unfortunately that is not the same as performing some task like outputting
audio at an accuracy of 12us, but that is the next challenge :-)
Indeed, and you will likely want to look at very matched systems (PCs
and transmitters - the
On 29/04/2014 15:35, Rob wrote:
[]
But with a modular approach you would not need to rebuild to add
a standard refclock, that would just be the installation of another
package containing the precompiled refclock or refclock bundle.
That is no different from having a program like Perl as a base,
On 29/04/2014 15:33, Paul wrote:
On Tue, Apr 29, 2014 at 10:12 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
However, many of my users who use PPS or other ref-clocks run Windows
The subject line is Attn LINUX distributors. And it's really about
timepps.h
.. and I would
On 2014-04-29, Brian Inglis brian.ing...@shaw.ca wrote:
On 2014-04-29 00:47, David Woolley wrote:
On 29/04/14 03:59, Brian Inglis wrote:
I understand that the NBFM
transmitter starts with phase modulation then integrates, multiplies,
and filters
the result to the FM carrier frequency
You
On 2014-04-29 00:33, David Taylor wrote:
On 29/04/2014 06:35, A C wrote:
[]
The original error messages were:
A timeout was reached (3 milliseconds) while waiting for the Network
Time Protocol Daemon service to connect.
followed by
The Network Time Protocol Daemon service failed to
On 2014-04-29 03:14, Martin Burnicki wrote:
A C wrote:
On 2014-04-28 22:23, David Taylor wrote:
On 29/04/2014 05:51, A C wrote:
[]
Followed the same instructions, no dice.
.. and what are the messages in the Windows Event Log(s)?
The original error messages were:
A timeout was reached
On 2014-04-29, Rob nom...@example.com wrote:
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
Unfortunately that is not the same as performing some task like outputting
audio at an accuracy of 12us, but that is the next challenge :-)
Indeed, and you will likely want to look at very
William Unruh un...@invalid.ca wrote:
The problem is not the electronics, it is the response of the system to
the interrupt. That interrupt processing time is in the usec range.
This does not really matter when it is constant.
And my experience is that the jitter on the PPS refclock is usually
On 2014-04-29 07:00, Martin Burnicki wrote:
Jason Rabel wrote:
Ok, so on a whim I purged it completely from the system. Installed from
scratch and the same problem occurred, no starting up of the process. I
let the installation complete without letting it try to start the
service again.
On 2014-04-29 06:40, Jason Rabel wrote:
Ok, so on a whim I purged it completely from the system. Installed from
scratch and the same problem occurred, no starting up of the process. I
let the installation complete without letting it try to start the
service again. Then I simply performed a
On Tue, Apr 29, 2014 at 11:21 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
But the threat of breaking NTP into two separate parts had been mentioned,
and it was that which I was addressing
Sure. But I really have no idea what Harlan was speaking to there and, for
Windows
William Unruh un...@invalid.ca wrote:
On 2014-04-29, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
The problem is not the electronics, it is the response of the system to
the interrupt. That interrupt processing time is in the usec range.
This does not really matter
Martin Burnicki writes:
Harlan Stenn wrote:
This is something that may be different in the upcoming rewrite.
Do you have a pointer to those plans?
Not yet - we can start a discussion topic on the wiki and I doubt I'll
have time to do much with it for at least a month. Right now I have a
33 matches
Mail list logo
