Backend
Input-Constrained Active Disturbance Rejection Control for AUVs
arXiv eess.SY0 views
arXiv:2610.17498v1 Announce Type: new Abstract: This paper addresses the control of autonomous underwater vehicles (AUVs) operating in dynamic environments, where wave-induced forces, modelling errors, and actuator limitations make reliable control challenging. Active disturbance rejection control (ADRC), together with an extended state observer (ESO), estimates lumped uncertainties online, simplifying control design using nominal models. However, existing stability analyses typically assume bounded control inputs and derivatives, which are difficult to guarantee under unknown disturbances and measurement noise. To bridge this theory--practice gap, this paper introduces an ADRC framework with active input saturation and post-saturation low-pass filtering. The saturation constrains the control magnitude, while the filter regularizes the saturated signal to ensure bounded input-rate variations. By explicitly enforcing these conditions, the proposed system guarantees semi-global practical asymptotic stability. High-fidelity simulations and experiments on an underwater robotic platform demonstrate robust control performance under severe environmental disturbances and actuator constraints. A supplementary video is available at https://youtu.be/AEFlZ69Yg00.
Source:https://arxiv.org/abs/2610.17498PreviousDirect Electromechanical Actuation of the Shift Drum in Non-Synchronized Motorcycle Transmissions: From Actuator Sizing and Electronics Design to Closed-Loop Position ControlNextMulti-Day Stochastic Dispatch for Power Systems With Long-Duration Storage Using Diffusion-Generated Weather Forecasts
Related posts
Redis 8.12 RC2's SEXPIRE command cuts a set membership check from two round trips to one
0dev.to Database
Does AbortSignal Cancel a Node.js Database Query? 4 Drivers Tested
0dev.to Database
I read all 308 open jobs at xAI: 54% are in its data center team, and most of them are in Memphis
0dev.to AI
Claude Code marketing analytics with an app-scoped key
0dev.to AI
I red-teamed my own support bot with 30 scenarios. It failed 7 — here's the harness.
0dev.to AI
The Log That Told Everyone the Password: Redacting Secrets in n8n Execution Logs
0dev.to WebDev