On Tue, Jan 09, 2018 at 05:21:39PM +0100, Miroslav Lichvar wrote:
> > I think I said that this works when N==GM.
>
> Hm, does that change anything? If the delay of event messages going
> from GM/N to S is larger than the delay of messages going from S to
> GM/N, the clock of S will be running behi
On Tue, Jan 09, 2018 at 07:52:11AM -0800, Richard Cochran wrote:
> On Tue, Jan 09, 2018 at 11:09:43AM +0100, Miroslav Lichvar wrote:
> > It's not clear to me how would that work. Let's say I have a
> > grandmaster GM, slave S and monitoring node N, and I don't know how
> > much asymmetry is there o
On Tue, Jan 09, 2018 at 11:09:43AM +0100, Miroslav Lichvar wrote:
> It's not clear to me how would that work. Let's say I have a
> grandmaster GM, slave S and monitoring node N, and I don't know how
> much asymmetry is there on any of the paths GM-S, GM-N and S-N. How
> will measuring offset of GM
On Mon, Jan 08, 2018 at 09:02:52PM -0800, Richard Cochran wrote:
> On Mon, Jan 08, 2018 at 03:56:29PM +0100, Miroslav Lichvar wrote:
> > You mean asymmetry added by boundary clocks on the path to the
> > grandmaster?
>
> Yes, or from any other source at all.
It's not clear to me how would that wo
On Mon, Jan 08, 2018 at 03:56:29PM +0100, Miroslav Lichvar wrote:
> You mean asymmetry added by boundary clocks on the path to the
> grandmaster?
Yes, or from any other source at all.
> One thing I find odd is that the sync message doesn't have a TLV
> attached too. Does the specification say an
On Mon, Jan 01, 2018 at 08:05:31PM -0800, Richard Cochran wrote:
> This series adds support for Meinberg Funkuhren's NetSync Monitor
> (NSM) protocol. NSM allows a node with a local time reference (like a
> GM using GPS) to measure the offset of a given clock. In a nutshell,
> NSM works by having
