When a piece of equipment trips, a whole cascade of conditions can go bad within a fraction of a second. A compressor that loses lube oil quickly also sees pressure and vibration excursions, and by the time an operator looks, half a dozen shutdown inputs are showing bad. The problem is figuring out which one actually happened first, because that is the root cause and the rest are consequences. First-out logic is the PLC technique that captures the true initiator of a trip out of a series trip string, so operators are not left guessing among symptoms that all arrived at nearly the same instant.
Trip string and first-out logic in one line: A trip string is the series chain of shutdown initiators wired so that any one going bad breaks the chain and trips the equipment. First-out logic is the PLC technique of latching which initiator in that string became active first, so that when several conditions cascade within the same scan, the operator can see the genuine root cause rather than a wall of equally-lit trips. It captures the first bad input at the moment of the trip and holds it for review.
A trip string is conceptually the mirror of a permissive string. Where a permissive chain says all of these must be true to start, a trip string is a series arrangement of healthy contacts that must all stay closed to keep running; if any single initiator goes bad, its contact opens, the chain breaks, and the equipment trips. It is a clean, robust way to enforce that any one of many protective conditions can shut the machine down, and mechanically it is beautifully simple: the current either flows through every link or it does not flow at all.
The weakness of the string, taken alone, is that it discards the one piece of information the operator most wants. The chain only knows whether it is intact or broken; it does not remember which link broke first. Once the trip has occurred, other conditions rapidly go bad as a consequence, and every one of them opens its contact too. Looking at the string afterward, all you see is that it is broken and that many inputs are now bad. The mechanical trip string, by its nature, cannot tell you which of those was the initiator and which were merely the aftermath.
This matters because the wrong root cause leads to the wrong fix. If a bearing failure caused high vibration that tripped the machine, but the operator sees only that high vibration, low oil pressure, and high temperature all show bad, they may chase the oil system when the real problem was the bearing. Cascades are the norm, not the exception, in fast trips, so a protection scheme that only reports the final state of the string is telling the operator what the machine looks like after the accident, not what started it.
First-out logic solves this by adding memory that records which initiator went bad while the machine was still healthy. The key idea is timing: at the moment the trip string is still intact, meaning the equipment is running normally, the logic watches each initiator. The instant one of them changes to the bad state, and only that one has yet gone bad, the logic latches a first-out bit for that specific input. That latched bit is the captured root cause, frozen at the moment of transition before any consequential conditions have had a chance to follow.
The crucial detail is that first-out capture is gated by the healthy state. The logic only arms itself to capture a first-out while everything is normal, and it latches on the first transition to bad. Once that first bit is set and the trip has been declared, the logic stops capturing, so the flood of consequential trips that follow within the next few scans does not overwrite or add to the first-out record. This is what lets it distinguish the initiator from the aftermath even when they are separated by only a scan or two, which a running operator could never resolve by eye.
In practice the first-out bit is latched and held until the operator resets it, exactly like a latched alarm, so the captured cause survives on the screen long after the fast transient is over. Because it is latched, it also rides comfortably over a slow SCADA poll: the remote system can read the held first-out state at its own pace and still report the correct initiator. The result is that the operator, whether standing at the panel or watching from a control room hundreds of miles away, is told the one condition that started the shutdown, not the dozen that finished it.
Take a compressor emergency shutdown. The trip string might include low lube oil pressure, high vibration, high discharge temperature, high discharge pressure, and an overspeed. In a real event these are heavily coupled: an overspeed drives temperature and pressure up, a bearing problem drives vibration and then oil pressure, and within a handful of scans several of these initiators are all bad. Without first-out logic, the post-trip picture is a cluster of red, and the analysis becomes an argument about which came first.
With first-out logic in place, the controller latched the single input that went bad while the string was still intact, say high vibration, and holds it. When the operator investigates, the first-out display points straight at high vibration as the initiator, and the other trips are correctly understood as consequences that piled on afterward. The maintenance effort goes to the vibration source, the bearing or the coupling, instead of being scattered across every system that happened to trip. The root cause has been preserved through the chaos of the shutdown.
This capability is especially valuable for remote and unmanned compression, where no one witnessed the trip and the only record is what the controller kept. A cloud dashboard that surfaces the latched first-out cause turns a remote shutdown from a mystery into a diagnosis: a supervisor sees not just that the unit tripped, but the specific initiator the controller captured at the instant it happened. Reconstructing that from a raw list of everything that ended up bad would be guesswork; the first-out record makes it a fact, which is what makes remote troubleshooting of fast trips actually workable.
A series trip string only knows whether it is intact or broken; it does not remember which link opened first. When a trip happens, consequential conditions rapidly go bad too and open their contacts as well, so afterward the string shows many bad inputs with no indication of the order. It reports the state of the machine after the accident, not the initiator that started it, which is why separate first-out capture is needed.
It arms itself only while the trip string is still healthy and the equipment is running normally. The instant one initiator transitions to the bad state, before any others have gone bad, it latches a first-out bit for that specific input and then stops capturing. Because the flood of consequential trips arrives a scan or two later, they cannot overwrite the first-out record, so the captured bit is the genuine initiator.
They share the same goal of identifying the initiating cause, but this is the logic technique inside the controller that latches the first bad input in a trip string, rather than a hardware annunciator panel. The captured first-out bit is held until reset and can be read by a SCADA system at its own pace, so a remote operator sees the true root cause of a shutdown even without any local annunciator hardware.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.