Talk:Robotics/Design Basics

This goal is too simple. The ideal "robot" to traverse a powered track is not a robot at all, but an automaton: namely an electric train. A simple electric train may be purchased for less than the cost of an electrical engineering textbook.


 * Well what's the difference? One uses sensors and feedback decision-making to stay on the track, and the other uses mechanical forces (feedback) to stay on the track?  Where does one end and the other begin? - Omegatron 14:16, 8 Oct 2004 (UTC)

The difference is how it acts when something goes "wrong". Let's say someone puts a big box on the robots track. Can it addapt? If it just bumps into it, it's an automaton. Otherwise if it looks for a way around then it could be called a robot. But that's my oppinion. The border between the 2 is very fuzzy. --Patrik 13:35, 16 Dec 2004 (UTC)

I agree that this particular goal can be fulfilled (and at lower cost) by simple electric train, rather than a robot. However, I think this book needs some "simple" goals before working towards more complicated goals. Simple goals are good.
 * The lowest-cost "program" to display the words "Hello, world" is to simply write them on paper with a pencil.
 * But writing a program to display those words is still an excellent early goal while learning a programming language.
 * The lowest-cost hardware to blink an LED certainly does not include a microprocessor.
 * But programming a microprocessor to blink an LED is still an excellent early goal while learning embedded Systems.

Would an even simpler goal (simpler than "follow a powered track") be even better? --DavidCary 05:13, 12 June 2007 (UTC)