Read a stack light by tapping the signal that drives each lamp or by fitting a light sensor to each segment, then map each color to a state for that machine. Add a part count, because green often means the machine is ready, not that it is producing.
Why monitor a lamp at all
A stack light is the machine's own summary of its state. The builder has already wired the hard logic into it, so a lamp can hand you a fault signal without anyone opening the program.
That makes it a low-risk source on a machine with a closed or unreadable controller. You only listen to the lamp, and you never touch the logic behind it.
The people side matters too. Operators already understand the colors, as they use the same signal as an andon, so the data matches what they see.
Two ways to read the lamp
Tap the electrical signal
A qualified electrician connects each lamp's control wire in parallel to an input on an I/O module, usually through an isolating relay. This is clean and immune to room light, but it does mean opening the panel or lamp base.
The electrician checks the voltage first. Many stack lights run on 24 V DC and others on AC mains, so the input must suit the lamp, and the panel must be made safe before anyone opens it.
Fit an optical sensor to each segment
A small light sensor sits against each lit segment, and nothing is wired into the machine. It is quick to fit and easy to move, which helps in a pilot.
The weak points are ambient light, knocks and dirt. Shade the sensors, and set their trigger levels with the lamp both on and off in real shop lighting.
Some sites use a third route, a camera that watches the lamps. It can work, as long as the view stays clear and the camera handles flashing correctly.
Map colors to states, machine by machine
A common pattern exists, but no rule forces a builder to follow it. Amber can mean low material on one machine and a door open on the next.
Ask the operator and check the manual, then write the map down.
| Lamp pattern | Meaning on this machine | State |
|---|---|---|
| Red, steady or flashing | Alarm, machine halted | Fault |
| Amber flashing | Material low, still running | Keep current state, flag it |
| Amber steady, green off | Cycle stopped, waiting | Stopped |
| Green steady, parts counted | Auto, producing | Running |
| Green steady, no parts | Auto, ready, no output | Stopped (no output) |
| All dark, machine powered | Manual mode, or a blown lamp or sensor | Check, do not assume |
Handle flashing lamps
A flashing lamp is a stream of on and off pulses. Logged raw, one alarm can turn into hundreds of tiny faults.
The fix is to hold the on state through short dark gaps. Example: treat a lamp as on until it has been dark for 3 seconds, which must be longer than its flash gap.
Cut the hold time off the end of the stop, so a 3-second tail does not inflate each fault. On machines with many short alarms, that small error can add up.
Watch for a lamp test too. Some machines light every segment briefly at power-up, and a short hold timer on red stops that from reading as a fault.
Worked example: the green trap
Example: a machine is scheduled for 480 minutes. The lamps show green for 384 minutes, amber for 62 and red for 34.
Green alone suggests 384 / 480 = 80.0% availability. A part sensor then shows that for 41 of the green minutes, nothing came out: the machine was starved, in auto, with its green lamp on.
Those 41 minutes are the reason to pair the lamp with a counter. Part counting sensors shows what to fit, and blocked and starved explains what those minutes usually are.
The count also gives you performance, and a good or reject count adds quality. With those you have a full OEE number, so check it with the OEE calculator.
What a stack light cannot tell you
- Why it stopped. Red says fault, not which fault. Operators need to tag the cause from a short list of reason codes.
- Whether a stop was planned. A changeover and a jam can show the same lamp, so use a mode signal or an operator input.
- Short stops under the lamp logic. Some machines do not change the lamp for a brief pause. Compare with the count, and see what are micro-stops.
- Speed. A green lamp looks the same at half speed. Only a count shows that.
Fitting it on one machine
Ask the operator what each color means, steady and flashing, and write it down.
Tap the signal for long-term use, or use optical sensors for a quick pilot.
A qualified electrician handles any work in the panel or lamp base.
Without one, green time overstates production.
Compare lamp states with what you see at the machine.
Adjust the hold times and the priority, then copy to the next machine.
Mistakes that make lamp data wrong
- Copying the color map across machines. Different builders use amber differently.
- Treating dark as stopped. A blown lamp, a failed sensor or a cut wire looks the same as a stop. Flag long dark periods for a check.
- Skipping the shade. Sun moving through a skylight can trigger an optical sensor at the same time every day.
- Changing the machine's own lamp wiring. Only monitor it in parallel, and leave the machine's behavior alone.
A lamp is one route among several, and it may not be your best one. If you can read a controller, start with PLC signals for OEE instead.
If the choice is still open, compare the routes in how to connect old machines.
A lamp shows that a machine stopped, but the reason needs a person. In Fabrico, a light MES for OEE, stops, speed and counts come live 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. See how Fabrico tracks stops.
What people ask next
What do the colors on a stack light mean?
A common pattern is green for normal running, amber for a warning or attention, and red for a fault, with blue sometimes used for an operator request. The meaning is set by the machine builder or your own site, so confirm it for each machine. Write the map down before you use the data.
Can I connect to a stack light without touching the machine's wiring?
Yes. Optical sensors attach to the outside of each segment and read the light, with no electrical connection. They need shading and tuning, as room light can affect them.
Do stack lights give accurate downtime data?
They give accurate timing of what the lamp showed, which may differ from what the machine was doing. Green can include time with no output. Pair the lamp with a count, and test it as in downtime data accuracy.
How do I monitor a stack light with a flashing signal?
Hold the on state through dark gaps shorter than a set time, such as 3 seconds, and then trim that time from the end of the stop. The hold must be longer than the lamp's flash gap. Otherwise one alarm logs as many short faults.
What if the machine has no stack light?
You can fit one, but it needs a signal to drive it. On most old machines, a clamp-on current sensor with a part counter is a simpler route to the same state data.
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.