On 10/06/2021 09:24, YENDstudio wrote:
Hi Jacob,
Thanks for the info.
I have seen the fault recovery working on the slave machine. But the master
port of the BC machine didn't recover (no activity on the port). Most of the
fault occurs after sending a sync message and requesting the tx-times
Yes, I have tried with 100ms timeout, and the issue still exists.
On Thu, Jun 10, 2021, 10:17 Grygorii Strashko
wrote:
>
>
> On 10/06/2021 09:24, YENDstudio wrote:
> > Hi Jacob,
> >
> > Thanks for the info.
> > I have seen the fault recovery working on the slave machine. But the
> master port of
Hi Jacob,
Thanks for the info.
I have seen the fault recovery working on the slave machine. But the master
port of the BC machine didn't recover (no activity on the port). Most of
the fault occurs after sending a sync message and requesting the
tx-timestamp which would be sent in the follow-up mes
On 6/7/2021 1:19 PM, YENDstudio wrote:
> Hello,
>
> I have configure one of my machines as a unicast BC which is
> synchronized to the grandmaster clock via the first of it's two ports.
> The second port is used to provide sync to another local machine. This
> setup works for a few hours after
Hello,
I have configure one of my machines as a unicast BC which is synchronized
to the grandmaster clock via the first of it's two ports. The second port
is used to provide sync to another local machine. This setup works for a
few hours after which one of the ports (master port) is marked as faul
