You have six main options: an old serial port, a protocol converter, tapping existing relays into a new I/O module, external sensors, a camera, or operator input. Work through them in that order and stop at the first one that safely gives you state and count, which on many no-port machines is a current sensor plus a part counter.
First, get clear on what you need
You are not trying to modernize the machine. For OEE, you need to know when it runs, how many parts it makes, and how many are good.
That small list opens many options. A full controller upgrade is one route, but it is rarely the first thing to try for data alone.
"No usable port" also covers several different problems. The controller may be closed, the port may be an odd legacy type, nobody may have the program, or the machine may have relays and no PLC at all.
Work down this list
Check for serial, fieldbus or Ethernet on the controller, drive, HMI or any meter.
Converters exist for many older PLC families, and turn their port into a modern network.
Read a spare auxiliary contact into a new I/O module, leaving the existing logic alone.
Use a current clamp, a stack light reader and a part sensor, all outside the logic.
Watch product flow or the machine, where the output is visible.
A tablet or a button gives you a start now, and the context that signals miss.
Option 1: a port you have missed
Old does not always mean closed. Look at the controller, and also at drives, temperature controllers, HMIs and counters on the machine.
Many of them have an RS-232 or RS-485 port, or a fieldbus connector. A drive that speaks Modbus can tell you its run status and speed even when the PLC beside it cannot.
CNC machines deserve a special check. Some controls offer a data interface such as MTConnect, or FOCAS on Fanuc controls that support it, though it may be a paid option or need an adapter or Ethernet board, so ask the maker or dealer.
Option 2: a protocol converter
If the PLC has a port but nothing in your plant can talk to it, a converter can bridge the gap. These devices connect to the old port and present the data over a modern network.
You will still need to know which addresses hold the values. Without the program or a person who knows it, this route can stall, so ask early.
See PLC signals for OEE for what to read once you are in. An IIoT gateway often includes such drivers.
Option 3: tap the existing relays
A relay machine still has signals, in the form of switched contacts. A motor starter, for example, often has an auxiliary contact that closes when the motor runs.
A spare contact wired to a small I/O module gives a clean run signal, and a limit switch or cycle relay can give you a count. This is often the most dependable result on an old machine, because it reads what the machine itself uses.
Three rules protect you here:
- Use a spare contact, or an interposing relay. Do not load a control circuit with new wiring that could change how it behaves.
- Stay out of safety circuits. Leave E-stops, guards and safety relays alone.
- Use a qualified electrician, with the panel made safe, and update the drawings. The next person to fault-find must see what you added.
Option 4: external sensors
When you cannot or will not enter the panel logic, watch the machine from outside. This is where most no-port machines land.
- A clamp-on current sensor shows whether the main motor is working. It sits inside the panel, so a qualified electrician fits it.
- A stack light reader gives you faults, where the machine has a lamp.
- A part sensor gives counts, speed and proof of output.
- A vibration sensor can indicate motion on a machine with an unclear current signal, after a test on that machine.
The neighbor guide retrofit sensors for OEE works through a full example from sensors to an OEE number. The join between signals is covered in machine state detection.
Option 5: a camera
A camera touches nothing on the machine. It works best where product leaves in a clear stream, and it can also record what happened at a stop.
Dust, steam and poor light can hurt it, so test before you rely on it. Computer vision for OEE covers the limits.
Option 6: operator input
A button or a tablet needs no wiring into the machine at all, and it can start today. Manual records miss short stops and round off times, so treat the result as a first view.
Even with sensors, you still need people for causes. See operator downtime logging.
How the options compare
| Option | State | Count | Fault detail | Needs | Main risk |
|---|---|---|---|---|---|
| Existing port | Yes | Often | Often | Address map | Missing documents |
| Protocol converter | Yes | Often | Often | Converter, addresses | Addresses unknown |
| Relay tap | Yes | If a cycle signal exists | Some | Electrician, I/O module | Poor wiring practice |
| External sensors | Yes | Yes | No, unless a lamp is read | Mounting, power, electrician for the clamp | Threshold drift |
| Camera | From flow | If visible | Video of the stop | Clear view | Light, dust, view |
| Operator input | Coarse | Manual | Words, not codes | Tablet or paper | Missed short stops |
Example: a plan for six old machines
Example: a hypothetical plant has six machines with no usable PLC data, all built before networks were common. Here is how a team might sort them in an afternoon's walk.
- Two mechanical presses: a proximity sensor on the ram gives strokes, and a current sensor gives motor state.
- One lathe with an old CNC control: the control has a serial port, but no data protocol is known, so a current sensor goes on the spindle drive supply and a part count comes from the bar-feed signal.
- One relay-based bagger: a spare contact on the cycle relay gives a clean count, and an auxiliary contact gives run state.
- One moulding machine: its temperature controllers speak Modbus, but that shows heat and not production, so a cycle signal from a spare relay is used instead.
- One hand-loaded oven: a current sensor plus operator input, because batches are visible only to the person loading them.
Notice that no single answer covered all six. Fit the method to each machine, and keep one data model behind them all, so that their OEE numbers compare.
What the number of signals buys you
You can start small. Each added signal gives you a sharper view of the same machine.
A lower number here is progress. Now you can see the loss, and track it with the team.
Four ways this goes wrong
- Replacing a controller just to get data. That can make sense for other reasons, but it is a large, risky project for a few signals.
- Skipping the pilot. Fit one machine of each type first, and compare it with a hand log for a shift.
- Writing to old controllers. Your connection should read only. An accidental write to a machine that has no backup program can stop production for days.
- Leaving no owner. Sensors drift and brackets get knocked, so someone must own the data after go-live.
Start with one walk
Walk your oldest machines with an electrician and a phone camera, and let the electrician open any cabinet. For each one, photograph the controller, drive labels and spare contacts, then pick the first option from the list that fits.
Start with the machine that causes the most arguments. A week of data there will teach you more than a survey of all of them.
Data from an old machine only pays off when someone can act on it. Fabrico, a light MES for OEE, takes stops, speed and counts from PLCs or external IoT sensors on older machines, with add-on AI cameras counting output where a machine has no usable signal, with OEE per line and shift. See how Fabrico connects older machines.
What people ask next
Can you get OEE from a machine with no PLC at all?
Yes. A run signal from a current sensor or a relay contact, plus a part count, gives availability and performance. Add a reject count or entry for quality, as shown in retrofit sensors for OEE.
Is it safe to connect to an old PLC?
A read-only link is generally low risk, but old controllers can be sensitive to extra network or serial traffic. Back up the program first if you can, test while someone who knows the machine is present, and read slowly at first. Never write to it.
Should I replace an old controller to get data?
Usually not for data alone. External sensors or a spare contact can give you state and count with much less risk. Replace the controller when spare parts or reliability force the decision, and use the upgrade to add data access.
What hardware do I need besides the sensors?
Something has to read the signals and pass them on. That is usually an I/O module or a wireless sensor node, with a gateway or a local network link to your software. IIoT gateway explains when you need one.
What about machines with no network nearby?
Options include a wired run, wireless sensor nodes or a cellular gateway. Check signal strength at the machine, because metal, motors and thick walls can block radio signals. A gateway that stores data during gaps protects your records.
How long does it take to connect an old machine?
It depends on access, panel work and site rules, so plan one machine as a pilot and time it. Add the test against a hand log to that plan, because the checking often takes longer than the fitting.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.
Related guides: Shop Floor Data Collection: Methods Compared · Shop Floor Kiosk: Hardware That Survives the Line · MES vs HMI: Two Screens, Two Different Jobs