123 Main Street, New York, NY 10001

PIR Motion Detector Hardware: Low-Noise AFE, AGC & Low-Power MCU

← Back to: Security & Surveillance

A robust PIR motion detector is won by evidence-based engineering: optics/installation, low-noise AFE bandpass, and temperature-aware thresholds must work together so the sensor stays sensitive without drifting into false alarms. This page shows what to measure first (baseline slope, dT/dt, pulse patterns, rail dips) and the fastest fixes to isolate drift, scene modulation, power injection, and contamination in the field.

H2-1. Definition & Boundary

What this page covers

One-sentence definition

A PIR motion detector is a passive infrared change detector: Fresnel optics segment the field of view into zones, a dual-element pyroelectric sensor converts spatial IR changes caused by motion into a tiny bipolar AC signal, and a low-noise AFE plus low-power MCU pipeline turns that signal into a robust wired/wireless alarm event.

Typical applications (hardware viewpoint)

  • Indoor room: wide FOV, false-alarm control vs HVAC and sunlight reflections.
  • Corridor / hallway: zone geometry drives direction sensitivity and reduces cross-traffic triggers.
  • Stair / entry: large temperature gradients; requires stronger drift rejection and arming rules.

Deliverables of this page

  • A measurable signal chain (optics → sensor → AFE → MCU → I/O/power) and where each failure shows up.
  • False-alarm vs miss evidence (waveform shape, band energy, temperature rate, event statistics).
  • Low-power wake pipeline (sleep → arm → sample → decide → report → sleep) with practical tradeoffs.
Scope Guard

In scope (Allowed)

  • PIR optics/zones, dual-element sensor coupling, low-noise AFE, BPF/AGC/temp compensation.
  • MCU duty-cycle detection, thresholds/debounce, I/O wiring level, module-level wireless interface and power gating.
  • Port-level protection (ESD/EFT/surge), validation plan, field debug evidence.

Out of scope (Banned)

  • Camera/NVR/VMS/video analytics, radar TRx design details, fiber perimeter sensing.
  • PoE switch design, PTP timing architecture, access controller/reader internals.
  • Crypto/secure boot deep dive, protocol-stack tutorials, cloud platform architecture.

Boundary rule: if a paragraph needs protocol deep-dive, platform architecture, video pipeline, or radar TRx theory to stand, it does not belong on this PIR page.

Figure F1 — PIR detector system block (navigation map)

PIR Motion Detector — Hardware Signal Chain Optics Fresnel zones PIR Sensor Dual element Low-noise AFE BPF • AGC • Temp comp Gain / Filter AGC Temp adjust MCU Sleep / wake pipeline I/O Wired / Wireless Power & Protection Battery/regulator • Brownout guard • Port ESD/EFT Sun / reflections HVAC airflow Supply noise
F1 is the navigation map for the whole page: each later chapter should map back to one block (optics, sensor coupling, AFE, MCU pipeline, I/O, power).
Cite this figure: ICNavigator · PIR Motion Detector · Figure F1 (System Block Diagram)

H2-2. Detection Physics in Engineering Terms

Engineering meaning of “motion”

What the sensor actually measures

PIR does not measure absolute body temperature. It measures change: as a warm object moves across the segmented field of view, the infrared energy entering the sensor shifts from one zone to the next. This creates a bipolar (positive/negative) AC signature at the sensor output, typically concentrated at low frequencies where slow drift and fast vibration must be rejected by design.

Why Fresnel zoning creates a bipolar waveform

  • Fresnel optics (or an aperture mask) splits the scene into multiple zones.
  • Crossing zone boundaries converts spatial movement into alternating increases/decreases of incident IR energy.
  • The result is a small bipolar pulse train rather than a DC level, which is why band-pass shaping is fundamental.

Why dual-element (differential) sensing matters

A dual-element pyroelectric sensor effectively behaves like a differential pickup: slow common changes (room warming, gradual sunlight heating) appear similarly on both elements and are largely canceled, while a moving target produces a time-shifted response between elements and survives the subtraction. This is the first layer of false-alarm defense, before any MCU logic exists.

Main disturbance classes (and what they look like)

  • Slow thermal drift: baseline wander; energy piles up near very low frequency; often correlates with temperature slope.
  • Sunlight / reflections: large slow steps or long pulses when a bright spot sweeps; repeats with time-of-day patterns.
  • Airflow / HVAC: low-frequency “rolling” variations; correlates with vents, fans, or heating cycles.
  • Vibration / shock: higher-frequency bursts; correlates with door slam, enclosure vibration, or loose mounting.

Evidence checklist (what to measure first)

  • AFE output waveform: bipolar pulse shape vs drift/step signatures.
  • Band energy proxy: compare low-frequency drift vs motion band (filter output RMS in window).
  • Temperature and its rate-of-change: rising drift-trigger coincidence is a strong discriminator.
  • Event statistics: clustering by time-of-day or HVAC cycle points to optical/environment causes.

Figure F2 — Signal signatures: motion vs drift vs vibration

Motion Signature — What to Expect on the Waveform Raw PIR differential AFE band-pass output MCU event after threshold Drift Vibration Bipolar pulses Drift removed Event pulses
F2 shows what “motion” looks like in practice: raw differential contains drift + motion; band-pass emphasizes motion; MCU logic reduces it to events.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F2 (Signal Signatures: Motion vs Drift vs Vibration)

H2-3. Optics & Mechanics

Why false alarms often start here

Optics and mounting do not “boost” PIR; they encode space into time. Fresnel zoning converts motion into a bipolar pulse pattern, and the same encoding can accidentally convert sun reflections, HVAC thermal plumes, or moving shadows into motion-like pulses. A stable detection system therefore starts by constraining what enters the field of view.

Practical rule: if the field of view includes a heat source, reflective glass, or strong airflow path, threshold tuning becomes a band-aid. Optics + installation must remove the trigger at the source.

Fresnel lens selection (FOV, zones, range)

  • FOV (horizontal/vertical): wider FOV increases coverage but also increases the chance of capturing sunlight, reflections, or warm equipment surfaces.
  • Zones / segmentation density: more zones produce clearer alternating pulses for true motion, but can also make slow environmental changes look “pulsed” when they move across zones.
  • Range: longer range reduces angular speed at the sensor, pushing the motion signature toward lower frequencies where drift rejection becomes critical.
  • Vertical curtain vs wide: curtain optics constrain the scene (doorway/corridor) and naturally reduce cross-traffic and window reflections; wide optics require stronger environmental control and drift handling.

Pet immunity (optics + mounting constraint)

  • Pet immunity is primarily achieved by limiting low-height zones and preventing near-floor thermal changes from producing strong alternating pulses.
  • Mount height and downward tilt shift zone intersections; the goal is to keep “small moving warm objects” from repeatedly crossing multiple zones.

Window / filter stack (8–14 μm pass, visible/sunlight blocking)

  • IR passband targets room-temperature emissions; the window should avoid leaking visible/near-IR that can create large offsets or long pulses under sunlight.
  • Sunlight robustness often depends on the window + internal baffle preventing a moving hot spot from sweeping across zones.
  • Condensation / contamination changes transmission and creates apparent motion when airflows move temperature gradients across the window surface.

Evidence patterns that point to optics/window (fast discrimination)

  • Time-of-day clustering (morning/evening spikes) → strong hint of sun angle/reflections.
  • HVAC-cycle correlation (trigger bursts align with fan/heater state) → thermal plume in FOV.
  • Single-location only (one install site fails, others pass) → mounting geometry/scene content, not AFE gain.

Mechanical & environment checklist (installation constraints)

  • Avoid reflective glass in the center of FOV (windows, glossy floors, mirrors) where reflections move with sun or people.
  • Avoid direct view of heaters, radiator pipes, warm appliances, or sunlit walls that drift quickly.
  • Avoid HVAC outlets that blow warm/cool air across the FOV or directly onto the detector window.
  • Keep stable mounting: vibration or loose brackets turn mechanical shocks into high-frequency bursts that can trip thresholds.
First measurement for site issues: log event timestamps vs sunlight/HVAC cycles, and capture AFE waveform around triggers. If waveform energy grows during HVAC transitions or sun angle changes, installation constraints must be corrected first.

Figure F3 — FOV zoning & installation do’s/don’ts

Optics & Installation — Zone Geometry Drives False Alarms Field of View (zones) PIR Wide vs Curtain Zones / Range Mount height Avoid in FOV Sun reflections HVAC airflow Direct heat
F3 highlights how Fresnel zoning converts scene content into pulses; controlling the field of view and mounting constraints is the fastest path to lower false alarms.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F3 (FOV Zones & Installation Constraints)

H2-4. PIR Sensor & Front-End Coupling

Win the noise budget first

The pyroelectric element behaves like a very high-impedance charge source. Useful motion energy is tiny and low-frequency, so input leakage, bias current, and parasitic capacitance can reduce sensitivity or create long settling that looks like motion. This chapter treats the sensor + PCB + AFE input as one coupled system.

Diagnostic priority: before changing thresholds or MCU logic, verify that input leakage and bias are under control. Otherwise, drift and noise dominate the decision stage.

Equivalent model (charge source + capacitance + leakage)

  • Charge source (Q): motion across zones produces a small differential charge variation.
  • Sensor capacitance (Cs): sets the relationship between charge and voltage at the node.
  • Leakage path (Rleak): includes sensor leakage, PCB surface leakage, humidity films, and contamination residues.

What each non-ideal produces (symptom mapping)

  • Higher leakage (lower Rleak) → reduced low-frequency gain, baseline wander, “washed-out” motion pulses.
  • Higher input bias current → offset drift, longer recovery after transients, threshold instability.
  • Extra input capacitance (layout/ESD/clamps) → slower response, altered band-pass corner behavior.

PCB contamination & humidity (common hidden cause)

  • Flux residue + humidity can create a weak conductive film, collapsing the effective Rleak and increasing low-frequency noise.
  • Fingerprints / dust near the high-impedance node are enough to shift drift and settling behavior.
  • Conformal coating can stabilize leakage if applied with correct keep-outs and compatible materials.

Evidence chain (what to capture)

  • AFE output: baseline drift slope, noise RMS, and motion pulse amplitude distribution.
  • Trigger timing: correlation with humidity events, condensation, or cleaning/rework history.
  • Repro check: same unit behaves differently in a dry vs humid environment → leakage dominates.

Protection & clamp side effects (noise + recovery time)

  • ESD clamping provides a discharge path, but adds parasitic capacitance and potentially leakage at the sensor node.
  • Input clamps can create a “recovery window” after an ESD/EFT event where the AFE output slowly returns, causing false triggers.
  • Layout rule: keep the high-impedance node short and guarded; place protection so it does not load the sensor node directly unless required.
Field clue: if false alarms cluster after storms, cable handling, or ESD events, measure recovery time at the AFE output and inspect clamp loading/leakage.

Figure F4 — Sensor equivalent model & AFE input constraints

Sensor Coupling — Leakage & Bias Decide SNR PIR equivalent model Q Charge source Cs Rleak Leakage rises with humidity / contamination Low-noise AFE input + High impedance node Bias current Input leakage Parasitic C load Protection ESD clamp Clamp C Too much load → long recovery
F4 emphasizes the real enemy in PIR front-ends: leakage and bias can dominate the tiny motion signal; protection must not overload the high-impedance node.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F4 (Sensor Model & AFE Input Constraints)

H2-5. Low-Noise AFE Architecture

Architecture drives noise, drift, and recovery

A PIR front-end is not a “high gain amplifier”; it is a drift-controlled, band-limited charge-to-voltage system. The chosen topology decides whether low-frequency drift is rejected early, whether 1/f noise dominates the motion band, and whether startup or ESD recovery produces false triggers.

Selection principle: prioritize leakage/bias control and recovery behavior before optimizing gain. A stable baseline produces predictable thresholds.

Common AFE topologies (when to use, what it costs)

  • Charge amplifier: strong match to high-impedance charge sources; drift rejection can be defined by the feedback network. Cost: leakage sensitivity and recovery time are set by the same RC.
  • “TIA-style” current/charge conversion: gain is explicit and easy to budget. Cost: input bias and board leakage can collapse low-frequency response if not controlled.
  • AC-coupled multi-stage band-pass: removes slow drift early and emphasizes motion energy in a narrow band. Cost: an overly aggressive high-pass can miss slow motion across zones.

Key metrics that map to field symptoms

  • Input noise density & 1/f corner: dominates the motion band when drift is large; causes “phantom motion” in quiet scenes.
  • Input bias current / leakage: creates baseline wander and long settling; gets worse with humidity and contamination.
  • CMRR / PSRR: determines sensitivity to supply ripple and digital activity; poor PSRR turns load steps into pulses.
  • Startup / overload recovery: defines the false-trigger window after power-up, ESD, or large transients.

Band-pass filtering (drift vs vibration/EMI)

  • High-pass (HPF) suppresses slow thermal drift and sunlight-induced offsets. Trade-off: too high a corner frequency reduces sensitivity to slow motion.
  • Low-pass (LPF) suppresses vibration, relay shock, and coupled switching noise. Trade-off: too low a corner frequency blunts motion pulses and increases threshold uncertainty.
  • Design goal: maximize motion-band energy while pushing drift and fast interference out of band.
Verification shortcut: compare band-limited RMS in the motion band vs baseline slope under temperature and humidity changes. If baseline slope dominates, fix leakage/bias before adjusting thresholds.

Startup & recovery (the hidden false-alarm source)

  • Power-up: input node charging and feedback settling can create a burst of pseudo-pulses if the decision stage is enabled too early.
  • ESD/EFT events: protection loading can cause long-tail recovery; the tail may cross thresholds multiple times.
  • Measurement: record the time-to-stable baseline and event counts in the first minutes after power-up or stress.
Practical mitigation: enforce a recovery gate (warm-up timer) and log recovery time; if recovery time drifts with humidity, suspect node leakage or clamp loading.

Figure F5 — AFE functional blocks (from sensor to decision)

Low-Noise AFE — From Sensor Node to Decision PIR Sensor Node Guard Leakage Protection ESD/Clamp Input Stage Charge / TIA Gain Noise budget BPF HPF + LPF AGC / Temp Gain/Threshold Comparator / ADC Decision input MCU Decision Window Threshold / Timing Evidence / Logging RMS / Drift / Events Wired / Wireless I/O Relay / RF Risk points: leakage • PSRR pulses • recovery tail Goal: stable baseline → predictable threshold → lower false alarms
F5 turns the PIR analog chain into testable blocks. Each block has a measurable failure signature (drift, noise, PSRR pulses, recovery tail).
Cite this figure: ICNavigator · PIR Motion Detector · Figure F5 (Low-Noise AFE Block Diagram)

H2-6. AGC & Temperature Compensation

Reduce thermal drift without killing sensitivity

Temperature changes affect PIR detection through two paths: (1) the sensor/AFE path (leakage, bias, 1/f noise, settling), and (2) the scene path (sun-heated surfaces, HVAC plumes, moving reflections). Compensation must separate these causes: electronic compensation cannot fix an optical scene problem.

Boundary reminder: if triggers correlate with sunlight angle or HVAC cycles, correct FOV and installation constraints first (H2-3), then fine-tune AGC/threshold behavior.

AGC strategies (selection logic)

  • Fixed gain + temperature threshold table: predictable and easy to validate; may underperform at extremes if noise rises.
  • Segmented gain steps: keeps motion pulses in a stable range across temperature; requires hysteresis to avoid gain hunting.
  • Adaptive threshold (noise-aware): tracks baseline noise and drift; must clamp min/max thresholds to avoid missing real motion.

Temperature inputs and what they control

  • NTC near PIR/AFE or on-die temperature to index a compensation table.
  • Outputs: threshold vs temperature, (optional) gain index vs temperature, (optional) HPF corner vs temperature.
  • Add hysteresis on both temperature and gain index to prevent oscillation near boundaries.

Engineering workflow (measurable, traceable)

  • Step 1 — Capture: temperature sweep; collect baseline slope, motion-band RMS, and event counts.
  • Step 2 — Segment: define cold/nominal/hot regions; assign gain/threshold targets for each segment.
  • Step 3 — Clamp: enforce min/max threshold and gain limits; prevent over-adaptation.
  • Step 4 — Hysteresis: avoid boundary hunting; require persistence before switching.
  • Step 5 — Log: record temperature, gain index, threshold value, and trigger rate for field traceability.
  • Step 6 — Version: store table version + CRC; enable rollback and audit in production.

Evidence chain (what to log in field)

  • T (temperature) and dT/dt (rate of change)
  • gain_index (or gain_dB) and thr_value (threshold) with clamp limits
  • band_rms (motion-band RMS) and baseline_slope (drift indicator)
  • event_count and event_rate histogram per temperature segment
If event rate rises with temperature but band_rms stays flat while baseline_slope increases, leakage/bias drift dominates. If event rate rises with sunlight/HVAC while temperature is stable, the scene path dominates.

Figure F6 — Segmented threshold & gain vs temperature (with hysteresis)

Temp Compensation — Segments, Hysteresis, and Clamps Temperature Threshold Gain index Cold Nominal Hot Hys Hys Threshold Clamp max Clamp min Gain Segmented Hysteresis Clamp
F6 shows a stable implementation pattern: segmented behavior across temperature, hysteresis at boundaries, and clamp limits to prevent runaway adaptation.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F6 (Temperature vs Threshold/Gain)

H2-7. MCU Low-Power Detection Pipeline

Sleep-first design without missed motion

A practical PIR detector uses a wake-on-event pipeline: an analog threshold (or window comparator) wakes the MCU, the MCU performs a short sampling window, makes a decision, then returns to sleep. This structure reduces average current without sacrificing detection reliability in real rooms.

Core pattern: AFE = coarse gate, MCU = short verification. Avoid continuous ADC sampling unless battery life is irrelevant.

Typical pipeline (event → verify → sleep)

  • Interrupt wake: band-limited AFE output crosses a threshold and triggers an IRQ.
  • Short sampling: MCU samples ADC (or counts comparator edges) during a bounded window.
  • Decision: accept only motion-like signatures (pulse count/spacing/energy) and reject slow drift.
  • Re-arm: apply a brief inhibit period to avoid bursty re-triggers during recovery or vibration.

Duty cycling knobs (what each one trades off)

  • Ton (sampling window): longer improves capture of pulse shape; shorter saves energy but risks partial evidence.
  • Toff (blanking/off time): longer saves energy; too long increases miss probability when motion falls into the gap.
  • Twake (wake latency): must be below the motion-feature time scale; excessive latency truncates the leading pulse.
  • Re-arm / inhibit: reduces false bursts; too aggressive can mask back-to-back passes in corridors.
A stable design logs Ton/Toff/Twake-related counters in field builds. “Low power” is validated by measured active time, not by configuration intent.

Low-power reliability essentials

  • IQ budget: track sleep current of AFE + MCU + wake circuitry; leakage dominates in humid/dirty environments.
  • Clocking: use RTC/low-frequency clock for stable windows; avoid drift that changes effective Ton/Toff.
  • Brownout behavior: choose BOD thresholds aligned with battery ESR and cold-start droop; prevent “half-awake” decisions.
  • Wake sources: whitelist only necessary sources; noisy GPIO wake-ups can destroy battery life via spurious wake storms.

Field evidence pack (minimum logs)

  • wake_count and wake_reason histogram (who woke the MCU)
  • active_time_ms accumulator (true duty cycle)
  • reset_count and brownout_count (power integrity)
  • band_rms, baseline_slope, pulse_count summary per sampling window
  • alarm_count vs temperature and battery voltage segments
Diagnosis shortcut: if wake_count rises but alarm_count stays flat, the system is burning power on false wakes; if alarm_count drops with low battery, brownout gating or wake latency is the dominant risk.

Figure F7 — Low-power state machine

MCU Low-Power Pipeline — State Machine Ton Toff Twake SLEEP RTC on / AFE armed ARM Gate / inhibit end SAMPLE ADC / edge count DECIDE Pulse / energy check ALARM Output / report RESET Re-arm / settle Wake IRQ Arm ready Window end Pass Fail Re-arm inhibit Return
F7 captures the minimal, repeatable structure: wake on analog evidence, sample briefly, decide, then enforce a controlled re-arm window before returning to sleep.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F7 (Low-Power State Machine)

H2-8. Wired/Wireless I/O & Power Tree

Module-level interfaces only

This section covers hardware-level interfaces for wired outputs, tamper inputs, indicators, and optional wireless modules. The boundary stays at pins, rails, protection, and wake lines—no protocol-stack deep dives.

Integration rule: treat AFE as an analog island. Keep high di/dt loads (relay, RF bursts, LEDs) from injecting ground bounce into the AFE band.

Wired I/O blocks (alarm, tamper, indicators)

  • Alarm output: open-collector/open-drain preferred for system voltage flexibility; add pull-up and edge control to reduce EMI.
  • Relay / high-side driver (optional): include flyback path and current-step containment; log relay events to correlate with false triggers.
  • Tamper switch: debounce + ESD protection; long leads require robust clamping and defined biasing.
  • LED/buzzer: limit peak current; isolate load steps from AFE rail to prevent pseudo-pulses.

Wireless module interface (UART/SPI + wake + power gating)

  • Data bus: UART or SPI for module-level transport; keep lines short and protected at the connector edge.
  • Wake/IRQ lines: explicit WAKE_IN/WAKE_OUT to avoid keeping the MCU active during RF activity.
  • Power gating: load switch or controlled LDO enables the RF rail only when needed; prevents idle leakage and wake storms.
  • RF pulse coupling: protect against burst-current droop and ground bounce by rail separation and local decoupling.

Power tree (rails, inrush, and brownout)

  • Battery/DC input → regulation → separated rails: AFE, MCU, RF/IO.
  • Inrush and load steps: prevent rail dips from masquerading as motion pulses; validate with brownout counters and scope captures.
  • Brownout thresholds: align to battery ESR and cold behavior; avoid unstable operation in the “almost alive” region.

Port-layer protection (no stack discussion)

  • ESD/EFT/surge entry is handled at the port boundary: TVS, RC, common-mode choke, and isolation as needed.
  • Evidence: log reset/brownout and port fault flags; measure recovery time after stress.
If false alarms correlate with RF transmissions, relay switching, or LED bursts, treat it as a power/ground injection issue first—then revisit thresholds.

Figure F8 — Power tree and I/O protection blocks

Power Tree & I/O Protection — Module Integration View Battery / DC Inrush control Regulators LDO / DC-DC Sequencing AFE Rail MCU Rail RF / IO Rail Wired Ports OC OUT • Relay • Tamper LED/Buzzer TVS RC Wireless Module (Optional) UART / SPI • WAKE • IRQ • RESET Power gating ISO CM Port protection stays at the edge: TVS / RC / CM choke / isolation. Separate rails reduce ground injection into the AFE band.
F8 keeps the scope at module integration level: separated rails, explicit wake lines, and protection at the port boundary to prevent transients from turning into motion events.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F8 (Power Tree & I/O Protection)

H2-9. Anti-False-Alarm Engineering

Scene → Evidence → Discriminator → First Fix

False alarms become tractable when every event is forced into a repeatable attribution workflow. Each scenario below is written with the same structure: what happens, what to measure, how to distinguish, and the first fix that stays inside the PIR module boundary.

Discipline: do not “fix” by only raising the threshold. First identify whether the dominant cause is optics/scene, thermal drift, power injection, or mechanical disturbance.

Sun sweep / reflection

Scene: sunlight sweeps across the window or reflects from floors/walls, slowly changing the IR field inside the FOV.

Evidence: elevated baseline_slope, strong very-low-frequency energy, long event duration, correlation with time-of-day and window direction.

Discriminator: if the waveform is dominated by slow drift and lacks repeated alternating pulses across zones, it is primarily scene drift rather than human motion.

First fix: adjust zoning/遮蔽 the sun direction, tune HPF corner slightly higher, require a short second-confirm window that expects alternating pulses, and tighten thresholds when dT/dt is high.

Headlight sweep / strong transient light

Scene: car headlights sweep through an entryway or corridor-facing sensor.

Evidence: short, high-amplitude spikes with fast recovery; strong repeatability for the same direction/time; weak multi-pulse “zone walk” signature.

Discriminator: a single sharp pulse without a short sequence of zone-crossing alternations indicates optical transient rather than motion.

First fix: reduce exposure to the driveway direction using optics/shrouds, apply pulse-count requirements (minimum N pulses), and use time-gated confirmation instead of globally raising gain/threshold.

Warm airflow / HVAC

Scene: warm or cold airflow moves across the sensor, causing thermal gradients and slow IR field shifts.

Evidence: strong correlation with fan cycles; elevated dT/dt; low-frequency dominant energy; repeated events with consistent period.

Discriminator: if triggers align with fan timing and show slow-drift signatures, the dominant cause is thermal flow rather than a person crossing zones.

First fix: prioritize installation changes (avoid vents and direct heat paths), increase drift rejection with HPF, and tighten thresholds dynamically when dT/dt rises.

Curtain / plant motion in the FOV

Scene: curtains or plants move due to wind or HVAC, modulating the IR pattern.

Evidence: periodic triggers matching the motion frequency; lower amplitude but long persistence; correlation with wind or airflow conditions.

Discriminator: strong periodicity with small-amplitude repeats suggests scene modulation instead of multi-zone traversal.

First fix: reduce zoning density toward that region, apply minimum motion-energy criteria, and add rate limiting for repeated periodic triggers to prevent alarm storms.

Pet immunity (low-height movers)

Scene: pets move within lower zones and near-floor paths, often close to the sensor.

Evidence: triggers cluster by low-height trajectories; shorter bursts; patterns that over-weight lower zones; frequent near-field events.

Discriminator: if events localize to the lower region and lack strong multi-zone alternations at human height, treat it as optics zoning rather than threshold tuning.

First fix: use pet-immune zoning (suppress lower zones), require stronger multi-zone consistency for alarms, and keep temperature compensation focused on drift—not on masking pets.

Insects / near-lens disturbances

Scene: insects crawl on or near the lens, creating localized IR modulation with abnormal proximity effects.

Evidence: unusually frequent triggers; near-field signatures; distorted waveforms that do not match zone-walk sequences; time-of-night clustering.

Discriminator: high repetition without zone-crossing alternation indicates near-field interference rather than room motion.

First fix: add mechanical barriers (mesh/shields), enforce “alternation” criteria in a second-confirm window, and rate-limit repetitive events with logging for maintenance actions.

Cross-class checks: power injection and mechanical disturbance

  • Power injection: triggers correlate with RF TX bursts, relay switching, LED current steps, or brownout counters. First fix is rail separation, local decoupling, edge control, and wake-source filtering.
  • Mechanical disturbance: vibration changes the FOV or mounting alignment. Evidence includes vibration correlation and repeatable patterns during door slams; first fix is mounting stiffness and isolation.
A fast field discriminator: if wake_count spikes during unrelated electrical activity, suspect power/ground injection; if events correlate with vibration sources, suspect mechanical coupling.

Figure F9 — False alarm attribution map

False Alarm Attribution Map Class Typical scenes Evidence tags First fix Thermal drift slow baseline HVAC airflow sun heating / gradients warm surfaces baseline_slope dT/dt long duration HPF tune temp table 2nd confirm Optics / scene FOV modulation headlight sweep curtain / plant pets / insects pulse_count repeat alt pulse pattern zoning shroud confirm window Power injection rail / ground RF TX bursts relay / LED steps brownout reset_count wake_reason event timing rail split edge control wake filter Mechanical vibration door slams mount flex repeat pattern stiffen mount isolate
F9 turns false alarms into an attribution problem: classify the event by evidence tags, then apply the matching first-fix strategy without sacrificing detection margin.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F9 (False Alarm Attribution Map)

H2-10. Validation Test Plan

Reusable SOP matrix with measurable pass criteria

Validation must prove two independent properties: motion detection performance and false alarm probability. The plan below is structured as a repeatable SOP: each test specifies setup variables, pass criteria, and the minimum log fields needed for attribution.

temperature dT/dt battery_v baseline_slope band_rms pulse_count thr_value gain_index wake_reason active_time_ms reset/brownout

SOP matrix (Test / Setup / Pass criteria / Logs)

Test Setup Pass criteria Logs
Sensitivity sweep
range × angle × speed
Move a calibrated thermal target along a defined path at multiple distances/angles/speeds; keep ambient stable for baseline runs. Meets targeted detection probability across the specified envelope; no systematic missed zones. band_rms, pulse_count, baseline_slope, alarm_count, temperature
False-alarm stress
temp + airflow + light
Temperature cycling with controlled airflow and step/sweep lighting conditions; run long enough for hourly statistics. False alarm rate below target per hour; events are attributable by evidence tags (no “unknown” class). event duration, repeat period, dT/dt, baseline_slope, wake_reason
Power disturbance
brownout & recovery
Inject controlled supply droops and recoveries under representative load steps (RF burst / relay step if present). No latch-up; recovery within target time; no spurious alarm storm post-recovery. battery_v, reset_count, brownout_count, active_time_ms
Port transients
ESD / EFT (edge)
Apply ESD/EFT at exposed ports and I/O boundaries per product class; verify after-stress behavior and logging. No permanent behavior change; recovery within target time; no persistent increase in wake storms. wake_count, wake_reason, reset/brownout, post-stress alarm_count
Aging & contamination
lens & leakage
Introduce lens contamination/humidity and simulate board leakage at the sensor input node; repeat sensitivity and false-alarm tests. False-alarm increase remains bounded; baseline settles; detection margin stays acceptable. baseline_slope, band_rms, gain_index, thr_value, temperature
Required practice: every validation run records the same core fields so failures can be traced back to optics, drift, power injection, or mechanics without guessing.

Figure F10 — Test bench overview (target path + recorded items)

Validation Bench — Motion, Stress, and Logging Thermal Target Move along defined path HOT HOT PIR Module (DUT) Lens → Sensor → AFE → MCU AFE MCU I/O Temp • Airflow • Light Instruments Oscilloscope Logger PSU / Brownout ESD / EFT Inject Recorded items (minimum) temperature dT/dt battery_v baseline_slope band_rms pulse_count thr_value gain_index wake_reason active_time_ms reset / brownout
F10 is a buildable bench: controlled motion path, combined stresses, and a consistent logging set so failures map back to drift, optics, power injection, or mechanics.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F10 (Validation Bench Overview)

H2-11. Field Debug Playbook (Symptom → Evidence → Isolate → Fix)

Fast attribution with minimal tools

This playbook turns field issues into a repeatable workflow. Each symptom uses the same four steps: SymptomEvidenceIsolateFix. The goal is to converge quickly without sacrificing detection margin.

Rule: do not start by “just raising the threshold”. First classify the event as thermal drift, optics/scene modulation, power injection, or mechanical disturbance.

Minimal tools (what is enough on-site)

  • DMM: battery/rail voltage, static current, voltage drop under load.
  • Simple scope or sampler: AFE output / comparator output / rail dip timing.
  • Temperature readout: NTC or on-board temperature sensor.
  • Isolation props: cardboard遮挡 for FOV masking, tape/shroud, small fan, small heat source.

Evidence checklist (minimum fields to log)

Category Fields (examples)
Thermal / drift temperature, dT/dt, baseline_slope, event_duration
Signal / decision band_rms, pulse_count, thr_value, gain_index (or agc_state)
Power / wake battery_v (or rail_vmin), wake_reason, active_time_ms, reset_count, brownout_count
Keep the field set consistent. A consistent log schema is what makes attribution scalable across installations.

Symptom 1 — False alarms are frequent at night

SYMPTOM
Triggers cluster at night, often near windows, HVAC vents, or in rooms with large temperature gradients.
EVIDENCE
dT/dt elevated (or periodic), baseline_slope large, events have long duration, and pulse sequences lack clear alternating “zone-walk” structure.
ISOLATE
  • FOV mask test:遮挡 the window/door direction. If false alarms drop, it is optics/scene-driven.
  • Airflow test: switch HVAC off or redirect airflow; check if events track fan cycles (periodicity).
  • Drift-only test: no movement in the room; if triggers persist, it is drift/power/mechanical—not true motion.
FIX (FIRST ACTIONS)
  • Optics: reduce zones facing windows/heat sources; add a simple shroud.
  • Filtering / decision: slightly increase HPF corner to reject slow drift; add a second-confirm window requiring alternating pulses and minimum pulse_count.
  • Temp compensation: tighten threshold when dT/dt is high; use a segmented temp table.
Quick re-check: run a 60-minute “no-motion” soak under the same night conditions and verify false alarm rate drops without degrading daytime detection.

MPN examples (typical fixes for this symptom)

  • Low-power temperature sensor: TI TMP117 / TMP116; Microchip MCP9808.
  • Comparator for clean wake interrupt: TI TLV3691 / TLV3701; Microchip MCP6561.
  • Ultra-low-Iq LDO (battery powered): TI TPS7A02; Analog Devices ADP160; Microchip MCP1700.

Symptom 2 — Missed detection (should trigger but does not)

SYMPTOM
Human motion within the expected range/angle does not reliably trigger alarms, especially at certain paths or distances.
EVIDENCE
band_rms small, pulse_count low, waveform looks overly smoothed, or thr_value too high relative to noise margin. gain_index stuck low (or AGC clamps unexpectedly).
ISOLATE
  • Path sweep: repeat the same motion at multiple distances/angles/speeds to see if misses correlate with specific zones (optics issue).
  • Filter check: temporarily widen the passband (software thresholding after raw sampling) to see if “lost energy” is the cause.
  • Install check: verify height and aiming; avoid mounting that places the main walk-path inside a “dead” zone.
FIX (FIRST ACTIONS)
  • Optics: adjust lens zoning / coverage for the actual path; correct mounting height and tilt.
  • AFE: increase gain only after verifying noise margin; avoid shifting to a band that amplifies vibration/EMI.
  • Decision: tune pulse_count / energy thresholds rather than a single static level.
Quick re-check: repeat 20 identical passes and compare detection probability before/after; confirm false alarms did not rise.

MPN examples (common building blocks relevant to missed detection)

  • PIR sensor elements: Murata IRA-S210ST01 (example); Panasonic EKMB series (example).
  • Low-noise op-amp for PIR AFE: TI OPA333 / OPA388; Analog Devices ADA4528-1; NXP (legacy) MC33202 (higher-power reference).
  • Precision resistors / low-leakage passives: Vishay TNPW thin-film; Panasonic ERA series; NP0/C0G capacitors for stable corners.

Symptom 3 — Random triggers in the first minutes after power-up

SYMPTOM
After power-up, alarms occur without motion; the system stabilizes after several minutes.
EVIDENCE
baseline_slope high immediately after boot, gain_index/AGC state oscillates, rail_vmin shows startup sag or ringing, event_duration tends to be long.
ISOLATE
  • Boot-no-motion test: power up with a fully static scene. If triggers persist, focus on startup recovery and power integrity.
  • Rail dip capture: observe battery/rail during boot. If dips align with triggers, it is power injection.
  • Baseline settle time: measure how long baseline_slope takes to approach steady-state.
FIX (FIRST ACTIONS)
  • Arming delay: add an ARM phase (sleep → arm → sample) and only enable alarms after baseline settles.
  • Soft-start: reduce inrush and avoid comparator/AFE operating near undervoltage.
  • Reset/brownout policy: ensure brownout thresholds are consistent with AFE stability (avoid borderline operation).
Quick re-check: cold-boot 20 times; measure “false alarms in first X minutes” and verify it collapses after the fix.

MPN examples (startup stabilization and power integrity)

  • Load switch / inrush control: TI TPS22910A / TPS22918; onsemi NCP380.
  • eFuse / protection (if needed at module edge): TI TPS2595; Analog Devices LTC4365 (OV protection use-case).
  • Supervisor / reset: TI TPS3839; Microchip MCP100/MCP1316.

Symptom 4 — Wireless reporting drops (power-burst coupling)

SYMPTOM
Motion detection happens, but wireless reporting is unreliable; sometimes alarms “disappear” or coincide with brownouts.
EVIDENCE
battery_v/rail_vmin dips during TX, brownout_count increases, active_time_ms stretches (retries), and triggers correlate with TX timestamps.
ISOLATE
  • TX-disable A/B: disable radio transmission while logging local events. If stability returns, it is TX power coupling.
  • Decoupling A/B: add temporary bulk + high-frequency bypass at the radio rail and re-test.
  • Timing shift: move TX away from critical sampling windows; check if false alarms/misses reduce.
FIX (FIRST ACTIONS)
  • Power partition: separate AFE rail from radio bursts (local LDO or RC isolation), increase local energy storage.
  • Schedule: transmit after decision, not during sampling; log TX time to correlate with events.
  • Brownout margin: adjust thresholds only after confirming the AFE remains stable across the TX dip.
Quick re-check: burst TX stress test; verify rail_vmin improves and brownout_count stays flat while detection remains stable.

MPN examples (wireless power-burst containment)

  • Ultra-low-Iq LDO for analog rail isolation: TI TPS7A02; ADI ADP160; Microchip MCP1700.
  • DC/DC for higher efficiency (if budget allows): TI TPS62740; ADI LTC3335 (energy-harvesting style use-cases).
  • Radio modules (examples): Nordic nRF52832 / nRF52840; Silicon Labs EFR32MG series; TI CC1352R (Sub-GHz + BLE class).

Recommended additions (common in the field)

  • Door slam / vibration triggers: isolate by tapping/mount flex test; fix with mounting stiffness, lens shroud, and mechanical isolation.
  • Relay/LED step triggers: correlate with rail_dip and wake_reason; fix with edge control, rail split, and improved return paths.
  • Humidity/rain increases false alarms: simulate leakage; fix with input cleanliness, coating strategy, and leakage-aware thresholding.

Figure F11 — Field triage decision tree (fast attribution)

Field Triage Decision Tree (PIR) Start: classify by evidence baseline_slope • dT/dt • pulse_count • rail_dip • repeat pattern Drift-like? baseline_slope high OR dT/dt high Not drift-like look at pulses / rails / vibration Thermal drift / airflow driven Fix: install away from HVAC • HPF tune • temp table • 2nd confirm Motion-like pulses? pulse_count high AND alternating pattern True motion but missed / unstable Fix: optics zoning & install • gain/band tune • decision thresholds Power injection rail_dip • TX/relay timing Fix: rail split • bypass • schedule Mechanical vibration correlation Fix: mount stiffness • isolation If none match: suspect AFE noise / leakage / contamination → re-run drift soak + leakage simulation
F11 is meant for rapid field routing: classify with a few evidence tags, then apply the first fix within the PIR module boundary.
Cite this figure: ICNavigator · PIR Motion Detector · Figure F11 (Field Triage Decision Tree)

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-12. FAQs (12)

QDoes a PIR detector need calibration? What must not be changed in the field?

PIR modules need calibration only to lock a stable baseline: threshold, gain step points, and temperature compensation tables. In the field, do not rewrite analog trims (gain/HPF corners), temp-table version, or brownout policy; those changes break validation. Measure baseline_slope and false_alarm_rate before/after any change. MPN examples: TMP117 (temp), TLV3691 (comparator).

QWhy do false alarms spike when HVAC or warm air turns on? Which two evidences first?

HVAC usually creates fast dT/dt and airflow-driven scene modulation. First check dT/dt (or temperature) and baseline_slope around trigger time. Isolate with a 10-minute fan OFF test and a quick FOV mask toward the vent/window. Fix by relocating/shrouding the lens, tightening temp-comp thresholds, and slightly raising HPF corner. MPN: TMP116/TMP117.

QSunlight on curtains triggers alarms: optics issue or filter settings?

If sunlight on curtains triggers alarms, decide optics vs filter by waveform shape: true motion shows alternating pulses (zone-walk), while sun drift looks like slow baseline push with long events. Isolate by masking the window direction; if it stops, it’s optics. If not, tune HPF/second-confirm window and avoid over-gain. MPN: OPA388 (AFE op-amp).

QWhat really enables “pet immunity”: lens zoning or algorithm thresholds?

“Pet immunity” is primarily optics zoning plus decision rules, not just a higher threshold. The lens aims most zones above pet height, and the MCU rejects short/low-height patterns (event_duration and pulse_count). Prove it by height/path sweeps (pet-level vs adult-level). Fix with correct lens/tilt and keep temp-comp consistent. MPN examples: Panasonic EKMB, Murata IRA-S210ST01 (PIR).

QFalse alarms in the first 5 minutes after power-up: AFE recovery or MCU state machine?

Triggers within 5 minutes of power-up are usually baseline recovery or rail sag confusing the comparator/MCU state machine. Check baseline_slope vs time since boot and capture rail_vmin during startup. Isolate with a no-motion cold-boot test. Fix with an arming delay, soft-start, and a clean reset/brownout policy. MPN: TPS3839 (supervisor), TPS22910A (load switch).

QMissed detections: is fast walking or slow walking easier to miss, and should you change filters or gain?

Fast walkers shift energy higher; slow walkers push energy lower. Misses on slow motion suggest HPF too high; misses on fast motion suggest LPF too low or sampling windows too sparse. Measure band_rms and pulse_count across speed sweeps. Fix bandpass corners first, then adjust gain/threshold with margin. MPN: OPA333 (zero-drift op-amp).

QAdding TVS made false triggers worse: return path issue or clamp recovery time?

If adding TVS increases false triggers, suspect return-path injection or clamp recovery ringing, not “extra protection” itself. Correlate triggers with ESD events and look for rail ripple after clamping. Isolate by swapping to a lower-capacitance TVS and shortening the ground loop. Fix with tighter return, series damping, and appropriate TVS selection. MPN: PESD5V0S1UL, SMF5.0A (examples).

QBattery still shows charge but wireless doesn’t report: battery ESR or brownout threshold first?

Battery ‘has charge’ but wireless fails is almost always TX peak current + battery ESR causing rail dips. Check rail_vmin during TX and brownout_count/reset_count. Isolate by disabling TX while logging local events, then add temporary bulk capacitance. Fix with rail partitioning, reservoir caps, and TX scheduled after sampling. MPN: TPS62740 (buck), nRF52840 (radio SoC).

QSame hardware behaves differently after changing mounting height: change lens first or thresholds?

If performance changes with mounting height, fix optics first: the zone pattern may miss the main walk path or amplify low-height motion. Prove it with a height/tilt sweep while logging pulse_count distribution. Choose the correct lens/zoning and aim angle, then re-verify temp-comp and thresholds. MPN: TMP117 (temp) to stabilize compensation.

QLED indicators cause false alarms: power ripple coupling or ground bounce?

LED indicators can inject ripple or ground bounce into the AFE/comparator. Correlate triggers to LED edge timing and measure rail ripple during toggles. Isolate by disabling LED or slowing edges (series resistor/PWM ramp). Fix by separating returns/rails and adding local bypass near AFE. MPN: TPS22918 (load switch), TPS7A02 (LDO).

QOnly one unit false-alarms among many: fastest way to prove contamination or leakage?

If only one unit false-alarms, prove leakage/contamination fast: clean/dry the PCB, then run a humidity A/B test and compare baseline_slope/noise. Simulate leakage with a high-value resistor across the sensor input to see if behavior matches. Fix with cleaning, conformal coating, and guarding. MPN: Vishay TNPW thin-film resistors (stable high-value).

QHow do you set and verify a quantitative false-alarm-rate target?

Set measurable targets: false_alarm_rate (events/hour) under defined HVAC/light conditions, detection probability over 20 repeat passes, startup false alarms in first X minutes, and recovery time after rail dips. Use one log schema (temperature, dT/dt, baseline_slope, rail_vmin, pulse_count). MPN: TPS3839 (supervisor), TMP116 (temp).