• Davide Ciminaghi's avatar
    compliance: 11.2 c: take followup cf into account · c371afa5
    Davide Ciminaghi authored
    11.2 c says:
    
    If the twoStepFlag bit of the flagField of the of the Sync message is TRUE,
    indicating that a Follow_Up message will be received, then
    
            <offsetFromMaster> = <syncEventIngressTimestamp> -
           <preciseOriginTimestamp> - <meanPathDelay> -
           correctionField of Sync message -
           correctionField of Follow_Up message.
    
    Before this patch, only the correctionField of the Sync message was
    subtracted. We fix things by adding the Follow_Up correctionField to the
    Sync correctionField.
    
    Now m_to_s_dly as calculated in pp_servo_got_sync is:
    
    t2 - t1 - sync_cf - follow_up_cf
    c371afa5
Name
Last commit
Last update
..
Makefile Loading commit data...
arith.c Loading commit data...
bmc.c Loading commit data...
common-fun.c Loading commit data...
common-fun.h Loading commit data...
fsm-lib.c Loading commit data...
fsm-table.c Loading commit data...
hooks.c Loading commit data...
msg.c Loading commit data...
open-close.c Loading commit data...
servo.c Loading commit data...
state-disabled.c Loading commit data...
state-faulty.c Loading commit data...
state-initializing.c Loading commit data...
state-listening.c Loading commit data...
state-master.c Loading commit data...
state-passive.c Loading commit data...
state-pre-master.c Loading commit data...
state-slave.c Loading commit data...
state-uncalibrated.c Loading commit data...