In industrial control projects, the single board computer is rarely just a computing module. It becomes part of the machine. It has to read signals, drive displays, communicate with other equipment, survive power noise, keep software stable, and work for years without daily maintenance. This is why many serious industrial products eventually need a custom SBC instead of a standard development board.
A development board is good for the first stage. It helps the software team bring up Linux or Android, test a UI, verify a display panel, connect a few peripherals, and prove that the basic idea works. But once the project moves closer to production, the limitations become obvious. The board may have too many unused connectors. The power input may not match the machine. The mounting holes may not fit the enclosure. RS485 or CAN may need an extra adapter. The display connector may face the wrong direction. These small issues can create real cost and reliability problems in mass production.
A custom SBC solves these problems by designing the board around the final product. It is not only about changing the PCB shape. It is about matching the processor, memory, storage, power circuit, display interface, industrial communication, mechanical structure, thermal design, and software package to the actual control system.
What Makes an SBC “Industrial”?
An industrial SBC is different from a consumer-style embedded board. The difference is not always visible at first glance. Both may have a processor, RAM, eMMC, USB, Ethernet, and display output. But the design priorities are different.
A consumer board may focus on price, features, and short-term performance. An industrial SBC must focus on stability, service life, electrical robustness, production consistency, and supportability. It may be installed inside a cabinet, behind a display, near motors, inside an outdoor terminal, or in a device that runs every day for many years.
In industrial control, the board should tolerate unstable power, cable noise, temperature change, static discharge, and unexpected user operation. It should also be easy to test at the factory and easy to recover in the field. These requirements are not optional details. They are part of the product.
Why Custom SBC Design Is Often Necessary
A standard SBC is designed for many possible users. A custom SBC is designed for one product or one product family. This difference changes many engineering decisions.
For example, a standard board may include HDMI, camera, audio jack, debug headers, multiple USB ports, and several expansion connectors. These are useful for development. But in a finished industrial panel, many of them may never be used. Unused ports still take PCB space, increase BOM cost, and create potential EMI or ESD paths.
A custom board can remove unnecessary circuits and add the interfaces that the machine really needs. It can place connectors in the correct position. It can use locking connectors instead of loose consumer connectors. It can include protection circuits for external signals. It can match the enclosure, display cable, and assembly process.
This is the practical value of customization. It makes the electronics fit the product instead of forcing the product to fit an evaluation board.
Typical Requirements in Industrial Control Boards
Different industrial control products have different requirements, but some patterns are common. Most systems need stable power input, a reliable operating system, a display or control interface, field communication, and some form of local or remote update.
| Design Area | Common Requirement | Engineering Notes |
|---|---|---|
| Processor | ARM SoC, MCU, or hybrid control platform | Select based on UI, protocol, AI, and software workload |
| Memory | DDR3, DDR4, LPDDR4, or LPDDR5 | Leave enough margin for future software expansion |
| Storage | eMMC, NAND, SPI flash, or SSD | Consider write endurance and OTA update safety |
| Display | RGB, LVDS, MIPI-DSI, HDMI, or eDP | Confirm timing, brightness, cable length, and rotation |
| Touch | I2C capacitive touch or USB touch | Check noise immunity, grounding, and ESD protection |
| Communication | RS485, CAN, Ethernet, USB, UART, SPI, I2C | Add protection for external interfaces |
| Power | 5V, 12V, 24V, PoE, or wide voltage input | Design for ripple, surge, and voltage drop |
| Reliability | Watchdog, RTC, recovery partition, logging | Needed for unattended operation |
| Production | Test points, factory test tool, serial number | Reduces mass production risk |
This table is only a starting point. The real specification should come from the machine, the installation environment, and the expected product life cycle.
Processor Selection: Not Too Weak, Not Unnecessarily Large
The processor or SoC is the center of a custom SBC. It decides the computing performance, graphics capability, multimedia support, peripheral resources, and software ecosystem. However, selecting the SoC only by performance is a common mistake.
For a simple industrial HMI, the main workload may be a fixed UI, Modbus communication, Ethernet connection, data logging, and several GPIO controls. In this case, a low-power platform may be enough. A more powerful processor may only add cost and heat.
For a modern Android control panel, the requirement is higher. The device may need smooth touchscreen operation, video playback, Wi-Fi, Bluetooth, cloud connection, OTA update, and a more complex UI. A mid-range platform such as RK3566, RK3568, or RK3576 may be more appropriate.
For edge AI, machine vision, multiple cameras, or high-resolution multi-display applications, a stronger SoC such as RK3576 or RK3588 may be needed. The important point is to match the SoC to the real workload. The best platform is the one that has enough margin without making the board unnecessarily expensive or hot.
Display-Centered Design
Many industrial control devices are built around a screen. The display may be the main way users understand the machine status, change settings, handle alarms, or read production data. Because of this, display design should not be treated as a late-stage accessory.
The first step is to define the display size, resolution, interface, brightness, viewing angle, operating temperature, and touch structure. A 7-inch 1024x600 panel and a 10.1-inch 1280x800 panel may look similar from a software point of view, but the hardware details can be different. The cable, connector, backlight voltage, PWM dimming, and LCD timing must all be confirmed.
Display interface selection also matters. RGB is simple and low-cost but can be sensitive to routing and EMI at higher resolutions. LVDS is common for industrial panels and works well over moderate cable lengths. MIPI-DSI is compact and widely used in modern embedded systems, but it requires careful high-speed layout. HDMI and eDP are useful for larger or external displays.
A custom SBC gives engineers control over the display connector, cable direction, backlight circuit, and mechanical placement. This can make assembly easier and reduce field problems.
Touch Panel and User Input
Touch input looks simple when it works, but it can be difficult in industrial environments. Capacitive touch panels are commonly connected through I2C with reset and interrupt signals. In a lab, the touch panel may respond perfectly. In a real product, it may be affected by electrical noise, metal frames, thick cover glass, gloves, water drops, or grounding problems.
A good custom SBC design should consider touch power filtering, signal routing, ESD protection, and proper grounding. The touch controller firmware may also need tuning for the final glass and enclosure structure.
For products that require physical buttons, rotary encoders, emergency input, or LED indicators, the board should provide clean GPIO design. External buttons should not be connected like internal debug pins. They need debounce handling, protection, and sometimes isolation.
A simple input test tool can be useful during factory testing:
./input_check --touch --keys --encoder --timeout 60
This type of tool is not complicated, but it helps production workers find problems before the product is shipped.
Field Communication Interfaces
Industrial control is communication-heavy. The SBC often needs to talk to PLCs, meters, sensors, motor drives, cloud servers, barcode scanners, printers, card readers, or other control boards.
RS485 is one of the most common interfaces. It is used for Modbus RTU and many proprietary protocols. CAN is common in vehicles, energy systems, and equipment networks. Ethernet is used for factory LAN, remote maintenance, data upload, and web configuration. USB may connect scanners, cameras, storage devices, or service tools.
The hardware design of these interfaces is as important as the software driver. RS485 lines may need termination, biasing, surge protection, and isolation. CAN needs a suitable transceiver and protection. Ethernet needs correct magnetics, layout, and ESD design. USB ports exposed to users need protection and enough current margin.
A custom SBC can integrate these interfaces directly instead of relying on external adapters. This reduces wiring, saves space, and improves consistency in production.
Power Design for Real Industrial Conditions
Power problems are one of the most common causes of instability in industrial devices. A board may work perfectly with a clean bench power supply but fail in the actual machine. The input voltage may drop when a motor starts. A long cable may cause voltage loss. A 24V line may contain noise. A user may connect the polarity wrong. Lightning or static discharge may enter through external wiring.
For this reason, the power input of a custom SBC should be designed according to the installation environment. The board may need wide voltage input, reverse polarity protection, fuse or resettable fuse, TVS diode, input filtering, and good DC-DC converter selection.
The power tree also needs careful planning. The SoC core, DDR, I/O voltage, eMMC, display, touch panel, wireless module, USB devices, and backlight may all have different power requirements. If the power sequencing is wrong, the system may boot randomly or fail under load.
Power design is not glamorous, but it is one of the foundations of a reliable industrial control board.
Watchdog, Recovery, and Safe Update
Industrial products often operate without an engineer nearby. If the system crashes, it should recover by itself. If a firmware update fails, it should not permanently brick the device. If the power is cut during writing, the file system should not become unusable.
A hardware watchdog is strongly recommended for many industrial control products. The application or system service should feed the watchdog only when the system is healthy. If the software hangs, the watchdog resets the board.
OTA update design is equally important. A safe update system may use dual partitions, recovery mode, version checking, rollback logic, and update logs. The exact method depends on the operating system, but the goal is the same: the device should either complete the update successfully or return to a known working state.
A basic recovery test may include repeated update and power interruption tests:
./ota_test --package update.img --repeat 50 --power-cut-simulation
In real projects, this kind of test may reveal problems that normal function testing never finds.
Linux, Android, and Application Framework
The software platform should be selected based on the product type. Linux is often the first choice for industrial control because it is flexible, stable, and suitable for background services, protocol handling, and custom drivers. It works well with Qt, GTK, LVGL, web servers, MQTT, Modbus, CAN, and RS485 applications.
Android is a better fit when the product needs a rich touchscreen interface, multimedia playback, app-like behavior, or easier UI development for commercial users. It is common in smart panels, retail terminals, access control products, and EV charger displays.
The BSP quality is critical for both systems. Engineers should verify U-Boot, kernel, device tree, display driver, touch driver, GPU acceleration, Ethernet, Wi-Fi, Bluetooth, audio, GPIO, watchdog, and storage. A powerful SoC with an unstable BSP can waste more time than a moderate SoC with a mature software stack.
For a custom SBC, the BSP should not remain in demo-board condition. It should be cleaned for the final hardware. Unused devices should be removed. GPIO names should be documented. Boot logs should be checked. The production image should be repeatable.
Thermal and Mechanical Integration
Thermal testing must be done inside the real mechanical structure. A board that runs cool on a desk may become hot behind an LCD or inside a sealed enclosure. Heat from the SoC, PMIC, backlight driver, Ethernet PHY, wireless module, and storage can accumulate slowly.
Engineers should test the device at maximum brightness, high CPU load, active communication, and expected ambient temperature. The test should run long enough to show heat saturation, not just a short temperature rise.
Mechanical integration is also part of reliability. Connector direction, cable bend radius, mounting hole position, board thickness, component height, antenna location, and heat transfer path all matter. A custom SBC can be designed to match the enclosure, reduce cable stress, and simplify assembly.
Factory Testing and Traceability
A custom SBC should be easy to test during production. This requirement should be considered during schematic and PCB design, not after mass production starts. Test points, debug UART, programming interface, power measurement points, and clear connector labeling can save a lot of factory time.
A factory test program should check the major functions quickly and clearly. The test result should be easy to understand, and the log should be saved if possible.
./factory_test --display --touch --eth --rs485 --can --gpio --audio --wifi --storage --rtc
For larger projects, each board should have a serial number or QR code. The production record may include firmware version, MAC address, test result, date, and operator. This makes field support much easier when a customer reports a problem months later.
Cost Control Without Weakening Reliability
Custom design is not always more expensive. In many production projects, it can reduce total cost by removing unused parts, reducing cable adapters, simplifying assembly, and improving test efficiency.
However, cost reduction should be done carefully. Removing unnecessary connectors is reasonable. Using a poor-quality power supply component is not. Choosing the right memory capacity is reasonable. Using unknown low-end storage for a logging-heavy product is risky.
Industrial cost control should focus on value. Spend money on the parts that affect reliability: power input, protection, connectors, storage, thermal path, and testability. Save money by removing unused features, simplifying the mechanical design, and improving production flow.
Standard SBC or Custom SBC?
| Question | Standard SBC May Be Enough | Custom SBC Is Usually Better |
|---|---|---|
| Project stage | Early software evaluation | Final product development |
| Volume | Very small quantity | Repeated production or mass production |
| Mechanical fit | Board can be mounted easily | Enclosure and connector positions are fixed |
| Interfaces | Common ports are enough | RS485, CAN, isolated I/O, custom display needed |
| Power input | Clean adapter power | 12V/24V/wide input or noisy field power |
| Software | Demo image is acceptable | Custom BSP, OTA, watchdog, and factory test needed |
| Life cycle | Short-term use | Multi-year product support |
| Certification | Not critical | CE/FCC/ESD/surge requirements exist |
This comparison does not mean every project must start with a custom board. A standard SBC is often the right first step. But when the product requirements become clear, custom design usually gives better control over quality, cost, and long-term support.
Project Flow for a Custom Industrial SBC
A practical custom SBC project usually follows a staged process. First, the engineering team reviews the requirements and selects the SoC. Then the hardware team designs the schematic and PCB. After the prototype is built, the BSP team brings up bootloader, kernel, display, storage, and basic interfaces. Then the product-specific functions are tested one by one.
After basic bring-up, the project should move into reliability testing. This includes power cycling, thermal testing, communication stress testing, storage writing tests, ESD pre-check, and OTA recovery testing. Only after these steps should the board enter pilot production.
This process may look slower than using a ready-made board, but it reduces risk later. Debugging a connector, power, or display problem after thousands of units have been produced is far more expensive than solving it during prototype validation.
Conclusion
A custom SBC for industrial control is a production tool, not just a computer board. It gives the product team control over interfaces, power design, display integration, mechanical fit, software behavior, factory testing, and long-term maintenance.
For industrial HMI, machine control panels, EV charger terminals, factory gateways, medical devices, access control systems, smart building panels, and other embedded control products, a custom SBC can make the difference between a working prototype and a reliable product.
The best design is usually not the most powerful or the most complicated. It is the design that matches the real machine, handles the real environment, and can be produced consistently. In industrial control, reliability is built from many small engineering decisions. A well-designed custom SBC brings those decisions together on one board.