24V integration

The layer where software actually touches the machine. A 24 volt signal that opens a valve, drives an ejector or stops a line.

A DIN rail with terminal blocks, a compact industrial computer and relay modules

This is the part usually missing from a software quote, and where a project stalls if nobody has taken it on.

Why this is a subject of its own

A model that recognises a defect does nothing until the verdict reaches the machine. That machine does not listen to an API call but to a voltage on a terminal. Between those two worlds sits a separation you make deliberately, because a fault on the field side must not take your compute board with it.

What the connection looks like

Opto isolation

The 24V field side and the computer's electronics stay galvanically separated. The signal crosses as light, not as current. A voltage spike on a sensor cable therefore stays on the side where it started.

Digital inputs and outputs

Inputs to know when a product passes or when the line is running. Outputs, often through relays, to sort, eject or stop. The channel count and isolation voltage come from the datasheet per model, not from a brochure.

Power and mounting

Industrial edge computers run on the same 24V that is already there and mount on DIN rail in the cabinet. Passively cooled, so no fan and no filter. The temperature range of this category goes well beyond what an office PC handles.

To the PLC

Two routes, and usually both. Directly as a digital output for the fast action, and as an OPC UA variable so the verdict is visible in the rest of your systems too. The first one acts, the second one records.

Safety stays where it belongs

An AI verdict is not a safety function. Emergency stop, light curtains and interlocking stay in the safety chain that is certified for it. What we connect drives the process, not the protection of it. We keep that line explicit, even when it is technically tempting to blur it.

With partners where that fits

Panel building, inspection and the safety chain we do with parties who stand behind that work. We supply the software, the connection and the integration, they supply the cabinet and the certification. That is not a referral afterwards but how we lay out the project from the start.

Our approach

From advice to management, with one partner

The same rhythm for every project.

1

Advice

We start with a conversation, not with code. First clarity on what you need and what you do not.

2

Build

We build and integrate to measure, with technology that fits you. You own your data and your code.

3

Manage

We stay involved: monitoring, adjusting and growing with your business.

Stuck between software and the machine?

Tell us what should happen when the model sees something, and we work back to what it takes.

Call 085 083 5775

A 30-minute intake