Robotics Portfolio Template Example

01 / Case studies

Selected work

Case 01Final-year team project

My role Navigation & integration

A student rover project exploring localisation and repeatable navigation in a changing indoor route.

Context: The team could drive the rover manually, but it lost track of its position when a wheel slipped or the corridor layout changed.
Objective: Connect localisation, route planning and motion control, then make the failure cases understandable to the next team.
My contribution: I integrated the encoder and lidar inputs, checked coordinate frames, and wrote a repeatable route procedure. Recorded runs helped separate localisation errors from controller tuning problems.
Outcome: The project handover included route recordings, configuration notes and examples of recovery failures. Reflective surfaces remained an open issue for the next iteration.

Case 02Design module

My role Mechanism design

A compact gripper prototype built to compare finger geometry and contact behaviour on objects of different shapes.

Context: Rigid fingertips made contact unevenly and pushed lightweight objects out of the grip.
Objective: Explore a compliant finger design within the existing actuator and manufacturing constraints.
My contribution: I modelled interchangeable fingers, printed prototypes and photographed their contact patterns. A simple force-sensor fixture helped compare iterations under the same conditions.
Outcome: The final report explained which shapes the design could hold and where the fingers still twisted. It included the CAD revisions and the limits of the test fixture.

Case 03Personal project

My role Firmware & system documentation

An integration exercise tracing a distance measurement from the sensor driver to a motor command, with a visible stop condition.

Context: A working sensor driver and motor driver did not yet form a predictable complete system.
Objective: Define the data path and document how the controller handles stale or missing readings.
My contribution: I separated sampling from motor updates, added timestamped logs, and exercised the stop condition with disconnected and delayed sensor inputs.
Outcome: The write-up links each state transition to an observed log sequence. Further work would test the same behaviour under processor load.