Stimulating Higher Order Thinking in Mechatronics by Comparing PID and Fuzzy Control
This paper presents a semester-long mechatronics project where students compare PID and fuzzy control for leader-follower behavior without predefined criteria, successfully fostering higher-order thinking skills by requiring them to design their own evaluation methods and experiments to solve an open-ended, real-world engineering problem.
Original paper dedicated to the public domain under CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are teaching a class of future engineers. Traditionally, you might give them a recipe book: "Here are the ingredients, here are the steps, and here is the perfect cake you must bake." If they follow the steps and the cake looks good, they get an A.
But in the real world, engineers rarely get a recipe. They get a problem like, "We need a vehicle that can follow another vehicle safely, but we don't know exactly how to do it, and we have two different tools to try."
This paper describes a class at the US Military Academy where the instructors decided to stop handing out recipes. Instead, they gave their students a "kitchen challenge" to see if they could learn to think like real engineers.
The Challenge: The "Follow-Me" Robot
The students were tasked with building a robot car that could autonomously follow a lead car. To do this, they had to write computer code that acted as the robot's brain. They were given two different "brains" (control methods) to choose from:
- PID Control: Think of this like a strict, mathematical rulebook. It calculates exactly how much to turn or speed up based on precise numbers.
- Fuzzy Control: Think of this like a human driver's intuition. It uses "rules of thumb" (e.g., "If the car ahead is a little too far, speed up a bit") rather than rigid math.
The Twist: No Answer Key
In most engineering classes, the teacher would say, "Use PID, set the numbers to X and Y, and you are done."
In this class, the teachers said: "Here are the two tools. Here is the goal. You decide which one is better, you decide how to test them, and you decide how to measure success."
The students weren't told:
- How fast the cars should go.
- How far apart they should stay.
- What "good performance" actually looked like.
They had to invent their own tests. It was like asking a student to judge which of two new sports cars is faster, but not telling them if they should race on a track, drive through a city, or climb a mountain. They had to figure out that the answer depends entirely on how they define the race.
The Journey: Learning by Doing
To get ready for this big challenge, the students did smaller "mini-projects" all semester. They learned how to:
- Use cameras to spot colored paper (like a robot's eyes).
- Program the cars to move.
- Build both the "strict math" brain (PID) and the "intuitive" brain (Fuzzy).
Then came the final project. The students had to run their own experiments. Some teams realized that testing the cars while they were stopped was different than testing them while moving. Some realized that if the car started too far away, the "brain" might panic and overcorrect. They had to design their own experiments to find the truth.
The Results: Growing Pains and "Aha!" Moments
The researchers found three main things:
- Students Liked the Realism: Even though it was harder, students appreciated that the problem felt like a real job. They weren't just memorizing facts; they were solving a puzzle.
- They Learned to Think Deeply: Because there was no single right answer, students had to use "higher-order thinking." Instead of just applying a formula, they had to analyze the data, synthesize a new plan, and evaluate which method was truly superior. They had to create their own criteria for success.
- They Discovered the Messiness of Engineering: Students realized that comparing two things isn't simple. There are too many variables (speed, distance, lighting, starting position). They learned that in the real world, there is rarely a "perfect" solution, only a "best fit" for a specific situation.
The Takeaway
The paper argues that to train engineers who can handle complex, ambiguous problems, we can't just teach them to follow instructions. We have to put them in a situation where they have to write the instructions themselves.
By forcing students to design their own experiments and defend their choices, the class turned them from passive recipe-followers into active problem-solvers who can think critically, just like the professional engineers they hope to become.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.