toolbox
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
blueprint [2009/01/20 04:40] jonmash |
blueprint [2009/01/20 15:49] (current) jonmash |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Submission Information ====== | ||
| + | |||
| + | //Date:// Wednesday, January 14, 2009. | ||
| + | |||
| + | //Submitted By:// **Group 8** | ||
| + | * Liliane Barbour | ||
| + | * Jonathan Mash | ||
| + | * Michael Studli | ||
| + | |||
| + | //Faculty Supervisor:// | ||
| + | * Dr. Hashtrudi-Zaad | ||
| + | * Department of Electrical and Computer Engineering | ||
| + | |||
| + | ===== Download ===== | ||
| + | {{:blueprint.doc|}} | ||
| + | {{:blueprint.docx|}} | ||
| ====== EXECUTIVE SUMMARY ====== | ====== EXECUTIVE SUMMARY ====== | ||
| Line 22: | Line 38: | ||
| The project is composed of a three-part framework: a sensing system to determine the position of viewers, a controller to compute the ideal position of the TV, and a drive system to accurately rotate the TV to a previously calculated position. See Figure 1 for a graphical representation. | The project is composed of a three-part framework: a sensing system to determine the position of viewers, a controller to compute the ideal position of the TV, and a drive system to accurately rotate the TV to a previously calculated position. See Figure 1 for a graphical representation. | ||
| - | {{:systemleveldiagram-proposal.jpg|}} | + | {{ :systemleveldiagram-proposal.jpg?300 }} |
| Figure 1: System level overview | Figure 1: System level overview | ||
| Line 28: | Line 44: | ||
| ===== WORK BREAKDOWN STRUCTURE ===== | ===== WORK BREAKDOWN STRUCTURE ===== | ||
| - | {{:wbs.jpg|}} | + | {{ :wbs.jpg }} |
| - | + | ||
| Figure 2: Work Breakdown Structure | Figure 2: Work Breakdown Structure | ||
| Line 56: | Line 72: | ||
| **MOTOR CONTROLLER:** The existing motor controller circuit was not tested due to the team’s lack of understanding of the circuit, the poor construction of the circuit, and the complexity of the wiring. | **MOTOR CONTROLLER:** The existing motor controller circuit was not tested due to the team’s lack of understanding of the circuit, the poor construction of the circuit, and the complexity of the wiring. | ||
| - | ===== DESIGN ===== | + | ==== DESIGN ==== |
| - | ==== MICROCONTROLLER SELECTION ==== | + | === MICROCONTROLLER SELECTION === |
| Due to the nature of the sensors that are being used in this design, a powerful processor with fast analog to digital conversion is required. Also, analysis of five analog channels (for five PIR sensors) is required to determine the position and movement of humans in the TV’s field of view. These requirements indicate that the microprocessor must have enough memory and fast enough clock speed to read, store, and analyze potentially thousands of samples per second. | Due to the nature of the sensors that are being used in this design, a powerful processor with fast analog to digital conversion is required. Also, analysis of five analog channels (for five PIR sensors) is required to determine the position and movement of humans in the TV’s field of view. These requirements indicate that the microprocessor must have enough memory and fast enough clock speed to read, store, and analyze potentially thousands of samples per second. | ||
| Line 66: | Line 82: | ||
| The Arduino is an easy to use microcontroller package that is based on the ATmega168 microprocessor (1). The term Arduino usually refers to the entire package which comprises of the PCB design, software API, programming IDE, and the bootloader. The Arduino system is open-source and publically available. The Arduino comes with an ATmega168 chip that is preloaded with the Arduino bootloader. The bootloader is used to easily program the chip without the use of and In-Circuit Serial Programmer (ICSP). This allows for quick and easy development at the loss of a small amount of program memory. The ATmega168 chip has 16kB of flash (program) memory, 1kB of SRAM (variable) memory, and 512 B of EEPROM (long term storage) (1). Although this is a relatively small amount of memory, the team is confident that it will suffice for the purposes of this project. The processor currently runs at 16 MHz but can be run up to a maximum of 20 MHz (2). This processor speed should be more than enough for the team’s purposes. The Arduino also has six 10-bit analog to digital converters and over ten digital I/O pins (1). This should be suitable for the team’s application. | The Arduino is an easy to use microcontroller package that is based on the ATmega168 microprocessor (1). The term Arduino usually refers to the entire package which comprises of the PCB design, software API, programming IDE, and the bootloader. The Arduino system is open-source and publically available. The Arduino comes with an ATmega168 chip that is preloaded with the Arduino bootloader. The bootloader is used to easily program the chip without the use of and In-Circuit Serial Programmer (ICSP). This allows for quick and easy development at the loss of a small amount of program memory. The ATmega168 chip has 16kB of flash (program) memory, 1kB of SRAM (variable) memory, and 512 B of EEPROM (long term storage) (1). Although this is a relatively small amount of memory, the team is confident that it will suffice for the purposes of this project. The processor currently runs at 16 MHz but can be run up to a maximum of 20 MHz (2). This processor speed should be more than enough for the team’s purposes. The Arduino also has six 10-bit analog to digital converters and over ten digital I/O pins (1). This should be suitable for the team’s application. | ||
| - | ==== SOFTWARE DEVELOPMENT ==== | + | === SOFTWARE DEVELOPMENT === |
| The software will be built in three stages. The first stage, which began as soon as the team selected the microcontroller, was to write code that can communicate with each individual device. Once this is complete, the team will start combining the software for the individual systems into one package. Inputs will be read from the sensory system, but no decisions will be made based on the input. Hard-coded data will be sent to the volume controller and motor controller. In the third stage, further development will implement an intelligence algorithm. It will take data from the sensors, and then make decisions that affect the output sent to the volume control system and motor controller. Since the intelligence algorithm is dependent on the integration of the hardware systems, full development and testing of the algorithm will occur after hardware integration begins, as can be seen in the Gantt chart in Appendix C. | The software will be built in three stages. The first stage, which began as soon as the team selected the microcontroller, was to write code that can communicate with each individual device. Once this is complete, the team will start combining the software for the individual systems into one package. Inputs will be read from the sensory system, but no decisions will be made based on the input. Hard-coded data will be sent to the volume controller and motor controller. In the third stage, further development will implement an intelligence algorithm. It will take data from the sensors, and then make decisions that affect the output sent to the volume control system and motor controller. Since the intelligence algorithm is dependent on the integration of the hardware systems, full development and testing of the algorithm will occur after hardware integration begins, as can be seen in the Gantt chart in Appendix C. | ||
| - | ==== MOTOR CONTROLLER ==== | + | === MOTOR CONTROLLER === |
| It was decided in the meeting with Dr. Hashtrudi-Zaad on November 20, 2008 (4), that two motor drivers will be developed. The first system will comprise of an off-the-shelf H-bridge integrated circuit that has all the basic capabilities necessary to run the stepper motor found in the turntable design. Time and budget permitting, a second system will be built. It will consist of a custom H-bridge controller with over-current protection that can be built to the exact specifications of the stepper motor. The two systems will require the same inputs and have the exact same outputs; this will reduce the amount of I/O required from the microcontroller and allow the two systems to be easily interchangeable. | It was decided in the meeting with Dr. Hashtrudi-Zaad on November 20, 2008 (4), that two motor drivers will be developed. The first system will comprise of an off-the-shelf H-bridge integrated circuit that has all the basic capabilities necessary to run the stepper motor found in the turntable design. Time and budget permitting, a second system will be built. It will consist of a custom H-bridge controller with over-current protection that can be built to the exact specifications of the stepper motor. The two systems will require the same inputs and have the exact same outputs; this will reduce the amount of I/O required from the microcontroller and allow the two systems to be easily interchangeable. | ||
| Line 79: | Line 95: | ||
| The off-the-shelf system is simplistic and industry proven. A custom system will allow the team to explore working with analog motor control and sensory circuits. It will also include over-current protection as an added safety feature. The use of the two systems should lead to a successful implementation of the motor controller driving circuit. | The off-the-shelf system is simplistic and industry proven. A custom system will allow the team to explore working with analog motor control and sensory circuits. It will also include over-current protection as an added safety feature. The use of the two systems should lead to a successful implementation of the motor controller driving circuit. | ||
| - | ==== CONTROL BOARD AND MOTOR CONTROL BOARD INTERFACING ==== | + | === CONTROL BOARD AND MOTOR CONTROL BOARD INTERFACING === |
| In a team meeting on January 7, 2009 (4), the team members decided on a PWM control system to serve as the basis for interfacing between the control board and the motor control board. The length of a single pulse will indicate the desired position of the TV in degrees. This design is very similar to a servo controller that uses a base timing of 1.5 seconds and a range of 1 to 2 seconds. One second would refer to the minimum possible rotation and 2 seconds refers to the maximum possible rotation. Exact timing specifications will be finalized during programming of both the central controller and motor controller boards. | In a team meeting on January 7, 2009 (4), the team members decided on a PWM control system to serve as the basis for interfacing between the control board and the motor control board. The length of a single pulse will indicate the desired position of the TV in degrees. This design is very similar to a servo controller that uses a base timing of 1.5 seconds and a range of 1 to 2 seconds. One second would refer to the minimum possible rotation and 2 seconds refers to the maximum possible rotation. Exact timing specifications will be finalized during programming of both the central controller and motor controller boards. | ||
| Line 100: | Line 116: | ||
| Table 1: Summary of Current Budget | Table 1: Summary of Current Budget | ||
| - | {{:smallbudget.jpg|}} | + | {{ :smallbudget.jpg }} |
| ====== PROBLEMS AND RISK MITIGATION ====== | ====== PROBLEMS AND RISK MITIGATION ====== | ||
| - | {{:risktable.jpg|}} | + | {{ :risktable.jpg }} |
| ====== CONCLUSIONS ====== | ====== CONCLUSIONS ====== | ||
| Line 121: | Line 137: | ||
| ====== APPENDIX A: PIR SENSOR OUTPUT ====== | ====== APPENDIX A: PIR SENSOR OUTPUT ====== | ||
| - | {{:appendixa.jpg|}} | + | |
| - | + | {{ :appendixa.jpg }} | |
| Output from a PIR sensor with movement of person from left to right of the field of view. | Output from a PIR sensor with movement of person from left to right of the field of view. | ||
| Line 129: | Line 146: | ||
| ====== APPENDIX B: DETAILED BUDGET ====== | ====== APPENDIX B: DETAILED BUDGET ====== | ||
| - | {{:appendixb.jpg|}} | + | |
| + | {{ :appendixb.jpg }} | ||
| ====== APPENDIX C: GANTT CHART ====== | ====== APPENDIX C: GANTT CHART ====== | ||
| - | {{:appendixc.jpg|}} | + | |
| + | {{ :appendixc.jpg }} | ||
| ====== APPENDIX D: DUAL FULL-BRIDGE DRIVER ====== | ====== APPENDIX D: DUAL FULL-BRIDGE DRIVER ====== | ||
| Source: (6) | Source: (6) | ||
| - | {{:appendixd-1.jpg|}} | ||
| - | {{:appendixd-2.jpg|}} | + | {{ :appendixd-1.jpg?150 }} |
| - | + | {{ :appendixd-2.jpg?150 }} | |
| - | {{:appendixd-3.jpg|}} | + | {{ :appendixd-3.jpg?150 }} |
| ====== APPENDIX E: MCP1401/02 DATASHEET ====== | ====== APPENDIX E: MCP1401/02 DATASHEET ====== | ||
| Source: (7) | Source: (7) | ||
| - | {{:appendixe-1.jpg|}} | ||
| - | {{:appendixe-2.jpg|}} | + | {{ :appendixe-1.jpg?150 }}{{ :appendixe-2.jpg?150 }}{{ :appendixe-3.jpg?150 }} |
| - | + | ||
| - | {{:appendixe-3.jpg|}} | + | |
| ====== APPENDIX F: MOTOR SPECIFICATIONS ====== | ====== APPENDIX F: MOTOR SPECIFICATIONS ====== | ||
| Source: (8) | Source: (8) | ||
| - | {{:appendixf.jpg|}} | + | |
| + | {{ :appendixf.jpg?150 }} | ||
Brought to you by: Liliane Barbour, Jonathan Mash and Mike Studli
With the support of: Dr. Hashtrudi-Zaad
