A friend recently described running OpenWrt on an industrial PC — the whole unit at 60 USD, with routing, firewall, and ad blocking set up in one pass. When asked why not just buy a router, the answer came back the same way it always does: fine at home, not fine on a plant floor. The exchange keeps surfacing an old question. Industrial PC, soft router, industrial router — all three can get a network online and run services. Where is the actual difference. Before picking one for a factory site, three things need to be separated: which is the hardware, which is the software, and which job each device was actually built for. The rest of the article works through the three devices one at a time, then puts them side by side.
An industrial PC (Embedded Industrial Computer) is not built for routing. Its main job is data acquisition plus edge computing. The typical configuration: ARM or x86 architecture, runs Linux Ubuntu, ships with RS485 / RS232 / CAN industrial bus interfaces, accepts a wide 9–36 V input, operates from −25°C to +75°C, with a fanless aluminum housing. On the software side, Node-RED, Docker, industrial protocols (Modbus, DLT645, IEC 104, BacNet), and PLC programming environments are preinstalled. The work scene is the shop floor — pull data from PLCs, sensors, and meters, run local logic on it, then push to the cloud. The multiple Ethernet ports, 4G, and WiFi are only there so the device itself can also get online and report its own data.
PUSR's USR-EG528 is a typical ARM-based industrial PC: RK3562 quad-core Cortex-A53 at 2.0 GHz, 2× RS485 + 2× RS485/RS232, 2× 100M Ethernet, HDMI, USB, preinstalled with Ubuntu 24.04, Node-RED, Docker, 9–36 V wide input, −25°C to +75°C operating range. For video AI, USR-EG828-GL: Rockchip RK3568, quad-core Cortex-A55, 1 TOPS NPU, 4 GB DDR + 32 GB SSD, with RS232 / RS485 / CAN and gigabit Ethernet. An industrial PC is a compute platform. Routing is a side job.
A soft router is not hardware. It is a way of using one. Take any small Linux-capable host (an x86 mini PC, an industrial PC, an old laptop, a Raspberry Pi), install OpenWrt, pfSense, VyOS, or ImmortalWrt, and it becomes a soft router. All of the value sits in software — traffic shaping, ad blocking, split routing, IPv6, multi-WAN aggregation, VPN server — everything is software-defined. The same box, swapped with a different image, can do almost anything network-related.
The setup mentioned at the start — a cheap fanless mini PC running OpenWrt, 60 USD total, handles ad blocking, WireGuard, and intranet penetration, the kind of features only home or SMB networks actually need. The pattern: hardware is interchangeable, software is the core, the OpenWrt plugin ecosystem is active, industrial interfaces (RS485 / CAN / DI / DO) are usually absent, wide temperature, wide voltage, EMC, and other industrial-grade characteristics are not guaranteed, and fault diagnosis is harder because the result is a software-plus-generic-hardware combination. Typical use cases: home, SMB, small office. A factory might use one occasionally, but it would not buy a dedicated unit just for "routing," and it certainly would not buy an industrial PC only to repurpose it as a soft router.
An industrial router (Industrial Router / 4G Cellular Router) exists to provide a network path. Power on, configure the APN, insert a SIM, the service is running. PUSR's USR-G806w is a typical model: Qualcomm platform, 1× WAN + 2× LAN, WiFi enhancement, OpenVPN / IPsec / PPTP / L2TP / GRE, hardware + software dual watchdog, −20°C to +70°C operating temperature, supports wall mount and DIN rail installation. 4G dial-up, VPN client, SIM slot, wide temperature, EMC, lightning protection, anti-static — every factory-grade requirement is already built in. The software is closed, runs vendor firmware, and supports remote batch management. An industrial router is a network path. Data acquisition is not its job.
|
Industrial PC (Embedded Industrial Computer) |
Soft Router |
Industrial Router |
|
Data acquisition + edge computing |
Routing / firewall / split routing |
Network uplink |
|
ARM / x86 + full industrial interfaces |
x86 / ARM general-purpose mini host |
|
|
Linux Ubuntu |
OpenWrt / pfSense |
Vendor firmware |
|
Industrial bus: yes |
No |
No |
|
−25°C to +75°C |
Consumer-grade, not guaranteed |
−20°C to +70°C |
|
Higher learning curve (Linux / PLC) |
Medium (OpenWrt) |
Low (plug and play) |
|
Highly flexible (Docker / Node-RED) |
High (plugin ecosystem) |
Low (vendor feature boundary) |
|
Self-supported |
Self-supported |
Vendor remote O&M |
That 60-USD "industrial PC running OpenWrt" setup is essentially using industrial PC hardware as a soft router, trading industrial interfaces and the Linux ecosystem for flexibility. It works at home or in SMB. Drop it into a factory, and the most valuable part of the industrial PC is left sitting idle — the bus interfaces go unused, the wide input tolerance is wasted, and the vendor-supported firmware cycle is replaced by a self-maintained OpenWrt build. In factory environments, networking and data work belong on separate gear — routing on industrial routers, data on industrial PCs, and a soft router only when custom routing behavior is actually needed and a dedicated engineer is on hand to keep it healthy.