EVident Battery: EVB-⁠01 vibration sensor

EVident Battery, Electrical Engineer, then Associate Engineering Manager

A Wi-⁠Fi vibration sensor, EVident Battery's first product. I designed its board and wrote its production firmware.

Mar 2025 to Oct 2026I designed the board and wrote the production firmware

The problem

EVB-⁠01 is a battery-powered vibration sensor: a 6-⁠axis IMU (an accelerometer and gyroscope in one chip) on an ESP32-⁠S3 Wi-⁠Fi module. It samples at up to 6,666 Hz, records to 16 MB of on-⁠board flash, and serves its own web page, so a phone or laptop needs no app (product page). It is EVident Battery’s first product.

I designed the board and wrote the firmware that shipped in October 2025. The hard part was data: at the top rate the IMU sends 6,666 samples a second from each of its two sensors, and every one has to be kept while the sensor streams live over Wi-⁠Fi.

The board

The board is 30 × 25 mm. USB-⁠C charges a single Li-⁠ion cell through a linear charger, and a P-⁠channel MOSFET with a Schottky diode runs the board from whichever source is present. The slide switch sits after the point where the two join, so it turns the board off on either source while the cell still charges.

The power path

Concept schematic of the EVB-01 power path. A USB-C connector's VBUS pin feeds a +5V net. Its CC pin has a 5.1 kΩ resistor to ground. Its D+ and D− pins pass through a two-line ESD array to the microcontroller. The +5V net feeds a linear Li-ion charger, whose BAT pin charges the cell. A Schottky diode runs from +5V to the VPWR net. A P-channel MOSFET runs from the cell to VPWR, with its gate on +5V. A slide switch connects VPWR to a 3.3 V LDO, whose output is the 3V3 rail. A fuel gauge reads the cell and talks I2C. Connections: +5V joins J1 VBUS, U1 IN, D1 A; CC joins J1 CC, R1; D+ joins J1 DP, U3 I1; D− joins J1 DN, U3 I2; VBAT joins U1 BAT, BT1 +, Q1 S, U4 CELL; VPWR joins D1 K, Q1 D, S1; SYS joins S1, U2 IN; 3V3 joins U2 OUT; USB D+ joins U3 O1; USB D− joins U3 O2; +5V joins Q1 G; I2C joins U4 I2C; GND joins R1, BT1 -.

Redrawn from the shipping design with part families, not part numbers. USB-⁠C feeds 5 V to the charger and, through a Schottky diode, to the board. A P-⁠channel MOSFET connects the cell when USB is out.

  1. The CC pin's 5.1 kΩ to ground marks the board as a plain USB sink, so the source supplies the default 5 V.
  2. A two-⁠line ESD array guards the data lines between the connector and the module's native USB.
  3. With USB in, +5 V holds the P-⁠FET's gate high, so it is off and the board runs through the Schottky. With USB out, it connects the cell.
  4. The switch sits after the point where the two sources join, so it turns the board off on either one while the cell still charges.
  5. The fuel gauge reads the cell's voltage directly and shares the IMU's I2C bus.

Left out: the microcontroller, IMU, flash and LED, the bulk capacitors, a bleed resistor on +5V, and the level shifter that carries the charger's status to the microcontroller.

Explore the sensor

Two layers: the board and the web app. Click a block to see what it does. The Web app layer is a working sample of the page the sensor serves, with made-⁠up data.

Two views of the EVB-01 board, 30 by 25 mm. Top side: the ESP32-S3 module at the right edge, its antenna end 4.6 mm past the edge into a hatched keep-out; the USB-C connector at the left edge, 1 mm past it; the ESD array beside it; the flash above; the fuel gauge below; the battery pads at the lower left; the slide switch at the bottom edge, its actuator 4 mm past it; the RGB LED at the lower right. Bottom side, seen through the board: the IMU under the module, the charger mid-left, the P-FET and diode below it, the 3.3 V LDO, and the EN and BOOT test pads at the right.

Click a labeled block to see what it does and what I changed.

The board

30 × 25 mm, the board that ships in EVB-⁠01: the module on top at the right edge with its antenna past the board, and most parts on the bottom. A concept drawing, not the layout.

In this layer

  • ESP32-S3 module The Wi-⁠Fi microcontroller: two cores, PSRAM, and an antenna at one end.
  • IMU Accelerometer and gyroscope in one chip, with an on-⁠chip FIFO; up to 6,666 samples a second from each.
  • Switch Turns the board off. Its actuator overhangs the bottom edge by 4.0 mm.
  • Gauge Reads the cell's voltage to estimate its charge, on the IMU's I2C bus.
  • P-FET and diode Runs the board from USB when it is plugged in, and from the cell when it is not.
  • Charger Charges the cell from USB's 5 V. Its status line reaches the module through a level shifter.
  • LDO A linear regulator that feeds the module, the IMU and the flash from the switched rail.
  • USB-C Power in, and the module's native USB for programming.
  • Flash Holds the recordings, on the module's SPI bus.
  • EN and BOOT Two 1 mm pads on the bottom for reset and boot.
  • LED Shows the sensor's state.
  • Cell pads Where the battery's leads are soldered.

The web app

The sensor serves its whole interface from its own flash: one page of cards for settings, the live plot, recording, files and Wi-⁠Fi. This is a working sample of that page's layout with made-⁠up data; use it, and this panel explains the part you touched.

In this layer

  • Data streaming Plots acceleration and rotation on three axes each as they arrive, over a window of 1 to 40 s.
  • Recording Stream watches live. Record saves a set number of seconds to the sensor's flash, with a progress bar.
  • File manager The recording on the sensor, with its date, length and size, to download as CSV or plot in full.
  • Sensor settings Which sensors to run, the sample rate from 12.5 to 6,666 Hz, the ranges and the units.
  • Accel calibration Calibrates the accelerometer from six poses, with a live 3D view of the sensor.
  • Network manager Shows the saved network, lists nearby 2.4 GHz networks and joins one.
  • Wi-Fi setup With no network saved, a phone that joins the sensor's own access point lands here.
  • Another tab More than one browser can watch the same sensor.

ESP32-S3 module

The Wi-⁠Fi microcontroller: two cores, PSRAM, and an antenna at one end.

Antenna

The antenna end overhangs the board by 4.6 mm into a keep-⁠out that covers all four copper layers, so no copper sits under it.

6-axis IMU

Accelerometer and gyroscope in one chip, with an on-⁠chip FIFO; up to 6,666 samples a second from each.

The bus

It shares an I2C bus with the fuel gauge. Carrying both of its sensors at 6,666 Hz over that bus took a faster I2C driver, which I designed.

Slide switch

Turns the board off. Its actuator overhangs the bottom edge by 4.0 mm.

Where it sits

After the point where USB and the battery join, so it turns the board off on either source while the cell still charges.

The power path

Concept schematic of the EVB-01 power path. A USB-C connector's VBUS pin feeds a +5V net. Its CC pin has a 5.1 kΩ resistor to ground. Its D+ and D− pins pass through a two-line ESD array to the microcontroller. The +5V net feeds a linear Li-ion charger, whose BAT pin charges the cell. A Schottky diode runs from +5V to the VPWR net. A P-channel MOSFET runs from the cell to VPWR, with its gate on +5V. A slide switch connects VPWR to a 3.3 V LDO, whose output is the 3V3 rail. A fuel gauge reads the cell and talks I2C. Connections: +5V joins J1 VBUS, U1 IN, D1 A; CC joins J1 CC, R1; D+ joins J1 DP, U3 I1; D− joins J1 DN, U3 I2; VBAT joins U1 BAT, BT1 +, Q1 S, U4 CELL; VPWR joins D1 K, Q1 D, S1; SYS joins S1, U2 IN; 3V3 joins U2 OUT; USB D+ joins U3 O1; USB D− joins U3 O2; +5V joins Q1 G; I2C joins U4 I2C; GND joins R1, BT1 -.

Redrawn from the shipping design with part families, not part numbers. USB-⁠C feeds 5 V to the charger and, through a Schottky diode, to the board. A P-⁠channel MOSFET connects the cell when USB is out.

  1. The CC pin's 5.1 kΩ to ground marks the board as a plain USB sink, so the source supplies the default 5 V.
  2. A two-⁠line ESD array guards the data lines between the connector and the module's native USB.
  3. With USB in, +5 V holds the P-⁠FET's gate high, so it is off and the board runs through the Schottky. With USB out, it connects the cell.
  4. The switch sits after the point where the two sources join, so it turns the board off on either one while the cell still charges.
  5. The fuel gauge reads the cell's voltage directly and shares the IMU's I2C bus.

Left out: the microcontroller, IMU, flash and LED, the bulk capacitors, a bleed resistor on +5V, and the level shifter that carries the charger's status to the microcontroller.

The fuel gaugeLoad sharing

Fuel gauge

Reads the cell's voltage to estimate its charge, on the IMU's I2C bus.

Where it sits

On the cell itself, so it reads the cell's voltage whether the board is on or off.

The power switch

P-FET and Schottky diode

Runs the board from USB when it is plugged in, and from the cell when it is not.

How it works

With USB in, 5 V holds the P-⁠channel MOSFET's gate high, so it is off and the board runs through the Schottky diode. With USB out, the MOSFET connects the cell.

The power path

Concept schematic of the EVB-01 power path. A USB-C connector's VBUS pin feeds a +5V net. Its CC pin has a 5.1 kΩ resistor to ground. Its D+ and D− pins pass through a two-line ESD array to the microcontroller. The +5V net feeds a linear Li-ion charger, whose BAT pin charges the cell. A Schottky diode runs from +5V to the VPWR net. A P-channel MOSFET runs from the cell to VPWR, with its gate on +5V. A slide switch connects VPWR to a 3.3 V LDO, whose output is the 3V3 rail. A fuel gauge reads the cell and talks I2C. Connections: +5V joins J1 VBUS, U1 IN, D1 A; CC joins J1 CC, R1; D+ joins J1 DP, U3 I1; D− joins J1 DN, U3 I2; VBAT joins U1 BAT, BT1 +, Q1 S, U4 CELL; VPWR joins D1 K, Q1 D, S1; SYS joins S1, U2 IN; 3V3 joins U2 OUT; USB D+ joins U3 O1; USB D− joins U3 O2; +5V joins Q1 G; I2C joins U4 I2C; GND joins R1, BT1 -.

Redrawn from the shipping design with part families, not part numbers. USB-⁠C feeds 5 V to the charger and, through a Schottky diode, to the board. A P-⁠channel MOSFET connects the cell when USB is out.

  1. The CC pin's 5.1 kΩ to ground marks the board as a plain USB sink, so the source supplies the default 5 V.
  2. A two-⁠line ESD array guards the data lines between the connector and the module's native USB.
  3. With USB in, +5 V holds the P-⁠FET's gate high, so it is off and the board runs through the Schottky. With USB out, it connects the cell.
  4. The switch sits after the point where the two sources join, so it turns the board off on either one while the cell still charges.
  5. The fuel gauge reads the cell's voltage directly and shares the IMU's I2C bus.

Left out: the microcontroller, IMU, flash and LED, the bulk capacitors, a bleed resistor on +5V, and the level shifter that carries the charger's status to the microcontroller.

The power switch

Linear Li-ion charger

Charges the cell from USB's 5 V. Its status line reaches the module through a level shifter.

Where it sits

On 5 V before the switch, so the cell charges with the unit off.

3.3 V LDO

A linear regulator that feeds the module, the IMU and the flash from the switched rail.

Where it sits

After the switch, on the bottom side, so the switch cuts it on either source.

USB-C and ESD array

Power in, and the module's native USB for programming.

What it does

5.1 kΩ resistors on the CC pins mark the board as a plain USB sink, and a two-⁠line ESD array guards the data lines. The connector overhangs the left edge by 1.0 mm.

The EN and BOOT pads

16 MB NOR flash

Holds the recordings, on the module's SPI bus.

Package

A small WSON package on the bottom side.

EN and BOOT test pads

Two 1 mm pads on the bottom for reset and boot.

Why pads

The board programs over USB-⁠C, so reset and boot are needed only for recovery. A probe on the pads does that.

RGB LED

Shows the sensor's state.

Power

It is powered from a GPIO, so it draws nothing when it is off.

Cell pads

Where the battery's leads are soldered.

Assembly

The battery's leads are soldered to two plated pads, not a connector.

Live plot

Plots acceleration and rotation on three axes each as they arrive, over a window of 1 to 40 s.

What I did

I designed the live plot to draw what the full data would, pixel for pixel, and scroll smoothly on the sensor's clock.

Stream, Record and Stop

Stream watches live. Record saves a set number of seconds to the sensor's flash, with a progress bar.

What I did

A recording ends cleanly, whether it is stopped by hand or the store fills.

Downloads

The recording on the sensor, with its date, length and size, to download as CSV or plot in full.

What I did

The page fetches the recording in its compact binary form and converts it to CSV in the browser.

Sensor settings

Which sensors to run, the sample rate from 12.5 to 6,666 Hz, the ranges and the units.

What I did

Settings and units are saved on the sensor across reboots, and the page locks them while a stream or recording runs.

Calibration wizard

Calibrates the accelerometer from six poses, with a live 3D view of the sensor.

What I did

I designed it in October 2026. The result is stored on the sensor and applied to its readings.

Network manager

Shows the saved network, lists nearby 2.4 GHz networks and joins one.

What I did

Forget Network clears the saved network and restarts the sensor into its setup access point.

The setup page

With no network saved, a phone that joins the sensor's own access point lands here.

How it works

Pick a network and type its password. The sensor shows its progress, then restarts onto your network.

Several tabs at once

More than one browser can watch the same sensor.

What I did

Open tabs stay in sync: a setting changed in one shows in the others, and a recording started in one shows its progress in all. A recording runs to its end even if its tab closes.

The firmware’s design and the board’s revision history are not on this page. I can walk through them in an interview.

How I used AI

The boards and the firmware that shipped in October 2025 are my own work, done before I used AI coding tools. From February 2026 I used Claude Code for the firmware’s later work. I set the design and the number it has to hit, Claude Code writes the code to that brief, and the bench decides whether it stays.

When AI came in

Blocks: 2025: by hand (the boards, and the firmware that shipped); February to September 2026 (the I2C driver, power management, the stress harness); From October 2026 (a multi-agent workflow for the EVB-01 Pro firmware, on its page).

  • 2025: by hand to February to September 2026.
  • February to September 2026 to From October 2026.

How a change gets in: the I2C driver as the example

Blocks: Set the target (both sensors at 6,666 Hz need more than the stock driver moves); Write the code (an I2C driver run from interrupts, to my brief); Prove it on the bench (keeps up with both sensors on the bench); Accept or send back (kept once the bench agrees).

  • Set the target to Write the code: brief.
  • Write the code to Prove it on the bench: build.
  • Prove it on the bench to Accept or send back: numbers.
  • Accept or send back to Set the target: misses (dashed).
I set the target and judge the result; Claude Code writes the code in between. A change that misses its number goes back to the brief.

Results

I2C fast enough for both sensors

With both sensors at 6,666 Hz, the IMU sends close to everything a 1 MHz I2C bus can carry, and the stock driver could not keep up. I designed a driver that runs the ESP32-⁠S3’s I2C controller from interrupts, and it carries both sensors with a little room left on the bus.

I2C bus use at 6,666 Hz, accelerometer and gyroscope

Bar chart of I2C bus use with the accelerometer and gyroscope both at 6,666 Hz: the stock driver falls short of what both sensors need, and the interrupt-driven driver keeps up, just under the bus ceiling. Stock driver: falls short of the need: %; My interrupt-driven driver: keeps up: %; Line at 89.4 %: Both sensors need; Line at 100 %: Bus ceiling.

Drawn to scale as a share of the most a 1 MHz I2C bus can carry. The need is the IMU's real output, which runs a little fast.

Lower idle current

I designed the power management, and measured the same build with it off and on, on a Nordic PPK2 bench power profiler. Idle current fell by about 70 % with Wi-⁠Fi on, and by about 95 % with the radio off.

Idle current, power management off and on

Dumbbell chart of the sensor's idle current with power management on, relative to off: about 70 % lower with Wi-Fi connected and about 95 % lower with the radio off. Wi-Fi connected: about 70 % lower; Radio off: about 95 % lower.

Measured on a Nordic PPK2, the same build with power management off and on, each drawn against its own off reading.

Certification and production

I took EVB-⁠01 through CE RED, FCC Part 15B and ISED ICES-⁠003 testing as the lab contact. For 2026 I moved assembly to a contract manufacturer, and built the flashing tool used on its line.

Credit

I designed every board revision and wrote the firmware that shipped in October 2025, before I used AI coding tools. From February 2026, Claude Code wrote the firmware changes to my designs, and I proved each one on the bench. Another engineer wrote an earlier prototype firmware, and teammates restyled the web page in early 2026.