1. Design Review Presentation Lost Caf é 66

2. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng Team Name: Lost Café 66

3. Block Diagram Micromouse Programming Design Debug Dynamic C Map maze Control of Mouse Everything else ChassisPlacement Sensors PC board MotorsBatteries

4. Outlook Attempt to have a bi-directional mouse Design an algorithm that would work efficiently Attempt to find center and map out maze efficiently Basically a mouse that would find the center (not necessarily win the entire competition)

5. Modules Build it simple and lightweight Aluminum 90-deg. Angle Bars Holds motor and batteries and everything else Chassis

6. Getting ready to…Drill it

7. Chassis Completed Chassis, so far…

8. Completing the Chassis Kang Lu working on the chassis w/ safety goggles (JUST IN CASE!!!)

9. Modules Sensors Top-down sensors Read and track the top of the walls Sensors directly in front and back Have sensors in front to detect what lays ahead Also have sensors on the side to keep the mouse aligned -

10. Sensors Proposed Sensor Layout

11. Modules Rabbit Heart of the mouse Sends command to motor Receives input from the sensors Inappropriate use would cause malfunction Cost $ 50 to replace the rabbit

12. Problems Getting the motor running Some ports don’t work Wrong ports for output and input Sensors not working correctly Not enough current going through the motors (LED drawing too much current) Connecting the computer to the rabbit Delivering the wrong amount of voltage to each component

13. Problems Building the Chassis Designing, finding right parts at right prices Band-saw broke. Had to cut out chassis by hand Mistakes in measuring and building the chassis 90 deg Angle Bars not 90 degrees, causing difficulty to place motors

14. Potential Problems Programming Being able to create a working and efficient algorithm Being able to actually program the mouse Finding the right input and output for the rabbit Mapping maze Keeping track of location of the mouse Debugging the code Using Dynamic C

15. Potential Problem Time We might not have enough time to finish the project Meeting time conflicts among team members

16. Time Line 3/13Finish Chassis and Design Layout 3/27Assemble Everything/General outline of code 4/3Finish Code 4/10Get the mouse moving 4/10- END Debug PAU!!!

17. AND … WE ’ RE DONE Questions???