MEJK Bridge
← Back to website DE
Live signal

Retrofit gateway · any machine → umati / OPC UA

Old machine in. umati out.

A small box that speaks to the machine you already have — CAN, Modbus, serial, OPC UA — and republishes it as a standard OPC UA / umati server, live in your dashboards. No new controls. Nothing lost on the way. Minutes, not months.

Scroll

The problem

A hall full of machines.
None of them talk.

Your newest cell speaks OPC UA. The 2010 press speaks Modbus. The 2003 laser speaks a serial dialect only its vendor remembers. To an MES — or a umati tender — they're invisible. Ripping out working controls to modernize each one is a months-long intervention in running production.

2003
Laser welder
RS-232 · vendor ASCII
no data out
2008
CNC press
CAN bus
no data out
2011
Bending cell
Modbus RTU
no data out
2016
Cutting line
Modbus TCP
island of data
2021
Robot cell
OPC UA · own model
non-standard
The tender
requires umati
unmet

One box, every dialect

Bridge listens to whatever the machine speaks.

One driver per box, chosen in config. Six field protocols in — and a built-in simulator, so you can prove the whole chain on a laptop before a single cable is run.

Modbus TCPEthernet PLCs & drives
Modbus RTURS-485 serial registers
CAN busmotion & drive networks
RS-232 ASCIIlegacy vendor consoles
OPC UAmodern, non-standard models
Raw TCP/IPanything with a socket

Live · what the box actually does

Read. Map. Serve. And never drop a record.

Bridge polls the machine, maps raw registers to named fields, publishes them as a umati OPC UA server and pushes them to your office — while a store-and-forward journal guards the one thing that kills retrofits: the network dropping mid-shift.

MEJK Bridge — Store & Forward page after a real network outage: the queue-depth chart shows the climb and the in-order drain, 17 buffered · 17 delivered · 0 lost.
Not a mockup — the shipping UI after a real network cut: the journal drew the outage (flat → climb → drain), 17 buffered · 17 delivered · 0 lost. Verified end-to-end, including a second box reading the umati OPC UA server like any MES.

Why it matters

The tender says umati.
Your machine says 2003.

01

Standard out, retrofitted in

umati / OPC UA for Machinery — the address space MES vendors and tenders now demand — bolted onto machines that were never designed to speak it.

02

The controls don't move

Bridge only reads. The machine runs exactly as it does today — no re-commissioning, no safety re-approval, no risk to a line that already works.

03

Minutes, proven on a bench

Pick the protocol, map the tags, point at your dashboard. The built-in simulator lets you prove the full chain before you touch the real machine.

04

A DIN-rail box, not a project

Runs self-contained on a DIN-rail RevPi / IOT2050, or as a Windows service on the PC already at the machine. No custom board, no cabinet rebuild.

Where it shows up

Pick the front end.
The data's already flowing.

The same normalized stream feeds whichever view fits the job — from a full plant platform to a single screen at the machine.

Full platform
MEJK ControlCenter — fleet dashboard

MEJK ControlCenter

Fleet OEE, SPC, part-genealogy traceability and alarms across every machine — the Industry 4.0 platform for running the whole shop.

Lightweight
MEJK LiveView — single-machine live view

MEJK LiveView

A simple live dashboard for when you just want to see the machine, now — no rollout, no fleet, one honest window on the process.

At the machine
MEJK Core operator HMI

MEJK Core HMI

Feed the machine's own modern operator screen from the same stream — the retrofit that also gives the operator a display worth looking at.

And because Bridge serves standard umati OPC UA at the same time, any third-party MES or SCADA reads it too. You add data, not a lock-in.

Next step

See it on your machine.

30 minutes, live — the whole chain runs against a built-in machine simulator, no hardware needed. Then we map it to your machines, your registers, your dashboards.