Understanding Radar, Sonar, and Lidar in Technical Writing

Radar, sonar, and lidar are the silent engines behind modern autonomy, yet technical writers often reduce them to interchangeable acronyms. Precision demands we treat each as a distinct physics story with its own vocabulary, failure modes, and documentation rituals.

Mastering these stories lets writers turn raw spec sheets into safety-critical manuals that pilots, drivers, and surveyors trust with their lives. The payoff is documentation that survives audits, lawsuits, and midnight field repairs.

Electromagnetic vs. Acoustic vs. Light: Choosing the Right Lexicon

Radar paragraphs should pulse with radio verbs—reflect, scatter, attenuate—because microwaves care about dielectric constants, not color. Sonar sentences must sound wet: absorption spikes in warm thermoclines, multipath flares off hulls, bottom bounce smears the ping. Lidar prose needs optical clarity—photons diverge, Rayleigh scatters, aerosols depolarize—so writers mirror the beam’s own coherence.

Swap one verb family for another and the reader’s mental model collapses; a “lidar echo” is as jarring as a “sonar pixel.” Maintain domain fidelity by tagging every quantity with its native unit—dBsm for radar cross-section, dB re 1 µPa for sonar pressure, photons m⁻² sr⁻¹ for lidar return.

Frequency Bands and Wavelength Branding

X-band radar lives at 8.2–12.4 GHz, a range so specific that writing “X-band” without the numbers triggers avionics reviewers. Sonar splits cleanly—below 1 kHz is low-frequency for basin-scale sensing, above 10 kHz is imaging class for mine disposal. Lidar wavelengths are branded by chemistry: 905 nm silicon photodiodes cost dollars, 1550 nm InGaAs costs tens, and eye-safety margins flip between them.

Resolution Recipes: Crafting Sentences That Sharpen Beams

Radar range resolution equals cτ/2; compress that equation into a parenthetical (0.15 m per nanosecond of chirp) so installers instantly know 500 MHz buys 0.3 m. Sonar writers replace τ with pulse-length in meters, because sound travels 1500 m s⁻¹ in seawater; a 10 ms pulse is a 15 m smear that hides submarines. Lidar writers quote point spacing at 100 m, not angle—0.1 mrad equals 1 cm at that distance, a conversion field crews do in hard-hat math.

Bandwidth as Character Development

Give bandwidth a personality: narrowband is the cautious librarian who misses details, wideband is the speed-reader who sees every rivet. In radar, 500 MHz slant-range bandwidth paints a 0.3 m portrait; in sonar, 10 kHz bandwidth resolves 7.5 cm when the sound speed is 1500 m s⁻¹. Lidar’s gigahertz-plus modulation can profile asphalt grain, but only if the writer states the modulation order—binary PPM versus 16-QAM changes the point cloud density by 4×.

Noise Narratives: Turning Jargon into jeopardy

Thermal noise floors differ by physics: −174 dBm Hz⁻¹ for radar receivers, sea-state-zero knocks sonar to 40 dB re 1 µPa² Hz⁻¹, lidar fights 30 photons pixel⁻¹ ms⁻¹ of solar background. Translate each into a scenario: a 20 kt headwind raises radar noise 3 dB, a passing supertanker injects 20 dB of broadband sonar hiss, high noon desert sun can drown lidar at 50 m. Writers who embed these scenes let safety reviewers feel the stakes rather than skim a table.

Clutter Signatures as Plot Twists

Radar sea clutter follows a Weibull shape with a shape parameter below 2; say “spiky” once and move on—engineers already visualize the tail. Sonar bottom backscatter obeys Lambert’s law at 30° grazing, but writers must warn that mud volcanoes create 10 dB spikes that mimic mines. Lidar vegetation clutter is double-Gaussian: leaf bounce arrives early, trunk late; label them “canopy” and “ground” returns so SLAM algorithms know which to discard.

Platform Kinematics: Documenting Motion Blur in Three Languages

Radar Doppler is a signed integer—positive for closing targets, negative for receding—so air-traffic manuals color code blue and red without legend. Sonar Doppler shifts only 0.7 Hz per knot at 3 kHz, demanding millihertz precision in torpedo approach tables. Lidar line-of-sight velocity is inferred from consecutive pulses; write the Nyquist limit as v_max = λ/(4T) so roboticists see 10 m s⁻¹ is impossible with a 100 ns pulse interval.

Scan Patterns as Choreography Notes

Radar rotates at 24 rpm, painting a 360° slash every 2.5 s; note the update latency in the margin so drone pilots know why the map lags. Sonar prefers a 120° sector stepped at 1° increments; writers append “step-stare” to distinguish it from continuous towed-array streams. Lidar scan heads oscillate at 10–30 Hz; quote the line period (33 ms at 30 Hz) so SLAM engineers timestamp points against IMU drift.

Eye & Ear Safety: Liability Paragraphs That Save Companies

Radar peak power of 25 kW is harmless outside the near-field, but writers must still fence the 3 m exclusion zone with a hard-hat icon. Sonar above 180 dB re 1 µPa at 1 m ruptures human lung tissue; embed the 10 m diver-exclusion circle in the startup checklist, not the appendix. Lidar 1550 nm is retina-safe to 10 mW, yet 905 nm needs <0.5 mW; state the AEL class in the first line of the operator card so procurement lawyers see compliance at a glance.

Interlock Narratives

Marine radar triggers a “radiation hazard” relay when tilt drops below 5° above deck; describe the relay as a fail-closed contact so techs wire it into the engine-cut circuit. Sonar systems output a “ping active” TTL line; instruct ROV pilots to illuminate a red strobe whenever the line is high. Lidar enclosures demand a 945 nm interlock sensor; if the cover is ajar, the sensor must pull a fault pin to 0 V within 1 ms—spell the timing so firmware teams code the right debounce.

Data Formats: Structuring Clouds, Pings, and Echoes

Radar ASTERIX CAT-048 packs plots into 64-byte vectors; document the UAP (Unit, Address, Period) triplet so integrators know why byte 5 shifts between vendors. Sonar formats split—raw acoustic time series in .wcd, contact lists in .son, bathymetry in .gsf; provide a one-liner decoder for each so researchers don’t write three parsers. Lidar LAS 1.4 adds WKT CRS strings; warn that ignoring byte offset 375 drops the entire point cloud into null island.

Compression Trade-offs

Radar range-Doppler matrices compress 10:1 with FFT-wrapped zlib, but writers must note that phase is lost—crucial for SAR interferometry. Sonar spectrograms tolerate 24 kbit s⁻1 MP3 because human listeners, not algorithms, audit them. Lidar uses LASzip for 5:1 lossless; mention that vertical coordinate quantization to picometers still rounds z=123.456789012 m to 123.456789012 m, preserving survey-grade precision.

Calibration Ceremonies: Turning Specs into Trust

Radar corner reflector RCS is 4πa²/λ² for a trihedral of edge a; give a worked example—15 cm edge at 9.6 GHz yields 20 dBsm—so technicians pick the right target. Sonar calibration spheres use tungsten carbide for 94 % reflectivity; state the 0.01 dB tolerance so crews know a scratch invalidates the run. Lidar planar targets need 50 % Lambertian reflectance at 905 nm; specify Spectralon, not white paint, because gloss skews the return by 30 %.

Temperature Drift Stories

Radar LO shift is 1 kHz °C⁻¹ at 10 GHz; document the oven setpoint so airport techs retune before the morning shift. Sonar sound speed climbs 3 m s⁻¹ per °C between 10–20 °C; embed the linear correction in the logging script so surveyors don’t mis-map a 2 m shoal. Lidar time-of-flight ICs drift 20 ps °C⁻¹; remind writers that 20 ps equals 3 mm range error, enough to breach ISO 17123-9 tolerance.

Regulatory Dossiers: Mapping Standards to Sentences

RTCA DO-292A demands radar probability of detection ≥0.9 at 5.6 dB SNR; reproduce the curve in the manual so certification engineers overlay their test data. IEC 61108-4 sets sonar accuracy at ±1 m or 0.5 % of depth; phrase the requirement verbatim so ship captains know when to distrust the display. ASPRS Positional Accuracy Standards 2014 class lidar as 10 cm RMSEz for QL1; cite the clause in the metadata so county assessors accept the survey.

Traceability Tables

Each requirement needs a one-row trace: ID, text, test method, pass/fail, signature. Radar row example—REQ-42, “Detect 1 m² RCS at 3 NM,” test method “MIL-STD-810G 522.3,” result “PASS – 3.2 NM,” signed by test conductor STA-004. Sonar rows append water temperature and salinity columns; lidar rows add flight altitude and scan angle so any auditor can replay the exact geometry.

User-Error Forensics: Writing Defensive Procedures

Radar operators forget to disable MTI when taxing; insert a bold note “Set GROUND MODE before throttle advance” at the top of the pre-taxi checklist. Sonar captains mis-set salinity to 35 ppt in brackish 8 ppt estuaries; code the logger to flash red when sound speed differs 10 m s⁻¹ from seasonal norm. Lidar drone pilots fly at 120 m agl instead of 80 m; cap the flight-plan importer so software rejects heights above the ASPRS QL0 limit.

Diagnostic Flowcharts

Start each chart with a symptom in plain English—“No targets below 500 m”—then branch to radar STC curve, sonar absorption coefficient, lidar range gate offset. End every branch with a measurable action: replace the STC resistor, enter the salinity probe offset, shift the range gate 2 m. Keep boxes narrow; one inspection question per box prevents cognitive overload inside a vibrating cockpit.

Maintenance Prose: Turning MTBF into Mindshare

Radar magnetron MTBF is 5 000 h; translate to “Replace every 18 months on a 24/7 ferry” so procurement schedules the part before the season. Sonar transducer urethane windows erode 0.1 mm per 1 000 h in sandy water; state the wall-thickness gauge interval so deckhands don’t wait for catastrophic delamination. Lidar laser diode lifetimes double every 20 °C drop; recommend a heat-sink swap at 40 °C ambient so survey companies budget before the desert summer.

Fault Code Glossaries

Radar error 0x0B means “waveguide VSWR >2.5”; expand the hex code to “Check flange for bird nest.” Sonar code 0x47 is “transmit current over-limit”; add “Inspect transducer for seaweed.” Lidar code 0x92 flags “APD bias drift”; follow with “Verify thermistor 3.3 V ±0.05 V.” Glossaries belong on the inside front cover—techs refuse to scroll PDFs while hanging from a harness.

Future-Proofing: Embedding Extensibility Hooks

Reserve a paragraph for software-defined radar that will swap magnetrons for solid-state arrays; note the forthcoming 200 MHz chirp so mechanical drawings leave IF bandwidth headroom. Warn sonar readers that low-frequency MIMO will replace single-hull transducers; spec the mounting rail now to avoid dry-dock later. Tell lidar customers that FMCW engines will displace time-of-flight; leave 50 mm extra depth in the fairing so the new optics fit without redesign.

Technical writing that treats radar, sonar, and lidar as interchangeable acronyms is a liability waiting to crystallize in court. Anchor every spec to its native physics, give every number a story, and your documents will outlast the hardware they describe.