Selector control is the mechanism that lets two or more controllers compete for one valve, with a simple block choosing whichever output wins. The selector picks the highest or the lowest signal - a process sometimes called auctioneering - and passes it to the final element, so a constraint loop can seize control from a normal loop the instant a limit is threatened. This guide focuses on the selector block itself: how high and low signal selectors work, how they enforce constraints, and the reset windup trap that comes with them.
Selector Control in one line: Selector (auctioneering) control uses a high signal selector or low signal selector block that receives the outputs of two or more controllers and forwards only the highest or lowest of them to the final element; this lets a constraint or protective controller automatically take command of a shared valve whenever its output crosses that of the normal controller, enforcing a limit without operator intervention.
At its heart a selector is a trivially simple block: it looks at several input signals and outputs one of them. A high signal selector (HSS) passes the highest input; a low signal selector (LSS) passes the lowest. The inputs can be measurements, but in constraint control they are usually the outputs of competing controllers, all aimed at the same valve. Because the block continuously compares the candidates and picks a winner, the arrangement is often described as auctioneering - the controllers effectively bid for the valve, and the selector awards it to the one whose output is highest or lowest, depending on the block type.
Which block you use follows from the direction of the protection. If the valve is fail-safe such that a lower output is the safer, more restrictive command, a low selector guarantees that the most conservative controller always wins. If a higher output is the protective direction, a high selector does the same. The elegance is that the transfer between controllers is automatic and bumpless: nothing switches loops or throws a mode change - the block simply keeps forwarding whichever signal currently qualifies, so control slides seamlessly from the normal loop to the constraint loop and back as conditions change.
The classic use is holding a process at its normal target while a second controller stands guard over a limit. Consider a compressor whose flow controller runs it to the production setpoint, while a separate controller watches discharge pressure and must not let it exceed a maximum. Both drive the same speed or recycle valve, feeding a selector. Under normal conditions the flow controller wins and the pressure controller sits idle at a losing output. The moment discharge pressure approaches its limit, the pressure controller's output crosses the flow controller's, the selector hands it the valve, and the constraint is enforced - then control reverts automatically once the pressure danger passes.
The same pattern protects against many limits at once by feeding several constraint controllers into one selector: a pump can be run for flow while low-suction-pressure and high-motor-current controllers each stand ready to pull it back. Whichever demands the most restrictive action at any instant takes the valve. This is what distinguishes the selector approach - it is not a single override loop but a general voting mechanism where any number of guardians can seize control, and the winner is decided moment to moment by the block rather than by a fixed hierarchy.
Selector schemes carry a specific hazard: reset windup on the losing controllers. A controller whose output is not selected still sees its own error and, if it has integral action, keeps integrating - its output drifts far past the valve's real position. When conditions later swing in its favor, its wound-up output is nowhere near reality, so it either grabs the valve too late or dumps a lurching command. The standard cure is external reset (also called back-calculation or integral tracking): every controller's integral is fed the selector's actual output, so a losing controller tracks reality and is ready to take over cleanly. Getting this feedback right is the hard part of building a reliable selector scheme.
On a cloud SCADA platform the selector's behavior becomes far easier to understand and audit. Merobix can trend each competing controller's output alongside the selected signal and the valve position, so an operator can see exactly which controller currently owns the valve and how often control changes hands. A compressor that keeps ceding its flow loop to the high-pressure constraint controller is visibly running against a limit - a production bottleneck that is otherwise invisible from a single-valve view. Because Merobix logs the selection over time, an engineer can also spot a losing controller that never regains the valve, which often points to a windup problem or a genuine, persistent constraint that needs engineering attention rather than a tuning tweak.
A high signal selector passes the highest of its input signals to the output; a low signal selector passes the lowest. Which you choose depends on the protective direction: use a low selector when a lower, more restrictive output is the safe command, and a high selector when a higher output is protective. That guarantees the most conservative controller always wins the valve.
They overlap heavily - override control is usually implemented with a selector. The distinction is one of focus: override control describes the overall strategy of a constraint loop taking over from a normal loop, while a selector is the specific block that mechanically picks the winning signal. A selector can also auction among many controllers at once, not just two, making it a general voting mechanism.
When a controller's output is not selected, its integral term keeps accumulating error and drifts far from the valve's real position. If it later wins the valve, its wound-up output is unrealistic and it responds badly. The fix is external reset or integral tracking, which feeds the selector's actual output back to every controller's integral so losing controllers stay aligned with reality and take over cleanly.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.