On Mon, Sep 05, 2022 at 05:31:55PM +0600, - - wrote:
> Thank you for your help.
>
> But I'm not quite clear:
> Sync message
> Follow_up message
> Delay_req message
> Delay_resp message
> Delay_req message
> Delay_resp message
>
> So it looks like there is a surplus here
> Delay_req message
>
Hi,
Then probably the first question would be - is this unicast or multicast? Or
using a particular profile?
Regards
Dennis
-Original Message-
From: Miroslav Lichvar
Sent: Monday, September 5, 2022 11:10
To: Dennis Hagarty (dehagart)
Cc: artst...@gmail.com;
Thank you for your help.
But I'm not quite clear:
Sync message
Follow_up message
Delay_req message
Delay_resp message
Delay_req message
Delay_resp message
So it looks like there is a surplus here
Delay_req message
Delay_resp message
Is this normal?
Best regards,
Vyacheslav
пн, 5 сент. 2022 г.
On Mon, Sep 05, 2022 at 08:11:48AM +, Dennis Hagarty (dehagart) via
Linuxptp-users wrote:
> In IEEE 1588-2019, the requirement for regular messages is outlined in
> “9.5.11.2 Timing requirements” – generally they should be transmitted at an
> interval above 90% of the desired inter-message
Hi,
The slave sends the delay_Req to the master.
The slave should transmit a delay_Req at a regular interval depending on the
configuration or negotiation of the inter-message interval (the desired time
between each message).
In IEEE 1588-2019, the requirement for regular messages is outlined
On Mon, Sep 05, 2022 at 12:25:20AM +0500, - - wrote:
> I understand that depending on the mod ptp can work without Follow_up.
Follow up is needed when the hardware cannot modify the timestamp in
the sync message as it is being transmitted. This seems to be rare in
computer HW.
> So it looks like
