Many manufacturers evaluating an Embedded industrial computer find that the requirement is not just "run some software" — the machine has to actually connect to field devices: infrared alarms, door contacts, smoke detectors, strobe-horn alarms, water pumps, access-control magnetic locks. Most of these devices have no network port; they output dry-contact signals, and that is exactly what the digital I/O (DIO) on the host is for. This article covers three things: what DIO actually connects to, how alarm and automation scenarios are built, and what to confirm before selecting a model.

1. First, what kind of signals does DIO handle?

DIO on an Embedded industrial computer falls into three types:

① DI (digital input): reads on/off switch signals. Both normally-open and normally-closed contacts work. Typical devices: door contacts, infrared/PIR detectors, emergency buttons, smoke-detector alarm outputs, level switches, flow switches. A change in the open/closed state is treated as an event.

② DO (digital output): outputs switch signals to drive external devices. Through relay or transistor outputs, it can drive strobe-horn alarms, warning lights, magnetic locks, water pumps, fans, and indicator lamps.

③ AI (analog input, available on some models): connects 4-20 mA / 0-10 V sensors such as level gauges and temperature/humidity transmitters, reading continuous physical values as numbers.

Reading and writing at the software level is not complicated: in Node-RED, dragging a node polls DI or toggles DO; a Python or C program does the same. The most common minimal alarm chain in industrial settings is "DI trigger → local logic → DO action + event reporting", closed loop within a single device, with no dependency on a host computer.

2. A direction that came up in real discussion

In the homelab community, a hobbyist showed off a fanless industrial computer with eight PoE ports. The most-discussed use among commenters was not a NAS but one scenario: surveillance. One comment put it directly — with that many PoE ports, the machine is a solid NVR/VMS host and can power IP cameras directly; "the DIO port can also be used for alarm signals". Others noted that machines with PoE and I/O are "well suited for security cameras", and after seeing the configuration, one commenter simply said "it looks like a mobile NVR".

This matches what manufacturers commonly need: cameras handle "seeing", while alarms, access control, and sensors handle "preventing", and the two have to work together — with a hub missing in between. An Embedded industrial computer is exactly that hub: video flows over the network ports, switch signals go through DIO, and alarm judgment plus action execution happen on the same device.

3. Scenarios in practice: how to wire and how to use

Scenario 1: Site/warehouse security — video + access control + alarm integration

Requirement: when the gate infrared is triggered, the corresponding camera immediately starts event recording, the strobe-horn alarm sounds, and the alarm message is pushed to the guard room.

• DI connects the door contact or infrared detector; an intrusion changes the signal state;

• Cameras connect via PoE/network ports; the host doubles as the NVR;

• When the program detects a DI event, it marks that camera feed as event recording and toggles DO to drive the strobe-horn alarm;

• Alarm records are reported to the cloud platform via 4G/5G or pushed as messages.

For this, the EG928A is a good fit: RK3588J with a 6 TOPS NPU, up to 32 network cameras, onboard DI/DO, RS485, and CAN, with built-in WukongEdge edge computing supporting face recognition, license-plate recognition, and object detection. AI-detected anomalies can also trigger DO-linked alarms without relying on sensors — an extra layer of proactive detection.

Scenario 2: Electrical room/server room monitoring — sensor collection + device control

Requirement: when water leakage, smoke, or abnormal temperature/humidity occurs, automatically start the fan or drainage pump and sound the alarm.

• RS485 via Modbus collects temperature/humidity, smoke, and water-leak sensors;

• DI connects access-control switches and emergency buttons;

• DO drives the fan contactor, drainage-pump relay, and strobe lamp;

• The logic runs locally, with fallback even when the network or power is lost, while periodic reporting continues.

ARM industrial computers like the EG228/EG528/EG628 fit here: RS485/RS232/CAN support, pre-installed Ubuntu and Node-RED, and protocol compatibility with IEC 61850, IEC 104, DLT645, DNP3.0, BACnet, and more, so most serial field devices can be connected. Wide 9-36 V input and -25 to 75 °C operating temperature mean long-term operation in a cabinet without extra cooling. If local display and manual operation are needed, the USR-SH800 industrial touchscreen HMI can be added.

Scenario 3: Small-scale I/O control — fast prototyping and low-cost retrofits

Requirement: only a few switch-signal channels to collect and control, with a short development cycle.

The EG118 is an Arduino open-source gateway with 2×DO, 1×DI, and 1×AI onboard, supporting Arduino IDE and ESP-IDF development, plus RS485/232, Ethernet, and Wi-Fi. It fits the "validate the logic first, then scale to production" rhythm: the Arduino ecosystem gets the prototype running quickly, and the production phase can migrate to a Node-RED solution on the same platform.

Scenario 4: Sites that must run the Windows ecosystem

Some third-party NVR and SCADA software is Windows-only, or the site explicitly requires a PC-compatible environment — in these cases, choose the X86 architecture. The USR-EC100/EC300/EC500 are X86 industrial computers: the EC100 (Celeron J6412) is low-power, suited for light collection and monitoring; the EC300 carries 14 GPIO channels, 2×RS232/485 (galvanically isolated) and 2×CAN, better for machine vision and motion-control needs; the EC500 has more computing power with a PCIe 4.0×4 expansion slot, suitable for AI inference and high-precision control. The whole series supports wide-voltage input and -20 to 60 °C operation (optional -40 to 85 °C), and runs Windows 10/11 or Linux.

4. Four things to sort out before selecting

① List the DI/DO requirements: how many inputs, how many outputs, dry contact or isolated; 

② Confirm video needs: how many cameras, what resolution — this decides between the NPU-equipped EG928A and a standard ARM model; 

③ Confirm field protocols: Modbus RS485, CAN, or custom protocols; 

④ Confirm environment and installation: supply voltage, temperature range, DIN-rail mounting or embedding inside equipment.

Working through these four before picking a model saves far more effort than picking hardware first and then trying to make the interfaces fit. In real projects, the most common cause of rework is not confirming interface types and channel counts in advance.

5. Where to start

The fastest path: take an EG118 or EG228, run the minimal "DI trigger → DO action" chain with Node-RED, then add video and cloud reporting step by step. The value of DIO is not the hardware itself — it is that video, sensing, control, and reporting close the loop on a single Embedded industrial computer. One fewer device means one fewer point of failure, and one less layer of integration cost.