uaefame
New Member
hes got 6 legs, and probably has two joints per leg, as well as the joint where the leg connects to the body, for a toal of 18 joints. 1 servo at each joint, and you have 18 servos.
now, my question is this. In general computing, its easier to layer things, as you can make each task less complex, and can more efficiently route traffic. This can be seen when making a computer cluster. its easier to fill a switch with nodes, and then connect taht switch to a second switch, that will in turn connect another node filled switch. its slightly slower, but its easier to understand what's happening.
Is the same idea possible from a µC point of view? for example, could he have three servos per µC, and the 6 µCs connected to a master µC? The master would not directly control the servos, but would instead tell the slave µCs what to do, and they would in turn control the motors. This sounds kind of redundant seeing as they make TQFP µCs with 100+ pins, but still, imagine this on a large scale. even at a small scale, you could take a Java-like approach and re-use the code in each of the slave controllers. Then you have the master designate which signal to send to which slave. It cuts down on overall coding, as you can program multiple devices with the same information, and cuts down on troubleshooting as there is less going on so there is less to check through. Can someone tell me if this can be done? I'm really good at thinking like this, but I don't know enough about µCs to know whether or not this mode of thinking is practical.
Oh, and I'm signing up for a digital electronics class, as well as a semiconductor applications class next semester. Hopefully they won't diappoint.
I am interested if that is possible. But don't you think its abit tomuch to have 7 PIC 16F818 around. The less the number The less the complication right or I am wrong?