Pressing start on a compressor package does not slam the machine straight into service. Behind that single command sits a choreographed set of steps that the unit controller walks through in order, confirming each one before it allows the next. A compressor unit start sequence is that timed, step-by-step progression from a proven-ready standstill to a loaded, running machine, with checks and time limits built into every stage. This page walks the whole sequence, explains how the sequencer confirms and times each step, and describes what happens when a step fails to complete.
Compressor Unit Start Sequence in one line: A compressor unit start sequence is the ordered, timed set of steps a PLC or unit controller runs to bring a compressor from standstill to loaded operation. It typically moves through a permissive check, pre-lube of the bearings, a purge or crank to clear the machine, driver light-off or motor start, a ramp to minimum operating speed, and finally load enable. The sequencer confirms each step against feedback and a time window, and if any step does not prove within its allotted time it holds or aborts the start rather than advancing.
The sequence begins only when the unit is proven ready to start, which means the interlock string is fully made up and no shutdown is latched. Once the operator or a higher-level command initiates the start, the first physical action is usually pre-lube: an auxiliary lube oil pump runs to establish oil pressure and flow to the bearings before anything rotates, so the machine never turns on dry metal. The controller waits for the oil pressure switch or transmitter to confirm adequate pressure, and only then does it consider the pre-lube step complete.
With lubrication proven, the sequence moves to purge or crank depending on the driver. On an engine or gas turbine driver, the starter turns the machine over while a purge airflow sweeps the combustion and exhaust volumes clear of any residual fuel, so light-off cannot occur into an accumulated fuel pocket. On a motor-driven unit the equivalent step may be a barring or crank check that confirms the shaft is free to turn. After the purge count or crank confirmation, the driver is brought to life: fuel and ignition are enabled and the controller watches for a stable flame or successful firing, or the motor contactor closes and the controller confirms the machine is accelerating.
Once the driver is running, the unit ramps to a minimum operating speed while the antisurge and recycle path holds the compressor in full recycle so it is not asked to make head against the system before it is ready. When speed, temperatures, and pressures are stable at the minimum operating point, the final step is load enable: the sequencer hands control to the process control loops, the recycle valve is allowed to begin closing, and the unit starts pushing gas into the station. Only at this point is the start considered complete and the machine in normal service.
Every step in the sequence has two things attached to it: a confirmation condition and a time window. The confirmation is the feedback the controller must see to believe the step actually happened, such as oil pressure above a threshold for pre-lube, a completed purge volume count for purge, or a proven flame for light-off. The controller does not advance on a command alone; it advances on evidence. This is what separates a real start sequence from a simple relay chain, because a bad valve, a failed pump, or a starter that will not engage is caught at the step where its feedback fails to appear.
The time window is a maximum, and sometimes a minimum, duration for the step to prove. If pre-lube oil pressure has not reached its target within the allowed seconds, the controller concludes the aux pump or the oil system has a problem and does not proceed to crank. If a flame is not established within the light-off window, the controller trips the fuel to avoid dumping unburned gas into a hot machine. These timers turn each step into a bounded question with a yes, a no, or a timeout, and the sequence only walks forward on a clean yes within the window.
Some steps also require a minimum dwell before advancing, so the sequencer holds even when the confirmation arrives early. A purge, for instance, must run long enough to sweep the required number of volume changes regardless of how quickly airflow is confirmed, so the step will not complete until both the flow is proven and the minimum purge time has elapsed. This combination of confirmation plus timing is what makes the sequence both safe and repeatable, because it enforces the same proven, time-bounded path every single start rather than relying on how fast an operator happens to move.
On a modern package the start sequence lives in the unit PLC, but its state is exposed to the operator through the HMI and, increasingly, through SCADA and cloud monitoring. Rather than a single start light, the operator sees which step is active, how long it has been in that step, and what feedback it is waiting on. That visibility matters most when a start does not complete, because instead of a vague failed start the operator sees precisely that the sequence stalled at pre-lube waiting on oil pressure, or aborted at light-off on no flame, which points straight at the subsystem to investigate.
Remote and unattended stations lean heavily on this instrumentation. When a dispatcher or an automatic station controller commands a unit start from a control room hundreds of miles away, there is no one at the machine to watch the purge airflow or listen for the driver catching. The sequencer's step-by-step confirmations become the only trustworthy account of whether the start is progressing, so each step transition and each timeout is logged and telemetered. A start that repeatedly aborts at the same step is a maintenance signal that surfaces long before it becomes a stranded, non-starting unit.
A monitoring platform such as Merobix adds value here by recording the sequence history across many starts and many units, so patterns emerge that a single event would hide. If pre-lube times are creeping longer season over season, that trends toward a tiring aux pump or a fouling oil filter; if light-off attempts are needing more cranks than they used to, that points at ignition or fuel-gas quality. Treating each start as timed, step-resolved data rather than a pass or fail turns the start sequence into an early diagnostic on the whole package.
After confirming the unit is proven ready with no shutdown latched, the sequence normally begins by pre-lubing the bearings. An auxiliary lube oil pump runs to build oil pressure and flow before anything rotates, so the machine never turns on dry bearings. The controller waits for a proven oil pressure signal before it will advance to the next step, and it will not crank or start the driver until that confirmation appears.
A permissive string is the set of static conditions that must all be true before a start is even allowed, and it is essentially a gate that either lets the start begin or blocks it. The start sequence is the timed, multi-step progression that runs after the gate opens, moving through pre-lube, purge, light-off, ramp, and load enable, confirming and timing each step. The permissive answers whether you may start; the sequence carries out the start step by step.
Each step in the sequence has a confirmation condition and a time window, so the controller can pinpoint exactly where a start went wrong. If a step does not prove its feedback within its allotted time, the sequencer holds or aborts at that step rather than blindly advancing, which prevents actions like enabling fuel with no proven flame. Aborting at a specific step also tells the operator which subsystem to investigate instead of leaving a vague failed start.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.