Custom SBC for Industrial Control: Designing a Board That Can Survive Real Machines

Industrial control hardware is usually judged in a very practical way. It does not matter how good the specification looks if the board cannot run reliably inside the final machine. A product may pass the first software demo, show a clean user interface, and communicate with a sensor on the engineer’s desk. But the real test begins later: when the board is installed inside a cabinet, connected to long cables, powered by a noisy supply, placed behind a hot display, and expected to work every day without special care.

This is why a custom SBC is often the right direction for industrial control products. A standard single board computer can be useful during evaluation, but it is rarely perfect for a production machine. Industrial products normally have fixed mechanical space, specific power input, defined connectors, required communication ports, and long-term service expectations. A custom SBC allows the electronics to be designed around those requirements instead of forcing the product to adapt to a general-purpose board.

For industrial HMI, machine control panels, EV charger terminals, smart building controllers, medical devices, access control systems, factory gateways, and embedded IoT equipment, the SBC is not just a computer. It is the main control platform of the product.

What Is a Custom SBC?

A custom SBC, or custom single board computer, is a board designed for a specific product or product family. It usually integrates the processor, memory, storage, power management, display interface, touch interface, communication ports, I/O signals, and sometimes wireless or security functions on one board.

The word “custom” does not always mean a completely new design from zero. In many projects, the design may start from a proven SoC platform or an existing reference board. Then the hardware is modified to fit the final product. Unused interfaces are removed. Required industrial ports are added. Connectors are moved. Power input is redesigned. Display and touch interfaces are matched to the selected panel. Software is cleaned and configured for the final hardware.

This approach is different from using a development board. A development board is made for flexibility. A custom SBC is made for production. Flexibility is useful in the lab, but production needs consistency, reliability, and cost control.

Why Industrial Control Needs Custom Hardware

Industrial control systems have different priorities from consumer electronics. A consumer device may focus on appearance, short replacement cycles, and feature marketing. An industrial device must focus on stable operation, long service life, electrical protection, repeatable production, and field maintenance.

In a factory or equipment room, the environment is not always friendly. Power may be unstable. Grounding may be imperfect. Motors, relays, compressors, chargers, and inverters may create electrical noise. Cables may be long. Users may plug and unplug connectors while the system is powered. The enclosure may have poor airflow. The device may run 16 hours a day or continuously for years.

A board that works well on a desk may not behave the same way in this environment. This is why industrial SBC design must consider power protection, ESD, EMI, thermal margin, connector reliability, watchdog recovery, and software robustness from the beginning.

Standard SBC vs Custom Industrial SBC

This does not mean standard boards are useless. They are valuable in the early stage. They help the team evaluate the SoC, test the operating system, and develop the first application. But once the product definition is clear, custom design usually gives better control.

Designing Around the Real Application

A good custom SBC project starts with the machine, not with the chip. The engineering team should first understand what the product really needs to do.

For example, an industrial HMI may need a 10.1-inch display, capacitive touch, Ethernet, two RS485 ports, speaker output, a few GPIO signals, and a 12V power input. An EV charger display may need Android, 4G, Wi-Fi, RS485 or CAN, secure storage, payment module support, and OTA update. A factory gateway may need dual Ethernet, isolated RS485, CAN, local logging, MQTT, and DIN-rail mounting.

These products may all use an ARM-based SBC, but the board requirements are not the same. If the same generic board is used for all of them, the final product may contain unnecessary adapters, cables, converters, or mechanical compromises. A custom SBC reduces these compromises.

SoC Selection: Practical Performance Matters

The SoC is the center of the SBC. It decides CPU performance, graphics capability, display output, video processing, memory support, peripheral resources, and the software ecosystem. But in industrial control, the best SoC is not always the newest or fastest one.

A simple Linux control panel may only need a stable low-power SoC. It may run a fixed UI, read Modbus data, control a few GPIOs, and upload logs over Ethernet. In this case, excessive performance may only increase heat and cost.

A modern Android panel needs more resources. It may run a richer UI, handle video playback, manage Wi-Fi and Bluetooth, connect to a cloud service, and support OTA updates. In this situation, platforms such as RK3566, RK3568, or RK3576 may be a better fit.

For edge AI, multi-camera processing, machine vision, or high-resolution display systems, RK3576 or RK3588 class platforms may be more suitable. RK3576 is especially useful when the product needs stronger performance than older mid-range SoCs but does not need the full cost and power level of a high-end processor.

The right SoC should provide enough margin for current software and future updates. Industrial software rarely becomes lighter over time. Customers add more pages, logs, communication protocols, security functions, remote access, and diagnostic tools after the first version.

Display and Touch Integration

Many industrial control products are built around the display. The LCD is not only an output device. It is the main interface between the user and the machine. If the display is unstable, noisy, too dim, or poorly integrated, the whole product feels unreliable.

A custom SBC should be designed together with the selected LCD panel. Engineers need to confirm the display size, resolution, interface, timing, backlight voltage, brightness control, connector type, cable length, and screen orientation. Common interfaces include RGB, LVDS, MIPI-DSI, HDMI, and eDP.

Touch integration is just as important. Capacitive touch panels usually use I2C with reset and interrupt signals. In real industrial environments, touch behavior can be affected by grounding, cover glass thickness, water, gloves, EMI, and cable routing. The board should include proper ESD protection, stable power for the touch controller, and clean signal routing.

During production, a simple test tool can help confirm display and touch functions:

./panel_test --display --touch --brightness 100 --duration 60

The command itself is simple, but this type of factory check can prevent many shipment problems.

Industrial Communication Interfaces

Communication is a major part of industrial control. The SBC may need to connect to PLCs, meters, sensors, relays, motor drives, scanners, cameras, printers, or cloud servers.

RS485 is common because it is robust and suitable for long-distance differential communication. CAN is widely used in vehicles, energy equipment, and industrial systems. Ethernet is used for factory networks and remote management. USB may connect scanners, service tools, cameras, or storage devices. GPIO may control buzzers, LEDs, relays, buttons, or power-enable signals.

These interfaces should not be treated as simple pins on a schematic. External communication lines need protection. RS485 may require termination, biasing, surge protection, and isolation. CAN needs a proper transceiver and protection design. Ethernet needs good magnetics, impedance control, and ESD planning. GPIO connected to field wiring may need filtering, level shifting, or isolation.

A custom SBC allows these interfaces to be designed directly into the board instead of using external USB converters or messy adapter cables. This improves reliability and makes assembly cleaner.

Power Design: The Hidden Reliability Factor

Power design is one of the most important parts of an industrial SBC. Many system problems that look like software bugs are actually power problems. A board may reboot randomly when the display backlight turns on. The system may freeze when a wireless module transmits. USB devices may fail when the input voltage drops. These issues are often caused by insufficient power margin or poor power sequencing.

Industrial devices may use 5V, 12V, 24V, PoE, or a wide input voltage range. The input may include noise, surge, ripple, or short interruption. A custom SBC should include suitable DC-DC conversion, input filtering, over-voltage protection, over-current protection, and sometimes reverse polarity protection.

The power tree must also match the SoC requirements. Core voltage, DDR voltage, I/O voltage, storage power, display power, touch power, and wireless module power may all have different timing and current needs. If this is not handled properly, the board may pass basic testing but fail randomly in the field.

Watchdog and Recovery Design

An industrial device should not depend on a person standing nearby to restart it. If the application hangs, the system should recover. If an update fails, the device should have a fallback path. If power is lost during operation, the file system should remain usable.

A hardware watchdog is often necessary. The application or system service should feed the watchdog only when the system is healthy. If the software stops responding, the watchdog resets the board.

OTA update also needs careful design. A safe update mechanism may include dual partitions, recovery mode, version checking, rollback logic, and update logs. This is especially important for remote devices, where physical service is expensive.

A basic reliability test may include repeated reboot and update cycles:

./reliability_test --reboot 500 --ota update.img --log result.txt

This type of testing is not glamorous, but it often reveals problems before mass production.

Thermal Design Inside the Enclosure

Thermal testing should be done inside the real mechanical structure. An open development board may run at a comfortable temperature, but the final product may place the SBC behind a warm LCD, inside a sealed plastic enclosure, or near a power supply.

Heat sources include the SoC, PMIC, DDR, eMMC, Ethernet PHY, wireless module, backlight driver, and sometimes external USB devices. The internal temperature may rise slowly and reach a stable point only after several hours.

A useful thermal test should include maximum backlight brightness, high CPU load, network activity, storage writing, and normal application behavior. Engineers should also test the expected ambient temperature, not only room temperature.

Good thermal design may use copper area, metal frame contact, thermal pads, heat spreaders, proper component placement, and software thermal limits. In fanless industrial products, small thermal details can decide long-term stability.

Software Platform and BSP Work

The software platform depends on the application. Linux is common in industrial control because it is flexible, stable, and suitable for custom drivers and background services. It works well with Qt, GTK, LVGL, MQTT, Modbus, CAN, RS485, local databases, and web services.

Android is useful when the device needs a rich touchscreen interface, multimedia playback, app-style UI, or user-friendly configuration. It is common in smart panels, access control terminals, retail devices, EV charger screens, and commercial control panels.

A custom SBC project needs more than a demo image. The BSP should be adjusted for the final board. U-Boot, kernel, device tree, display driver, touch driver, Ethernet, Wi-Fi, Bluetooth, audio, GPIO, watchdog, storage, and update tools should be verified. Unused features should be disabled. Boot messages should be checked. GPIO definitions should be documented.

For production, the software image should be repeatable. Engineers should be able to build the same firmware version again, trace changes, and provide updates to customers later.

Factory Testing and Production Control

Factory testing should be considered during board design. If there are no test points, no debug UART, no clear programming method, and no simple test software, production becomes inefficient.

A good factory test process checks the major hardware functions quickly. The test should include display, touch, Ethernet, RS485, CAN, USB, audio, GPIO, storage, Wi-Fi, Bluetooth, RTC, and any product-specific interface. The result should be clear enough for factory workers to understand.

A typical test command may look like this:

./factory_test --display --touch --eth --rs485 --can --usb --audio --gpio --wifi --storage

For larger projects, each board should have a serial number or QR code. The production record can include MAC address, firmware version, test result, date, and operator. This helps trace problems later.

Cost Control Without Damaging Reliability

Custom SBC design can reduce cost, but cost reduction must be done carefully. Removing unused connectors, unused ICs, and unnecessary adapters is reasonable. Reducing PCB size may also help. Optimizing assembly and testing can save labor cost.

But saving money on key reliability parts can be dangerous. Poor storage can fail early in logging applications. Weak power components can cause random resets. Cheap connectors can create field service problems. Insufficient ESD protection can increase return rates.

Industrial cost control should focus on total cost, not only BOM cost. A slightly more expensive protection device may save many after-sales issues. A better connector may reduce installation failures. A good factory test tool may save hours of manual checking.

How to Start a Custom SBC Project

A practical custom SBC project should begin with a clear requirement list. The team should define the display, touch, operating system, SoC class, memory, storage, power input, communication interfaces, enclosure size, mounting method, temperature range, certification target, and production volume.

It is also important to separate fixed requirements from flexible ones. The enclosure may already be fixed. The LCD may be selected. The operating system may be required by the customer. But the SoC, connector type, memory size, or wireless module may still be flexible. Identifying these points early prevents unnecessary redesign.

A normal project flow includes requirement review, SoC selection, schematic design, PCB layout, prototype build, board bring-up, BSP customization, display and touch debugging, interface testing, thermal testing, EMI pre-check, factory test development, pilot production, and mass production.

Conclusion

A custom SBC for industrial control is not only a board with a processor. It is the hardware and software foundation of the final machine. It must match the real display, real communication ports, real power input, real enclosure, and real operating environment.

For industrial HMI, EV charger terminals, factory gateways, medical terminals, access control systems, smart building panels, and machine controllers, a custom SBC can reduce wiring complexity, improve reliability, simplify assembly, and provide better long-term control over the product.

The best industrial SBC is not necessarily the most powerful one. It is the one that fits the application, survives the environment, supports stable software, and can be produced consistently for years. In industrial control, good engineering is usually not one big feature. It is the result of many small decisions made correctly.