Devices/Linux edge IoT gateways
works with InfiIoT · certified partner

Linux edge IoT gateways

A compact Linux gateway for bringing PLC data into InfiIoT without changing the control program.

Linux edge IoT gateways
2–4 GB
RAM · edge compute
4+
native PLC protocols
palm-size
DIN-rail footprint
Linux edge IoT gateways
[ Detail / port view ]
[ Installed on-site ]
Overview

These certified-partner Linux gateways provide 2–4 GB RAM and 16 GB storage in a palm-sized enclosure. Native drivers cover Siemens S7, Mitsubishi MC, Modbus RTU/TCP, and PROFINET; MQTT(S) and HTTP(S) carry normalized data northbound. Gigabit Ethernet, dual-band Wi-Fi, BLE 5.0, optional 4G, and digital I/O leave enough room for filtering, buffering, and local rules at the machine.

Specifications

representative · class-level
ComputeQuad-core ARM, 2–4 GB RAM, 16 GB eMMC
PLC driversSiemens S7, Mitsubishi MC, Modbus RTU/TCP, PROFINET
NorthboundMQTT(S), HTTP(S), OPC UA
NetworkingGigabit Ethernet ×2, dual-band Wi-Fi, BLE 5.0, optional 4G
I/O8 × DI, 3 × DO (model-dependent)
Environment-20 to 60 °C, DIN-rail, 9–36 VDC
Deployment scenarios

Where this class earns its place.

Retrofit without touching the PLC program
For the digitization lead

Retrofit without touching the PLC program

The gateway reads S7 or Mitsubishi traffic without altering validated control code.

A gateway cost that works across the fleet
For the CFO

A gateway cost that works across the fleet

Locally engineered gateways lower the per-machine cost when a rollout grows from a pilot to a 200-machine estate.

Keep the field layer portable
For the solution architect

Keep the field layer portable

The gateway is not tied to one cloud provider, so an infrastructure change does not require replacing field hardware.

Works with InfiIoT

The protocol, variable mapping, and platform handshake have already been tested.

Linux · 2–4 GB RAMS7 · MC · Modbus · PROFINETMQTT(S) / HTTP(S)GigE · Wi-Fi · BLE · 4G8 DI / 3 DO optional
Connected-product assessment

Bring one product. Leave with a clear next step.

Use 30 minutes to test the fit around one product and one blocked decision. If there is a fit, we will outline the two-week Product Blueprint.

30-minute fit callOne productNo prepared deck