NORVI Controllers

Compare Devices

Six product lines, one table. Toggle devices in or out, search for a spec, or isolate just the rows where models actually differ.

Accuracy check Cross-referenced directly against live datasheets for ENET-AE06-V, NORVI X CPU-ESPS3-X1, and EC-M12-BC-C6-C-A. Rows confirmed this way carry a datasheet tag. Agent One, GSM, and IIOT are families with 10 to 90 model variants each, so their rows reflect the original comparison page rather than one specific SKU, so check the exact model's datasheet before ordering. NORVI X is modular (I/O comes from separate plug-in cards, not the CPU module itself) and EC-M12 is a battery-powered IP67 telemetry node rather than a DIN-rail controller, so several rows are structurally "not applicable" for those two.

Which one do you actually need?

Five of these are line-powered DIN-rail controllers, one is a battery-powered outdoor telemetry node. The real decision usually comes down to how you're getting power and network to the panel, not the spec sheet.

NORVI XController

Choose it when: your I/O mix isn't fixed yet, or will grow. One CPU, plug in whatever combination of DI/AI/AO/relay/RTD cards the project needs, up to 200 I/O.

Skip it if you just need one fixed configuration, ENET or IIOT will be cheaper and simpler to wire.

ENETController

Choose it when: the panel already has a wired Ethernet drop and you know exactly which I/O you need (V, I, R, or T variant), no dependency on Wi-Fi or cellular signal.

Skip it if there's no Ethernet cabling to the panel location.

IIOTController

Choose it when: you have solid Wi-Fi coverage at the site and want to skip running an Ethernet cable, compact fixed I/O, same V/I/R/T logic as ENET.

Skip it if Wi-Fi is weak or contested where the panel sits, that's an Ethernet or cellular job instead.

GSMController

Choose it when: there's no LAN or Wi-Fi at the site at all, remote pump stations, mobile equipment, temporary installs, pick 2G or 4G LTE by coverage and budget.

Skip it if Ethernet or Wi-Fi is already available, cellular data plans cost more over time than either.

Agent OneController

Choose it when: you need many small, cheap nodes rather than one central controller, especially battery-powered ones (STM32L variants) or sites needing LoRa/NB-IoT for scattered sensors.

Skip it if you need one controller handling a lot of I/O in one place, that's more of a NORVI X or ENET job.

EC-M12Telemetry Node

Choose it when: there's no mains power at all, tanks, wellheads, remote agriculture, outdoor unattended sites. IP67, runs for years on its own Li-SOCl2 batteries, reports over cellular.

Not a controller, it's a 2-input sensor logger. If you need relay/transistor outputs or more than 2 inputs, this isn't the right category, look at the controllers above instead.

Differences only

How the bus works

The NORVI X CPU module talks to expansion cards over a shared I2C bus, with each card claiming a unique I2C address. A few expansion cards skip I2C entirely and wire straight to CPU GPIO pins instead, which is where the one real conflict in the lineup comes from. Four chip families sit behind the expansion cards, and each one caps how many cards of that family you can stack on one CPU.

I2C expander chips and max count per CPU

Each address-selectable chip has a fixed number of DIP-switch address slots. That slot count is the hard ceiling on how many cards using that chip can share one bus, mixed models included.

The GPIO conflict: X-DI4, X-Q4, X-UARTIO

These three cards do not use I2C. X-DI4 and X-UARTIO wire directly to the same four CPU pins (GPIO5, GPIO6, GPIO7, GPIO10), so they can never coexist. X-Q4 sits on its own pins (GPIO11 to GPIO14) and is free to pair with either of the other two, just not both at once.

Only one supported combination of these three cards can be attached to a single CPU at a time (e.g. one X-DI4 + one X-Q4), since they are pin-addressed rather than I2C-addressed and can't be multiplied the way PCA9538/PCA9555/ADS1115 cards can.

Quick reference: what can stack with what

Source: NORVI's own "NORVI X Module Mixing Possibilities" document. One inconsistency worth flagging to NORVI directly: the text describes X-RTD4 addresses as sitting in the "0x3X" range, but the address table beneath it lists the same 0x50 to 0x5F values shown for X-AQ4. Reproduced as-is below; confirm the real X-RTD4 addresses against hardware or support before wiring up 16 of them.

Order Quantity	Lead Time	Notes
Under 10 units	2–3 wks	Standard processing
10 – 100 units	4–5 wks	Mid-volume batch
Above 100 units	6+ wks	Contact us for slot