Rubik's Cube Microprocesseur
Un microprocesseur réussit à solutionner le fameux Cube de Rubik
University of Michigan students Doug Li, Jeff Lovell, and Mike Zajac created this strange yet fascinating “Rubik’s Cube Solver” robot for their final project
The processor, MPC823, was supplied by the class and the only other choice was a MPC555 on a battery powered dev board (for mobile RC car style projects). So they used as much processing power as was available. Other than that we only had like a $50 budget and the materials of the hand made frame and color sensors ate that up pretty quick. The black/white encoder wheels were needed since they had to mod the servos to rotate 360... but after the mod, there was no way to know the current position of the servo with the original rotational pot, since that could only do ~270 degrees. They needed to very very precisely know where the servo was at because as mentioned below... the rig had a tendency of jamming up quite a bit. Actually a big portion of their debug time was spent in stopping the robot from jamming. They also put a lot of time into lubing the cube as best as they could. It was incredibly low friction after they did this.
A microprocessor can solve the famous Rubik's Cube
University of Michigan students Doug Li, Jeff Lovell, and Mike Zajac created this strange yet fascinating “Rubik’s Cube Solver” robot for their final project
The processor, MPC823, was supplied by the class and the only other choice was a MPC555 on a battery powered dev board (for mobile RC car style projects). So they used as much processing power as was available. Other than that we only had like a $50 budget and the materials of the hand made frame and color sensors ate that up pretty quick. The black/white encoder wheels were needed since they had to mod the servos to rotate 360... but after the mod, there was no way to know the current position of the servo with the original rotational pot, since that could only do ~270 degrees. They needed to very very precisely know where the servo was at because as mentioned below... the rig had a tendency of jamming up quite a bit. Actually a big portion of their debug time was spent in stopping the robot from jamming. They also put a lot of time into lubing the cube as best as they could. It was incredibly low friction after they did this.
A microprocessor can solve the famous Rubik's Cube
Category
😹
Amusant