[{"data":1,"prerenderedAt":67},["ShallowReactive",2],{"blog-eye-diagram-analysis-pcb-en":3},{"title":4,"description":5,"date":6,"lastUpdated":6,"category":7,"image":8,"imageAlt":9,"readingTime":10,"wordCount":11,"timeRequired":12,"htmlContent":13,"faq":14,"tags":30,"slug":36,"sourceLocale":37,"availableLocales":38,"jsonld":43},"How to Compare Eye Diagram Measurements on a PCB","Compare PCB eye measurements using the same test plane, pattern, clock recovery and equalization, then investigate differences with supporting evidence.","2026-11-20","design","/assets/blogs/eye-diagram-analysis-pcb/eye-diagram-nrz-concept.svg","Conceptual overlay of binary signal paths forming an eye opening",11,2078,"PT11M","\u003Cp>Eye diagrams can be compared only when the measurement plane, pattern, clock recovery, equalization, acquisition and measurement definitions are known. A smaller opening can indicate a channel problem, but it can also result from a different probe or analysis setting; the image alone does not establish the cause or the receiver&#39;s error rate.\u003C/p>\n\u003Cp>Compare captures and select the next diagnostic measurement before changing hardware. For channel-wide budgets and release decisions, see \u003Ca href=\"/en/blog/waveform-integrity-hf-pcb/\">waveform integrity in high-frequency PCB channels\u003C/a>. When a specification requires a BER contour or mask, record its method and target; a finite raw eye is not automatically an eye at a particular BER.\u003C/p>\n\u003Cp>\u003Cimg src=\"/assets/blogs/eye-diagram-analysis-pcb/eye-diagram-nrz-concept.svg\" alt=\"Conceptual overlay of binary signal paths forming an eye opening, not measured data\">\u003C/p>\n\u003Ch2>1. Know the Unit Interval First\u003C/h2>\n\u003Cp>The unit interval (UI) is one symbol interval. For binary NRZ, one symbol carries one bit, so the UI equals one bit period; for PAM4, each symbol represents two raw bits before coding overhead. PAM4 has three eyes, and the interface specification defines which eyes and measurement method apply. The examples below use binary signaling.\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Interface\u003C/th>\n\u003Cth align=\"right\">Data rate\u003C/th>\n\u003Cth align=\"right\">UI\u003C/th>\n\u003Cth align=\"right\">Nyquist frequency\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>DDR4-3200\u003C/td>\n\u003Ctd align=\"right\">3.2 GT/s\u003C/td>\n\u003Ctd align=\"right\">312.5 ps\u003C/td>\n\u003Ctd align=\"right\">1.6 GHz\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>10GBASE-R\u003C/td>\n\u003Ctd align=\"right\">10.3125 Gb/s\u003C/td>\n\u003Ctd align=\"right\">97.0 ps\u003C/td>\n\u003Ctd align=\"right\">5.2 GHz\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>PCIe Gen4\u003C/td>\n\u003Ctd align=\"right\">16 GT/s\u003C/td>\n\u003Ctd align=\"right\">62.5 ps\u003C/td>\n\u003Ctd align=\"right\">8 GHz\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>25G NRZ\u003C/td>\n\u003Ctd align=\"right\">25.78 Gb/s\u003C/td>\n\u003Ctd align=\"right\">38.8 ps\u003C/td>\n\u003Ctd align=\"right\">12.9 GHz\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>PCIe Gen5\u003C/td>\n\u003Ctd align=\"right\">32 GT/s\u003C/td>\n\u003Ctd align=\"right\">31.25 ps\u003C/td>\n\u003Ctd align=\"right\">16 GHz\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>A 10 ps timing contribution is approximately 3.2% of a 312.5 ps UI and 32% of a 31.25 ps UI. These ratios illustrate the available time scale; they do not establish eye closure or identify a board defect.\u003C/p>\n\u003Ch2>2. The Measurements That Matter\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Measurement\u003C/th>\n\u003Cth>Definition\u003C/th>\n\u003Cth>What closes it\u003C/th>\n\u003Cth>Note\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Cstrong>Eye height\u003C/strong>\u003C/td>\n\u003Ctd>Vertical opening at a defined sampling window and measurement method\u003C/td>\n\u003Ctd>ISI, reflections, crosstalk, power noise\u003C/td>\n\u003Ctd>Record the window, population and any statistical contour\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Eye amplitude\u003C/strong>\u003C/td>\n\u003Ctd>Difference between the measured mean high and low levels\u003C/td>\n\u003Ctd>Transmitter swing, channel response and termination\u003C/td>\n\u003Ctd>Record the measurement window; amplitude alone does not establish margin\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Eye width\u003C/strong>\u003C/td>\n\u003Ctd>Horizontal opening at the specified voltage threshold and measurement method\u003C/td>\n\u003Ctd>Jitter, ISI, skew within a differential pair\u003C/td>\n\u003Ctd>Record the threshold and any BER contour or mask method\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Crossing percentage\u003C/strong>\u003C/td>\n\u003Ctd>100 × (crossing − 0 level) / (1 level − 0 level)\u003C/td>\n\u003Ctd>Duty-cycle distortion, unequal rise and fall\u003C/td>\n\u003Ctd>50% ideal; 55% means crossings sit high\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Rise and fall time\u003C/strong>\u003C/td>\n\u003Ctd>20–80% or 10–90%, per the specification\u003C/td>\n\u003Ctd>Loss and dispersion, scope bandwidth\u003C/td>\n\u003Ctd>Compare with the same thresholds the spec uses\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Mask margin\u003C/strong>\u003C/td>\n\u003Ctd>Margin according to the specified mask and scaling method\u003C/td>\n\u003Ctd>All of the above\u003C/td>\n\u003Ctd>Follow the applicable mask alignment and hit or statistical criteria\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>For differential signals, use the differential waveform required by the test. Single-ended measurements of both legs can provide additional evidence of imbalance and common-mode behavior; interpret them with the probe reference and instrument configuration documented.\u003C/p>\n\u003Ch2>3. Raw Eye vs BER Eye\u003C/h2>\n\u003Cp>One illustrative statistical model represents random jitter (RJ) with Gaussian tails and deterministic jitter (DJ) using a dual-Dirac approximation. Under a specified model and tail convention, an extrapolated total jitter can be written:\u003C/p>\n\u003Cdiv class=\"math-block\">TJ = DJ + 2Q · RJ\u003Csub>rms\u003C/sub>\u003C/div>\n\n\u003Cp>Assume a hypothetical 10 Gb/s binary link (100 ps UI), 20 ps DJ and 1.5 ps rms RJ. Using two illustrative tail multipliers, 4.75 and 7.03, define a width as 1 UI minus modeled total jitter:\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Assumed \u003Cspan class=\"math-inline\">Q\u003C/span>\u003C/th>\n\u003Cth align=\"right\">Modeled TJ\u003C/th>\n\u003Cth align=\"right\">Illustrative eye width\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>4.75\u003C/td>\n\u003Ctd align=\"right\">34.3 ps\u003C/td>\n\u003Ctd align=\"right\">65.8 ps, 0.66 UI\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>7.03\u003C/td>\n\u003Ctd align=\"right\">41.1 ps\u003C/td>\n\u003Ctd align=\"right\">58.9 ps, 0.59 UI\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>The modeled widths differ by about 6.8 ps. They are not measurements of a real receiver and do not establish compliance. The mapping of \u003Cspan class=\"math-inline\">Q\u003C/span> to a BER depends on the tool&#39;s tail and error conventions. The result also depends on decomposition, clock recovery and distribution tails; correlated effects or non-Gaussian tails can invalidate the approximation. A raw acquisition does not become a measurement at 10⁻⁶ merely because it contains millions of bits. For actual acceptance use the interface&#39;s specified measurement or extrapolation method, and report error count, bits tested and confidence when reporting measured BER.\u003C/p>\n\u003Ch2>4. Rule Out the Measurement First\u003C/h2>\n\u003Cp>Measurement setup can alter an apparent eye. Check these conditions before changing the layout:\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Check\u003C/th>\n\u003Cth>Why\u003C/th>\n\u003Cth>Example\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Scope and probe bandwidth\u003C/td>\n\u003Ctd>Rise-time estimates depend on instrument response and edge definition\u003C/td>\n\u003Ctd>Under a Gaussian-response approximation with system rise time 0.4 / bandwidth, a 20 ps edge estimates 32 ps at 16 GHz and 23 ps at 33 GHz; verify the actual system response\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Probe loading and ground lead\u003C/td>\n\u003Ctd>Probe loading or a long ground lead can introduce or alter ringing\u003C/td>\n\u003Ctd>Compare suitable probe arrangements and loading\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Fixture and cable loss\u003C/td>\n\u003Ctd>Adapters, cables and test boards add loss and reflections\u003C/td>\n\u003Ctd>Compare at a documented reference plane using validated fixture S-parameters and de-embedding\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Where you probe\u003C/td>\n\u003Ctd>Probing at the receiver pin vs at a via or test point several mm away gives different eyes\u003C/td>\n\u003Ctd>Reflections appear or disappear with probe position\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Reference equalization\u003C/td>\n\u003Ctd>Compliance eyes often apply a defined CTLE/DFE; raw eyes do not\u003C/td>\n\u003Ctd>A closed raw eye at 16 GT/s may be compliant after reference equalization\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Pattern length and record length\u003C/td>\n\u003Ctd>Short patterns can miss pattern-dependent ISI; short records can miss rare events\u003C/td>\n\u003Ctd>PRBS7 vs PRBS31 can give different eye heights on a lossy channel\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Clock recovery settings\u003C/td>\n\u003Ctd>The recovery loop bandwidth defines which jitter is tracked and which is counted\u003C/td>\n\u003Ctd>Use the loop bandwidth the specification defines\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Ch2>5. Eye Symptoms and the Next Check\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Eye symptom\u003C/th>\n\u003Cth>Possible causes\u003C/th>\n\u003Cth>Evidence before a change\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Rounded edges, eye height shrinks with trace length, long-run bits ride higher than single bits\u003C/td>\n\u003Ctd>Insertion loss and ISI, or limited measurement bandwidth\u003C/td>\n\u003Ctd>Compare channel loss and the measurement response before changing routing, material or equalization\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Ledges or steps after transitions at a fixed time offset\u003C/td>\n\u003Ctd>Reflections, pattern-dependent ISI or fixture artifacts\u003C/td>\n\u003Ctd>Check probe position and pattern, then correlate with \u003Ca href=\"/en/blog/impedance-control-pcb/\">impedance control\u003C/a> and \u003Ca href=\"/en/blog/tdr-testing-pcb/\">TDR testing\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Notch or resonance-like closure at specific data rates\u003C/td>\n\u003Ctd>Via stubs, connector or fixture resonances\u003C/td>\n\u003Ctd>Compare channel and fixture measurements before considering \u003Ca href=\"/en/blog/backdrill-pcb/\">backdrilling\u003C/a> or other geometry changes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Thick 1 and 0 rails, noise uncorrelated to the data pattern\u003C/td>\n\u003Ctd>Crosstalk, power-supply noise or instrument noise\u003C/td>\n\u003Ctd>Correlate rails and aggressor activity; see the \u003Ca href=\"/en/blog/crosstalk-in-high-frequency-pcb/\">crosstalk guide\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Wide crossing region, eye width shrinks, height mostly fine\u003C/td>\n\u003Ctd>Clock jitter, ISI or recovery settings\u003C/td>\n\u003Ctd>Compare jitter and recovery settings, then correlate clock and supply measurements\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Crossing not at 50%, or asymmetric edges\u003C/td>\n\u003Ctd>Duty-cycle distortion, unequal edges, skew or mode conversion\u003C/td>\n\u003Ctd>Compare rising and falling edges and differential and individual-leg measurements\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Overshoot and ringing at edges\u003C/td>\n\u003Ctd>Termination, discontinuities or probe artifacts\u003C/td>\n\u003Ctd>Check probing, source/load configuration and TDR before revising termination\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Double bands on the edges, overshoot above the 1 level\u003C/td>\n\u003Ctd>Equalization, pattern dependence or reflections\u003C/td>\n\u003Ctd>Compare approved equalization settings and pattern-correlated waveforms\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>When one lane differs from its neighbors, compare routing, via count, connector position, settings and measurement setup before attributing the difference to the board.\u003C/p>\n\u003Ch2>6. Hypothetical Review: A Lane With a Delayed Feature\u003C/h2>\n\u003Cp>Assume a binary 10.3125 Gb/s lane has a 97 ps UI and a feature approximately 35 ps after a transition. This is an illustrative investigation, not a measured customer case. Suppose the team is testing whether a reflection could contribute to the feature:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Check the setup\u003C/strong>: document the measurement plane, pattern, bandwidth, clock recovery, equalization and fixture. Compare another suitable measurement setup to investigate probe artifacts.\u003C/li>\n\u003Cli>\u003Cstrong>Estimate a distance\u003C/strong>: if 35 ps is a round-trip delay from the reference plane and the assumed one-way propagation delay is 7 ps/mm, then \u003Cspan class=\"math-inline\">35/(2 × 7) = 2.5\u003C/span> mm. Real propagation, the reference plane and the feature&#39;s origin must be established; this estimate does not locate a particular via or breakout by itself.\u003C/li>\n\u003Cli>\u003Cstrong>Seek independent evidence\u003C/strong>: compare TDR and channel measurements with the model, including fixture and package contributions. Examine pattern correlation and alternate causes such as ISI.\u003C/li>\n\u003Cli>\u003Cstrong>Evaluate a proposed change\u003C/strong>: only after correlation, compare the relevant geometry or equalization options and repeat the same measurements. An improved eye still needs the interface&#39;s prescribed acceptance evidence.\u003C/li>\n\u003C/ol>\n\u003Cp>If the delay is not a simple round trip, the estimate is not applicable. Do not treat a visible ledge alone as proof of a board fault or a successful fix.\u003C/p>\n\u003Ch2>7. Compare Two Captures Before Changing Hardware\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Comparison field\u003C/th>\n\u003Cth>Capture A\u003C/th>\n\u003Cth>Capture B\u003C/th>\n\u003Cth>Decision\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Plane and fixture\u003C/td>\n\u003Ctd>Receiver test pad, fixture included\u003C/td>\n\u003Ctd>Connector plane, fixture removed\u003C/td>\n\u003Ctd>Not directly comparable; reconcile the reference plane and de-embedding\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Pattern and activity\u003C/td>\n\u003Ctd>PRBS7, aggressors idle\u003C/td>\n\u003Ctd>PRBS31, aggressors active\u003C/td>\n\u003Ctd>Repeat with matched patterns and aggressor state, then vary one condition\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Clock and equalization\u003C/td>\n\u003Ctd>Recovered clock, equalization off\u003C/td>\n\u003Ctd>Different recovery bandwidth, reference equalization on\u003C/td>\n\u003Ctd>Match the specified settings before attributing the opening difference to hardware\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Reported result\u003C/td>\n\u003Ctd>Finite captured eye\u003C/td>\n\u003Ctd>Statistical contour at a stated BER\u003C/td>\n\u003Ctd>Preserve both labels; neither alone establishes measured receiver BER\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>The rows are hypothetical examples of mismatched conditions, not measurements. Record actual settings, calibration, sample depth, waveform files and any confidence assumptions with each result.\u003C/p>\n\u003Ch2>8. Specifying Eye Diagram Verification\u003C/h2>\n\u003Col>\n\u003Cli>\u003Cstrong>State the interface and specification\u003C/strong>: data rate, compliance specification and the measurement point (TX pins, RX pins, connector).\u003C/li>\n\u003Cli>\u003Cstrong>State the method\u003C/strong> for eye height, width and any BER contour or mask, and whether reference equalization is applied.\u003C/li>\n\u003Cli>\u003Cstrong>Define the pattern\u003C/strong> (PRBS length or compliance pattern) and the clock recovery settings.\u003C/li>\n\u003Cli>\u003Cstrong>Define the fixture\u003C/strong> and how it is de-embedded.\u003C/li>\n\u003Cli>\u003Cstrong>Tie the board-level controls to the result\u003C/strong>: impedance tolerance and coupons, backdrill depth, loss targets.\u003C/li>\n\u003C/ol>\n\u003Cp>HILPCB&#39;s \u003Ca href=\"/en/products/high-speed-pcb/\">high-speed PCB\u003C/a> catalog lists back-drilling, controlled impedance and advanced VNA, eye diagram and jitter test options. Send the stackup, impedance and loss targets, test plane and measurement requirements in a \u003Ca href=\"/en/quote/\">quote request\u003C/a>; confirm the feasible construction, test scope and deliverables for the specific project. The designer owns the channel requirements, the fabricator confirms the board construction and the product owner defines system qualification. For the overall design flow, see the \u003Ca href=\"/en/blog/high-speed-pcb-design/\">high-speed PCB design guide\u003C/a>.\u003C/p>\n\u003Cdiv data-component=\"BlogQuickQuoteInline\">\u003C/div>\n\n\u003C!-- faq:start -->\n\u003Ch2>FAQ\u003C/h2>\n\u003Ch3>What does an eye diagram show?\u003C/h3>\n\u003Cp>It overlays repeated intervals of a serial waveform. Eye height, width and crossing behavior describe the opening under a defined measurement method. Loss, reflections, noise, jitter and setup can produce similar symptoms, so use additional evidence to distinguish causes.\u003C/p>\n\u003Ch3>What is a good eye height and eye width?\u003C/h3>\n\u003Cp>There is no universal number. Use the interface specification&#39;s measurement plane, mask or other limits, acquisition or BER method, and any required equalization. A raw opening and a modeled contour are different results and must be labeled accordingly.\u003C/p>\n\u003Ch3>Why does my eye look open on the scope but fail compliance?\u003C/h3>\n\u003Cp>A finite capture can miss rare events and is not automatically an eye at a particular BER. Compliance tests may use different filters, patterns, clock recovery or a specified statistical method; reconcile those conditions before comparing results.\u003C/p>\n\u003Ch3>What causes a closed eye diagram on a PCB?\u003C/h3>\n\u003Cp>Insertion loss over long or lossy routes, reflections from impedance discontinuities and via stubs, crosstalk from adjacent signals, power-supply noise, clock jitter, and intra-pair skew. Probe and fixture problems can also look like a closed eye, so check the measurement first.\u003C/p>\n\u003Ch3>Do I need an eye diagram if I have TDR and S-parameters?\u003C/h3>\n\u003Cp>TDR and S-parameters characterize channel behavior at defined planes; an eye shows waveform behavior under its own source, measurement and processing conditions. An eye may use a reference receiver rather than the actual receiver, and neither measurement alone proves system BER or compliance.\u003C/p>\n\u003C!-- faq:end -->\n\u003Csection class=\"related-links\" aria-label=\"Related\">\u003Ch3>Related links\u003C/h3>\u003Cul>\u003Cli>\u003Ca href=\"/en/blog/waveform-integrity-hf-pcb/\">Waveform Integrity in High-Frequency PCB Channels\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/impedance-control-pcb/\">Impedance Control PCB: Precision Engineering for High-Speed Electronics\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/tdr-testing-pcb/\">TDR Testing PCB: Advanced Quality Control for Mission-Critical Electronics\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/backdrill-pcb/\">Backdrill PCB: Removing Via Stubs for High-Speed Signal Integrity\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/crosstalk-in-high-frequency-pcb/\">Crosstalk in High Frequency PCB: Causes, Analysis, and Prevention\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/products/high-speed-pcb/\">high-speed PCB\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/quote/\">quote request\u003C/a>\u003C/li>\u003C/ul>\u003C/section>",[15,18,21,24,27],{"question":16,"answer":17,"answerText":17},"What does an eye diagram show?","It overlays repeated intervals of a serial waveform. Eye height, width and crossing behavior describe the opening under a defined measurement method. Loss, reflections, noise, jitter and setup can produce similar symptoms, so use additional evidence to distinguish causes.",{"question":19,"answer":20,"answerText":20},"What is a good eye height and eye width?","There is no universal number. Use the interface specification's measurement plane, mask or other limits, acquisition or BER method, and any required equalization. A raw opening and a modeled contour are different results and must be labeled accordingly.",{"question":22,"answer":23,"answerText":23},"Why does my eye look open on the scope but fail compliance?","A finite capture can miss rare events and is not automatically an eye at a particular BER. Compliance tests may use different filters, patterns, clock recovery or a specified statistical method; reconcile those conditions before comparing results.",{"question":25,"answer":26,"answerText":26},"What causes a closed eye diagram on a PCB?","Insertion loss over long or lossy routes, reflections from impedance discontinuities and via stubs, crosstalk from adjacent signals, power-supply noise, clock jitter, and intra-pair skew. Probe and fixture problems can also look like a closed eye, so check the measurement first.",{"question":28,"answer":29,"answerText":29},"Do I need an eye diagram if I have TDR and S-parameters?","TDR and S-parameters characterize channel behavior at defined planes; an eye shows waveform behavior under its own source, measurement and processing conditions. An eye may use a reference receiver rather than the actual receiver, and neither measurement alone proves system BER or compliance.",[31,32,33,34,35],"eye diagram","signal integrity","eye height","eye width","high-speed PCB","eye-diagram-analysis-pcb","en",[37,39,40,41,42],"de","cn","fr","ru",{"blog":44,"breadcrumb":53},{"@context":45,"@type":46,"headline":4,"description":5,"image":8,"url":47,"datePublished":6,"dateModified":6,"timeRequired":12,"keywords":48,"articleSection":7,"author":49,"publisher":52},"https://schema.org","BlogPosting","https://hilpcb.com/en/blog/eye-diagram-analysis-pcb/","eye diagram, signal integrity, eye height, eye width, high-speed PCB",{"@type":50,"name":51},"Organization","HILPCB",{"@type":50,"name":51},{"@context":45,"@type":54,"itemListElement":55},"BreadcrumbList",[56,61,65],{"@type":57,"position":58,"name":59,"item":60},"ListItem",1,"Home","https://hilpcb.com/",{"@type":57,"position":62,"name":63,"item":64},2,"Blog","https://hilpcb.com/en/blog/",{"@type":57,"position":66,"name":36,"item":47},3,1795278537016]