lidar is light detection and ranging that estimates distance and reflectivity from transmitted laser light and its return. Lidar supplies three-dimensional geometry for autonomous vehicles, robots, mapping, factories, and AR systems using lasers, scanning optics, sensitive detectors, timing, and point-cloud processing.

Ranging principles. Direct time of flight measures delay with R = cΔt/2; pulsed systems need precise timestamps and enough photon energy for range. Flash lidar illuminates a field and images depth without moving scan optics. FMCW lidar chirps a coherent laser and measures beat frequency for distance plus Doppler velocity, with strong ambient-light rejection but demanding coherence and photonic integration. Phase-shift methods serve shorter controlled ranges.

Scanning architectures. Mechanical spinning units provide wide field and mature long-range performance but have size and moving-part concerns. MEMS mirrors steer compact beams; optical phased arrays use controlled waveguide phase; flash arrays trade peak power and detector count for no scanning. Field of view, angular resolution, frame rate, points per second, aperture, eye safety, and scan pattern are coupled. Motion during a scan distorts the cloud unless timing and ego-motion are corrected.

Semiconductor building blocks. 905-nm systems use mature silicon APDs or SPADs and compact edge-emitting or VCSEL sources, while 1550-nm systems can transmit more eye-safe power but require InGaAs-class detectors and costlier optics. SPAD arrays count single photons with dead time, dark counts, afterpulsing, and crosstalk. TIAs and time-to-digital converters set sensitivity and timing; drivers deliver narrow high-current laser pulses; silicon photonics can integrate FMCW routing and coherent receive.

Perception and safety. Return probability depends on range squared, target reflectivity, incidence angle, weather, aperture, pulse energy, and background. Multiple returns identify vegetation or transparent boundaries. Calibration aligns beams, timing, intensity, camera, radar, and vehicle coordinates. Point-cloud AI detects, segments, tracks, and estimates free space, but performance must be validated on sparse, reflective, dark, wet, foggy, and interfering scenes. Eye safety and laser functional safety constrain every mode.

Characterization and production. A production implementation begins with explicit terminal conditions, operating ranges, loading, accuracy, noise, latency, efficiency, area, cost, lifetime, and fault behavior. Schematic or architectural models establish feasibility; extracted, package, board, thermal, and control-loop models then reveal interactions hidden by ideal sources and loads. Verification spans process, voltage, temperature, mismatch, aging, startup, shutdown, overload, brownout, and recovery. Teams should define measurement bandwidth, observation point, stimulus, pass limit, guard band, and statistical confidence before simulation. Layout review covers current return, thermal gradients, matching, parasitic coupling, electromigration, voltage stress, latch-up, ESD paths, and test access. Correlation retains netlists, models, scripts, tool versions, raw results, lab conditions, calibration status, and explanations for outliers. This evidence turns a nominal design into a reproducible component that can be signed off across device, circuit, package, firmware, and system teams. Corner selection should follow sensitivity rather than blindly combining labels. Deterministic sweeps expose monotonic trends, targeted Monte Carlo analysis estimates distribution tails, and importance sampling can explore rare failures. Reviewers should distinguish model uncertainty from manufacturing variation and avoid claiming yield from too few samples. The interface contract must state what happens outside normal operation. Open and short terminals, reverse polarity, hot plug, disabled bias, floating control pins, clock loss, thermal shutdown, current limiting, and repeated fault cycling often determine field reliability even though they are absent from the nominal transfer function. Dynamic behavior deserves the same attention as steady state. Settling, overshoot, ringing, slew, recovery from saturation, mode transitions, and interaction with external poles can violate a system limit long before a DC endpoint does. Time-domain tests should include realistic edge rates and source impedance. Noise should be referred to the signal or supply point that matters to the application and integrated only over a stated bandwidth. Thermal, flicker, quantization, switching, reference, substrate, and electromagnetic contributions may combine differently across modes, so a single spot-noise number rarely completes the specification. Power and thermal claims should include quiescent, active, transient, and fault states. Average efficiency can hide localized current density or hot spots; electrothermal simulation and temperature-aware device models connect electrical stress to lifetime, drift, and protection thresholds. Physical design must preserve the assumptions behind the schematic. Symmetry, common-centroid placement, dummies, shielding, guard rings, Kelvin sensing, wide current paths, via arrays, controlled coupling, and quiet reference routing are selected according to the dominant error rather than applied as decoration. Production test strategy is part of design. Trim range, observability, loopback modes, built-in self-test, boundary conditions, test time, and instrument uncertainty determine which specifications can be guaranteed economically. Characterization across wafers and lots should feed model and guard-band updates. System telemetry can extend laboratory correlation into deployed products. Error counters, calibration codes, temperatures, supply monitors, fault flags, margin measurements, and performance events help distinguish random failures from systematic drift without exposing sensitive implementation details. A useful comparison normalizes alternatives at equal output requirement and environment. Peak headline values can be misleading when bandwidth, drive, voltage, area, cooling, external components, calibration, or reliability differs; the decision record should name the workload and weighting used. Cross-functional review should trace each requirement from physical mechanism through circuit behavior to application impact. That trace prevents duplicated margin, exposes assumptions that span ownership boundaries, and makes later process or package substitutions safer.

<svg viewBox="0 0 760 470" xmlns="http://www.w3.org/2000/svg" font-family="-apple-system,Segoe UI,Roboto,sans-serif">
  <rect width="760" height="470" fill="#0d1117"/>
  <defs>
    <marker id="liCyanArrow" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6" markerHeight="6" orient="auto">
      <path d="M0 0L10 5L0 10Z" fill="#38bdf8"/>
    </marker>
    <marker id="liGreenArrow" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6" markerHeight="6" orient="auto">
      <path d="M0 0L10 5L0 10Z" fill="#34d399"/>
    </marker>
    <linearGradient id="liBeam" x1="0" x2="1">
      <stop offset="0" stop-color="#38bdf8" stop-opacity=".9"/>
      <stop offset="1" stop-color="#38bdf8" stop-opacity=".15"/>
    </linearGradient>
    <radialGradient id="liPulseGlow">
      <stop offset="0" stop-color="#7dd3fc" stop-opacity=".45"/>
      <stop offset="1" stop-color="#38bdf8" stop-opacity="0"/>
    </radialGradient>
    <filter id="liPhotonGlow" x="-90%" y="-90%" width="280%" height="280%">
      <feGaussianBlur stdDeviation="4" result="blur"/>
      <feMerge><feMergeNode in="blur"/><feMergeNode in="SourceGraphic"/></feMerge>
    </filter>
  </defs>

  <text x="380" y="31" fill="#e6edf3" font-size="21" font-weight="700" text-anchor="middle">LiDAR — Measure Distance with Light Travel Time</text>
  <text x="380" y="53" fill="#8b98a5" font-size="12.5" text-anchor="middle">a scanner launches short laser pulses; photon return time and direction place points in three-dimensional space</text>

  <!-- Sensor module: emitter, steering mirror, receiver, timing electronics -->
  <g transform="translate(24 84)">
    <text x="96" y="-8" fill="#93c5fd" font-size="10.5" font-weight="700" text-anchor="middle">LiDAR SENSOR</text>
    <rect width="192" height="226" rx="13" fill="#0b1726" stroke="#60a5fa" stroke-width="1.7"/>

    <!-- Laser diode -->
    <g transform="translate(15 25)">
      <rect width="72" height="44" rx="7" fill="#10233b" stroke="#38bdf8"/>
      <path d="M12 22h17M29 10v24l23-12Z" fill="none" stroke="#7dd3fc" stroke-width="1.8"/>
      <path d="M52 12v20M57 15l9-6M57 22h11M57 29l9 6" stroke="#38bdf8" stroke-width="1.5"/>
      <text x="36" y="58" fill="#93c5fd" font-size="8.2" text-anchor="middle">pulsed laser</text>
    </g>

    <!-- MEMS/scanning mirror -->
    <path d="M87 47H113" stroke="#38bdf8" stroke-width="2.5" marker-end="url(#liCyanArrow)"/>
    <g transform="translate(117 22)">
      <circle cx="29" cy="29" r="29" fill="#151f2b" stroke="#a78bfa"/>
      <path d="M10 39L48 19" stroke="#c4b5fd" stroke-width="5" stroke-linecap="round"/>
      <path d="M17 9A27 27 0 0 1 52 16" fill="none" stroke="#a78bfa" stroke-width="1.7" marker-end="url(#liCyanArrow)"/>
      <text x="29" y="69" fill="#c4b5fd" font-size="8.2" text-anchor="middle">scan mirror</text>
    </g>

    <!-- Receive aperture and SPAD -->
    <g transform="translate(17 111)">
      <path d="M0 22Q22-8 44 22Q22 52 0 22Z" fill="#142b44" stroke="#60a5fa" stroke-width="1.8"/>
      <circle cx="23" cy="22" r="9" fill="#0e4055" stroke="#38bdf8"/>
      <path d="M44 22H66" stroke="#38bdf8" stroke-width="2" marker-end="url(#liCyanArrow)"/>
      <rect x="70" y="5" width="80" height="34" rx="6" fill="#171426" stroke="#a78bfa"/>
      <text x="110" y="19" fill="#c4b5fd" font-size="8.5" font-weight="700" text-anchor="middle">SPAD / APD</text>
      <text x="110" y="31" fill="#8b98a5" font-size="7.2" text-anchor="middle">single-photon detector</text>
      <text x="23" y="55" fill="#93c5fd" font-size="8" text-anchor="middle">receive lens</text>
    </g>

    <!-- Time-to-digital converter -->
    <g transform="translate(17 181)">
      <rect width="158" height="29" rx="6" fill="#10251f" stroke="#34d399"/>
      <path d="M11 18h13V8h10v10h13" fill="none" stroke="#6ee7b7" stroke-width="1.5"/>
      <text x="102" y="12" fill="#6ee7b7" font-size="8.2" font-weight="700" text-anchor="middle">TIME-TO-DIGITAL</text>
      <text x="102" y="23" fill="#8b98a5" font-size="7.2" text-anchor="middle">timestamp Δt</text>
    </g>
  </g>

  <!-- Outgoing scan fan -->
  <path d="M170 113L324 105" stroke="url(#liBeam)" stroke-width="2.5" marker-end="url(#liCyanArrow)"/>
  <path d="M170 113L451 162" stroke="url(#liBeam)" stroke-width="2.5" marker-end="url(#liCyanArrow)"/>
  <path d="M170 113L633 210" stroke="url(#liBeam)" stroke-width="2.5" marker-end="url(#liCyanArrow)"/>
  <path d="M170 113L694 112" stroke="#38bdf8" stroke-width="1" stroke-opacity=".25"/>
  <path d="M170 113L694 260" stroke="#38bdf8" stroke-width="1" stroke-opacity=".18"/>
  <text x="229" y="93" fill="#7dd3fc" font-size="8.5">emitted pulse t₀</text>

  <!-- Physical scene -->
  <g transform="translate(236 77)">
    <text x="247" y="0" fill="#e6edf3" font-size="10.5" font-weight="700" text-anchor="middle">SCANNED SCENE</text>
    <path d="M0 232H495" stroke="#3a4453" stroke-width="2"/>
    <path d="M0 233L495 233L470 265H24Z" fill="#111820"/>
    <g stroke="#28384a" stroke-dasharray="8 10">
      <path d="M26 248H469"/><path d="M150 232l-12 33M316 232l12 33"/>
    </g>

    <!-- Near retroreflective sign -->
    <g transform="translate(73 28)">
      <path d="M15 0v203" stroke="#64748b" stroke-width="5"/>
      <rect x="-13" y="0" width="57" height="48" rx="5" fill="#263548" stroke="#e6edf3" stroke-width="2"/>
      <path d="M15 8L34 39H-4Z" fill="#f87171" stroke="#fecaca"/>
      <text x="15" y="32" fill="#fff" font-size="16" font-weight="700" text-anchor="middle">!</text>
      <text x="15" y="218" fill="#8b98a5" font-size="8.5" text-anchor="middle">bright sign · 20 m</text>
    </g>

    <!-- Mid-range dark vehicle -->
    <g transform="translate(177 103)">
      <path d="M0 78l13-44q5-15 20-17l87-2q16 1 24 14l22 49Z" fill="#161a20" stroke="#64748b" stroke-width="2"/>
      <path d="M33 22h82q10 0 16 12l10 21H20l7-22q2-9 6-11Z" fill="#111827" stroke="#52647b"/>
      <circle cx="37" cy="79" r="17" fill="#0d1117" stroke="#64748b" stroke-width="4"/>
      <circle cx="137" cy="79" r="17" fill="#0d1117" stroke="#64748b" stroke-width="4"/>
      <circle cx="13" cy="68" r="5" fill="#f87171"/>
      <text x="83" y="105" fill="#8b98a5" font-size="8.5" text-anchor="middle">dark car · 50 m · weak return</text>
    </g>

    <!-- Far wall -->
    <g transform="translate(406 36)">
      <rect width="65" height="197" fill="#202b38" stroke="#52647b" stroke-width="2"/>
      <path d="M0 35h65M0 75h65M0 115h65M0 155h65M20 0v35M47 0v35M32 35v40M15 75v40M50 75v40M30 115v40M17 155v42M49 155v42" stroke="#35475c"/>
      <text x="32" y="216" fill="#8b98a5" font-size="8.5" text-anchor="middle">wall · 80 m</text>
    </g>
  </g>

  <!-- Return photons travel back along the same path -->
  <path d="M324 105L178 135" stroke="#34d399" stroke-width="2" stroke-dasharray="6 4" marker-end="url(#liGreenArrow)"/>
  <path d="M451 162L178 147" stroke="#34d399" stroke-width="1.7" stroke-opacity=".55" stroke-dasharray="6 4" marker-end="url(#liGreenArrow)"/>
  <path d="M633 210L178 158" stroke="#34d399" stroke-width="1.5" stroke-opacity=".36" stroke-dasharray="6 4" marker-end="url(#liGreenArrow)"/>
  <g fill="#34d399" filter="url(#liPhotonGlow)">
    <circle cx="288" cy="113" r="4"/><circle cx="390" cy="159" r="3"/><circle cx="554" cy="201" r="2.5"/>
  </g>
  <text x="264" y="143" fill="#6ee7b7" font-size="8.5">reflected photons</text>

  <!-- Measured points sit on the surfaces hit by rays -->
  <g fill="#38bdf8" stroke="#bae6fd" stroke-width=".7">
    <circle cx="309" cy="105" r="3"/><circle cx="324" cy="105" r="3"/><circle cx="339" cy="105" r="3"/>
    <circle cx="437" cy="158" r="3"/><circle cx="451" cy="162" r="3"/><circle cx="465" cy="166" r="3"/>
    <circle cx="620" cy="207" r="3"/><circle cx="633" cy="210" r="3"/><circle cx="646" cy="213" r="3"/>
  </g>

  <!-- Time-of-flight waveform connects each range to a delayed peak -->
  <g transform="translate(25 342)">
    <text x="355" y="-10" fill="#fbbf24" font-size="10.5" font-weight="700" text-anchor="middle">PHOTON ARRIVAL HISTOGRAM · EACH DELAY BECOMES A RANGE</text>
    <rect width="710" height="90" rx="11" fill="#15140f" stroke="#f59e0b" stroke-width="1.6"/>
    <path d="M36 68V14M36 68H684" stroke="#3a4453"/>
    <text x="13" y="20" fill="#8b98a5" font-size="8" transform="rotate(-90 13 20)">counts</text>
    <text x="676" y="82" fill="#8b98a5" font-size="8">time</text>

    <!-- Emission trigger -->
    <path d="M45 68h15V22h9v46h58" fill="none" stroke="#38bdf8" stroke-width="2.5"/>
    <text x="64" y="16" fill="#7dd3fc" font-size="8.5" text-anchor="middle">emit t₀</text>

    <!-- Returns: near/bright tall, dark/mid weak, far delayed -->
    <path d="M128 68h29l7-9 6-34 6 34 7 9h82" fill="none" stroke="#34d399" stroke-width="2.8"/>
    <path d="M265 68h73l7-5 6-14 6 14 7 5h104" fill="none" stroke="#34d399" stroke-width="2"/>
    <path d="M468 68h85l7-7 6-23 6 23 7 7h92" fill="none" stroke="#34d399" stroke-width="2.3"/>
    <g stroke="#52647b" stroke-dasharray="3 3">
      <path d="M170 25v43M351 49v19M566 38v30"/>
    </g>
    <g fill="#e6edf3" font-size="8.5" text-anchor="middle">
      <text x="170" y="82">Δt₁ = 133 ns → 20 m</text>
      <text x="351" y="42" fill="#fca5a5">weak dark return</text>
      <text x="351" y="82">Δt₂ = 333 ns → 50 m</text>
      <text x="566" y="82">Δt₃ = 533 ns → 80 m</text>
    </g>
    <g transform="translate(513 8)">
      <rect width="167" height="24" rx="12" fill="#10251f" stroke="#34d399"/>
      <text x="83.5" y="16" fill="#6ee7b7" font-size="11" font-weight="700" text-anchor="middle">d = cΔt / 2</text>
    </g>
  </g>

  <text x="380" y="458" fill="#6b7684" font-size="11" text-anchor="middle">Range accuracy depends on pulse width, timing jitter, photon statistics, reflectivity, atmosphere, and calibration.</text>
</svg>

Connection to CFS platform. Use the relevant CFS RF, optical, device, circuit, signal-processing, package, thermal, and system simulators with linked glossary topics to turn these concepts into quantified engineering decisions.