Coffee Maker Electronics: Temp/Pressure AFEs, Drives & Power
← Back to: Smart Home & Appliances
Coffee Maker — Electronics & Control
Coffee maker consistency is an evidence problem: stable taste comes from closing the temperature and pressure/flow loops with the right sensing chain, drive waveforms, and brownout-proof power rails. When results drift, the fastest fix is to correlate commands to measurable signals (dT/dt, P_ripple, flow pulses, Vlogic_min) and isolate whether the root cause is sensing, actuation, water-path, or power integrity.
H2-1 — System Boundary & What Counts as a Coffee Maker (Scope Lock)
This page treats a coffee maker as a closed electromechanical control system: a water path (reservoir → pump → heater/thermoblock → valves → brew head) driven by actuator power stages and stabilized by sensor feedback (temperature, pressure, flow, and safety interlocks). The goal is to keep the content vertically deep on measurable signals, failure evidence, and design choices—while preventing cross-page duplication with other kitchen appliances.
Variants included (only where they change the electronics)
- Drip coffee: heater control + basic water-level/temperature behavior; pressure sensing is often absent or implicit.
- Capsule brewer: frequent pump/valve switching and tight packaging; rail droop, EMI coupling, and “start-up reset” symptoms are common.
- Home espresso (boiler/thermoblock): strong temperature/pressure dynamics; pressure ripple, pre-infusion timing, and thermal cutoffs dominate the debug evidence.
Core subsystems (organized by energy path vs signal path)
Energy path: mains → protection → PSU
Actuation: heater / pump / solenoid valves
Sensing: temp / pressure / flow / level
Control: MCU + timing + fault logic
UI: keys/encoder + display + indicators
Evidence: logs + counters + test points
This page covers
- Measurement chains: sensor placement assumptions, AFE/ADC constraints, noise coupling paths, plausibility checks.
- Control loops: how temperature and pressure/flow loops are built, what “stable” means in measurable terms.
- Power & safety: brownout, inrush, surge/ESD points that directly explain field failures (resets, trips, stuck drives).
- Debug evidence: “first two measurements,” discriminators that separate mechanical, electrical, and sensing causes.
- Other kitchen appliances: induction cooktop inverter, microwave magnetron drive, oven/steam-oven control, range hood systems.
- Platform/app tutorials: cloud backend, mobile app walkthroughs, whole-home hub architecture (Matter gateway deep-dive).
- Textbook deep dives: PFC topology derivations, generic EMC theory that does not tie to coffee-maker evidence signals.
Practical rule: any paragraph must reference at least one coffee-maker-specific evidence signal (rail droop, sensor waveform, drive node behavior, event counter, leakage trip symptom). If not, it belongs on a different page.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F1 (System Boundary) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Tip: keep the citation URL aligned with the final page slug.
H2-2 — Top-Level Architecture: Water Path + Control Loops (Mental Model)
A coffee maker becomes debuggable when every symptom is mapped to a specific loop: (1) the temperature loop controlling delivered water temperature and thermal safety, and (2) the pressure/flow loop shaping extraction dynamics and detecting hydraulic faults. Both loops are anchored in measurable signals: sensor outputs, drive node behavior, and rail integrity.
Water path (physical stages)
- Reservoir → inlet: water level/leak states define safe enable conditions.
- Pump: generates flow/pressure; introduces characteristic ripple that can be used as a diagnostic fingerprint.
- Heater / thermoblock: adds thermal energy; high power switching is the #1 source of rail droop and EMI injection.
- Valves / relief (OPV): route flow, control pre-infusion/steam functions, and protect over-pressure conditions.
- Brew head → cup: downstream restrictions convert flow into pressure; clogging and scale show up here first.
Control loops (what is controlled, what is measured, what is actuated)
-
Temperature loop:
Temp sensor → AFE/ADC → control logic → heater drive (triac/SSR/MOSFET)
Key evidence signals: heat-up slope, overshoot, steady-state ripple, and disturbance when the pump/valves switch. -
Pressure/flow loop:
Pressure + flow feedback → control logic → pump/valve actions (+ OPV behavior)
Key evidence signals: pressure ripple signature vs drive, flow pulse timing distribution, ramp/hold/decay profile consistency.
What “good” looks like (defined by measurable profiles, not marketing terms)
- Stable brew temperature band: repeatable warm-up, minimal overshoot, predictable disturbance under pump load.
- Stable pressure/flow profile: consistent ramp, bounded ripple, and a flow curve that matches expected restriction and valve timing.
- Power integrity margin: pump start + heater switching do not cause brownout resets, ADC corruption, or false safety trips.
Fast symptom-to-loop mapping (keeps later chapters tightly scoped)
- Watery/weak extraction → suspect pressure/flow loop first (restriction/valve/flow sensing), then temperature stability.
- Bitter/burnt taste → temperature loop overshoot/lag + sensor placement; confirm with heat-up and brew disturbance traces.
- Resets when pump starts → power integrity path (inrush + rail droop + UVLO/MCU brownout), not “random firmware.”
- Over-temp trip → confirm whether it is real heating or sensor/ADC corruption by drive noise; check plausibility logic later.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F2 (Water Path + Control Loops) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Later chapters should reference these blocks and TPs instead of repeating generic theory.
H2-3 — Temperature Sensing Chain (Temp AFE): What to Measure, What Can Lie
In a coffee maker, “temperature” is not a single truth. Brew consistency depends on the temperature of water at the relevant point in the hydraulic path, while the electronics only see a sensor signal shaped by placement, thermal lag, biasing, ADC timing, filtering, and ground reference. The chain can look stable while the delivered water temperature is drifting or being disturbed during pump/valve switching.
Sensor options (placement matters more than type)
- NTC thermistor: cost-effective and sensitive, but nonlinearity, lead resistance, self-heating, and moisture leakage can skew readings.
- RTD: more linear and stable, but needs controlled excitation and wiring discipline; errors often come from current setting and connector resistance.
- Thermocouple: used mainly when temperature ranges or mechanical constraints demand it; tiny signals make it vulnerable to switching noise and ground offsets.
Practical rule: a “better sensor” rarely fixes taste drift if the sensor is thermally decoupled from the water path.
Verify thermal contact and time constant before changing the sensor type.
AFE and ADC concerns (where a “stable number” can be wrong)
Bias network
Too low impedance increases self-heating and power loss; too high impedance increases EMI susceptibility and leakage sensitivity in wet environments.
Too low impedance increases self-heating and power loss; too high impedance increases EMI susceptibility and leakage sensitivity in wet environments.
ADC resolution vs timing
More bits do not help if sampling occurs during heater phase switching or pump/valve edges. Timing discipline often beats resolution.
More bits do not help if sampling occurs during heater phase switching or pump/valve edges. Timing discipline often beats resolution.
Sampling rate & filtering
Heavy filtering makes the trace look clean but hides disturbances; weak filtering makes control chase noise and creates overshoot.
Heavy filtering makes the trace look clean but hides disturbances; weak filtering makes control chase noise and creates overshoot.
Ground reference
Heater and pump return currents can shift the sensor reference. Ground bounce can appear as a false temperature step.
Heater and pump return currents can shift the sensor reference. Ground bounce can appear as a false temperature step.
Placement pitfalls (why the chain “lies”)
- Thermal lag: sensor far from the effective water temperature point causes delayed feedback, producing overshoot and slow recovery.
- Heater coupling: sensor measuring heater body temperature rather than water temperature leads to systematic bias during flow changes.
- Airflow/steam effects: steam vents and airflow can heat or cool the sensor area, adding drift unrelated to water temperature.
- Assembly variance: clamp force, adhesive thickness, and thermal grease coverage can create unit-to-unit taste inconsistency.
Evidence checklist (minimum measurements that resolve ambiguity)
- Sensor resistance/voltage vs time during heat-up: focus on slope, inflection points, and whether pump events create steps or spikes.
- Overshoot and settling time: quantify overshoot and recovery; long settling suggests lag or overly aggressive filtering.
- Noise during pump/valve switching: look for synchronous spikes or steps correlated with drive edges, indicating coupling or reference shift.
Debug hook: If temperature looks stable but taste varies, prioritize placement/lag and sampling + filtering discipline
before assuming a faulty sensor. A stable trace can be the result of smoothing, not stability in delivered water temperature.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F3 (Temp Sensing Chain) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: reference “Physical layer” vs “AFE timing” vs “Coupling” when explaining why a stable reading can hide real instability.
H2-4 — Pressure / Flow Sensing Chain: Pressure Sensor + Flow Meter Reality
Pressure and flow are coupled outcomes of pump behavior, hydraulic restriction, valve timing, and relief paths (OPV). Misdiagnosis is common when pressure is interpreted without flow—or when sensor chains are assumed ideal in a wet, noisy environment. A reliable method is to correlate three signals: pump drive, pressure ripple, and flow pulse timing.
Pressure sensing (what “offset drift” looks like in the field)
- Offset drift: baseline pressure does not return to a consistent value when the pump is off, or it moves with temperature and warm-up time.
- False stability: a filtered pressure trace can hide ripple that should match pump strokes; missing ripple can indicate sensor chain or reference problems.
- Sanity check: if the pump drive is active but pressure ripple signature is absent, suspect sensing/grounding/installation before blaming plumbing.
Flow sensing options (direct pulses vs inferred flow)
- Turbine flow meter (pulse output): straightforward for volume tracking but vulnerable to pulse jitter, missed pulses, and mechanical sticking.
- Inferred flow from pump current: useful as a secondary estimate, but non-linear under restriction, leakage, valve actions, and rail voltage changes.
AFE + signal integrity (the real-world failure mechanisms)
- Pulse capture & debounce: too aggressive debounce drops real pulses; too weak debounce counts EMI spikes as flow.
- EMI pickup: heater switching and solenoid flyback can inject spikes into high-impedance inputs and long harnesses.
- Wet-environment connectors: moisture leakage and corrosion shift bias points and create intermittent edge detection failures.
- Reference and routing: shared ground returns with pump/heater currents can distort both pressure analog readings and flow pulse thresholds.
Evidence checklist (three-signal correlation)
- Pressure waveform ripple: look for the pump stroke signature and its amplitude stability across time and modes.
- Flow pulse interval histogram: check for long tails or multi-modal patterns (missed pulses, sticking, or EMI false edges).
- Correlation: align pump drive edges with pressure ripple and flow pulses; mismatch strongly suggests sensing/AFE issues.
Key discriminator: low pressure with normal pump drive is most often leak / OPV early relief / valve timing / sealing
rather than a weak pump. If the pressure ripple signature is missing or inconsistent with the drive, treat it as a sensing-chain problem first.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F4 (Pressure/Flow Correlation) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Field usage: if pressure is low but pump drive is normal, check whether the ripple signature exists; missing signature usually points to sensing/AFE/reference issues.
H2-5 — Pump / Valve / Heater Drive: What the Waveforms Should Look Like
Drive waveforms define the energy delivered into water flow, pressure, and heat. In coffee makers, unstable behavior is often caused by timing errors, misfiring, or uncontrolled flyback rather than “weak hardware.” A practical approach is to treat each actuator as a measurable plant: command → drive waveform → current response → mechanical outcome.
Vibration pump (AC) control
BLDC pump drive basics
Solenoid flyback
Triac/SSR control
Burst firing
Stuck-on detect
Pump drive styles (what to expect on the scope)
Vibration pump (AC)
Typical control uses burst firing (whole cycles on/off) or simplified half-cycle gating. Expected evidence includes a stable on/off envelope, repeatable inrush behavior, and a pressure ripple signature that tracks the drive pattern.
Typical control uses burst firing (whole cycles on/off) or simplified half-cycle gating. Expected evidence includes a stable on/off envelope, repeatable inrush behavior, and a pressure ripple signature that tracks the drive pattern.
- Good: consistent envelope, repeatable current peaks, pressure ripple signature present.
- Bad: missing cycles / random dropout / irregular gating → unstable pressure/flow and EMI spikes.
BLDC pump
Reliability depends on controlled startup, commutation stability, and current limiting. Warm and wet environments can expose marginal supply rails and cause repeated restart loops.
Reliability depends on controlled startup, commutation stability, and current limiting. Warm and wet environments can expose marginal supply rails and cause repeated restart loops.
- Good: clean startup, stable current limit behavior, no repeated “spin-up then reset.”
- Bad: commutation stalls, current clamp always active, rail dips during startup.
Valve drive (solenoid coil): flyback, heat, and PWM reality
- Flyback strategy sets release speed and EMI. Fast release can improve timing but increases voltage stress and coupling risk.
- PWM hold reduces heating but adds switching edges that can inject noise into sensors and logic rails if routing/reference is weak.
- Coil heating changes resistance and actuation margin; long on-time can shift timing and produce intermittent symptoms.
Heater control (triac/SSR vs DC MOSFET)
- Triac/SSR phase control: flexible but sensitive to misfire and noisy edges; can disturb sensing if sampling is not time-managed.
- Burst firing: easier to schedule measurements in the quiet window; common for stable control without excessive EMI.
- DC heater via MOSFET: enables PWM control and cleaner timing coordination, but requires attention to current ripple and thermal design.
Evidence-based faults to recognize:
triac misfire (random missed conduction), solenoid flyback ringing (overshoot + oscillation), and pump drive dropout
are waveform patterns that often explain instability better than replacing mechanical parts.
Mandatory protections (hardware + logic proofs)
- Overcurrent: detect clamp/limit events and record counters; repeated limiting explains low pressure/flow despite active drive.
- Over-temperature: independent thermal cutoffs remain the final layer; control logic should detect abnormal heating response early.
- Stuck-on detection: if command is off but current/temperature still rises, trigger shutdown and log an event; watchdog logic prevents silent hazards.
Minimum “first probes” for drive diagnosis:
measure drive node (gate/triac/coil), actuator current (or proxy), and logic rail dip during switching events.
This triangulation separates electrical misfire from mechanical restriction.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F5 (Drive Waveform Map) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: point to “Bad” windows when describing triac misfire, coil ringing, or drive dropout patterns.
H2-6 — Power Management & Safety: Mains Entry → Low-Voltage Rails (Coffee-Maker Specific)
Coffee makers combine large, fast load steps (pump start, solenoid edges, heater switching) with sensitive logic and sensing rails. Practical power design prioritizes rail stability under load events, sequencing discipline, and a measurable safety chain, rather than pursuing textbook efficiency metrics. Most “random resets” and “ghost inputs” are power integrity problems with clear evidence.
Common rail needs (what must remain stable)
- Logic + sensing rail: MCU, ADC, sensor bias networks; the most sensitive to noise and brownout.
- Driver rail: gate drivers, solenoid drivers, pump controller; must tolerate current spikes and inductive events.
- UI rail: display/backlight, touch controller, buzzer; can inject PWM noise if not partitioned.
- Optional Wi-Fi rail: burst currents during TX can expose weak impedance and cause resets if shared with logic.
Isolated vs non-isolated rails (decision by safety and coupling)
- Isolation is driven by safety boundaries and user-accessible structures, not by preference. When isolation exists, its return strategy must not corrupt sensor references.
- Non-isolated designs must treat leakage and reference placement seriously in wet environments; measurement accuracy can degrade before safety failures appear.
Inrush + surge (why heater + pump events brown out logic)
MOV/NTC placement matters
Poor placement or marginal parts can turn line disturbances into repeated low-voltage dips on the PSU output, especially during heater switching.
Poor placement or marginal parts can turn line disturbances into repeated low-voltage dips on the PSU output, especially during heater switching.
Sequencing discipline
If heater and pump transitions overlap without coordination, the logic rail can dip below BOR threshold. Symptoms look “random” until captured at the rail test point.
If heater and pump transitions overlap without coordination, the logic rail can dip below BOR threshold. Symptoms look “random” until captured at the rail test point.
Fast discriminator for brownout: correlate logic rail dip with pump start or heater switching.
If the dip aligns with the event and reset counters increment, the root cause is power integrity and sequencing.
Safety chain (hardware last line + software evidence)
- Thermal fuse / bimetal cutoff: independent hard stop for runaway heating; treat as non-negotiable safety layer.
- Dry-boil detection: use response plausibility (commanded heating vs temperature rise profile) to detect abnormal conditions early.
- Interlocks: water level, lid/door switches; verify with debounced, logged state transitions to avoid false trips.
Deliverable: Power Tree checklist (publish-ready)
- For each rail: nominal voltage, peak current, allowed droop, and a physical TP label for measurement.
- For each load event (pump start, valve release, heater switching): worst-case rail dip and the mitigation method (sequencing, local decoupling, partitioning).
- Reference strategy: keep high-current returns from sharing sensor reference paths; verify by observing sensor output during drive edges.
Deliverable: Brownout symptom table (symptom → evidence → isolate)
| Symptom | First evidence to capture | Most likely cause & fast isolate |
|---|---|---|
| Pump start → reboot | Logic rail dip at TP + BOR/reset counter increments | Inrush + weak rail impedance; isolate by disabling heater during pump start and re-testing |
| Heater switching → sensor spikes | ADC trace spikes aligned to triac/SSR edges | Reference shift / coupling; isolate by sampling in quiet window and checking grounding path |
| Valve release → false UI touches | UI line glitch aligned to flyback event | Flyback ringing and EMI pickup; isolate by comparing “fast vs slow” flyback clamp behavior |
| Wi-Fi TX → intermittent resets | 3.3V burst droop aligned to TX activity | Shared rail overload; isolate by powering RF module from a partitioned rail and logging droop |
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F6 (Power Tree & Safety Chain) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: reference TP1/TP2/TP3 when diagnosing brownout during pump start or heater switching events.
H2-7 — Recipe / Control Algorithms: Turning Sensors into Repeatable Taste (No Cloud)
Repeatable taste is created by making measurable profiles (temperature, pressure, flow) track a target timeline using only the available actuators (heater, pump, valves). The focus is not theoretical control derivations, but behavior tied to evidence: what should the signals look like during each phase, and what patterns prove a fault.
Temp loop (PID)
Anti-windup
Lag compensation
Pre-infusion
Ramp / Hold / Decline
Plausibility checks
Control map: measurable signals → actionable levers
Signals
- Temperature: influenced by heater power and flow load.
- Pressure: reflects resistance + pump behavior + valve actions.
- Flow: direct turbine pulses or inferred proxies (limited).
Actuators
- Heater: burst firing / phase control / DC PWM (design-dependent).
- Pump: burst, duty control, or BLDC speed/limit behavior.
- Valves: open/close timing, PWM hold (if used), relief/OPV actions.
Temperature control: PID behavior that matters on real hardware
- Anti-windup is mandatory: heater power saturates (fully on/off). Without windup control, the integrator accumulates error during saturation and drives overshoot.
- Lag-aware updates: sensor placement and thermal lag can make “stable readings” hide real output variation. Compensation is implemented as controlled gain scheduling and update timing, not complex math.
- Quiet-window sampling: update control from samples taken away from heater switching edges and valve flyback events to prevent chasing electrical noise.
Pressure/flow profile: what can actually be achieved with available actuators
A practical recipe is a state machine with phases that match real actuation capability. The same target taste can be achieved by different combinations of pressure and flow depending on the mechanical path (head restriction, scale, valve dynamics).
| Phase | Goal (signal shape) | Levers (what changes the outcome) |
|---|---|---|
| Pre-infusion | Low pressure/flow to wet the puck; gentle temperature stability | Pump burst/duty + valve timing; avoid abrupt heater edges during first wetting |
| Ramp | Pressure/flow rises to target; temperature stays within a band | Pump drive increase, valve settle time, heater power to counter flow heat load |
| Hold | Stable region; minimal oscillation in P/F; tight temp band | Small duty trims; schedule sampling in quiet windows; avoid actuator chatter |
| Decline | Controlled drop to end extraction without spikes | Reduce pump duty; manage valve release; prevent flyback noise from corrupting final measurements |
Plausibility checks (fast discriminators using only evidence)
Temp rises but pressure/flow stays flat
- Most likely: blockage, valve not opening, pump not delivering, or sensing path corruption.
- Evidence: pump drive present? pressure ripple signature present? flow pulse activity present?
Pressure high but flow low
- Most likely: clog/scale/restriction, or flow sensing missing pulses.
- Evidence: strong pressure ripple + long-tail flow pulse interval histogram points to missing pulses; stable long intervals with strong P points to real restriction.
Minimum profile logging set:
record time, Temp, Pressure, Flow, plus actuator events (pump on/off, valve switch, heater bursts).
Correlation across these channels turns “taste drift” into a debuggable signal story.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F7 (Profile Timeline) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: use phase separators to explain how pre-infusion and ramp affect the pressure/flow curve shape and how sampling aligns with events.
H2-8 — UI & Local Connectivity: Only What Impacts Hardware Evidence
UI and local connectivity blocks are often the hidden source of measurement instability. Backlight PWM, buzzer edges, and wireless burst currents can inject noise into ADC references or pull down shared rails. This chapter focuses on evidence-based interference and a repeatable sampling schedule pattern to keep sensing stable.
Knob / buttons
Encoder debounce
LCD/OLED
Backlight PWM
Buzzer
Wi-Fi/BT bursts
UI blocks (hardware-only view)
Inputs
- Buttons / knob / encoder (debounce + event logging)
- Touch keys (reference-sensitive, easily disturbed by ground bounce)
Outputs
- LCD/OLED + refresh current pulses
- Backlight PWM (dominant periodic noise source)
- Buzzer drive edges (fast current steps)
Noise coupling that breaks sensor evidence
- Backlight PWM → ADC: periodic current ripple shifts reference/ground, creating correlated spikes in temperature/pressure readings.
- Buzzer edge → rails: short, high di/dt steps can cause momentary rail dips or reference jumps.
- UI refresh → bus lines: display interface activity can couple into high-impedance sensor nodes if routing is marginal.
Fast proof test: capture the sensor ADC trace with backlight PWM enabled vs disabled.
A strong reduction in noise indicates coupling through rails/reference rather than true sensor dynamics.
Optional wireless module coexistence (power/EMI only)
- Burst current during TX can pull down shared 3.3V rails and trigger BOR resets or sensor bias drift.
- EMI can create false pulses on flow capture or false touches if reference integrity is weak.
- Evidence is always correlation: TX activity timing aligned with rail droop or measurement artifacts.
Deliverable: UI interference checklist
- Backlight PWM on/off: compare ADC noise floor and spurious spikes.
- Buzzer active: check for synchronous rail dips or sensor glitches.
- Encoder events: verify event bursts are not synchronized to pump/heater switching (false triggers).
- Display refresh: verify sensor readings do not change with UI update rate.
- Wireless TX: correlate 3.3V droop or resets to TX bursts.
Deliverable: ADC sampling schedule pattern (repeatable template)
Scheduling pattern:
sample sensors in quiet windows (away from heater switching edges, valve flyback edges, backlight PWM edges, and wireless TX bursts),
then update control outputs after sampling. This avoids chasing noise and improves repeatability.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F8 (UI Coupling & Sampling Schedule) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: treat PWM/flyback/heater edges as “avoid zones” and place ADC updates in the quiet windows to reduce false control actions.
H2-9 — Calibration, Production Test, and Self-Diagnostics (Make It Manufacturable)
Manufacturability is created by converting “taste repeatability” into calibrated measurements, a concrete end-of-line (EOL) test flow, and self-diagnostic status that can be logged and audited. The intent is not generic calibration theory, but a measurable plan: what to trim, what to record, what to reject, and what to log in the field.
1–2 point trim
Offset / scale
Pulse-per-ml
EOL flow
Self-test bits
Event counters
Calibration scope: what gets trimmed vs what gets verified
Trim (store coefficients)
- Temperature chain: 1–2 point trim for sensor + bias/ADC gain/offset alignment.
- Pressure chain: offset + scale (static window + reference point).
- Flow chain: pulse-per-ml characterization (volume vs pulse count).
Verify (EOL + runtime evidence)
- Heater: response curve and reachability under controlled steps.
- Pump / valve: actuation signature and correlation (pressure ripple / flow activity).
- Safety hooks: plausibility and stuck-on / stuck-off detection using measured responses.
Temperature calibration: 1-point vs 2-point (and what to store)
- 1-point trim removes dominant static error (offset-equivalent) and is often sufficient when placement/lag dominates taste variation.
- 2-point trim corrects slope across a wider range and is preferred when tighter control bands are required across multiple brew modes.
- Store time: write coefficients at EOL after the heater response step verifies stability; include record versioning and integrity checks.
Coefficient record (NVM) — minimal robust structure
record_version
device_serial_hash
temp_cal: {offset, slope, cal_temp_1, cal_temp_2}
press_cal: {offset, scale, cal_press_ref}
flow_cal: {pulses_per_ml, cal_volume_ml}
crc32
valid_flag
Store a version + CRC so partial writes and mismatch records can be rejected deterministically.
Pressure & flow calibration: offset/scale + pulse-per-ml characterization
- Pressure offset: capture in a known state window (pump off, relief/valve state fixed) and record the stable mean + noise.
- Pressure scale: use a reference point (fixture or golden unit) and compute scale so the profile thresholds are consistent.
- Flow pulse-per-ml: run a fixed drive window, measure delivered volume, and compute pulses_per_ml; record pulse jitter/interval outliers to detect pickup/connector issues.
End-of-line (EOL) test plan: concrete steps and pass/fail evidence
| Step | What to do | Record + pass/fail discriminator |
|---|---|---|
| EOL-01 | Heater response step (fixed power/time window) | Record dT/dt, overshoot, settle time; fail if rise is too slow or unstable (indicates heater path / sensing / coupling issues). |
| EOL-02 | Pump actuation verification | Record pressure ripple present and amplitude trend; fail if pump drive exists but ripple signature is absent (airlock/weak pump/sensor path). |
| EOL-03 | Valve actuation verification (toggle sequence) | Record pressure/flow step response; fail if valve toggle produces no measurable response (stuck valve/drive path). |
| EOL-04 | Leak detect / water level check | Record water-level state consistency and “pump-on with low pressure + low flow” bucket; fail if leakage signature is detected. |
| EOL-05 | Logic rail robustness during load events | Record Vlogic_min at pump start + heater switching; fail if BOR/reset occurs or Vmin violates the design margin. |
Self-test hooks: plausibility + stuck detection + event logging
Plausibility checks (sensor behavior vs commands)
- Heater ON but Temp rise below threshold → heater path, dry-boil safety chain, or sensor coupling.
- Pump ON but pressure ripple absent → weak/airlocked pump, leak, or pressure sensing issue.
- Pressure high + flow low → restriction/scale or flow pulse loss; separate via pulse-interval outliers.
Stuck detection (dangerous faults)
- Stuck triac/heater: command OFF but heating evidence persists (temp slope / current proxy).
- Stuck valve: commanded state change with no pressure/flow response.
- Brownout: BOR/reset reason code increments; correlate to pump/heater events.
Deliverable: keep EOL records and self-test logs consistent across products by logging the same “evidence primitives”:
dT/dt, pressure ripple present, flow pulse count, pulse interval outliers, Vlogic_min, and event counters.
Deliverable: EOL checklist (short form) + self-test status bits to log
EOL checklist (short)
- EOL-01 Heater step → log dT/dt, overshoot, settle
- EOL-02 Pump ON → log P_ripple + amplitude trend
- EOL-03 Valve toggle → log ΔP/ΔFlow response
- EOL-04 Level/leak → log level state + leak signature bucket
- EOL-05 Load events → log Vlogic_min + BOR count
Self-test status bits (loggable)
- ST_TEMP_RISE_FAIL (heater ON, dT/dt too low)
- ST_P_RIPPLE_MISSING (pump ON, ripple absent)
- ST_FLOW_PULSE_LOSS (interval outliers beyond threshold)
- ST_HEATER_STUCK_ON (command OFF, heating evidence persists)
- ST_VALVE_NO_RESPONSE (toggle without ΔP/ΔFlow)
- ST_BROWNOUT_EVENT (BOR/reset reason increments)
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F9 (EOL & Self-Test Map) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: print the EOL flow as a station poster; keep the record fields consistent so field logs can be compared across builds.
H2-10 — Reliability & Field Failures: Symptom → Evidence → Isolate → Fix (Decision-Tree Style)
Reliability in the field is won by using a repeatable diagnostic structure. Each symptom is handled with the same block: First 2 measurements → Discriminator → Root-cause buckets → First fix. This avoids guesswork and improves auditability (EEAT) because conclusions are tied to recorded evidence.
First 2 measurements
Discriminator
Root-cause buckets
First fix
Evidence correlation
Evidence primitives (reused across all symptoms)
Measurement primitives
- Vlogic_min during pump start / heater switching
- P_ripple present (pump stroke signature) when pump is commanded ON
- Flow pulses: count + interval outliers within a fixed window
- dT/dt: temperature rise rate during a controlled heater step
Root-cause buckets
- Power (brownout, rail impedance, sequencing)
- Sensing (offset drift, pickup, reference integrity)
- Actuation (pump/valve/heater drive faults)
- Water-path (leak, airlock, restriction/scale)
- Safety/UI (trips, coupling, ghost touches)
Symptom playbooks (repeatable blocks)
Symptom: “Heats forever, never reaches target”
| First 2 measurements | dT/dt during a heater step; heater command evidence (switching/current proxy) aligned to the step. |
|---|---|
| Discriminator | Heater command present but dT/dt ~ 0 → heater path / safety cutoff / dry-boil logic. dT/dt normal but reported temperature flat → sensing chain/reference issue. |
| Likely root-cause buckets | Actuation (heater drive), Safety (thermal fuse/bimetal), Sensing (NTC/ADC reference), Water-path (no water / poor coupling). |
| First fix | Verify water-level state and dry-boil plausibility; re-run step with pump OFF; validate sensor reference stability during heater switching. |
Symptom: “Over-temp trips during brew”
| First 2 measurements | Temp timeline vs pump/valve events; Flow pulses + pressure trend during the trip window. |
|---|---|
| Discriminator | Temp spikes when flow drops → restriction/scale or valve issue. Temp rises despite heater OFF evidence → stuck heater/triac. |
| Likely root-cause buckets | Water-path (restriction/scale), Actuation (valve not opening), Safety (cutoff threshold), Heater stuck-on. |
| First fix | Confirm flow activity during heating; run a low-power heater step with pump ON; check stuck-on detection evidence and trip counters. |
Symptom: “Pressure unstable / pulsing”
| First 2 measurements | Pressure waveform ripple pattern; pump drive timing alignment (command vs ripple). |
|---|---|
| Discriminator | Ripple frequency aligns to pump strokes → expected; instability is excessive amplitude/jitter. No ripple despite pump ON → airlock/weak pump/leak/sensing fault. |
| Likely root-cause buckets | Actuation (pump drive), Water-path (air bubbles/leaks), Sensing (pickup/ground reference), Valve dynamics. |
| First fix | Toggle valve to confirm hydraulic response; compare ripple with flow pulse histogram; isolate sensing by sampling in quiet windows. |
Symptom: “Watery brew / short shot”
| First 2 measurements | Pressure trend + flow pulse count in the same fixed window. |
|---|---|
| Discriminator | Low pressure with normal pump command → leak/relief/valve path. High pressure with low flow → restriction/scale or flow pulse loss. |
| Likely root-cause buckets | Water-path (leak/restriction), Actuation (valve/OPV behavior), Sensing (flow pulse capture). |
| First fix | Run a short pump-only test with heater OFF; check pulse interval outliers; verify valve state steps create measurable ΔP/ΔFlow. |
Symptom: “Random resets when pump starts”
| First 2 measurements | Vlogic_min during pump start; BOR/reset reason code counter and timestamp alignment to events. |
|---|---|
| Discriminator | Vlogic dip aligns to pump start → rail impedance/inrush/sequencing. Resets align to heater switching or UI backlight PWM → coupling/scheduling. |
| Likely root-cause buckets | Power (inrush/brownout), UI coupling (PWM), Heater switching interference, Ground/reference integrity. |
| First fix | Stagger pump/heater switching; reduce simultaneous load steps; move ADC/control updates into quiet windows; confirm Vlogic margin after change. |
Symptom: “GFCI/RCD trips”
| First 2 measurements | Trip timing aligned to heater activation vs pump activation; moisture/condensation context and frequency. |
|---|---|
| Discriminator | Trips align to heater ON or wet conditions → leakage/insulation path around heater/water contact. Random trips without load correlation → wiring/connector integrity. |
| Likely root-cause buckets | Safety (leakage), Heater insulation degradation, Water ingress paths, Harness/ground faults. |
| First fix | Isolate by running heater-only vs pump-only test; log trip context; inspect water ingress and heater insulation-related evidence before altering control logic. |
Symptom: “Noisy touch / UI ghosting during heating”
| First 2 measurements | ADC noise trace vs backlight PWM frequency; correlation to heater switching edges (time alignment). |
|---|---|
| Discriminator | Noise locks to PWM frequency → UI coupling. Noise locks to heater switching → reference/ground bounce from power events. |
| Likely root-cause buckets | UI PWM coupling, Power/ground bounce, Sampling schedule, Reference routing. |
| First fix | Disable/retune backlight PWM for a proof test; move sampling to quiet windows; separate UI updates from sensor sampling intervals. |
Symptom: “Descale cycle never completes”
| First 2 measurements | Identify which phase stalls (heat / pressure / flow criteria); check flow pulses and pressure trend in that phase window. |
|---|---|
| Discriminator | Flow pulses missing with pressure evidence present → pulse capture or wiring; pressure/flow both low → pump weakness/leak/airlock; pressure high with low flow → restriction/scale. |
| Likely root-cause buckets | Water-path restriction, Flow sensing capture, Valve response, Pump degradation, Threshold tuning for self-test. |
| First fix | Run a fixed-window pump test to collect pulse histogram; toggle valve and confirm ΔP/ΔFlow; log the exact criterion that prevents completion. |
Deliverable mindset: store every failure as evidence primitives + phase context (profile phase, actuator commands, Vlogic_min, dT/dt, P_ripple, flow pulses).
This makes field data comparable across builds and reduces “unreproducible” reports.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F10 (Field Failure Decision Tree) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Figure usage: treat Vlogic_min, P_ripple, and flow pulses as the universal first step, then branch by correlation and command/response mismatch.
H2-11 — IC Selection Blueprint (MPN Example Buckets, Not a Vendor Ad)
This chapter converts field evidence into procurement-ready choices. Each function bucket lists key specs, why they matter (symptoms), and example MPNs (multi-vendor) that can be shortlisted and then validated with minimal measurements (noise correlation, step response, pulse histogram, brownout logs).
Evidence → Specs
Multi-vendor MPNs
Verify hooks
Not an ad
Anti-ad rule: example MPNs are provided as interchangeable buckets (multiple vendors). Final selection must be
validated against dT/dt, P_ripple, flow pulse histogram, and Vlogic_min / BOR evidence.
Selection table skeleton (filled with concrete example MPNs)
| Function | Key specs | Why it matters (symptom) | Example MPNs (multi-vendor) | Notes / verify hook |
|---|---|---|---|---|
| Temp sensing AFE / ADC | Ratiometric support; input leakage / bias (high-Z NTC); ENOB/noise; reference stability; digital filter options; sampling scheduling tolerance; ESD robustness. | “Temp stable but taste varies”; “Temp jumps when pump/valve/backlight switches”; noisy ADC during heating. |
TI ADS1220, TI ADS124S08, TI ADS1115 ADI AD7793, ADI AD7124-4 Microchip MCP3421, Microchip MCP3561 |
Verify: compare ADC noise with backlight PWM ON/OFF; log dT/dt repeatability. |
| Pressure sensor IF / ADC | Input range headroom; low offset drift; noise density; anti-EMI; sampling rate for ripple visibility; reference/ground strategy; protection against miswiring spikes. | “Pressure unstable/pulsing”; “Low pressure but pump drive normal”; “Offset drift after warm-up”. |
TI ADS1220, TI ADS1120 ADI AD7792, ADI AD7124-4 TI INA333, ADI AD8237 (front-end amp options) |
Verify: confirm pump-stroke P_ripple signature is observable (not filtered away). |
| Flow pulse capture | Timer capture / interrupt latency margin; Schmitt input thresholds; debounce/blanking; EMI immunity on wet connectors; max pulse rate margin; ESD tolerance. | “Descale never completes”; “Flow reads low but pressure is high”; missed pulses / jitter outliers. |
STM32G031K8, STM32C011F4 (MCU timer capture) NXP LPC804M101, NXP LPC824M201 TI SN74LVC1G17, Nexperia 74LVC1G17, TI LMV331 (external conditioning) |
Verify: log pulse interval histogram; correlate with pressure trend. |
| Pump/Heater drive ICs BLDC or triac/SSR interface |
UVLO behavior; current limiting; fault flags; dv/dt robustness; trigger consistency; EMI behavior; ability to separate high-load switching events. | “Pressure unstable”; “Resets at pump start”; triac misfire causing noise / heating anomalies. |
TI DRV10983, TI DRV11873 (sensorless BLDC) ST L6234, Allegro A4964 (3-phase drivers) onsemi MOC3063, Vishay VO3063 (zero-cross optotriac) Infineon BTS500xx family (protected switches, where applicable) |
Verify: align drive command → P_ripple + Vlogic_min; check trigger repeatability. |
| Solenoid valve driver | Coil current capability; flyback strategy (fast vs soft release); thermal behavior; diagnostics (open/short); clamp robustness to reduce ADC/UI coupling. | “Valve toggles but no ΔP/ΔFlow”; “ADC spikes at valve switching”; coil overheating / slow release. |
TI DRV110, TI DRV103 (solenoid drivers) Infineon TLE8102SG (low-side switch array) ST VND5T100LA (smart low-side) onsemi NCV8402 (protected low-side switch) |
Verify: valve toggle must create measurable ΔP/ΔFlow step; log ST_VALVE_NO_RESPONSE. |
| PMIC / Buck / LDO | Transient response; UVLO thresholds; soft-start; peak current margin; EMI behavior; PSRR (for sensor rails); fault protection. | “Random resets when pump starts”; “UI ghosting during heating”; ADC noise increases with load events. |
TI TPS62130, TI TPS62177, TI TPS54202 ADI LT8609S, ADI LT8610 onsemi NCP167 series (buck examples) TI TPS7A02, Microchip MCP1700, Diodes AP7333 (LDO examples) |
Verify: measure Vlogic_min at pump start + heater switch; confirm BOR counter stays flat. |
| Isolation & protection | ESD/EFT headroom; surge robustness; leakage constraints where required; signal integrity impact; clear return-path planning. | “ESD passed in lab but field resets”; “wet-environment connector pickup”; intermittent faults after surge. |
TI ISO7721, ADI ADuM1250 (digital isolators) Vishay VO615A (optocoupler example) Littelfuse SMBJ5.0A, Vishay SMBJ series (TVS examples) Bourns MOV-14D471K (MOV example), TDK/EPCOS B57236S (NTC inrush example) |
Verify: log brownout/reset counters during EFT/ESD events; confirm sensors remain plausible. |
How to use the table (fast workflow)
- Start from the symptom and evidence: dT/dt, P_ripple, flow pulse histogram, Vlogic_min/BOR.
- Pick the function bucket that “owns” the evidence primitive, then shortlist 3–6 MPNs across vendors.
- Run one proof test: correlation to events (pump/heater/PWM), command→response mismatch, and margin check.
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F11 (IC Selection Blueprint) — /coffee-maker-electronics — Accessed YYYY-MM-DD
Tip: keep the “verify hook” short and measurable (windowed sampling, pulse histogram, Vlogic_min at pump start). This prevents paper-only part selection.
Practical note (procurement + engineering)
- Example MPNs are intended for comparison. Final selection must match regional safety constraints and in-house EMC results.
- For long-lead items, maintain a second-source bucket per function with the same verify hooks.
Request a Quote
H2-12 — FAQs (Evidence-based, Coffee-Maker Scoped)
Each answer maps to measurable evidence: dT/dt and settling for temperature, P_ripple for pump stroke signature, flow pulse histogram for capture integrity, and Vlogic_min / BOR for brownout and reset root-cause isolation.
dT/dt + settle
P_ripple signature
Flow pulses
Vlogic_min / BOR
Command → response correlation
Safety note: mains/heater leakage and RCD/GFCI topics require qualified inspection. Do not bypass safety protection.
1) Why does brew temperature look stable but taste varies shot-to-shot?
“Stable temperature” can hide event-correlated noise and sensor lag. The goal is to separate true thermal variation from measurement artifacts.
- First 2 measurements: (1) Temp ADC noise vs time aligned to pump/valve/backlight PWM events; (2) dT/dt and overshoot/settle repeatability on a fixed heater step.
- Discriminator: Noise spikes locked to switching events → sampling/ground/reference coupling; slow, repeatable lag → placement/thermal coupling and tuning.
- First fix: Move sampling into a quiet window, A/B test backlight PWM OFF or frequency shift, then re-check settling.
Mapped: H2-3 (Temp chain) · H2-7 (Control behavior) · H2-8 (UI coupling)
2) Pressure reads normal but flow is low—what two signals separate clog vs sensor error?
Use pressure ripple and flow pulse statistics to distinguish hydraulic restriction from measurement/capture failure.
- First 2 measurements: (1) P_ripple presence and shape (pump stroke signature); (2) flow pulse interval histogram (missed pulses/long-tail gaps).
- Discriminator: Strong, consistent P_ripple but missing/erratic pulses → flow capture/connector/EMI; high pressure with low flow and plausible pulses → clog/scale/valve restriction.
- First fix: Correlate pump command → P_ripple → pulses; if pulses fail, add conditioning (Schmitt/comparator) or improve wet-connector robustness.
Mapped: H2-4 (Pressure/flow chain) · H2-10 (Decision tree)
3) Pump is loud and pressure ripples—what waveform proves mechanical vs electrical cause?
Differentiate “drive-induced ripple” from “mechanical/air ingestion ripple” by checking phase-lock to the drive event.
- First 2 measurements: (1) Pump drive waveform (current/command timing); (2) pressure ripple dominant frequency and phase stability vs drive.
- Discriminator: Ripple frequency/phase tightly locked to drive timing → electrical/drive or supply interaction; ripple drifting or bursty without lock → air bubbles, inlet restriction, or mechanical instability.
- First fix: Hold drive constant for a short window and observe whether ripple remains coherent; then adjust drive current limit or check inlet/priming evidence.
Mapped: H2-5 (Drive waveforms) · H2-4 (Ripple evidence) · H2-10 (Isolation)
4) Machine resets exactly when the pump starts—what are the first two probes?
Most “pump-start resets” are brownout or EMI-triggered resets. The first step is to prove which bucket applies.
- First 2 measurements: (1) Vlogic_min at the pump-start edge; (2) BOR/reset-cause flag and brownout counter alignment to the event.
- Discriminator: Vlogic dips below UVLO and BOR increments → power path/transient response; no dip but reset persists → EMI/ground bounce/reset-line susceptibility.
- First fix: Separate pump start from heater switching, then re-check Vlogic_min; add hold-up/decoupling or improve return path shielding.
Mapped: H2-6 (Power) · H2-5 (Drive events) · H2-9 (Log counters)
5) Heater “sticks on” occasionally—how to detect a triac/SSR fault safely?
Stuck-on faults must be detected by command-to-response mismatch plus independent evidence (temperature rise or current proxy), without bypassing safety protections.
- First 2 measurements: (1) Heater OFF command timestamp vs continued temperature rise slope; (2) stuck-on status bit / event log (if available) or heater current proxy evidence.
- Discriminator: Command OFF but dT/dt remains positive for an abnormal window → potential triac/SSR short or dv/dt misfire; command OFF with noisy spikes only → measurement coupling.
- First fix: Add “OFF-state plausibility” check and latch a fault; verify triac trigger integrity and dv/dt immunity.
Mapped: H2-5 (Heater control) · H2-9 (Self-test bits) · H2-10 (Safety isolation)
6) Over-temp trips mid-brew—sensor drift or real overheating? What evidence decides?
Real overheating usually correlates with abnormal flow/pressure (low cooling flow). Sensor drift often correlates with switching noise or reference/ground instability.
- First 2 measurements: (1) Flow and pressure trend in the trip window (does flow collapse?); (2) temperature waveform vs switching events (pump/valve/heater edges).
- Discriminator: Flow drops and pressure behavior changes → true overheat risk from restriction/scale; normal flow/pressure but noisy temp jumps → sensing chain artifact or placement lag.
- First fix: Apply plausibility checks (temp rising without flow evidence) and tune profile to avoid concurrent high-load switching.
Mapped: H2-4 (Flow/pressure) · H2-3 (Temp chain) · H2-7 (Profiles) · H2-10
7) Flow meter pulses are missing—EMI pickup or wet connector? Fast discriminator?
Pulse capture failures can be event-correlated (EMI/ground bounce) or environment-correlated (wet connector/contact intermittency). The fastest discriminator is correlation.
- First 2 measurements: (1) Pulse interval histogram (long-tail gaps vs random dropouts); (2) timing correlation to PWM/backlight, valve flyback, and heater switching edges.
- Discriminator: Dropouts aligned to switching edges → EMI/coupling; dropouts tied to moisture/handling with weak event correlation → connector/contact reliability.
- First fix: Add Schmitt conditioning and blanking, improve connector sealing/strain relief, and re-run the histogram under controlled switching states.
Mapped: H2-4 (Pulse integrity) · H2-8 (UI noise) · H2-5 (Flyback) · H2-10
8) Descale cycle never finishes—what plausibility checks prevent false fail?
Descale state machines should not “fail closed” on a single noisy sensor. Plausibility checks prevent false aborts when actuation evidence is healthy.
- First 2 measurements: (1) Command → response chain: pump command, P_ripple presence, and flow pulses; (2) heater command vs dT/dt consistency.
- Discriminator: Actuation evidence exists but one sensor goes implausible → measurement chain issue; no actuation evidence → drive/water-path problem.
- First fix: Gate failures on multi-signal consistency (pressure+flow+temp) and log a snapshot (phase ID + key signals) before aborting.
Mapped: H2-7 (Profiles/state) · H2-9 (Self-test/log) · H2-10 (Isolation)
9) Touch keys ghost during heating—PWM coupling or ground bounce? What to measure?
Ghost touches typically come from periodic coupling (PWM/backlight) or impulsive coupling (high-current switching and ground bounce). Distinguish by frequency alignment.
- First 2 measurements: (1) Touch false-trigger timestamps vs backlight PWM frequency/phase; (2) ADC noise or reference movement aligned to heater/triac edges.
- Discriminator: Strong same-frequency correlation → PWM coupling; edge-aligned bursts → ground bounce/return-path issues.
- First fix: Change PWM frequency or temporarily disable PWM, then schedule touch/ADC sampling away from switching edges; verify improvement with event correlation.
Mapped: H2-8 (UI interference) · H2-6 (Power/ground) · H2-3 (ADC noise)
10) GFCI/RCD trips sporadically—most common leakage paths in wet appliances?
Intermittent RCD/GFCI trips usually correlate with heater operation and moisture/contamination paths. The goal is to isolate “heater/leakage” vs “wiring/connector contamination” patterns.
- First 2 measurements: (1) Event correlation: trip timing vs heater ON, steam exposure, and post-descaling moisture; (2) log of abnormal resets/noise around the same window (can indicate insulation degradation impacts).
- Discriminator: Trips only during heater energization → heater insulation/leakage path likely; trips after moisture events with variability → contamination/creepage on harness/terminals.
- First fix: Enforce safety chain diagnostics and qualified insulation/leakage inspection; do not bypass protection.
Mapped: H2-6 (Safety chain) · H2-10 (Field reliability)
11) Pressure overshoots on pre-infusion—control tuning issue or valve lag?
Overshoot can come from aggressive pump ramp (control profile) or delayed valve response (actuator lag). Timing alignment between commands and pressure is decisive.
- First 2 measurements: (1) Pump command ramp vs pressure rise (time alignment); (2) valve command edges vs pressure step/relief response (lag measurement).
- Discriminator: Overshoot tracks pump command slope → tuning/profile issue; pressure changes occur late or step-like after valve commands → valve lag or flyback/drive behavior.
- First fix: Freeze valve strategy and soften pump ramp; if overshoot persists, validate valve actuation with a commanded toggle and expected ΔP/ΔFlow step.
Mapped: H2-7 (Profiles) · H2-5 (Valve drive) · H2-4 (Pressure evidence)
12) After months, pressure baseline drifts—what calibration strategy avoids frequent re-trim?
Baseline drift can be sensor/ADC reference drift or water-path aging. A robust approach uses opportunistic zeroing plus plausibility checks, not frequent blind re-trims.
- First 2 measurements: (1) Zero-window pressure reading vs temperature/time (drift signature); (2) correlation to usage counters (pump starts, valve cycles, over-temp events) and descale history.
- Discriminator: Drift strongly tracks temperature → sensor/reference drift; step-like changes after usage events → water-path/valve/OPV aging or contamination.
- First fix: Implement “safe zero window” calibration with versioned coefficients + CRC, and gate updates with multi-signal plausibility checks.
Mapped: H2-9 (Calibration/logging) · H2-4 (Pressure chain) · H2-10 (Root-cause buckets)
Cite this figure
Suggested citation:
Suggested citation:
ICNavigator — Coffee Maker Electronics — Figure F12 (FAQ Evidence Map) — /coffee-maker-electronics — Accessed YYYY-MM-DD
