<p>What’s the main difference between Robotics and Control? I’ve read the course descriptions and the mentioned concepts are vastly different but can someone who’s already taken these courses explain the main different between the two. Is the Robotics one more CS/AI focused? Is control more signal processing focused?</p>
<p>I’ve taken EE128 and it felt like a continuation of ME132 with a lab focusing on P, PD, PID controls through MATLAB and later combining everything you know to design a levitating magnet ball (which involves circuits) and inverted pendulum. It was a lot of work spending countless hours outside of official lab time to get the experiment done, but the feeling of getting your pendulum upside down or having your ball float was so worth it.
<a href=“http://www-inst.eecs.berkeley.edu/~ee128/fa11/Handouts/syllabus-ee128-f11.pdf[/url]”>http://www-inst.eecs.berkeley.edu/~ee128/fa11/Handouts/syllabus-ee128-f11.pdf</a>
You won’t learn too much about A/D or D/A signal processing like you did in EE20/120 (at least when I took it), but more on basic stuff such as linearization, BIBO stability, root locus, nyquist plot, lead-lag compensation, state space, and LQR.</p>
<p>I meant the above link to be this, not just another syllabus which you already probably looked it up anyway.
[Self-Erecting</a> Inverted Pendulum Demo (EE C128 / ME C134, UC Berkeley) - YouTube](<a href=“Self-Erecting Inverted Pendulum Demo (EE C128 / ME C134, UC Berkeley) - YouTube”>Self-Erecting Inverted Pendulum Demo (EE C128 / ME C134, UC Berkeley) - YouTube)</p>
<p>Thanks UpMagic!</p>
<p>Has anyone taken EE125, what did you think about it?</p>