On Tue, Feb 06, 2018 at 10:26:34AM +0000, Mikael Arvids wrote: > Looking at the code (process_sync, process_follow_up and port_syfusfm) it > seems that the intention is to handle the case when a follow up is processed > before the corresponding sync, not when the next sync is received before the > follow up. Is this a known issue and has anyone made any fix for this?
It is not an issue, known or unknown. This is the design of the protocol. Once a new Sync message has been received, the servo's deadline has been missed, and it is too late to do anything with the previous Sync message. You should find out why your Follow-Up messages are being delayed for so long. In the example you gave, the Fup comes one whole period (125 ms) later than expected. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
