60 ns delay in a faulty connection - how?

  • Thread starter Thread starter Borek
  • Start date Start date
  • Tags Tags
    Connection Delay
Click For Summary

Discussion Overview

The discussion revolves around the technical possibility of a 60 ns delay in signal timing due to a faulty connection in the context of the OPERA experiment, which involves time-stamping neutrinos. Participants explore how such a delay could occur, considering factors like signal propagation speed, clock synchronization, and potential errors in timing measurements.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant questions how a faulty connection could lead to a 60 ns delay, noting that signal propagation speed remains constant and the physical path did not change significantly.
  • Another suggests that if the signal is digital, a high impedance connection could slow the rise time, causing a delay in triggering the next stage.
  • A participant clarifies that the experiment involves time-stamping neutrinos rather than sending a signal, emphasizing the importance of clock synchronization and understanding all delays in the process.
  • One participant references an external comment as a potential explanation for the "faulty cable" issue, indicating a search for reasonable explanations.
  • Another participant reiterates the importance of GPS for clock synchronization, suggesting that any lost time could indicate improper synchronization.
  • A later reply emphasizes that synchronization is not in "real time" and discusses the complexity of measuring delays from GPS signals, while also proposing that errors in timing related to neutrino generation and detection could be a more likely source of delay.

Areas of Agreement / Disagreement

Participants express differing views on the source of the delay, with some focusing on the implications of faulty connections and others on synchronization issues. There is no consensus on the exact cause of the 60 ns delay, and multiple competing explanations are presented.

Contextual Notes

Participants acknowledge the complexity of timing measurements and the potential for errors in accounting for various delays, but do not resolve these uncertainties.

Borek
Mentor
Messages
29,204
Reaction score
4,626
Yes, it is about OPERA experiment, but it has nothing to do with neutrinos.

Can someone try to explain how is it technically possible that faulty connection could be responsible for additional signal delay? I understand it can make the signal unreadable, but delayed by 60 ns?

Main reason I can't understand the situation is that even if the link is faulty, signal still propagates with the same speed - approximately 1 feet per 1 ns. 60 ns is equivalent 60 feet. Signal path didn't change that much. What is the source of the delay? What am I missing?
 
Engineering news on Phys.org
Is it digital signal? If so, it might be possible that the faulty connection like a high impedance connection cause the rise time to slow way down and take a long time for signal to past the threshold to trigger the next stage. You'll see it as delay.
 
They are not actually sending a signal in the experiment. They "time stamp" the neutrinos at the source (i.e. they keep a record of when the pulse was sent), and time-stamp them again when they arrives at the detector.
Hence, the issue is not about delays; it is about whether or not they've managed to synchronize their clocks well enough, and if they understand all the delays involved in sending/detecting the neutrinos.
 
yungman said:
Is it digital signal? If so, it might be possible that the faulty connection like a high impedance connection cause the rise time to slow way down and take a long time for signal to past the threshold to trigger the next stage. You'll see it as delay.

Thanks, now I see a possible physics behind, that's what I was missing.

f95toli said:
Hence, the issue is not about delays; it is about whether or not they've managed to synchronize their clocks well enough, and if they understand all the delays involved in sending/detecting the neutrinos.

If I understand the situation correctly they used GPS to synchronize the clocks, so these lost 60 ns will mean clocks are not properly synchronized. I believe we say the same thing.

maimonides said:
FWIW: This comment on Cosmic Variance is the only hint at a reasonable explanation of the "faulty cable" I´ve seen so far.

At least it means I am not the only person wondering about it.
 
Borek said:
If I understand the situation correctly they used GPS to synchronize the clocks, so these lost 60 ns will mean clocks are not properly synchronized. I believe we say the same thing.

Yes, they use GPS. But the synchronization is not in "real time",which is what I thought you meant, there is no delay "compared to something" since they are not comparing two signals.
The issue is not so much the clocks themselves. it is that the total delay they have to account for in the timing is much longer than 60ns and if they've made a mistake when e.g. measuring the delay that comes from the signal traveling from the GPS antenna down into the tunnel this could -potentially- cause quite a large delay; although it is very unlikely that they would make such a huge mistake. Unless they've made a serious mistake somewhere their clocks should be synchronized to within 1 ns.

Another -in my view more likely -explanation is that there is an error in timing when it comes to generation/detection of the neutrinos; there is an awful lot of electronics between the detectors themselves and the clocks that time-stamp the data and that delay (which has to be added/subtracted from the time-stamps at each end) can be quite tricky to measure.
 

Similar threads

Replies
8
Views
2K
  • · Replies 11 ·
Replies
11
Views
3K
  • · Replies 43 ·
2
Replies
43
Views
6K
Replies
6
Views
4K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 12 ·
Replies
12
Views
4K
  • · Replies 8 ·
Replies
8
Views
3K
  • · Replies 5 ·
Replies
5
Views
3K
  • · Replies 11 ·
Replies
11
Views
3K
Replies
2
Views
5K