Connect 4 - That's right...it has claws

Cornell Project | Expansion Board Interface | Command Encoding
Cornell Project | MIT Handler | EECS 270 Lab
Manufacturer's Spec | HITACHI Spec | Umich Helpful Hints
subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link
subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link
subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link
subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link
subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link

Two Player Interactive Connect 4 by Neil Zieses & Andrew Cramer

Our project was a success, and eventually worked as we envisioned it, outside of the choppiness of the screen which was a limitation of the display we used. If we were to do this project again, there are a few things we could have done to streamline the process. One of these is drawing out exactly what each hardware component needs to accomplish instead of simply jumping in and hacking together a more complex device that does the same job less efficiently. We would not recommend driving a clock signal with combinational logic. Although we thought that we had avoided this, there was one gate that we missed that caused a significant loss of time to debugging. To any future groups, do not underestimate the amount of time required for integration. Just because the controller interface works perfectly on its own does not mean it will produce the same good data when integrated with an LCD screen and timers.

Contact Us | ©2006 Crames & Zieses Inc.