Edge Gateway
The ruggedized industrial appliance that bridges your existing PLC fleet to the network — embedded Linux, built-in Modbus TCP, cellular publish — on a DIN-rail box, no separate industrial PC for standalone gateway use today. A standalone PLC-to-network gateway today; the canonical EdgeConnect appliance once Linux ships.
DIN-rail · 24 V DC · embedded Linux · 4G / Wi-Fi / Ethernet · built-in Modbus TCP · 200 × 150 × 75 mm rugged enclosure · offline-capable.
One ruggedized box where the industrial PC used to be.
The Edge Gateway is a ruggedized industrial gateway running embedded Linux. It bridges existing PLC fleets to the network over Modbus TCP, publishes over cellular, and is web-configurable with USB firmware updates — on a DIN-rail box sized for a control cabinet. No separate industrial PC is required for standalone Modbus TCP + cellular gateway use today.
It is the appliance form of the Connectivity & Edge pillar — see the capability story → /capabilities/connectivity-edge. It has a dual identity: today a standalone PLC-to-network gateway (built-in Modbus TCP + cellular publish); tomorrow, once the EdgeConnect Linux runtime ships, the canonical EdgeConnect appliance — same hardware, two lifecycles. For the EdgeConnect runtime itself, see → /edgeconnect.
What it does — and what it removes from your BOM.
Bridges PLCs to the network
Built-in Modbus TCP server/client connects existing PLC fleets; publishes over cellular.
Embedded Linux, web-configurable
Configure sources and publishing from a browser; no separate industrial PC for standalone gateway use today.
Cellular + Wi-Fi + Ethernet
Connectivity for remote sites without running new cable.
USB firmware updates
Field-serviceable without a toolchain.
One Edge Gateway removes from the customer BOM:
- a separate industrial PC for standalone Modbus TCP + cellular gateway use today;
- a separate Linux gateway for protocol bridging;
- a separate cellular modem for remote sites;
- the need to host EdgeConnect on customer-owned Windows infrastructure once the EdgeConnect Linux runtime ships (until then, the full EdgeConnect runtime still runs software-only on Windows).
The box, in numbers.
| Compute | Embedded Linux; 256 MB RAM; 2 GB Flash |
| Power | 24 V DC. Current draw, terminal type, and circuit-protection recommendation confirmed during BOM scope. |
| Enclosure | Ruggedized, 200 × 150 × 75 mm |
| Ingress protection | IP65 / IP67-compatible configurations can be scoped where a site requires it; final protection level, enclosure approach, and any certification requirements confirmed during BOM scope. (Compatibility, not a certified rating — no formal IP certification is currently claimed.) |
| Mounting | DIN-rail (control cabinet). Cabinet clearance, cable routing, and antenna placement confirmed during BOM scope. |
| Connectivity | 4G (cellular) · Wi-Fi · Ethernet. SIM / carrier / antenna and static-IP / DHCP / firewall / local-admin assumptions confirmed during BOM scope. |
| Built-in protocol | Modbus TCP (server/client) |
| Onboard I/O | A PLC / network gateway, not a DAQ module — direct analog/digital sensor acquisition is handled by mDAQ. If a deployment needs direct sensor acquisition, scope mDAQ alongside or instead. |
| Management | Web-configurable; USB firmware updates |
| Cellular publish | Built-in (standalone mode today) |
How it installs.
| Mounting + power | DIN-rail mount in the control cabinet; 24 V DC industrial power. No separate industrial PC for standalone Modbus TCP + cellular gateway use today. |
| Connectivity | Cellular for remote sites; Wi-Fi or Ethernet where available. Publishes over cellular in standalone mode. SIM / carrier / antenna and static-IP / DHCP / firewall / local-admin assumptions confirmed during BOM scope. |
| Protocols today | Built-in Modbus TCP (server/client) for PLC bridging. Additional protocols arrive with the EdgeConnect Linux runtime. |
| Firmware | USB firmware updates — field-serviceable. |
| Offline | Operates without a persistent connection; cellular publish resumes when connectivity returns. |
| Operating environment | Temperature, humidity, exposure, and enclosure approach confirmed during BOM scope; IP65 / IP67-compatible configurations can be scoped where the placement requires it (no certified rating claimed). |
| Field-wiring + site fit | Enclosure dimensions, power, mounting, cabinet clearance, and antenna/cabling are confirmed during the BOM scope against the cabinet + site constraints. |
The appliance in the stack.
ArchitecturePanel.interactive variant.
The Edge Gateway is an option, not a requirement — EdgeConnect also runs software-only on customer hardware. See the runtime → /edgeconnect; the full stack → /architecture.
One unit, plus the software it grows into.
Packaging labels are illustrative until commercial packaging is approved; this section describes how the unit is bought + what it pairs with, not pricing.
The Edge Gateway is a hardware unit, scoped against controller count, site connectivity, cabinet constraints, field environment, and whether the appliance is used standalone today or as the future EdgeConnect appliance footprint. Today it ships in standalone mode (built-in Modbus TCP + cellular publish). When the EdgeConnect Linux runtime ships, the same hardware becomes the canonical EdgeConnect appliance — the appliance grows into the broader platform path without new hardware. Bring the PLC list, the site connectivity (cellular vs. wired), and the cabinet constraints; we'll scope the BOM. Contact Elpis for unit availability and BOM scoping; detailed pricing follows the BOM review.
Built for the cabinet, not the office.
Built for the cabinet, not the office.
Ruggedized enclosure, 24 V DC industrial power, DIN-rail mount, embedded Linux. Sized (200 × 150 × 75 mm) to drop into a control cabinet beside the PLCs it bridges.
Offline-first, remote-ready.
Operates without a persistent connection; built-in cellular publishes from remote sites and resumes on reconnect. No dependency on customer Windows infrastructure in appliance mode.
Formal third-party certifications are not currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope; IP65 / IP67-compatible configurations can be scoped where required, but certified/rated claims are published only when formal evidence exists for the specific product/configuration.
What plant engineers ask.
What are the dimensions and power?
200 × 150 × 75 mm ruggedized enclosure, 24 V DC, DIN-rail mount. Embedded Linux, 256 MB RAM, 2 GB Flash. See the specifications table above; exact figures are confirmed at quoting time.
What does it bridge today vs. later?
Today: built-in Modbus TCP (server/client) for PLC fleets, with cellular publish — standalone. The broader protocol set (FOCAS2, MTConnect, OPC UA Client, Siemens S7, …) arrives when the EdgeConnect Linux runtime ships on this hardware; see /edgeconnect for that matrix.
Do I still need a separate industrial PC or a Linux gateway?
For standalone Modbus TCP + cellular gateway use today, no — Edge Gateway combines the gateway, Linux appliance, and cellular modem in one DIN-rail box. For the full EdgeConnect runtime today, EdgeConnect still runs software-only on customer Windows hardware. Once the EdgeConnect Linux runtime ships, this same Edge Gateway hardware becomes the canonical EdgeConnect appliance footprint.
How are firmware updates handled?
Via USB — field-serviceable without a toolchain. Configuration is web-based.
Does it work where there's no cable / no internet?
Yes. Built-in cellular (4G) publishes from remote sites; Wi-Fi and Ethernet are available where present. It operates offline and resumes publishing on reconnect.
Is Edge Gateway certified? What about IP65 / IP67?
No formal third-party certifications are currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope. Where a site requires IP65 / IP67-class protection, Elpis can scope an IP65 / IP67-compatible configuration or enclosure approach; formal certification or rating claims are published only when the specific product/configuration has the required certification or test evidence.
Is the appliance required to run EdgeConnect?
No. EdgeConnect runs software-only on customer hardware (Windows today). The Edge Gateway is an option — a turnkey box for sites that prefer one — and becomes the canonical EdgeConnect appliance once the Linux runtime ships.
Does it have onboard sensor I/O? How is it different from mDAQ?
Edge Gateway is a PLC / network gateway, not a DAQ module. Direct analog/digital sensor acquisition (4–20 mA, 0–10 V, digital I/O) is handled by mDAQ. If your deployment needs direct sensor acquisition, scope mDAQ alongside or instead of Edge Gateway — confirmed during BOM scope.
Can it be mounted outside a control cabinet?
Cabinet placement, exposure, temperature, humidity, antenna placement, and ingress-protection requirements are confirmed during BOM scope. IP65 / IP67-compatible configurations can be scoped where required, but no formal certified IP rating is claimed unless evidence exists for the specific configuration.
Bring us your PLC fleet and your cabinet constraints.
A PLC list, your site connectivity (cellular vs. wired), and the cabinet space you've got — that's what we scope a BOM against. We confirm the dimensions, power, mounting, and connectivity for your site, not for a brochure.