外乱に頑健なマルチウェイポイントUAV到着のための階層型アウターループ制御
Layered Outer-Loop Control for Disturbance-Robust Multi-Waypoint UAV Arrival
UAVの位置制御を、滑らかな接近生成・バイアス補償・目標近傍の終端制御を分離した階層型アーキテクチャで実現し、PyBullet、PX4/Gazebo、実機で段階的に評価した。
詳しい要約
1. どんなもの？
2. 先行研究と比べてどこがすごい？
3. 技術・手法の肝は？
4. どうやって有効だと検証した？
5. 議論はある？
6. 次に読むべき論文は？
※ AIが要旨から生成した要約です。正確性は原文をご確認ください。
著者: Runfeng Ling
分類: cs.RO
原文アブストラクト
Disturbance-robust UAV position control is easy to demonstrate in benign simulations but much harder to make fast in approach, well behaved near the target, and credible beyond a single benchmark. This letter presents a layered terminal-control architecture for multi-waypoint UAV position regulation together with a staged evaluation across PyBullet, PX4/Gazebo, and hardware. Phase I uses a PyBullet benchmark with stochastic wind for rapid structural selection, identifying a controller core that separates smooth approach generation, persistent-bias compensation, and supervised near-target terminal regulation. Phase II carries only that main architecture into a more demanding PX4/Gazebo closed loop, where the outer-loop controller acts through a cascaded flight stack with delay-sensitive settling and stronger transit-to-hover coupling. This step exposes which benchmark gains survive autopilot-mediated dynamics and which refinements collapse once the loop becomes more deployment-like. In Phase I, the bare controller attains 0.024 m mean late-stage wind error. In Phase II, the final controller is selected using a transfer-oriented rule emphasizing absence of benchmark priors, cross-scenario balance, and deployable supervisory logic. Strict is used as the primary reporting reference; the supplementary retrospective Grace analysis shows that part of the residual failure set is sensitive to completion semantics rather than gross waypoint-miss behaviour. The evaluation is completed on one Vicon-tracked Tello stack through a two-level hardware study. Taken together, the results suggest that benchmark success becomes more informative when the main controller design is separated from benchmark-specific refinement and remains defensible under harder closed-loop evaluation.
