ChenboLin
01About02Work03Labs04Notes
GET IN TOUCH
Back to engineering work阅读中文版
AUTONOMOUS SYSTEMS5 min read

Propulsion and navigation for underwater vehicles.

A university engineering project covering propeller design, thrust testing and navigation code for an autonomous underwater vehicle.

Published
2026-08-18
Updated
2026-08-18

Project scope

2024 — PRESENT / UNIVERSITY RESEARCH

University engineering project

Physical system
Autonomous underwater vehicle
Propulsion work
Propeller design and thrust testing
Software work
Navigation programming and system integration

Topics

Propeller designThrust testingNavigation programming
01

Autonomy begins with the physical vehicle

Underwater navigation is inseparable from propulsion. A control algorithm can only request motions that the vehicle, propellers and available thrust can physically produce in the surrounding water.

The project therefore connects propeller design and thrust testing with navigation programming instead of treating the mechanical and software work as independent tracks.

02

The propulsion loop

Propeller concepts need to be translated into testable behaviour. Thrust testing provides evidence for comparing designs and for understanding what the control system can reasonably command.

The useful result is not only a stronger component. It is a better model of the vehicle's available actuation, including the limits and asymmetries that navigation logic must respect.

03

Navigation is a systems problem

Navigation programming depends on sensing, timing, coordinate assumptions, actuator response and the way the vehicle handles uncertainty. Each layer needs interfaces that make errors observable rather than silently passing them downstream.

This is where the project connects to my broader interest in physical intelligence: perception, decision and action only become useful when the whole loop can be evaluated in the real system.

04

What remains deliberately open

Because the work is ongoing, this page records the engineering scope rather than claiming a final result. Future updates should add test methods, validated measurements and design changes only when they are ready to be made public.

That boundary is important. A credible project page should distinguish what has been attempted, what has been measured and what is still a direction for the next iteration.

Public evidence boundary

This is an ongoing project. The brief does not publish a final vehicle performance figure, competition result, mission-readiness claim, or confidential team design data.

Each page states what the project covers, what evidence is public and what has not yet been verified.

Browse all engineering work
Chenbo Lin
© 2026 Chenbo Lin. All rights reserved.