Jake 2000 was UC Berkeley's first micromouse.
If you are interested in the Micromouse project and would like to discuss or hear about it, you may subscribe to our mailing list. I don't know of an automated way to subscribe, but if you send a message to micromouse@ieee.eecs.berkeley.edu and ask to be added to the mailing list, then I think someone will help you out. You should also join the UC Davis micromouse mailing list. To do so, send a message saying "subscribe micromousers" to listproc@ucdavis.edu. The current information about efforts at UC Berkeley regarding Micromouse should be available on the Berkeley IEEE site, but you'll probably just get pointed back here.
It was our intention to have a full simultation of the robot that would run on a PC, including a navigation module for choosing routes and a pilot module for executing the computed routes. This pilot module would be tested in a simulator running on a PC. Our intention was that the navigation and piloting routines developed in this 'test tube' environment would then be transferred, without modification, to the robot platform. In theory this was a great idea, but in practice it didn't work out quite so well — the main failure was in simulating all the annoyances of the physical environment (slippage, motor response at low battery voltages, etc). The result was that we lacked a robust control system for the robot's movement (that having been relegated down to "only a software problem"). Nonetheless, these software programs may still be useful, although they're written for rather archaic environments (one requires Borland Turbo Pascal and the other requires Borland Turbo C to compile, and both run in DOS).
NavigatorThe You may download the source (Borland C) and executable (DOS) in |
PilotThe |