Low-Power IoT in the Military Domain: Architecture, Standards, Coatings, and Field Results

thingslog — Sat, 18 Apr 2026 20:24:09 +0000

Two active military operations are running simultaneously right now, and both are producing a very visible lesson for embedded engineers: the ability to build electronics that operate for months or years on a small battery — without maintenance, without infrastructure — has become a defining characteristic of effective military sensing.

We just finished a 10-post research series on this topic. Here is the condensed version for people who want the engineering substance without wading through 10 articles.

The core architecture: hierarchical power domains

Every ultra-low-power military sensor node — unattended ground sensor, LoRa tactical tracker, soldier-worn biometric node — is built around the same fundamental pattern:

Always-on domain       ~100–500 nA
  └─ wake-up comparator, RTC, PMIC

Intermittent domain    µA range, ms duration
  └─ MCU + ADC + sensor acquisition

On-demand domain       mA range, 100–2000 ms
  └─ LoRa TX, GNSS, camera

The always-on domain gates the intermittent domain via hardware interrupt. The intermittent domain gates the on-demand domain only when there is a decision to transmit. Nothing higher in the stack is ever left drawing quiescent current.

This is not novel — but it is the discipline that separates a node that lasts 3 years from one that lasts 3 weeks.

Practical tip: The STM32WL (first LoRa-on-chip SoC) in deep sleep draws ~1 µA. Add a TPL5110 nano-timer (35 nA) and cut power to the STM32WL entirely between events — you drop system standby to the nano-timer floor. At 35 nA from a 3000 mAh AA lithium cell, theoretical standby lifetime exceeds 9 years.

The DARPA N-ZERO result is the benchmark

DARPA's N-ZERO programme (2015–2020) set the standard everyone in military sensing is now measured against:

Before N-ZERO: unattended ground sensor lifetime = weeks to months
After N-ZERO: up to 4 years on a coin cell
Battery size reduction: 20× for equivalent lifetime

The mechanism: MEMS-based conditional wake-up receivers that exploit the energy of the incoming signal (acoustic, seismic, RF) to trigger the electronics — rather than running active electronics to wait for a signal. Zero standby power because the wake-up path is passive analog hardware, not running firmware.

Lesson for commercial IoT: the same principle applies. If your event is infrequent, a hardware comparator at 10 nA will always beat a microcontroller polling at 1 mA — by a factor of 100,000.

LoRa in military tactical applications: what the research shows

Four IEEE papers track the trajectory from 2017 to 2025:

2017 — U-LoRa at 433 MHz for soldier tracking: 5 km range in open terrain, 2 km in forest, <1 mA average draw, full node BOM under $15. The 433 MHz choice (vs 868/915) was deliberate — better foliage penetration for infantry in woodland.

2018 — LoRaWAN evaluation for tactical military use: suitable for logistics tracking and environmental sensing; not suitable for real-time sub-second latency requirements under standard LoRaWAN Class A. Conclusion: use the LoRa physical layer with a custom MAC, not LoRaWAN's civilian protocol stack.

2019 — Cyber perspective: LoRa's chirp spread-spectrum achieves negative SNR reception (−20 dB at SF12), making signals difficult to detect passively. Narrowband jamming is less effective. But standard AES-128 LoRaWAN keys are insufficient for anything above unclassified — add a hardware secure element (ATECC608B or equivalent) and application-layer AES-256.

2025 — Complete tactical system: LoRa nodes + mobile gateway + encrypted messaging + store-and-forward when backhaul is unavailable. The store-and-forward piece is the one that makes it viable in denied comms environments.

Our own field data: Antarctica

We deployed ThingsLog LPMDL-1105 loggers at the Bulgarian Antarctic Base — a seasonally unoccupied research facility on Livingston Island — for the polar winter of 2024.

The constraint set maps almost exactly to a military unattended sensor network:

Antarctic constraint	Military equivalent
No mains power, no solar	Denied environment, no resupply
7 months no maintenance access	Multi-year UGS deployment
Intermittent Starlink only	Degraded comms environment
−28 °C outdoor	Arctic theatre
No personnel	Unattended operation

Architecture:

Sensors acquire 4 channels every 15 minutes → stored to local flash
96 readings (24h) buffered per node
Once per day: LoRa gateway powers on, collects all nodes, Starlink terminal powers on, uploads to cloud
Gateway and Starlink return to powered-off state

Radio config: SF8 fixed, ADR disabled. Reason: we needed to fit 96 readings into a single payload per daily window. SF8 with our binary protocol fit the payload; SF7 ADR would have dropped us below the required capacity.

Result: Full winter dataset, zero permanent data loss, no maintenance interventions.

The paper: "Deployment of a Low-Power LoRa-Based Monitoring Network for Environmental and Building Condition Assessment in Antarctica", IEEE CompSysTech 2025.

Protective coatings: the part most IoT engineers skip

This is where field deployments actually fail. The five coating types under MIL-I-46058C / IPC-CC-830:

Type	Code	Reworkable	Temp range	Best for
Acrylic	AR	Yes (solvents)	−65 to +125 °C	General purpose
Urethane	UR	With effort	−65 to +125 °C	Fuel/chemical exposure
Epoxy	ER	No	−65 to +150 °C	Potting, permanent installs
Silicone	SR	Difficult	−65 to +200 °C	Extreme thermal cycling
Parylene	XY	No (CVD)	−200 to +125 °C	Mission-critical, miniature, marine

Parylene is deposited by chemical vapour in a vacuum chamber at room temperature — it penetrates gaps as small as 0.01 mm, is pinhole-free at 0.5 µm, and passes 144-hour salt spray (MIL-STD-810F). It's on the DoD Qualified Products List under MIL-I-46058C.

The low-power angle nobody mentions: on an uncoated PCB in a humid environment, surface leakage between adjacent conductors can reach 1–100 µA. If your sleep budget is 300 nA, that leakage is 3–300× your entire power budget. Parylene's moisture barrier eliminates this.

Standards you actually need to know

If you're building for NATO or US DoD procurement, these are the ones that matter:

Environmental:

MIL-STD-810H — the US reference. Not a rating system — a test method library. You select which methods apply based on the platform life cycle.
STANAG 4370 / AECTP-200/400/500 — the NATO equivalent. AECTP-200 for climatic, AECTP-400 for mechanical, AECTP-500 for EMC.
DEF STAN 00-35 — UK MoD. Broadly equivalent to MIL-STD-810H with UK platform tailoring data.

EMC:

MIL-STD-461G — US. CE102/RE102 for emissions, CS116/RS103 for susceptibility.
AECTP-500 — NATO equivalent.
DEF STAN 59-411 — UK equivalent.

Power:

MIL-STD-1275E — 28V DC vehicle bus. Your power supply must survive load dumps to 100V, cold-crank dips to 9V, and reverse polarity to −18V indefinitely.
MIL-STD-704F — aircraft 28V DC / 115V AC.

Components:

MIL-PRF-38535 Rev N (Feb 2026) — military IC qualification. Class G (COTS-screened, −40 to +85 °C) is the practical entry point for tactical IoT nodes.

Ingress:

IEC 60529 IP67 minimum for dismounted infantry equipment. IP68 for buried sensors. IP69K for CBRN decontamination zones.
MIL-STD-810H Method 512 (1 m / 30 min) ≈ IP67. Dual-certify both in one test campaign.

The full series

If any section above is relevant to what you're building, the full posts are on the ThingsLog blog:

Happy to go deeper on any of the architecture, protocol, or standards topics in the comments.

DEV Community: thingslog