Most connectivity problems on an industrial site aren't RF problems, they're organizational ones. The plant Wi-Fi is IT-guarded, the pump house is out of range, and the machine you're shipping to a customer has no idea what network it'll land on. The fix a lot of teams land on eventually is the same one: stop depending on someone else's network and put a modem on the board.
This is a rundown of how that plays out in practice across four device classes, LTE vs LTE-M vs NB-IoT, and the modems that actually ship in each. Every part number below is cross-checked against live datasheets, not written from memory.
The radio decision, before the product decision
Four radio classes cover almost every industrial deployment. Pick the radio for the job first, then match a product to it.
- 4G LTE (Cat 1 / Cat 4) — highest data rate, lowest latency. Use it for real-time control, heavy MQTT publish rates, or anything that can't tolerate a slow uplink.
- LTE-M (Cat-M1) — a middle ground. Handles mobility, still reasonable on power, more headroom than NB-IoT for sensors that need it.
- NB-IoT (Cat-NB1) — best coverage penetration, lowest power draw, worst throughput. The right fit for fixed, low-data, battery-powered nodes.
- 2G fallback — legacy, but still the coverage floor in some regions, and useful as a last-resort path to keep OTA/debug access alive when NB-IoT roaming is patchy.
Modem-to-product mapping
Four modems, four different jobs. This is the part worth checking before you spec a BOM:
Four device classes, one design principle
NORVI GSM — modem built into the PLC
A DIN-rail controller (9–32V DC) with the cellular modem on the same board as the I/O. Nine I/O configurations across relay, transistor, and analog outputs. Ships in 4G LTE (-L, Quectel EC25) and 2G (-G, SIMCom SIM800) variants, the latter aimed at regions where 2G is still the coverage floor. Backup links: Wi-Fi and Ethernet. This is the pick when you want the controller itself online with no separate gateway box.
NORVI X — modular PLC, cellular on the CPU
ESP32-S3 dual-core at 160MHz, up to 200 I/O points via hot-swap modules, 24V DC panel power. Every CPU variant ships with Ethernet, RS-485, Wi-Fi, and Bluetooth as standard; the cellular CPUs (X2 with SIMCom A7672, X3 with Quectel EC25) add two antenna connections on top of that. The base X1 CPU has no modem at all if you don't need one. This is the lineup's answer when you want cellular alongside Ethernet as fallback, or a full expandable gateway.
EC-M12 — battery-powered, no grid power required
An STM32L072 ultra-low-power MCU in an IP67 sealed node, running SIMCom SIM7070 (NB-IoT/LTE-M/2G fallback) against a 38,000mAh Li/SOCl2 pack rated for 5+ years unattended. Five I/O configurations: dual 4-20mA analog, RS-485/Modbus, dual digital, mixed digital+analog, and strain gauge. Notably it uses an internal antenna, a deliberate tradeoff to keep the IP67 seal intact rather than punching a hole for an external connector.
Agent One — Modbus/sensor bridge, no PLC replacement
A low-I/O node built to wire in parallel to an existing Modbus network or sensor set and push straight to MQTT. SIM7600 covers the 4G LTE variant family, with NB-IoT and LoRa variant families for power- or range-constrained deployments. If the goal is cellular telemetry on equipment that already exists, this skips replacing anything.
Antenna, SIM, and carrier notes that actually matter in the field
- DIN-rail devices (GSM, X) ship with external antennas: SMA for cellular, RP-SMA for Wi-Fi/Bluetooth. X carries two separate antenna connections.
- EC-M12 uses an internal antenna to preserve the IP67 rating, so there's nothing external to break, unseal, or get stolen.
- All cellular NORVI devices take a nano SIM; eSIM is available on NORVI X and EC-M12.
- Mount external antennas outside metal enclosures. A steel panel behaves like a Faraday cage, and cellular antennas should stay clear of VFDs and contactors to cut EMI.
- NB-IoT roaming is genuinely patchy, it's a network-level reality, not a device limitation, which is why 2G or 4G fallback paths matter for keeping an OTA/debug path alive.
- Field-tested global IoT SIM providers: 1NCE and Things Mobile.
When cellular is the wrong call
It isn't always the right answer. Skip it when the system needs to run fully offline with no future monitoring or remote-support requirement, when there's nobody on the team who can own embedded firmware work (see NORVI's GitHub for example firmware and libraries before ruling this out), or when recurring SIM costs don't make sense against a site that already has solid Ethernet or Wi-Fi. In that last case, a wired ESP32 controller does the same job for less ongoing cost.
Reference
- Full spec sheets, the modem comparison table, and datasheet links for all four device classes are maintained on NORVI's ESP32 industrial IoT controller (cellular & 4G LTE range) page, cross-checked against live product datasheets rather than written from memory.
- Documentation hub (per-device datasheets, application guides): https://norvi.io/docs/
- GitHub (firmware examples, libraries): https://github.com/NORVIControllers
- Contact / technical consultation: https://norvi.io/contact-us/
- If you're speccing a build and want a second opinion on modem choice or antenna placement, NORVI's engineering team takes free technical consultations.
Top comments (0)