A hydraulic top-drive system in active service. The equipment earns while it runs, so it cannot be taken offline to accommodate engineering work, and there is no test rig equivalent to it. Whatever gets written has to be correct against the real machine the first time it touches it. That is a different discipline from most software work: no staging environment, no safe rollback window, and a feedback loop for a mistake that runs through several tonnes of moving hydraulic machinery.
A fixed-gain controller tuned at one operating point drifts out of specification as load, temperature, and wear move the plant away from it, and a live machine never sits still. The controller does not fail loudly when this happens; it just holds the setpoint less well, in conditions nobody is watching for. Two more constraints bind below the control law: the loop deadline is part of the specification and the protocol round-trip to the PLC happens inside it, and the controller behaves as it implements Modbus rather than as the standard describes, discoverable only against this controller.
The reflex, and the fix.
A fixed-gain PID
Faster to deploy, well understood, and fine in a demonstration.
It cannot hold across the operating range of live equipment, and its degradation is silent, which means nobody finds out until the machine is out of specification.
An adaptive control law
More design and tuning work, carried out against a running machine with conservative bounds and a fallback to the known-good controller.
Stability held across the range of conditions the machine actually meets rather than only at the point it was commissioned at.
Adapt to the operating regime, because the plant will not hold still and a silent drift out of specification is the worst available failure mode.
Protocol and transport as ground truth
Read and write the controller over Modbus TCP through an industrial VPN gateway, treating the controller's observed behavior as ground truth rather than the standard's description of it. The round-trip is measured and budgeted as part of the loop, not assumed.
A gain-scheduled law rather than fixed gains
The controller carries a tuning per operating regime and moves between them, so stability holds across the range of load, temperature, and wear the machine actually meets rather than only at the commissioning point. The scheme runs inside a safety-instrumented basic process control system, which bounds what the adaptation is permitted to do.
The deadline as part of the specification
The loop closes inside its deadline with the protocol round-trip accounted for and headroom reserved, because a control loop that meets its deadline on average and misses it occasionally is a control loop that does the wrong thing occasionally.
Correct against the running machine, first time
The only available test environment is the equipment in service, which raises the bar on everything upstream: staged rollout, conservative adaptation bounds, and the ability to fall back to the known-good controller at any point.
A single headline number hides where a system fails. This work was scored on the dimensions that actually decide whether it holds in production, measured on real, held-out cases rather than the demo path.
A controller tuned beautifully at commissioning that quietly stops holding specification a few months later, in operating conditions nobody instrumented, with no alarm and no obvious cause.
Stable control held across the machine's real operating range, on equipment that stayed in service throughout, over an industrial protocol path with the round-trip budgeted inside the loop deadline.
What it owns, and what it hands to a person.
Adaptive control widens the range over which a controller holds. It does not remove the need for the plant to stay inside the envelope the law was designed for, and a mechanical fault is still a mechanical fault. The adaptation is bounded deliberately, because an unbounded adaptive law on live hydraulic equipment is a worse failure mode than a slightly detuned fixed one.
There is no machine learning in this engagement. The work is a control law, a timing budget, an industrial protocol, and the discipline of being correct against hardware you cannot stop. It sits directly alongside the real-time closed-loop work in robotics and the fail-closed architecture in defense, and the same discipline appears in all three: the deadline is part of the specification, the hardware is ground truth rather than the document, and what the system does at its boundaries is designed rather than discovered.