8000 Where is the source calculating delay=(t2-t1+t4-t3)/2 ? · Issue #87 · ptpd/ptpd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Where is the source calculating delay=(t2-t1+t4-t3)/2 ? #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ZENG-XINGJI opened this issue Dec 3, 2021 · 2 comments
Open

Where is the source calculating delay=(t2-t1+t4-t3)/2 ? #87

ZENG-XINGJI opened this issue Dec 3, 2021 · 2 comments

Comments

@ZENG-XINGJI
Copy link

Hi,

I'm developing a hardware which synchronizes its time to O-DU. What I want to realize is a hardware PTP as the following:

  • calculate delay(=(t2-t1+t4-t3)/2) using ptpd
  • save the calculated delay in the hardware register
  • the hardware adjust the its time according to the delay value automatically

However, I'm stuck as I can't find out the location of source which calculates delay=(t2-t1+t4-t3)/2. Does anybody has
idea about this..? I am beginner of ptpd and I'm so suffering from finding a specified code from tons of source..

My ptpd version is PTPDv2 version 2.3.1.1. Please reply if you need any additional information!

Best regards
Xingji
@wowczarek
Copy link
Member

Although ptpd doesn't call them t1...t4, you'll find it here:

ptpd/src/dep/servo.c

Line 118 in 1ec9e65

updateDelay(one_way_delay_filter * mpd_filt, const RunTimeOpts * rtOpts, PtpClock * ptpClock, TimeInternal * correctionField)

ptpd/src/dep/servo.c

Line 358 in 1ec9e65

updatePeerDelay(one_way_delay_filter * mpd_filt, const RunTimeOpts * rtOpts, PtpClock * ptpClock, TimeInternal * correctionField, Boolean twoStep)

ptpd/src/dep/servo.c

Line 441 in 1ec9e65

updateOffset(TimeInternal * send_time, TimeInternal * recv_time,

updatePeerDelay is for P2P mode.

@liu-jeff
Copy link

Although ptpd doesn't call them t1...t4, you'll find it here:

ptpd/src/dep/servo.c

Line 118 in 1ec9e65

updateDelay(one_way_delay_filter * mpd_filt, const RunTimeOpts * rtOpts, PtpClock * ptpClock, TimeInternal * correctionField)

ptpd/src/dep/servo.c

Line 358 in 1ec9e65

updatePeerDelay(one_way_delay_filter * mpd_filt, const RunTimeOpts * rtOpts, PtpClock * ptpClock, TimeInternal * correctionField, Boolean twoStep)

ptpd/src/dep/servo.c

Line 441 in 1ec9e65

updateOffset(TimeInternal * send_time, TimeInternal * recv_time,

updatePeerDelay is for P2P mode.

Hello, I am very sorry to bother you , but I have some confusion about this, why is NeighborRateRatio not considered when measuring PTP path delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wowczarek @ZENG-XINGJI @liu-jeff
0