Design Review Presentation

Lost Café 66

Introduction of Team

Team Leader: Arthur Phanphengdy

Members: Quincy Quach

Kang Lu

Jackson Ng

Team Name: Lost Café 66

Block DiagramMicromouse

Programming Design Debug

DynamicC

Mapmaze

Control ofMouse

Everythingelse

Chassis Placement

SensorsPC

boardMotors Batteries

Outlook

Attempt to have a bi-directional mouseDesign an algorithm that would work efficientlyAttempt to find center and map out maze efficientlyBasically a mouse that would find the center (not necessarily win the entire competition)

Modules

Build it simple and lightweightAluminum 90-deg. Angle BarsHolds motor and batteries and everything else

Chassis

Chassis

Getting ready to…

Drill it

ChassisCompleted Chassis, so far…

Completing the Chassis

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

Modules

SensorsTop-down sensorsRead and track the top of the wallsSensors directly in front and backHave sensors in front to detect what

lays aheadAlso have sensors on the side to keep

the mouse aligned

-

SensorsProposed Sensor Layout

Modules

RabbitHeart of the mouseSends command to motorReceives input from the sensors Inappropriate use would cause

malfunctionCost $ 50 to replace the rabbit

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

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

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

Potential Problem

TimeWe might not have enough time to finish

the projectMeeting time conflicts among team

members

Time Line3/13 Finish Chassis and Design Layout

3/27 Assemble Everything/General outline of code

4/3 Finish Code

4/10 Get the mouse moving

4/10-END

Debug

PAU!!!

AND… WE’RE DONE

Questions???