On Sat, Sep 10, 2022 at 09:18:04PM +0530, Raj wrote: > We are observing that When ECU1 is active ECU2 initially takes a long time > (randomly 10 sec - 2min approx) to sync with ECU1(GM) and once ECU2 > successfully syncs with ECU1 then after that there is no issue. ECU2 > throwing "SLAVE to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES" error and > considering itself as GM by sending announce packet , after that again > considering ECU1 as GM and going to slave mode, this fluctuation on ECU2 is > happening intially when ECU2 is trying to sync with ECU1 and after some > time (randomly 10 sec -2min) ECU2 successfully getting synchronozed with > ECU1. > > > The question is why does ECU2 take more time initially to select ECU1 as GM > ?
If you capture PTP traffic on ECU2, do you see announce messages from ECU1 every two seconds (following logAnnounceInterval=1) ? -- Miroslav Lichvar _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
