A fanless industrial computer mounted in a refrigerated delivery truck runs the same software it ran on the day it was installed: engine speed and fuel consumption off the CAN bus, cargo compartment temperature, position reporting, and the day's job list on the driver's display. Not a line of the software has changed, and the hardware has already reached the point where a consumer PC would be replaced.
Consumer electronics are replaced on a schedule set by software. The operating system moves up a version, applications move up a version, and the old machine can no longer keep up. The unit in the truck works the other way around: the software stays put and the hardware reaches end of life first. A longer lifecycle, then, is not about a thicker enclosure. It is about hardware keeping pace across a decade in which the software does not move, and about the swap going smoothly on the day it happens.
A portable industrial machine from the early 1990s illustrates the point. Its case, keyboard and CRT are still in service, and what was replaced is the computing part inside. The original controller board came out and an ISA single-board computer went in, the floppy bay was converted to a CF card, and the operating system became a stripped-down Linux. The machine outlives the computing part inside it by a wide margin, provided the ports and the form factor are not swapped out along with it.
Across the pages of most industrial computer makers, long service life comes down to a single reason: the fan is the only moving part. Remove it and there is no bearing to wear out, and dust and moisture lose their main way in. That reasoning holds. Washdown lines, foundries, paint shops, outdoor cabinets and installations under constant vibration all benefit from it.
It also assumes something — that if the machine does not fail, ten years takes care of itself. What stalls a purchase is usually the other half. Will the same model with the same ports and the same operating system still be available in ten years? Once it arrives, will the software recognize it? If one port is missing, does that mean another converter hanging off the side? The first half asks whether the machine will fail. The second asks whether the swap will go smoothly. The first is a hardware question; the second sits with ports, operating system and settings.
So the breakdown runs backwards from the software, not downwards from the clock speed.
This decides whether a swap is possible at all. Fixed-function software of this kind tends to lock onto three things: the operating system version and its runtime libraries, the COM port numbering on the serial ports, and the drivers and protocol stack. Legacy dispatch software that only runs on Windows has to land on an x86 platform. Collection and reporting jobs that speak only standard protocols — Modbus, OPC UA, MQTT — run just as well on an ARM platform with Linux preinstalled.
The platform choice also shapes maintenance over the following decade. ARM models in the same family share the WukongEdge and Node-RED software layer, so application logic ports across models without a rewrite. Baking that logic into one proprietary package instead means the logic has to move along with the next machine.
A truck usually needs several kinds of port at once: CAN for road speed, engine speed and fuel consumption, RS485 for temperature and axle load, RS232 for an older temperature controller, Ethernet for cameras and the driver display, and digital I/O for switch signals. Miss one on the replacement and an external converter becomes necessary; every extra converter adds one more failure point and one more round of revalidation.
The USR-EG628 is specified against exactly that list: 2 RS485, 1 RS232, 1 CAN, 2 Ethernet and 2 USB ports, an industrial-grade RK3562J quad-core Cortex-A53 running at up to 2.0GHz, 4GB of memory and 32GB of storage with SD expansion, 4G/5G plus Ethernet plus Wi-Fi able to back each other up, routing, VPN and firewall built in, GPS/BeiDou on the GL version, wide-range power input, -20 to 70°C, and 118×87×60mm for wall or DIN-rail mounting. Space and supply voltage are both tight in a vehicle, so these are the items worth checking against the spec sheet before ordering.
On swap day, settings take longer than wiring. Four serial parameters — baud rate, data bits, parity and stop bits — plus the Modbus station number and register map, plus the reporting point table: leave any of these unrecorded and they have to be worked out on site, one at a time.
The way around it is to keep the point table configured inside the machine. The USR-EG528 ships with local SCADA/HMI and Node-RED, so data can be read out against a point table without writing code. Of its 4 serial ports, 2 switch between RS232 and RS485; DC 9-36V with reverse polarity protection, -25 to 75°C, and a TF card slot holds the image, with a cloud backend for changing parameters remotely. With the image stored, a swap comes close to the cost of flashing a card.
A fanless aluminium chassis, wide-range input with reverse polarity protection, a wide temperature range, hardware and software watchdogs, and 7×24 continuous operation — these are what get compared once the first three hold up. Where the depot side runs legacy Windows dispatch software, the USR-EC300 is the matching choice: i5-7200U, 8GB of memory expandable to 32GB, a 128G wide-temperature SSD, 6 serial ports of which 2 switch between RS232/RS485/RS422, HDMI and VGA, DC 12-36V, -20 to 60°C, all-aluminium fanless construction, and a 255-level programmable watchdog.
Put the supply period into the request for quotation; that saves more trouble than hunting for a substitute later. Keep two or three interchangeable models on the same platform — EG628, EG528 and EG228 share one software layer, so application logic does not need a rewrite when the model changes. Flash the standby unit with the same image version on acceptance day rather than configuring it after something starts failing. For cross-border routes, check that certifications cover the countries of operation: the EG628 carries 3C, CE, FCC, RCM, ANATEL, NBTC, MTC, ROHS and WEEE.
A fanless industrial computer is often chosen as simply a more durable machine. Durability is the prerequisite, but what actually sets the ten-year cost is whether the ports, the operating system and the settings all line up on the day it gets swapped in. Working backwards from the software gives a better answer than comparing clock speeds.
1. How much longer is the lifecycle of an industrial PC compared with a consumer PC?
Consumer PC are replaced every three to five years, on a schedule set by the operating system and the applications running on top of it. A machine in a vehicle or at a depot runs fixed-function software and often stays untouched for five to ten years. Those extra years do not come from a particular chip; they come from the supply period, the port layout and the operating system version staying consistent across a model change. Putting the supply period into the request for quotation saves more trouble than hunting for a substitute later.
2. Does fanless automatically mean a long service life?
Not entirely. Removing the fan takes away the bearing most likely to fail first and closes off the main path for dust and moisture, which answers whether the machine will fail in the field. What tends to stall a swap is a different set of questions: are there enough ports, will the operating system version be recognized, can the settings be copied over. The two halves are assessed separately — the first through thermal design and construction, the second through the port list and the software layer.
3. For a truck installation, ARM or x86?
Start with the software. Legacy dispatch software that only runs on Windows has to sit on an x86 platform; ARM will not run it. Collection and reporting jobs that speak only standard protocols — Modbus, OPC UA, MQTT — run just as well on an ARM platform with Linux preinstalled, with lower power draw and a smaller footprint. The deciding factor is what the software depends on, not which specification is higher.
4. What happens when a model is discontinued?
There are two routes. One is to keep interchangeable models on the same platform, so application logic does not need a rewrite when the software layer is shared. The other is a standby unit, flashed with the same image version on acceptance day rather than configured after something starts failing. EG628, EG528 and EG228 sit on the same WukongEdge and Node-RED software layer, which keeps porting costs down at a model change.
5. Which items get missed most often during a swap?
The four serial parameters — baud rate, data bits, parity, stop bits — the Modbus station number and register map, and the reporting point table. Any of these left unrecorded has to be worked out on site. Close behind are the small differences in ports: how many RS485 lines the original had, whether it had RS232 at all. A missing port means an external converter, and every extra converter means another round of revalidation.
6. Why check wide-range input and wide temperature separately?
Supply voltage in a vehicle or an outdoor cabinet moves with the engine, with charge and discharge, and with load; the nominal figure is only one point on a curve. Wide-range input with reverse polarity protection keeps voltage swings and a miswired connector from destroying the machine outright. Temperature works the same way: mounted inside a compartment wall or an outdoor enclosure, measured values often run above the nominal ambient figure, so selection should leave headroom for the measured location rather than follow indoor conditions.
7. Why do certifications matter on cross-border routes?
Radio and electrical compliance is usually assessed per country of operation when vehicles and equipment cross borders, and the certifications a model carries determine whether it can legally go into service and connect to a network. The EG628 carries 3C, CE, FCC, RCM, ANATEL, NBTC, MTC, ROHS and WEEE, a wider coverage than a model certified for a single market. Checking each certification against the actual countries of operation before ordering is easier than arranging them after shipment.
8. How far does a standby unit need to go?
The minimum is direct replacement: the same number of ports, the same operating system version, and parameters and point table preloaded, so it runs as soon as it is fitted. The practical approach is to take an image of the same version on acceptance day and store it in the standby unit. A model with a different port layout does not qualify as a standby, because fitting it would mean configuring everything again. The value of a standby unit shows up in downtime — the closer the configuration is to the machine in servic
