Selecting an embedded industrial computer is a different exercise from building a DIY PC.

Here is a real-world comparison. A hardware enthusiast spent a year building a CNC-machined aluminum mini case. Choosing the components was the easy part — the hard part came later: tolerances, quality control, shipping, each consuming a huge amount of effort. The spec sheet was just the starting point. This is exactly where an embedded industrial computer makes the difference: the platform, I/O, enclosure, power supply and certifications are integrated and validated by the manufacturer before shipping, so the only thing left for the buyer is to determine whether the machine matches the site. Another characteristic is pre-configuration: the OS, drivers and protocol stacks are pre-installed at the factory, ready to run on power-up — no OS installation, no driver hunting.

How to make that call? Answer four questions first.

1. Where It Is Installed: Decide the Platform

The installation location determines the power budget and the platform choice.

Inside a distribution cabinet, inside equipment, or in an outdoor cabinet, space is tight and most have no air conditioning. Low-power ARM platforms are the mainstream choice. ARM industrial PCs like the EG628 run at low power with a fanless design; heat is dissipated through the chassis, so no ventilation space is needed.

Conversely, if the application needs Windows-based host software, SCADA systems or a local database, an ARM platform will not suffice — an X86 unit (such as the EC100/EC300/EC500 series) is required, sized according to the computing needs of the site.

If human-machine interaction is needed on site, an all-in-one unit with a built-in touchscreen is a better fit than a separate host plus monitor — one less cable, one less point of failure.

2. What It Does: Decide the Compute Tier

A list of tasks is more useful than benchmark numbers. List the applications one by one and match them to a tier:

• Data acquisition, protocol conversion and cloud forwarding only: field protocols such as Modbus and IEC 104 run comfortably on ARM platforms.

• Running several containers, a Node-RED flow and multiple acquisition streams at the same time: RAM becomes the bottleneck — entry-level models with 512MB RAM are fine to start, but heavier workloads call for more memory.

• Machine vision, object detection and LLM inference: look at NPU performance, not CPU clock speed. Edge AI boxes such as the EG928A integrate an NPU and can run detection models directly.

Workload can be quantified: how many data points per second, how large each one is, and how long they must be retained — this calculation gives the lower bound for storage and RAM; the number of concurrent protocol conversions decides the CPU tier. Paying for "maybe needed in the future" most often ends in idle compute.

3. What It Connects To: Decide the I/O List

The I/O ports of an embedded industrial computer are fixed on the board at the factory and cannot be extended on site. Make a list of the devices to be connected and sort them by communication method:

• Meters, VFDs and sensors communicate over RS485; legacy equipment over RS232; vehicle and machinery applications over CAN. Count how many ports of each type are needed, then match against the models — some ARM units carry RS485, RS232 and CAN at the same time.

• Ethernet is the baseline for the main link — at least one port is a must; for link redundancy or separating internal and external networks, look for multi-port models. If the site already has a ring or stacked network, confirm the port speed and count are sufficient.

• Where cabling is difficult or the device moves, 4G/5G or WiFi becomes a necessity — choose models with cellular modules or WiFi.

Many projects end up finding that the bottleneck is not compute but a shortage of serial ports. The I/O list should be made on day one of selection.

4. How Long It Runs: Decide Storage and Reliability

• Size storage by log retention: industrial sites have vibration, so mechanical hard drives are the first thing to rule out; eMMC and wide-temperature SSDs are the common choices. Estimate the lower bound as "records per second x record size x retention period" — for example, one telemetry stream reporting 100 bytes per second comes to less than 4GB a year, so 128GB eMMC is more than enough.

• Choose power input by site voltage: where the mains is unstable, a wide-range input (such as 9-36V DC) can connect directly to vehicle or equipment power — one less conversion stage, one less point of failure.

• Choose temperature range by installation location: fanless units do not collect dust or make noise, but they dissipate heat through the chassis, so verify that the maximum site temperature stays within the operating range.

• Reliability comes down to mechanisms: a watchdog and automatic restart after power loss determine whether the device recovers on its own after an outage, instead of waiting for someone to press the power button on site.

Finally, Do Not Skip Certifications

Certification lists such as CE, FCC, 3C and RCM determine whether the product can be legally sold locally and whether it qualifies for project bids. Verify them at the selection stage, not after the goods arrive.

In short, selecting an embedded industrial computer comes down to four things: where it is installed, what it does, what it connects to, and how long it runs. Once the four questions have answers, the spec sheet writes itself. Choosing the right embedded industrial computer saves not only hardware cost but also t