Timeline & Testing

Team Minion uses a staged testing process to progressively validate Kevin and Noodle before advancing to autonomous operation over water. Testing begins in a controlled environment before progressing to real-world conditions, allowing the team to identify and resolve issues before moving to the next stage.

Development & Test Strategy

UAV testing is primarily conducted inside a netted enclosure measuring approximately 50 ft × 50 ft × 30 ft. The enclosed environment provides a controlled testing area while reducing the risk of environmental interference or accidents.

Testing over water requires approval from the University Safety Review Board (SRB) and the local authority. To support safe progression toward autonomous on-water operation, Team Minion follows a defined sequence of tests:

1.) In-Cage Manual Test

2.) In-Cage Autonomous Test

3.) On-Water Manual Test

4.) On-Water Autonomous Test

Each stage must be successfully completed before progressing to the next. If a failure occurs at any stage, the vehicle returns to the first stage and must successfully complete the preceding tests again before continuing.

Flight Testing

Testing evaluates both UAV platforms as their mechanical, electrical, sensing, communications, and payload systems are integrated. Over-water testing includes vehicle-specific capabilities such as locating and landing on the landing pad and retrieving colored tins. Testing evaluates both UAV platforms as their mechanical, electrical, sensing, communications, and payload systems are integrated. Over-water testing includes vehicle-specific capabilities such as locating and landing on the landing pad and retrieving colored tins.

Test data is recorded throughout flight operations. ROS bag files are collected during testing to support post-test analysis and debugging, allowing the team to review system behavior and identify issues following each flight. Test data is recorded throughout flight operations. ROS bag files are collected during testing to support post-test analysis and debugging, allowing the team to review system behavior and identify issues following each flight.

Following each test, the UAV team conducts a debrief to review the results, identify areas for improvement, and determine changes or additional testing required before the next stage. Following each test, the UAV team conducts a debrief to review the results, identify areas for improvement, and determine changes or additional testing required before the next stage.

Kevin & Noodle Development Blog

Testing records document the progression of Kevin and Noodle from initial system checks through autonomous operation. Individual test events include the test objective, vehicle configuration, operating conditions, results, and design changes resulting from testing.

January 2026

First Iteration of Kevin was 3D modeled. This model was fully 3D printed.

February 2026

The first design iteration of Kevin was found to exceed the weight requirements of the competition.

March, 2026

Iteration 2 of Kevin was designed, keeping the 3D printed chassis, this iteration improved on weight efficiency.

April, 2026

Iteration 2 was found to still be slightly too heavy and lacked sufficient flight time.

May, 2026

Iteration 3 was developed and focused on reducing the weight and complexity of the capture mechanism.

June, 2026

After iteration 3 was 3D printed the chassis weight as substantially heavier than anticipated.

July, 2026

Iteration 4 of Kevin was designed, featuring a carbon fiber chassis to address the weight issues of the previous iterations.

September, 2026

Water ingress protection testing took place, redesigning the gasket to increase reliability.

September, 2026

Iteration 4 flight test was conducted revealing unforeseen issues regarding the landing gear and telemetry unit.

September, 2026

It was determined that due to time considerations that the effort of addressing the issues on Kevin would be reallocated to Junior, and Noodle would be taken to competition.