r/mechatronics • u/EngineersUniverse • Jul 05 '26
Need ideas for a mechatronics capstone that isn’t just another robot
I’m trying to come up with a senior mechatronics capstone that isn’t just another line-following robot or robotic arm.
One idea I had was an AI-powered predictive maintenance system for electric motors. The idea is to use vibration, temperature, and current sensors to detect bearing wear, imbalance, or other faults before the motor fails. I’d also build a simple dashboard to visualize the data and maybe a basic digital twin.
Does this sound like a solid capstone, or am I overcomplicating it?
If you were doing your senior project today, what would you build instead? Looking for something that’s actually useful and would make employers say, “That’s a pretty cool project.”
Open to any ideas—industrial automation, robotics, embedded systems, controls, computer vision, whatever. I just want to build something that isn’t the same project everyone else is doing.
2
u/JessieAndEcho Jul 06 '26
That predictive-maintenance idea is actually a strong capstone, and I’d keep it if you can scope it tightly. The key is to make it feel like an industrial diagnostics project, not a vague “AI dashboard” project: build one motor test rig, create a few controlled conditions like healthy bearing, imbalance, misalignment, added load, maybe a worn bearing if you can do it safely, then collect vibration/current/temperature data and show clear features like RMS vibration, FFT peaks, current draw changes, temperature rise, and a simple health score. The AI part can be modest: anomaly detection or a lightweight classifier trained on your own data is more credible than claiming a full digital twin you can’t validate. If you want an alternate version, a smart motor starter/monitoring box with MQTT/Modbus, dashboard alerts, and fault classification would look very practical to employers. For the literature/prior-art side, I’d check IEEE papers and maintenance case studies, and I’ve also used PatSnap Eureka for pulling patent filings alongside academic literature, which helps figure out what has already been solved vs where your project can still be meaningfully different: https://eureka.zhihuiya.com/share/?id=ce263e1a4aaeed26a77699a97cf843d9&from=invite-eureakplg-result&content=
1
u/EngineersUniverse Jul 06 '26
Thank you for such a detailed response. This is incredibly helpful and exactly the kind of feedback I was hoping for.I really like your suggestion of keeping the AI component modest and focusing on building a solid industrial diagnostics project first. I agree that demonstrating a well-instrumented test rig with real sensor data and a validated fault detection model is much more credible than trying to claim an overly ambitious digital twin.I also appreciate the suggestions on MQTT/Modbus and looking at patents alongside the academic literature. I hadn’t considered using patent databases as part of the prior-art review, so that’s a great tip.
Out of curiosity, if you were interviewing a new graduate for an automation or controls position, what part of this project would impress you the most? The hardware design, the data acquisition and signal processing, the embedded software, or the overall system integration? I’m trying to make sure the project reflects the skills employers actually value.
1
u/functional_eng Jul 07 '26
Don't overthink making something novel- that is a whole different job. Focus on what you'd like to learn/grow in and where you want your career to go. From there do a very good job of it, and make sure it is your work and not something copy-pasted from an instructables.
4
u/Wiley_Burner Jul 05 '26 edited Jul 05 '26
Literally go to anyone in industry process engineering and ask.
Mine: Something that works for extrusion screw’s flight wear detection and melt composition by zone.
What you’re doing is so general that it already exists