Deploying a remote IoT data logger sounds straightforward — until you factor in power constraints, unpredictable weather, and the cost of maintenance visits to a location 200 km away.
For engineers working on industrial remote monitoring, water utilities, environmental sensing, or agricultural automation, battery life and rugged connectivity are the two factors that make or break a deployment.
This article breaks down how the NORVI EC-M12-BC-C6-C-A solves both — and what hardware decisions actually drive multi-year field life.
Why Most Remote Loggers Fail in the Field
Here's the uncomfortable truth: most IoT sensors consume very little power during operation. The real power draw comes from cellular transmission — and this is where many logger designs fail.
Older 2G/3G modems draw hundreds of milliamps during data bursts. On a standard 6,000 mAh lithium pack sending readings every 15 minutes, you're looking at months, not years.
The root problems are almost always:
- Wrong modem technology — GPRS/3G radios burn 5–10× more power than modern LPWAN alternatives.
- Aggressive MCU idle current — mainstream microcontrollers don't have true ultra-low-power sleep modes
- Wrong battery chemistry — alkaline and lithium-ion both suffer from high self-discharge and poor cold-weather performance
Modern low-power IoT standards like LTE-M (Cat-M1) and NB-IoT were developed precisely to address the modem problem. Combined with the right MCU and battery chemistry, multi-year field life becomes achievable.
The Hardware Stack: Key Decisions
MCU: STM32L072CZT6TR
The logger runs on the STM32L072 — part of STMicroelectronics' ultra-low-power L0 family. This is a deliberate choice. The L072 is not the fastest or most capable MCU you could put in an IoT device; it's the one that draws the least current between measurement cycles.
Multiple low-power modes allow the processor to dramatically reduce draw while waiting to take the next reading. For a logger sampling every few minutes and transmitting every hour, the MCU spends the vast majority of its time in deep sleep. That idle current matters far more than clock speed.
Battery: 38,000 mAh LiSOCl₂
The device uses two ER34615H lithium thionyl chloride cells (19,000 mAh each) for a combined 38,000 mAh capacity.
LiSOCl₂ is worth understanding if you're specifying hardware for field deployments:
| Chemistry | Self-Discharge / Year | Cold Weather | Capacity |
|---|---|---|---|
| Alkaline | ~3–5% | Poor (capacity drops sharply) | Moderate |
| Li-ion | ~2–3% | Moderate | High |
| LiSOCl₂ | ~1% or less | Excellent | Very high |
For a device that may sit in a field cabinet through 5–10 winters, LiSOCl₂ is the correct answer. The chemistry is non-rechargeable, which some engineers see as a limitation — but for a true low-power deployment, it's a feature: no charging circuitry, no charge cycle degradation, no BMS complexity.
Cellular Modem: SIMCOM A7672
The A7672 supports LTE Cat-M1, NB-IoT (NB1 and NB2), and GSM/GPRS fallback — a multi-mode approach that matters for deployments where network availability varies by region or operator.
Band support covers B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B26/B28/B39, plus quad-band GSM. In practice, this means you're not locked to a single operator or region.
Data rates are well-matched to the use case:
- LTE Cat-M1: up to 588 kbps DL / 1,119 kbps UL
- NB-IoT: up to 26 kbps DL / 62.5 kbps UL
For a logger sending timestamped sensor readings every 15–60 minutes, NB-IoT bandwidth is more than sufficient. And NB-IoT's deep penetration characteristics make it valuable for underground or basement installations where LTE signal is weak.
The 4–20 mA Inputs: Industrial Standard, Implemented Properly
The 4–20 mA current loop is the backbone of industrial instrumentation — pressure transmitters, flow meters, level sensors, temperature probes, and hundreds of other field devices. Its noise immunity over long cable runs makes it ideal for outdoor deployments where signal integrity matters.
The EC-M12-BC-C6-C-A provides:
- 2 analog inputs (0–20 mA range, 26V DC max)
- ADS1115 16-bit ADC over I2C — high-resolution conversions
- Configurable sensor excitation supply: 12V / 5V / 3.3V outputs
That last point is significant. Many loggers require separate field power supplies for 2-wire transmitters. Having a configurable excitation supply built into the logger simplifies wiring considerably and reduces the BoM for a deployment.
Local Storage and Time Integrity
Two features that often get overlooked in logger specifications — and that cause real pain in the field:
DS3231 RTC — The DS3231 is a temperature-compensated real-time clock with ±2 ppm accuracy. Even through cellular outages or power interruptions, timestamps remain accurate. This matters when you're stitching together time series data from multiple loggers.
MicroSD card slot (SPI) — When connectivity is lost — due to network outage, coverage gaps, or cellular module failure — the logger buffers readings locally. When connectivity is restored, the buffered data uploads, preserving continuity in your time series. Without local storage, you get gaps. Gaps in environmental or industrial monitoring data are often unacceptable.
RS-485 (half-duplex) is also available, opening up Modbus RTU integration for deployments where you need to pull data from multiple sensors on a shared bus.
Enclosure and Environmental Specs
IP Rating: IP67 (fully dustproof, 1m immersion)
Operating Temp: –40°C to +85°C
Enclosure: ABS + Polycarbonate
Mounting: Wall / Pole
Connector: M8 12-pin with cable gland
Dimensions: 146 × 90 × 50 mm
Shock: 30g operating / 50g non-operating (11ms)
Certifications: CE (EN 61131-2:2007, EN 61010-1:2010)
IP67 is the minimum you should specify for any outdoor exposed installation. The –40°C lower bound matters for cold-climate deployments — and it's where LiSOCl₂ chemistry earns its place, since alkaline cells lose a significant fraction of their rated capacity at sub-zero temperatures.
Checklist: Evaluating Any Long-Life IoT Logger
When you're specifying a logger for a multi-year unattended deployment, five areas determine real-world performance:
- Battery chemistry — LiSOCl₂ for long life and cold weather; check self-discharge spec
- Total capacity — calculate your expected current budget and verify runtime
- MCU idle current — look for dedicated ultra-low-power MCU families (STM32L0/L4, nRF9160, etc.)
- Modem technology — LTE-M or NB-IoT over GPRS/2G/3G for meaningful power reduction
- Local storage — microSD or equivalent; essential for maintaining data integrity through outages
- IP rating — IP67 minimum for outdoor; check operating temperature range against your environment
Use Cases Where This Architecture Makes Sense
- Water utilities — pressure and flow monitoring across distribution networks
- Environmental monitoring — river level, soil moisture, air quality nodes
- Agriculture — irrigation pump monitoring, tank level sensing
- Oil & gas — remote well-head pressure and temperature logging
- Smart cities — utility metering, infrastructure health monitoring
- Industrial assets — vibration, temperature, pressure on remote plant
The common thread: locations with no mains power, intermittent maintenance access, and a requirement for continuous data.
Summary
Genuine multi-year battery life in a cellular IoT logger requires every layer of the hardware stack to work together. The NORVI EC-M12-BC-C6-C-A shows what that looks like in practice:
- 38,000 mAh LiSOCl₂ capacity (2× ER34615H)
- STM32L072 ultra-low-power MCU
- SIMCOM A7672 LTE-M / NB-IoT modem with GSM fallback
- 2 × 4–20 mA industrial analog inputs with ADS1115 16-bit ADC
- 1 x RS-485
- Built-in sensor excitation (12V/5V/3.3V)
- DS3231 RTC + microSD local storage
- IP67 enclosure, –40°C to +85°C operating range
- CE certified for industrial environments
For more details or to request a datasheet: norvi.io
Top comments (0)