← Back to the chapter · Previous detail · Next detail →
Technical detail · NFC IoT System Integration
Energy Harvesting and Battery-Less Commissioning
NFC can also power the device it configures. Energy-harvesting NFC front ends, such as NTAG devices with an I2C bridge and an energy-harvesting output, rectify the reader’s 13.56 MHz field into a small supply. That can wake a microcontroller, read a sensor, or store a short configuration record without a battery. The same tap provides the data channel and the temporary power.
That unlocks two patterns. Battery-less commissioning lets a phone wake a headless unpowered device, deliver Wi-Fi or configuration data through an NFC-to-I2C bridge, store it, and then leave normal power to run the device later. Tap-to-read lets an unpowered product wake just long enough to return a sensor value or diagnostic. A field-detection pin can also let a powered device sleep until an NFC field appears, reducing active work between taps; quiescent drain still needs a budget.
The hard engineering detail is the power budget, not the phrase “battery-less.” Treat harvested energy as a measured resource for one short transaction. A release note should show the measured harvested voltage under the final enclosure, the load current for the wake/write/sleep sequence, the worst-case write time, and whether the tap still succeeds when the user moves the phone slightly.
Do the arithmetic with measured values from the actual hardware. If the wake-and-store sequence draws 2.8 mA at 1.8 V, the load is about 5.0 mW. If the lab measurement at the planned tap position only supports 4.0 mW continuously, the design has negative steady-state margin and must not be released as battery-less commissioning. If a storage capacitor covers the shortfall, the evidence should show the capacitor voltage before and after the write, not just a successful demo video. If the final product adds a metal bracket that weakens coupling, the measurement must be repeated with that bracket installed.
Energy harvesting also changes the failure model. A normal powered gateway can retry, log locally, and use a network fallback. A battery-less label may brown out halfway through a write, so records need a version, checksum or integrity marker, and a safe “not configured” state. The mobile app should treat an interrupted tap as incomplete until it reads back the stored configuration or receives a signed confirmation through the later BLE or Wi-Fi path. That readback step prevents a field team from mistaking a partial NFC write for a commissioned IoT device.