Industrial IoT Gateways

An industrial IoT gateway is a small, usually fanless computer that connects machines, meters and sensors to a network or the cloud. It reads field protocols such as Modbus and CAN, filters and converts the data, and forwards it securely over Ethernet, Wi-Fi or cellular. Arm models handle simple collection, while x86 and AI models also run local applications.

A gateway is built around connections: field I/O, protocol conversion and a network or cellular uplink, on low-power hardware. An industrial PC is built around the application, with more processing, display outputs and expansion for control, HMI or vision. The two overlap, and many x86 edge gateways can also run a light control task, much like a DIN rail controller, or a dashboard.

Choose by the software. If the job is collecting, converting and forwarding data, an Arm gateway does it on a few watts with Debian or Yocto Linux. If you need Windows software, existing x86 Linux applications, a local database or containers, choose x86. Choose a Jetson or NPU model when cameras or sensors need AI inference on site.

At the hardware level, gateways read Modbus RTU over RS-485 or RS-232, Modbus TCP over Ethernet, CAN bus and digital or analog I/O. MQTT, OPC UA and other upstream protocols are software that runs on the gateway’s Linux or Windows image, such as Node-RED or a platform agent, so you can choose them to suit your SCADA or cloud platform.

Most take a 4G LTE module with a SIM, and the newer x86, Qualcomm and Jetson gateways take 5G as well. Wi-Fi and Bluetooth modules are common options, and GPS comes with the LTE module on selected Arm gateways. A LoRaWAN module is also offered as an option on selected Arm gateways, for low-power sensors spread across a site. If a site only needs an uplink and no protocol conversion, a router may be enough; our answer on how a gateway differs from a router explains where each fits.

In layers: TPM 2.0 and secure boot in the hardware, then a firewall, VPN tunnels and signed updates in the operating system, with isolated I/O keeping electrical faults on the field side. Our guide covers each layer and the IEC 62443 controls asset owners ask for.

Yes, if it has analog inputs. Some DIN-rail gateways read 4 to 20 mA current loops or 0 to 10 V signals on their own terminals, so flow, level and pressure transmitters connect without a separate I/O module. That makes the gateway a data acquisition gateway that scales, logs and forwards readings. For many more channels, add a dedicated I/O module.

Yes, on models built for it. A vehicle gateway reads engine and body data from the CAN bus, starts and stops with the ignition and runs from a 12 or 24 V supply, then forwards position and telematics data over 4G LTE. Selected models carry E-Mark approval for road vehicles, and heavier onboard work suits a full in-vehicle computer.

Yes. Most gateways here mount on a DIN rail or a wall bracket, and many run from −25 to 70 °C, with wide temperature x86 builds rated from −40 °C. Power comes from wide DC inputs on terminal blocks, with surge protection on many models, so the gateway can share the cabinet’s DIN rail power supply with the PLC.

Yes, where the manufacturer declares it. Some gateway makers publish TAA or NDAA declarations for selected models, which matters for US federal, utility and defense projects. No gateway here is sold as made in the USA or as Buy American Act compliant. Send us the clause your contract quotes and we’ll match it to the maker’s declaration for each model.

Yes. Integration is standard: every industrial IoT gateway we supply is configured and tested before it ships. Cellular, Wi-Fi and storage modules go in first, then the operating system image, serial port settings and network setup, with antennas, DIN-rail kits and power supplies matched to the site, so each gateway arrives ready to install.