The only maths you'll need at the beginning is basic control engineering (PID Loops), forward/inverse kinematics and Extended Kalman Filtering. The only other thing is maybe V=IR, anything else and you're just placating some professor's ego.
13 karma · joined November 15, 2024
The only maths you'll need at the beginning is basic control engineering (PID Loops), forward/inverse kinematics and Extended Kalman Filtering. The only other thing is maybe V=IR, anything else and you're just placating some professor's ego.
Not at my uni for sure. First (and only) microcontroller that we actually programmed that wasnt an arduino was in the final semester of the entire degree.
*Technically I did a robotics degree but the difference between mine and the EE degree at my university was at the most 5 modules, roughly 60 out of 360 credits.
The replacement modules certainly were not in anything to do with design or fabrication either. No soldering, no CAD, no ECAD.
You could have got through the entire degree without having once picked up a soldering iron or built a circuit. As long as you were good at maths you would get through, nothing else meaningfully mattered, except the dissertation of course.
You’re not wrong at all on the software side. With regards to the concepts though, we did a whole bunch of theory, but fairly often we did not do even the basics of applying it. I mean we literally did not do any, we did zero circuit/PCB design (the thing I’m trying to currently learn).
That’s why I went to uni to do EE/Robotics. I wanted the next step, suffice to say I did not get the next step from university.
I see what you’re getting at though. Just in time learning seems to be the way it will be. It’s just frustrating I don’t even have a base to go off of. Pretty much all my background knowledge has come from stuff I learnt outside of uni.