DTU, Industrial Router or IoT Gateway: How to Choose

A DTU, industrial router and IoT gateway may all use a cellular network, but they solve different problems. Start with the field interfaces, data ownership and required local behavior. Choosing by enclosure appearance or mobile-network generation often produces either an underpowered device or unnecessary complexity.

Use a DTU for controlled transparent transmission

A DTU is suitable when one or a few serial devices must send data transparently to a known server and protocol interpretation occurs elsewhere. Confirm RS232 or RS485 requirements, connection mode, heartbeat, reconnect behavior and whether local buffering is available.

Transparent transport does not remove the need to manage addressing, serial timing and server availability. It is less suitable when many device protocols must be normalized or local decisions must continue during a WAN outage.

Use an industrial router for IP connectivity

An industrial router connects Ethernet or Wi-Fi equipment to a WAN and commonly provides firewalling, NAT, VPN, dual-SIM and remote management. It is the right choice when field devices already speak IP protocols and the main requirement is secure site connectivity.

Check LAN count, routing modes, VPN throughput, failover time, temperature range, supply and cybersecurity update policy. A router does not automatically convert Modbus RTU registers into structured cloud data.

Use an IoT gateway for acquisition and edge processing

An IoT gateway combines interfaces with protocol drivers, tag mapping, local calculation, alarms, buffering and northbound services such as MQTT or HTTPS. It suits mixed Modbus, analogue and digital devices or projects that need normalized timestamps and quality flags.

Evaluate supported devices and function codes rather than accepting a generic claim of protocol compatibility. Confirm tag capacity, scan rates, scripting limits, storage retention and how configuration and firmware are backed up.

Define availability and cybersecurity

For every option, specify what happens when the carrier, VPN or cloud platform is unavailable. Required functions may include store-and-forward, local control, dual-SIM failover and remote diagnostics. Determine whether safety or essential control must remain independent of the gateway.

Use unique credentials, restrict management access, disable unused services and document update ownership. Remote access should use an approved VPN or managed service with audit records, not an exposed administration port.

Compare lifecycle cost, not hardware price

Include engineering, protocol integration, SIM plans, cloud fees, cybersecurity maintenance, spares and site support. A simple DTU can be the most reliable choice for a narrow task; a gateway can reduce system cost when it replaces custom protocol software and repeated site visits.

Confirm environmental ratings, EMC compliance, hazardous-area approvals where applicable, operating-temperature limits and long-term firmware availability. Standardize the selected model, configuration backup and replacement procedure before rolling it out across many sites.

Field checklist

• List every field interface, protocol, tag count and scan interval.
• State whether routing, VPN, conversion, edge logic or local control is required.
• Define outage buffering, recovery time and data-backfill rules.
• Review credentials, update policy and remote-access restrictions.
• Perform a proof-of-concept with real devices and the target platform.

Common questions

Can an IoT gateway replace a PLC?

Usually not for deterministic or safety-related control. A gateway can preprocess data and run non-critical logic, while the PLC retains validated control responsibilities.

Is 5G necessary for telemetry?

Often no. Band coverage, operator availability, data volume and recovery behavior matter more than the label. Select the network from measured requirements.

Which device is easiest to maintain?

The simplest device that meets the documented interfaces, availability and security requirements is usually easiest. Standardized configurations and remote diagnostics matter greatly.