1. ECE 477 Final Presentation Group 11  Spring 2005

2. Outline Project overviewProject overview Block diagramBlock diagram Professional componentsProfessional components Design componentsDesign components Success criteria demonstrationsSuccess criteria demonstrations Individual contributionsIndividual contributions Project summaryProject summary Questions / discussionQuestions / discussion

3. Project Overview MAVerick (Motorized Assault Vehicle) is a mobile gun platform controlled by a cellular phone that has the ability to establish full-duplex communication with a command center in order to transmit control and status signals. It will contain a paintball gun attached to the platform which will fire at moving targets and have the ability to detect obstacles.

4. Motivation To fill in a gap in the adult toys industryTo fill in a gap in the adult toys industry –Paintball enthusiasts –War games Military possibilitiesMilitary possibilities –With proper upgrades, could be a useful tool on the battlefield

5. Block Diagram

6. Professional Components Constraint analysis and component selection rationaleConstraint analysis and component selection rationale Patent liability analysisPatent liability analysis Reliability and safety analysisReliability and safety analysis Ethical and environmental impact analysisEthical and environmental impact analysis

7. Constraint Analysis Microcontroller

8. Constraint Analysis DTMF Encoder DTMF Decoder

9. Constraint Analysis Ultrasonic Sensor

10. Patent Liability Analysis Search criteriaSearch criteria - DTMF encoding/decoding/transmitting - Use of a toy tank - Detecting obstacles using an array of passive infrared sensors - Detect moving targets using an ultrasonic sensor

11. Patent Liability Analysis Literal InfringementsLiteral Infringements - Vehicle obstacle avoidance system Pat. No. 5,598,164 Pat. No. 5,598,164 Infringement under the Doctrine of EquivalentsInfringement under the Doctrine of Equivalents - Mobile-to-mobile DTMF signaling in tandem free operation Pat. No. 6,791,976

12. Patent Liability Analysis “Commercial” Product“Commercial” Product - SWORDS – Special Weapons Observation Reconnaissance Detection System

13. Reliability/Safety Analysis The evaluated components were chosen for three reasons: The evaluated components were chosen for three reasons: 1. All the components represent different blocks of the MAVerick’s circuits. 2. They were chosen for criticality. If any of these components fail, then their respective blocks will fail and the MAVerick will lose a major portion of its functionality. 3. They are all different types of components and demonstrate how different parts use their own unique variables, values, and equations to rate their reliability.

14. Reliability/Safety Analysis Four components were evaluated for reliability: Four components were evaluated for reliability: 1. Microcontroller – Atmel AtMega16L λP = 2.86 failures per 10 6 hours λP = 2.86 failures per 10 6 hours MTTF = 349,650 hours or 39.9 years MTTF = 349,650 hours or 39.9 years Main reason for unreliability: conservative temperature and quality factor Main reason for unreliability: conservative temperature and quality factor Way to improve: it will outperform its MTTF in reality Way to improve: it will outperform its MTTF in reality 2. Crystal Oscillator – 3.58 MHz λP = 0.399 failures per 10 6 hours λP = 0.399 failures per 10 6 hours MTTF = 2,506,265 hours or 286.1 years MTTF = 2,506,265 hours or 286.1 years Main reason for unreliability: none Main reason for unreliability: none Way to improve: very reliable, no change is needed Way to improve: very reliable, no change is needed

15. Reliability/Safety Analysis 3. Voltage Regulator – LM7805CT λP = 4.7952 failures per 106 hours MTTF = 208,542 hours or 23.8 years Main reason for unreliability: conservative temperature and high quality factor Way to improve: use a better quality part 4. Motor – DC λP = 9.09 failures per 106 hours MTTF = 110,000 hours or 12.56 years Main reason for unreliability: temperature Way to improve: add heat sinks,tank could be ventilated Way to improve: add heat sinks, tank could be ventilated

16. Ethical/Environmental Analysis Ethical AnalysisEthical Analysis –Careless/harmful usage –Accidental misfires –Warning labels

17. Ethical/Environmental Analysis Environmental AnalysisEnvironmental Analysis –Proper disposal of printed circuit board –Proper disposal of rechargeable batteries –Proper disposal of CO 2 tank –Lots of recyclable parts

18. Design Components Packaging design considerationsPackaging design considerations Schematic design considerationsSchematic design considerations PCB layout design considerationsPCB layout design considerations Software design considerationsSoftware design considerations

19. Packaging Design MAVerick is packaged in the above pictured tank. A paintball gun is integrated into the existing turret. The circuit board and all wires are housed inside of the tank. All sensors are mounted on the outside of the tank.

20. Packaging Design Goose is packaged in the above pictured joystick. The circuit board, battery pack, and all wires are housed inside the joystick. The height of the housing was augmented by 2.5 inches. Status LEDs and an on/off switch were added to the top.

21. Schematic Design Motor ControlMotor Control

22. Schematic Design Stepper Motor ControlStepper Motor Control

23. Schematic Design DTMF CircuitsDTMF Circuits

24. Schematic Design Ultrasonic SensorUltrasonic Sensor

25. Schematic Design Infrared SensorsInfrared Sensors

26. Schematic Design JoystickJoystick

27. Schematic Design MicrocontrollerMicrocontroller

28. Schematic Design HeadersHeaders

29. PCB Layout Design MAVerick (Tank)MAVerick (Tank)

30. PCB Layout Design Goose (Joystick)Goose (Joystick)

31. Software Design MAVerick ( Tank )MAVerick ( Tank ) - Size: 21.6% - ~1250 lines of code - Loop driven - Modules: main, init, get_tone, send_tone, motor, stepper, action, joyaction, ultrasonic, autonomous, joystick, and phone

32. Software Design Goose ( Command Center )Goose ( Command Center ) - Size: 7.4% - ~700 lines of code - Loop driven - Modules: main, init, get_tone, send_tone, read_adc, set_led

33. Software Design MAVerick (Tank)MAVerick (Tank)

34. Software Design Goose (Joystick)Goose (Joystick)

35. Success Criteria Demonstrations 1.Ability to detect moving targets using an ultrasonic/IR sensor - demo demo 2.Ability to detect and avoid obstacles - demo demo 3.Ability to encode and send control signals through a cellular phone to control the tank/gun - demo demo 4.Ability to receive and decode control signals from the cellular phone - demo demo 5.Ability to send status information from the tank to the controlling device - demo demo

36. Individual Contributions Team Leader – Chad BjorklundTeam Leader – Chad Bjorklund Team Member 2 – Paul DulleTeam Member 2 – Paul Dulle Team Member 3 – Pat McLaughlinTeam Member 3 – Pat McLaughlin Team Member 4 – Randall ScheifeleTeam Member 4 – Randall Scheifele

37. Team Leader - Chad Bjorklund Prototype DTMF CircuitryPrototype DTMF Circuitry Part ResearchPart Research PCB LayoutPCB Layout Ethical / Environmental AnalysisEthical / Environmental Analysis Software DevelopmentSoftware Development

38. Member 2 – Paul Dulle Component RationalizationComponent Rationalization Sensor Research / SelectionSensor Research / Selection Circuit PrototypingCircuit Prototyping H-Bridge / Stepper Driver DesignH-Bridge / Stepper Driver Design Circuit Schematic / IntegrationCircuit Schematic / Integration MAVerick (Tank) Board PopulationMAVerick (Tank) Board Population Physical Construction / MountingPhysical Construction / Mounting Cable / Debugging Tool ConstructionCable / Debugging Tool Construction Assisted Software DebuggingAssisted Software Debugging

39. Member 3 - Pat McLaughlin Circuit TestingCircuit Testing Board PopulationBoard Population Physical Design and ConstructionPhysical Design and Construction Safety and ReliabilitySafety and Reliability Prototype joystickPrototype joystick

40. Member 4 - Randall Scheifele DTMF Circuit PrototypingDTMF Circuit Prototyping Software DevelopmentSoftware Development Assisted Physical ConstructionAssisted Physical Construction Patent Liability AnalysisPatent Liability Analysis Software Design ConsiderationsSoftware Design Considerations DebuggingDebugging WebsiteWebsite

41. Project Summary Important lessons learnedImportant lessons learned –By prototyping hardware we were able to avoid flywire on the PCB –Our in-circuit programming headers allowed for rapid software debugging –Make sure to buy plenty of spares for high risk parts –Think of the software requirements while creating the schematic

42. Project Summary Second iteration enhancementsSecond iteration enhancements –Interrupt driven code instead of polling –Better cell phone integration –Y-axis turret movement –PWM for variable motor speeds –Infrared sensors for aiding target detection –Video broadcast over the cell phone –Faster motors

43. Questions / Discussion

44. Project Success Criteria Back