dknguyen said:
Robotics involves so many fields, there's no one specific thing that you need to be to work on robotics (the most straightforward path though is CE/EE rather than MechE).
There isn't a "Robotics Engineering" as much as there are engineers who specialize in different fields working on robotics. I've never met anyone who considered themselves a robotics engineer.
That's not necessarily true. Over here at Purdue, there is a grad course entitled ECE 595E Introduction to Robotics Engineering.
I was interested in the course, but didn't take it. Some collegause of mine took it and I skimmed over the text. It appears the subject material covered alot of vector matrix algebra and position control of industrial robotic arms.
The requirements were linear algebra, calculus, control systems and signals and systems.
What I think is that robotics is a field comprising many different sections of EE discipline. Like radar engineering, you have to be an ace in electronics, electro-magnetics, statistics and probability, digitial signal processing and signals and systems. you bascially have to be a superman, I learned this while working for Ball Aerospace in the Antennas and Video Technologies Group as an Rf engineer.
But yeah, the subject robotics engineering is complex and not just for EE's.
You guys ever think androids would be possible?