The Case for Replacement of Pilot Valves With Pilot Pumps in Hydraulic Control Systems
Bibliographic record
Abstract
Abstract Traditionally, hydraulic servo power for high bandwidth primary stage actuation in electrohydraulic pumps and valves is provided by small pilot stage valves. These often operate in a pressure-control mode against a spring to effect position control of the main valve spool or pump swash plate. This paper presents the case for replacing these valves with small fixed-displacement, electronically speed-controlled pumps. Depending on the system, advantages can include more linear control, faster response, lower development and component cost, and higher energy efficiency. This paper presents comparative analysis of this concept for two common cases: a two-stage spool valve, and an axial piston load sensing pump. The first demonstrates that for systems of comparable flow capacity a pump-controlled-pump system will respond faster than a valve controlled system due to supplying its maximum flow for the majority of the response, as opposed to a valve controlled system whose flow reduces as pressures equalize. This system also exhibits a more linear response, easing closed loop control design. The second case study presents a pump flow control application, which demonstrates the pump-controlled-pump system can be more easily and safely designed using linearized control system analysis techniques. The linearized analysis correctly identifies the stability limits for the pump-controlled-pump, but dangerously overestimates the proportional gain limits for a valve-controlled system.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.017 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.003 |
| Scholarly communication | 0.002 | 0.005 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".