Bike Pump Memory Function: How Preset Storage Works

Document Overview

TL;DR The ETENWOLF S0’s memory function stores up to 4 custom pressure presets in non-volatile EEPROM, so your saved values survive power-off without any battery backup. For a household running a road bike at 100 PSI, a mountain bike at 30 PSI, a motorcycle at…

Document type

Certification Report

Prepared by

Daniel Wright

Published

June 3, 2026

Last reviewed

June 3, 2026

Topics

Bike & Motorcycle Pumps

TL;DR

The ETENWOLF S0’s memory function stores up to 4 custom pressure presets in non-volatile EEPROM, so your saved values survive power-off without any battery backup. For a household running a road bike at 100 PSI, a mountain bike at 30 PSI, a motorcycle at 36 PSI, and a scooter at 50 PSI, that means zero re-entry between inflation sessions — just select and go.

How the S0 Stores Presets: EEPROM Architecture and Write Endurance

At the core of the S0’s memory system is a dedicated EEPROM (Electrically Erasable Programmable Read-Only Memory) cell on the microcontroller board. Unlike SRAM, which loses its state the instant power is cut, EEPROM retains data indefinitely without any charge. We chose EEPROM over flash storage for this application because EEPROM supports byte-level writes — you can update a single pressure value without erasing an entire memory block. That matters when a user is adjusting a preset value one PSI at a time.

The S0 allocates 4 addressable preset slots, each storing a 16-bit integer representing the target pressure in 0.1 PSI resolution. The write cycle is triggered automatically when the user confirms a new value and releases the SET button. From a hardware standpoint, the EEPROM cells we specify are rated for a minimum of 100,000 write/erase cycles per address. At realistic usage — say, one preset update per week — that yields over 1,900 years of functional life at that address. Write endurance is simply not a limiting factor for this use case.

On power-up, the microcontroller reads all 4 preset slots and the last-used slot index from EEPROM into working registers in under 5 milliseconds. The display shows the last-used preset value before the user touches any button. This last-used recall behavior is not just a convenience feature — it prevents the most common inflation error we see in field feedback: users forgetting which pressure they inflated to last and starting a session at the wrong target.

The pressure sensing subsystem that reads against these stored presets uses a piezoresistive MEMS sensor, calibrated to ±1 PSI accuracy across the operating range of 0–150 PSI. For context on how that accuracy specification relates to ANSI B40.7 grade classifications, see our detailed breakdown in Understanding ANSI B40.7 Accuracy Grades for Digital Tire Pressure Gauges.

Setting and Recalling Presets: Workflow and Button Logic

The S0 uses a 3-button interface: MODE cycles through the 4 preset slots, UP/DOWN adjusts the target value in the active slot, and SET confirms and writes to EEPROM. Here’s the exact sequence:

1. Power on — the unit displays the last-used preset (e.g., Slot 1 at 100 PSI).
2. Press MODE to cycle to the desired slot (Slots 1–4, indicated by a slot index on the display).
3. Hold SET for 2 seconds to enter edit mode. The pressure value begins blinking.
4. Use UP/DOWN to adjust the target. Each press increments or decrements by 1 PSI; holding either button triggers auto-scroll at 5 PSI/second.
5. Press SET once to confirm. The display stops blinking and the value is written to EEPROM immediately.
6. Attach the hose chuck, press the trigger — the inflator runs until the live pressure reading matches the stored preset, then auto-stops.

We designed the hold-to-edit entry (step 3) deliberately. A 2-second hold requirement prevents accidental preset overwriting when a user is simply cycling through slots to check values. In early firmware prototypes, a single press entered edit mode, and we saw unintentional writes in roughly 12% of test-bench button sequences. The hold threshold dropped that to near zero.

For multi-bike households, the recommended slot assignment strategy is by vehicle category rather than by individual bike. Assign Slot 1 to road/performance bikes (typically 90–120 PSI), Slot 2 to mountain/gravel bikes (25–40 PSI), Slot 3 to motorcycles (32–42 PSI), and Slot 4 to a wildcard — scooters, cargo bikes, or seasonal use cases. This way, the slot index itself carries meaning even without a label display.

The auto-stop pressure control system that acts on these presets is explained in depth at Understanding Auto-Stop Pressure Control in Tire Inflators.

Preset Accuracy Across Temperature: What Changes and What Doesn’t

A question we get regularly from technical buyers: does a preset value shift if the unit is cold? The short answer is no — EEPROM data is temperature-independent. A value written at 25°C reads back identically at -10°C or 50°C. The stored integer doesn’t drift.

What does change with temperature is the MEMS pressure sensor’s output offset. We compensate for this in firmware using a two-point temperature correction table stored alongside the presets. During our thermal validation, we cycled units between -10°C and 50°C across 80 thermal cycles while monitoring pressure reading deviation. At -10°C with a 36 PSI reference pressure (traceable to NIST calibration standards), uncorrected sensor output drifted up to +2.3 PSI. After applying the firmware temperature correction, deviation stayed within ±1 PSI across the full thermal range.

This is important for winter use: the preset you saved for your motorcycle tire at 36 PSI will still auto-stop at 36 PSI in a cold garage. The correction runs transparently. For a fuller picture of cold-weather inflation behavior, see Winter Tire Inflation: How Cold Weather Affects Inflator Performance.

Preset Comparison: S0 vs Common Inflation Workflows

The preset recall workflow eliminates the re-entry step entirely for repeat inflation tasks. Over a cycling season, a rider inflating both tires before every ride (5 rides/week, 30-week season) saves an estimated 75–125 minutes of setup time compared to manual re-entry — not a dramatic number in isolation, but the reduction in cognitive friction is the real value. A tool you don’t have to think about gets used more consistently, and consistent tire pressure is the actual safety outcome.

According to NHTSA, underinflated tires are a contributing factor in a significant share of tire-related crash fatalities annually. The friction cost of manual pressure entry is one reason riders skip pre-ride checks.

Maintenance & Best Practices

The memory system itself requires no maintenance — EEPROM is passive and sealed. The practices that keep the S0 functioning accurately over time are focused on the sensor and the mechanical components.

Sensor accuracy verification: Every 6 months or 500 inflation cycles, verify your stored preset values against a calibrated reference gauge. Use a quality digital gauge (see the ETENWOLF T600 Digital Tire Pressure Gauge: Accuracy & Usage Guide for a unit you can trust) and inflate a tire to a stored preset, then cross-check. If deviation exceeds ±2 PSI, recalibrate by adjusting the preset value to compensate, or contact us for a sensor offset reset.

Chuck seal inspection: Inspect the rubber valve chuck seal every 3 months. A degraded seal allows bleed-back during disconnect, making the inflated tire read slightly low. Replace if you see cracking or flattening. Replacement seals are available as spare parts.

Storage temperature: Store the S0 between -20°C and 60°C. Temperatures above 60°C (e.g., a hot car trunk in summer) won’t corrupt EEPROM data but can degrade the lithium cell over time, reducing the charge capacity available per session.

Firmware updates: If ETENWOLF releases a firmware update for the S0, apply it — future releases may refine the temperature correction table based on expanded field data.

Hose care: Coil the hose loosely after use. Tight coiling over years fatigues the hose wall at the connector junction, which is the #1 mechanical failure point we see in returned units.

Frequently Asked Questions

Q1: Will my saved presets be lost if the battery fully drains?
A: No. Presets are stored in EEPROM, which is non-volatile — it holds data without any power supply. A fully drained battery has no effect on saved values.

Q2: Can I store different unit formats — PSI for one slot and BAR for another?
A: All 4 slots store values in the unit currently selected on the device. The unit setting (PSI, BAR, kPa, kg/cm²) applies globally, not per-slot. If you switch units, the stored numbers remain the same integers but are now interpreted in the new unit — so reconfigure all 4 slots after a unit change.

Q3: How precise is the auto-stop cutoff relative to my stored preset?
A: The auto-stop engages within ±1 PSI of the stored target value under normal operating conditions (10°C–40°C ambient). At temperature extremes, firmware compensation keeps it within ±1 PSI as well, based on our -10°C to 50°C thermal validation data.

Q4: Does the S0 comply with any measurement accuracy standards?
A: The S0’s pressure sensor is calibrated against NIST-traceable reference standards at the factory. The ±1 PSI accuracy spec aligns with the ANSI B40.7 Grade B accuracy class for digital pressure gauges. Each unit is tested before shipment. The S0 also carries CE and RoHS certifications.

Q5: My preset seems to overshoot by 2–3 PSI consistently. What’s happening?
A: This is almost always a chuck seal bleed-back issue, not a sensor or memory error. When the chuck disconnects after auto-stop, a worn seal allows a small amount of air to escape before the valve closes, making the final tire pressure read lower than the target — which causes you to re-run and overshoot. Inspect and replace the chuck seal first. If the overshoot persists after a seal replacement, the sensor offset may need recalibration; contact our support team.

---

Published by ETENWOLF Technical Team | Request a quote