Hardware & Connectivity

We build the link between the shop floor and your software.

Factories usually have the machines, the controllers and the software. The connection between them is what is missing. We make our own communication units and run our own protocol middleware, so we read the equipment already installed without replacing it.

The chain

From a controller's memory to a decision on someone's screen.

Four hops, all of them ours to own. That is the difference between a dashboard that refreshes overnight and one that shows a fault while it is still happening.

  1. 01

    Machine / controller

    The controllers already on your line, whatever the make — we read them where they are.

  2. 02

    Our unit

    A dedicated unit we build and install. It opens a persistent real-time channel to the controller.

  3. 03

    Middleware layer

    Reads and normalises the native protocol — PROFINET, Modbus, CC-Link IE — into one common model.

  4. 04

    ERP & analytics

    Live signals become work orders, dashboards, alerts, and maintenance history inside the ERP.

Our hardware

Communication units, built for the plant.

Our units sit in the cabinet or on the line and hold a real-time channel to the controller. They are not a data logger bolted on afterwards — they read the same memory the machine's own program reads, so there are no extra sensors to install and nothing to recalibrate.

We build the hardware ourselves, so we can adapt it to your controller and your network instead of asking you to buy around a fixed product. Recent units run against the controllers already running on client lines.

Discuss a pilot unit
Channel
Persistent, event-driven — not a nightly export
Controllers
Any make of controller we can reach — no controller replacement
Protocols
PROFINET, Modbus, CC-Link / CC-Link IE, or optocoupler I/O
Footprint
Installed in the cabinet or on the line
Ownership
Unit, middleware and ERP from one supplier
Connectivity

We talk to the controller, whichever one you run.

We do not sell controllers and we do not ask you to replace them. We reach the controller you already have over an industrial protocol — or, where there is no network port to reach, at the I/O level through optocouplers.

Protocols and interfaces

PROFINET

Cyclic I/O and diagnostics over industrial Ethernet.

Modbus TCP / RTU

The lowest common denominator in the plant — on nearly every meter and drive.

CC-Link / CC-Link IE

Field and industrial Ethernet networks, read natively.

Optocoupler I/O

Galvanically isolated tapping of digital and analogue signals where a controller has no network port.

OPC UA

A standard route into newer controllers and SCADA layers.

EtherNet/IP

Another common industrial Ethernet dialect, on the same unit.

Signals

What we actually pull off the machine.

Everything the controller already knows but never sends anywhere — because there was no one to carry it out. Once the channel exists, this stops being a black box.

  • Machine state and mode
  • Error and fault codes, timestamped
  • Cycle counts and part counters
  • Stoppage durations, by cause
  • Setpoints and process values
  • Consumption from energy meters
Live tag read
lineL2 · assembly
plcline controller
protocolPROFINET
staterunning
error code—
cycles14 827
energy41.6 kW
Illustration of a single unit's tag view.
Energy

Meters read live, not read by hand.

Energy is the most common blind spot in a plant, because reading meters is usually somebody's side task with a clipboard. We read them the same way we read a controller.

Read through the middleware layer

Real meter readings, on a live feed.

Our middleware layer reads your energy meters over Modbus and streams active energy, instantaneous demand and phase-level values into the ERP. Consumption arrives continuously, attributed to the line or machine that produced it. Any meter with a Modbus interface works — we do not resell meters, and you are not tied to a brand.

  • Consumption per line, per machine, per shift
  • Live load and peak demand, as it happens
  • Budgets tracked against actuals, without manual entry
  • The same dataset feeding alerts and reporting
Getting started

A pilot that answers the question in days.

We do not begin with a proposal. We begin with your cabinet, and one machine.

  1. 01

    Plant survey

    We look at the controllers, the network, and one process you cannot currently see. No proposal document — a conversation about what is readable.

  2. 02

    One unit, one machine

    A pilot unit on a single line. It is the honest test: either the signal comes out or it does not, and you know within days.

  3. 03

    Decide with data

    You get the real signals from your own machine before committing to a rollout — to the ERP, more lines, or energy metering.

Questions

The things engineers ask first.

Do we have to replace our controllers?

No. The unit reads the controllers you already run and does not change your automation logic. Retrofitting a line does not mean rewriting it.

What if our controller is not on your list?

That is usually a protocol question, not a blocker. Tell us the make and model and we will tell you straight away whether we can read it.

Can you read energy meters too?

Yes. Our middleware layer reads energy meters over Modbus, and each reading is attributed to the line or machine that consumed the power.

Do we need your ERP to use the hardware?

The unit and middleware stand on their own. Most clients feed the ERP, because that is where a fault becomes a work order, but the signal is yours either way.

Tell us the controller and the meter.

Send us the controller, the energy meters, and one process you cannot see today. We will tell you what is readable and how long a pilot takes.