Engineering· · 5 min read
What chip for what kind of device
Plugged in or on a battery, one device or hundreds, standing still or moving: the kind of device picks the chip. Here is how we match them.
By Alessio Grespi, Founder & CEO
Every connected device has a small chip at its heart that runs it and talks to the outside world. Which one we use depends on what the device is. Plugged in and on Wi-Fi: an ESP32. Lots of battery sensors in one building: a RAK3172. One device on its own, or one that moves: a Nordic nRF9151. Something that talks to a phone or sits in a smart building: a Nordic nRF54L.
Each chip is built around one way of getting data out, so choosing the chip is mostly choosing the radio. We wrote about that choice in LoRaWAN, cellular, Wi-Fi or Matter. This post is the next step: once you know the kind of device, which chip goes inside it.
Plugged in, and doing real work: ESP32-S3
If the device has mains power and needs to think for itself (a camera, a screen, something that listens or recognises a pattern before it sends anything), the ESP32-S3 is the usual answer. It is fast for its size, has Wi-Fi and Bluetooth built in, costs little, and has one of the biggest communities of any chip, so most problems have been solved by someone already.
What you pay with: power. Sending over Wi-Fi, it draws about 70 times the current of the Bluetooth chip further down this page. On a wall supply that does not matter. On a small battery it does.
It is our pick for a mains-powered device that does some processing on the spot.
A simple plugged-in sensor on Wi-Fi: ESP32-C3, or the C6
For a device that only needs to take a reading and send it over Wi-Fi, the ESP32-C3 is the smaller, cheaper sibling. The ESP32-C6 does the same and also speaks Thread and Zigbee, the radios behind a lot of smart-building kit and the Matter standard.
What you pay with: Wi-Fi itself. It still needs mains power or a large battery, the building's Wi-Fi password, and the IT department's permission. That last one is why the products we sell through contractors never touch the building's network.
Lots of battery sensors in one building: RAK3172
When a site needs dozens of sensors that run for years on a battery, we use LoRaWAN, and the RAK3172 is the module we build on. It sends small readings a long way on very little power, to one gateway that serves the whole building.
What you pay with: a gateway on every site, messages measured in bytes rather than megabytes, and limited room for clever software on the device. For a sensor that reports a temperature every fifteen minutes, none of that matters.
Our water hygiene sensor node is built on the RAK3172. It reads four temperature probes and is the product contractors resell under their own brand.
One device on its own, or one that moves: nRF9151
A device in a field cabinet, on a vehicle or on an animal has no gateway nearby. It needs the mobile network. Nordic's nRF9151 puts a low-power mobile modem and GPS in one small package, so the device can report from anywhere with signal.
What you pay with: a SIM and a data plan in every device, and coverage that varies from one network to the next. Battery life depends on the network letting the device sleep properly, so we check the actual site before committing.
Our tracking tags are cellular and built on Nordic: the first on the nRF9151, the current one on a Nordic Bluetooth chip with a separate mobile modem.
Talks to a phone, or sits in a smart building: nRF54L
For something small that talks to a phone, a hub or other devices in the same building, Nordic's Bluetooth chips are the standard choice. The newer nRF54L series has the lowest sleep draw of anything in this post. The older nRF52840 is still everywhere and works well. Both also speak Thread, so they suit Matter devices too.
What you pay with: range. Bluetooth covers a room or a building, not a site, so something nearby has to pass the data on.
At a glance
| Kind of device | Chip | Why | The catch |
|---|---|---|---|
| Plugged in, does processing | ESP32-S3 | Fast, Wi-Fi built in, huge community | Hungry on power |
| Plugged in, simple sensor | ESP32-C3 or C6 | Cheap; the C6 also speaks Thread | Needs the building's Wi-Fi |
| Many battery sensors on one site | RAK3172 | Years on a battery, one gateway per site | Gateway needed, small messages |
| On its own, or moving | nRF9151 | Mobile network and GPS built in | SIM and data plan in every device |
| Talks to a phone or hub | nRF54L | Lowest sleep power | Short range |
Why sleep is the number that matters
A sensor spends nearly all its life asleep, waking for a moment to take a reading and send it. So the most useful figure on a datasheet is what the chip draws while it sleeps.
Asleep for a whole year, at the figures the makers publish: the nRF54L uses about 7 mAh, the RAK3172 about 15, the nRF9151 about 24 and the ESP32-C3 about 44. A typical AA cell holds a couple of thousand. So sleep alone does not flatten a battery. What decides battery life is how often the device wakes, how long its radio stays on, and the rest of the board.
The chip decides whether a device can live on a battery. How often it talks decides for how long.
What we build on
Our water hygiene node runs on a RAK3172. Our tracking tags run on Nordic. For anything else, tell us what you need to measure and where: a built-to-spec job is how new devices get built, and we choose the chip once we know the site.
The numbers, for engineers
Chip-level figures at the conditions in each datasheet. A real board adds a regulator, sensors and leakage, which often cost more than the chip.
| Part | Core | Memory | Radios | Lowest useful sleep | Radio current |
|---|---|---|---|---|---|
| ESP32-S3 | 2× Xtensa LX7, 240 MHz | 512 KB SRAM | Wi-Fi 4, BLE 5 | 7 µA deep sleep, RTC memory on | 340 mA TX at 21 dBm |
| ESP32-C3 | RISC-V, 160 MHz | 400 KB SRAM | Wi-Fi 4, BLE 5 | 5 µA deep sleep, RTC timer and memory | 335 mA TX at 21 dBm |
| ESP32-C6 | RISC-V 160 MHz + LP core 20 MHz | 512 KB SRAM | Wi-Fi 6, BLE 5, 802.15.4 | 7 µA deep sleep, RTC timer and LP memory | 354 mA TX at 21 dBm |
| nRF9151 | Cortex-M33, 64 MHz | 256 KB RAM, 1 MB flash | LTE-M, NB-IoT, GNSS | 2.7 µA PSM floor at 3.7 V | Up to 23 dBm |
| nRF52840 | Cortex-M4F, 64 MHz | 256 KB RAM, 1 MB flash | BLE, 802.15.4, NFC | 1.5 µA System ON, RTC wake, 3 V | 4.8 mA TX at 0 dBm |
| nRF54L15 | Cortex-M33, 128 MHz | 256 KB RAM, 1.5 MB RRAM | BLE, 802.15.4, NFC | 0.8 µA System OFF, RTC on, 3 V | 4.8 mA TX at 0 dBm |
| RAK3172 (STM32WLE5) | Cortex-M4, 48 MHz | 64 KB RAM, 256 KB flash | LoRa (sub-GHz) | 1.69 µA module sleep at 3.3 V | 87 mA TX at 20 dBm |
Sources
- Espressif, ESP32-S3 datasheet v2.2
- Espressif, ESP32-C3 datasheet v2.5
- Espressif, ESP32-C6 datasheet v1.6
- Nordic Semiconductor, nRF9151: product page and product specification
- Nordic Semiconductor, nRF52840: product page and product specification
- Nordic Semiconductor, nRF54L15 product page
- STMicroelectronics, STM32WLE5 datasheet DS13105
- RAKwireless, RAK3172 datasheet