A portable industrial machine built in the 1990s is still doing its job. The ISA backplane was never touched. The original control board came out and an ISA single-board computer went in. The floppy bay now takes a CF card, and the operating system is a slim Linux build. The case, keyboard and CRT are all original. The enclosure outlived the computing inside it, and that only worked because the interfaces and the form factor were never replaced along with the board.
Carried into a purchase decision today, the same observation points somewhere else. Whether a machine runs on the day it is installed, and whether a model with matching interfaces and a matching operating system can still be bought in year eight, are two separate questions. A fanless industrial computer tends to be compared as though it were simply a harder-wearing PC. Hard-wearing is the entry ticket. Long-term availability is the item that belongs on a request for quotation.
Industrial computer vendors mostly explain long service life through thermal design and environment: the fan is the only moving part, remove it and there is no bearing to wear out, and dust and humidity lose their main way in. The self-check questions on pages like that cover dust, washdown, vibration, the cost of downtime and ingress rating. Comparison tables line up cooling method, dust intake, moving parts, vibration, application and compute ceiling. Not one row asks which year the model is supplied to.
The environmental half holds up, but it rests on an unstated assumption: if the machine does not fail, ten years simply happen. What actually blocks a project in year eight is three other questions. Which year does supply run to. How much notice comes before end-of-life, and is a last-time-buy possible. Which model replaces it, and how many interfaces differ. Putting those three on the enquiry saves more than hunting for a substitute later. The effect is clearest on fleet and depot rollouts delivered in batches: when one model ends, spare parts, acceptance criteria and delivery documents for the whole batch change with it. Where more than one unit ships in the same batch, serial numbers and as-shipped firmware versions belong in a single register, so reorders and migrations can be checked against it.
Ten years should not rest on a single model number. Within one series the tiers differ by interface count, while the software layer and the serial interface form stay the same. Moving between tiers changes quantity, not code.
The USR-EC500 is the tier that gives the most: i5-7200U, 8 GB of memory expandable to 32 GB, 128 GB storage, 8 serial ports (4 switchable RS232/RS485 plus 4 fixed RS232), 5 Intel I210 gigabit Ethernet ports, HDMI and VGA dual display, DC 12-36V, 236 x 228 x 72 mm. It suits a depot where card readers, a weighbridge, temperature controllers and several terminals are all connected at once.
The USR-EC300 sits in the middle: the same i5-7200U and 8 GB (to 32 GB), 6 serial ports (2 switchable plus 4 RS232), 2 gigabit Ethernet ports, HDMI and VGA, DC 12-36V, 236 x 183 x 72 mm, all-aluminium fanless cooling, 255-level programmable watchdog. At a dispatch desk or transfer point the serial count is just right.
The USR-EC100 is the smallest tier: Celeron J6412 with Atom and 4th-to-13th-generation Core options, 8 GB (to 16 GB), 2 RS232/RS485 ports, 2 gigabit Ethernet ports, 2 HDMI plus 1 DP, DC 12V, 15 W idle, 159.6 x 127 x 53.2 mm, and desktop, DIN-rail or embedded mounting. It goes into a vehicle or a single-station cabinet corner. Those processor options also leave room inside the same model number when compute needs grow later.
All three ship with Windows preinstalled, Linux optional, Windows 10/11 on the EC500. With a wide-temperature SSD, operating temperature is -20 to 60 degrees Celsius and storage -40 to 85. The watchdog is 255-level, vibration 5 to 500 Hz at 2 Grms, shock 10 G at 11 ms, ESD 6 KV contact and 8 KV air. If one tier ends, the other two cover it and the software does not change.
Replacement cycles on commercial hardware are pushed by software. The operating system moves up a version, drivers and runtime libraries follow, and once a legacy application stops running the machine gets replaced. Fixed-function software works the other way: whatever was read on the day of installation is still being read three years later, not one line changed, and what reaches end of life first is the hardware refresh cycle.
A fanless all-aluminium chassis, wide-range input, wide temperature, a programmable watchdog and 7x24 continuous operation are what carry that stretch. Supply on a vehicle or at a depot swings with engine state, charge and discharge, and load, so the input range says more than a nominal voltage does. A wide-temperature SSD decides whether -20 to 60 degrees Celsius can actually be used inside a vehicle cavity or an outdoor enclosure.
There is also a cost that never appears on the quotation. Swapping a machine is not finished when the new one is bolted in. Licences and dongles for the legacy software, driver signing, and the customer's IT onboarding paperwork all have to go round again. Keep the model alive and all of that is avoided.
Two things: a spare that drops straight in, and a configuration that can be rebuilt.
The spare gets the same image version flashed on acceptance day, with an interface count matching the units in service, so it runs the moment it reaches site, rather than being configured later once trouble starts. A flashed image still needs one real swap: power down in a maintenance window, replace, power up, check point by point. An image that has never been through an actual swap does not count. The configuration record has to keep the four serial parameters, baud rate, data bits, parity and stop bits, along with the Modbus station numbers, the register map and the point table used for reporting. Miss those and replacement day is spent guessing on site. Archived file names carry the site number and the date, so nothing has to be inferred later.
Cross-border operation adds one more check: whether certifications cover the countries of operation. Certification lists are archived together with the model number, so border crossings and network onboarding do not turn into last-minute paperwork.
A fanless industrial computer is often shortlisted on durability alone. Durability is the premise; what decides the ten-year cost is whether it can still be bought in year eight, and whether the interfaces and the operating system still line up when it is swapped in. Asking which year supply runs to, before comparing clock speeds, is the more useful first question.
1. How does a fanless industrial computer differ from a commercial mini PC?
Commercial mini PCs are pushed through replacement by software. Within three to five years the operating system and applications drag the hardware along with them, and ports follow the consumer market. A fanless industrial computer removes the fan, the part most likely to fail first, and cools passively through the metal chassis; power input and temperature are specified with margin for industrial sites, and field interfaces such as serial ports are provided by count. The difference is not clock speed but whether interface form, input range and supply cadence were designed for long service.
2. How many years of supply should be asked for?
Work backwards from the service life of the equipment. If machines and lines run ten years or more, the commitment has to be asked for at that scale; a three-to-five-year commitment is still a commercial cadence. The question comes down to three items: which year supply runs to, how much notice precedes end-of-life, and which model replaces it. Clear answers to all three are what make long-term availability real.
3. Is notice given before a model is discontinued?
Practice differs between vendors, so this belongs on the enquiry rather than being assumed. A last-time-buy window is common, and a replacement model is usually named before end-of-life. Agreeing the notice period and the replacement at order time costs less than sourcing a substitute afterwards, particularly on fleets and depots delivered in batches, where one discontinued model changes spare parts and acceptance criteria together.
4. How to choose between the EC100, EC300 and EC500?
By the number of devices on site and the space available. The EC500 offers 8 serial ports and 5 gigabit Ethernet ports, and fits depots where equipment is concentrated. The EC300 gives 6 serial ports and 2 Ethernet ports, which matches a dispatch desk or transfer point. The EC100 has 2 serial and 2 Ethernet ports and measures 159.6 x 127 x 53.2 mm, mountable on a desktop, DIN rail or embedded, for vehicles or single stations. All three ship with Windows, so the software layer is identical and moving between tiers changes quantity only.
5. Must a spare be the same model as the units in service?
The minimum is a direct drop-in: same interface count, same operating system version, parameters and point table preloaded. The same model is simplest; another tier in the same series with the same interface count also works. A model with a different serial form or a different operating system version makes a poor spare, since it still needs configuring on the swap. The value of a spare shows up in downtime duration, and the closer its configuration, the faster the changeover.
6. What is most often missed during a swap?
The four serial parameters, baud rate, data bits, parity and stop bits, plus the Modbus station numbers, the register map and the reporting point table. Without them, replacement day is spent testing on site. Interface count comes next: how many RS485 ports were in use, whether RS232 was present. One port short means an external converter, and every converter is another failure point. Licences and driver signing for the legacy software should be inventoried at the same time.
7. Should the preinstalled operating system version be written into the order?
Yes. The stated position is Windows preinstalled with Linux optional, and the exact version and licensing are confirmed at order time. The point of putting it in writing is getting the same version for spares and migrations, so a swap does not turn into a rebuild over runtime or driver differences. The EC500 page specifies Windows 10/11; the other two are confirmed as Windows by default.
8. Why do certifications matter for cross-border operation?
When vehicles and equipment cross borders, radio and electrical compliance are required per country of operation, and the certifications carried by a model decide whether it can legally run and connect there. Certification lists are archived with the model and checked line by line against the actual countries before shipment, which is simpler than arranging them at the border. A migration needs the same check again, since a replacement model's certification coverage is not always identical to the original.
