What is the difference between an embedded computer and an industrial PC? An industrial PC is a general term for a ruggedised computer designed for industrial use. An embedded computer, or embedded system, is usually more application-specific: a compact platform designed into a machine, cabinet, vehicle or OEM product, often with fixed I/O and long-term availability. Many embedded systems are built using industrial PC technology, but with tighter constraints on size, power, interfaces and lifecycle.
How do I know if I need a standard embedded platform or a custom design? A standard embedded platform is usually suitable if you can work within its mechanical, electrical and I/O constraints. If the project has strict space limits, unusual interfaces, specific certifications or a requirement for a unique enclosure or layout, a more tailored or fully custom design may be appropriate. We typically start by assessing requirements against standard platforms and only move towards custom design if there is a clear need.
What information do you need to advise on an embedded system? The most useful starting points are: Application and main functions Required interfaces (e.g. serial, digital I/O, Ethernet, fieldbus, wireless) Operating system and software dependencies Environmental conditions (temperature, shock/vibration, ingress, EMC) Power input and mounting constraints Expected volumes and project lifetime With this information we can narrow down suitable platforms and highlight any areas that may need special attention.
Can you support both Windows and Linux-based embedded systems? Yes. We regularly work with Windows and various Linux distributions on embedded platforms. Support typically includes image preparation, basic configuration, driver considerations and version control. If a project needs a specific or hardened OS build, that can be discussed as part of the engineering scope.
How do you handle product lifecycle and obsolescence? Lifecycle is a key part of embedded system planning. We look at manufacturer roadmaps, typical availability periods and any announced end-of-life information when recommending platforms. For longer projects, we can discuss last-time-buy strategies, compatible successor products and how changes will be managed so that you are not faced with unexpected redesigns.
Do you only supply hardware, or can you help with integration and testing as well? Hardware supply is only one part of what we do. Our team can configure systems, fit expansion cards and storage, prepare OS images, label units and run agreed tests before shipment. The aim is that systems arrive as close as possible to “ready to install” for your engineers or installers.
What is the difference between using an embedded SBC and a boxed embedded PC? An embedded SBC (single board computer) is typically used when you are designing your own enclosure or product and want a board-level platform to integrate. A boxed embedded PC places the board and supporting components in a finished enclosure with predefined mounting and I/O locations. SBCs offer maximum flexibility at the mechanical level; boxed PCs reduce integration work and are often faster to deploy.
At what stage in a project should we involve you? It helps to talk once you have a basic idea of the application, environment and timescales, even if not all details are fixed. Early involvement can prevent choices that later limit performance, certification or reliability. We can give you a realistic view of what is achievable with standard embedded platforms and where custom design might become necessary.