Executive Summary - ECpE Senior Design | General...

1.0 Executive Summary

The executive summary will give a brief overview of the entire project, and the process the team underwent to reach the objective.

1.1 Project Need

An intelligent garage door system was needed. The objective of the project was to design, implement, test, and demonstrate a system that would determine if the garage door should be closed automatically upon departing the home. Some people drive a few blocks away from home and then return to make sure that they have closed the garage door. The project would involve determining the various conditions that could exist. Examples include: (1) departing car is parked inside the garage, (2) departing car is parked outside the garage on the driveway or street, and (3) garage door should remain open while resident mows or works on the lawn.

1.2 Project Activities

To start, the team brainstormed several ideas for how to solve the above problem. The idea that was picked is a system built of several different components. The brain of the system is a micro-controller, which takes inputs from several environmental sensors, makes a logical decision, and creates an output signal. The entire purpose of the sensors is to tell the “brain” of the system what state the garage door is in. The SGDS can be retrofitted with any opener that has open and closing contacts on the exterior of the base unit.

The entire team did research on different components of the SGDS system. Many of the components were free through help from our faculty advisors. Also, the fact this was a student project helped our team obtain many parts for free. The group began the testing process after all the parts were obtained. Several items were found to be incompatible at first and had to be exchanged for compatible components. There were no problems with making exchanges. After all the correct components were on hand, each was tested on an individual basis to make sure of proper working conditions. After all the testing was finished many of the original plans were slightly altered. However, the overall design follows the original plan the group created.

1.3 Final Results

When finished the project prototype worked and the final costs for the project were $180.82. The original estimate was $215, which means the project finished approximately 16% under budget. Time actually spent on the project was at a total of 563 hours and it was originally projected to be 690 hours, 18% under budget. Considering the facts that the project works as planned with finances and time allotment being under budget, the project is considered a success.

Smart Garage Door System -1- May 03-03

1.4 Recommendations for follow on work

If this project were to be considered for mass production, the following work would not only make the system more cost effective and run efficiently, but also save money in production expenses.

Create an original transmitter/receiver that will work for the system, not one purchased from a third party vendor. This would affect the cost of the overall system. If the system was mass-produced, this option might save money on production.

New microprocessor – The goal would be to find the cheapest microprocessor on the market that would be able to carry out all of the functions already in place. The current microprocessor (Motorola HC11) is overkill for the functions it is called to perform. The same functions can be carried out on a cheaper processor. This would help to lower the cost and area taken up by the present microprocessor.

Design for commercial use – This approach would broaden our customer base. This in turn would help sell more of the SGDS.

Design for more than two garage doors – This would allow customers with three or more garage doors, the abilities to operate each one with the luxury of only one remote.

Design for non-rail-type systems – This again will help to broaden the SGDS customer spectrum and bring in more business.


Acknowledgement:

The team of SGDS would like to take this opportunity to express their sincere appreciation to Ralph Patterson III and John Lamont for their time and expertise in making this system from a conceptual idea to one that can be thoroughly enjoyed by all homeowners.

2.1 Problem Statement

This section will provide a general background of the general garage opening problem, a technical description of the problem and what the solution is to be. It will explain the operating environment, the intended users, and assumptions and limitations the team was faced with during the project duration.

2.1.1 General Background

The current problem afflicting most homeowners as they leave their homes is the question, “Did I close my garage door?” As a direct result of this puzzlement, the homeowner is often forced to return back to their home to check on the status of their garage door. This type of problem costs the homeowner not only a headache, but also extremely precious time they could have spent elsewhere. The solution to this problem is the SGDS system. The SGDS is a system that determines if the garage door should be closed automatically upon departing the home.

This is accomplished by utilizing several devices, which are monitored by a master command module. These devices include a door timer, light timer, a micro-controller, a four-button main controller, a four-button remote control, and two contact limit switches. The four-button main controller mounts on the wall inside the garage, and replaces the normal wall mounted buttons for a regular garage door system. The four-button remote control can be carried in a vehicle or a person’s pocket or hand when they leave and want to run the system when they return. The contact limit switches mount on the rail of the opener system and are used to determine what position the garage door is in. The micro-controller is the “master command module” and is used for the timing devices along with the logic of the other sensing devices.

These devices install directly upon the existing garage door system and should in no way interfere with the proper or ordinary functionality of the regular garage door system.

2.1.2 Operating Environment

The SGDS system functions and includes the same type of environmental requirements as a normal garage door. This means the SGDS operates in rain, snow, extreme heat, and other related weather elements. The nominal operating temperature range for the SGDS system is from -40° F and +140° F. The SGDS may fail in conditions where the weather reaches extreme conditions and these conditions begin to interfere with the normal operation of the SGDS.


2.1.3 Intended Users

The intended users for the SGDS include the homeowner(s), family members who need access to the garage, and friends of the family. Other users who may be authorized to use the system include such examples as service people. Most anyone with access to a controller can operate the system.

The intended uses of the SGDS include the ability to automatically close the garage door. The system also offers the feature of allowing the user to push a button in order to disengage the automatic closing ability, and allows the garage door to remain in an open state.

It should be noted that while the SGDS has certain security and safety features, it is ultimately the responsibility of the end user to see that these features are not abused and that those using the system understand how it operates. The SGDS is also not meant to be the sole security for the house, but merely a supplement.

2.1.4 Assumptions and Limitations

Some of the assumptions that were made while designing the SGDS include that:

The system is to be installed on any garage door system with a residential grade opener.

The power source being used by the SGDS will be monitored and maintained by the end user.

The user’s garage system will allow for the proper installation of the SGDS system with minimal effort.

The limitations being made in the design of the SGDS include that:

The opener to which the SGDS system is being attached must have open and closing contacts readily available.

Obstruction sensors MUST be installed. Due to federal regulations under UL325, there is no way to bypass or eliminate obstruction sensors.

Remote controls will not operate outside a range of 120 ft. Batteries will be needed for the remote control and a power supply are needed for the

receiver and processor. Timers for the door(s) and driveway lights will have a maximum of 8.5 minutes and

minimum of 30 seconds.

2.1.5 Expected End Product

The SGDS is a garage door opener enhancer, which enables the owner/user to leave home without worry that the garage door might have been left open. The system is built of several different components. The brain of the system is a micro-controller, which takes inputs from several environmental sensors. The entire purpose of the sensors is to tell the “brain” of the system what state the garage door is in. The SGDS can be retrofitted with any opener that has control contacts on the exterior of the base unit.


2.2 Project Approach and Results

This section will explain the general approach to the design and all of the details of the final product that was developed.

2.2.1 End-Product Functional Requirements

Below is a list of functional requirements in which the SGDS system will be designed to meet:

Door Timer – When the garage door is opened and the SGDS is activated, a timer is initialized and starts a count down of length determined by the user settings. Upon the completion of the count down the garage door closes. If the user wishes for the door to remain open a SGDS override button exists. This button enables the user to switch off the SGDS and return the opener to its original operating mode.

Lights Timer – When the garage door open or close signal is present, driveway lights will come on based upon the output of a solar sensor. After the lights turn on a timer is initialized and begins a count down of length determined by the user settings. Upon the completion of the count down the lights will turn off

Light Sensor – The purpose of this sensor is to send a signal to the micro-controller telling the controller if it is light or dark outside. If it is dark then the driveway light function will be activated. (See appendix C)

Contact Limit Switches – These sensors are mounted on the garage door opener rail and positioned so detection of open and closed states is possible. The two contact switches should be mounted on the opener rail in a position so the door arm will engage either one of the two switches when the door is in the opened position or the other when the door is in the closed position.

Driveway Lighting Relay – This device shall have a set of contacts, which close when a signal is present. When the contacts close, the driveway lighting circuit will be energized and the lights will come on. This circuit will be wired in parallel with the power switch that resides in the home to give manual lighting control to the homeowner. (See Appendix D)

Micro-controller – The SGDS micro-controller takes input signals from the remote transmitter and wall-mounted buttons. Then it logically compares these signals with the contact switches, obstruction sensors, and solar sensor signals present at that time. After the signals are processed the micro-controller sends the appropriate signal to the outputs, which are the open and closing contacts of the door opener. (See Appendix E for program code)

Four-button Controllers – A wireless receiver and transmitter combo provides four different signals that are relayed via wire to the SGDS micro-controller. A four-button wall mounted control panel is wired in parallel with the receiver output wires running to the micro-controller. Connecting these in parallel will give the wall-mount controller the same functionality as the remote transmitter. The micro-controller is programmed in a way that the presence of different signals from the transmitter will output a different function.


2.2.2 Resultant Design Constraints

Limitations considered for design of the SDGS were:

Transmitter/receiver unit – Location of a device which had the exact functionality defined was too difficult and finding the exact match would be a task that would extend beyond the time frame given for the project.

Extreme cold – Extreme cold may affect the timing circuits. Placing the timer circuit inside the garage so harsh weather conditions are not a factor will solve this problem.

Battery power – This system will only work if the batteries used in the remote controller have enough power.

Two-door garage – The system will only control up to 2 garage doors.

2.2.3 Approaches Considered and One Used

The approach to this design problem was to draw up all the different scenarios and determine the correct functionality for the SGDS system. Below is a list of scenarios that apply to the functionality of the garage door system.

The different scenarios that exist in any garage door system are as follows.

The door is to stay open after initially being in a closed position and remain open. Example – The owner walks into the garage, decides to work outside, and desires to have the garage door open while they work.

The door is to close from the initial open position and remain closed. The door is to open from the initial closed position, stay open for a set amount of

time, and then close after time has elapsed.

A micro-controller was chosen for all the system logic due to the number of inputs this system has. Hardwire logic is an option but would be very hard to troubleshoot do to the size and complexity of the circuit. Outputs of this controller send a signal to the opener unit, which controls the actual opening and closing of the garage door.

A way of transmitting a signal from a remote control to the micro-controller was needed. Since so many transmitter/receiver systems already existed it made sense to purchase the product rather than waste time re-inventing. Also, a wall mount is needed for inside the garage. Momentary contact push buttons were purchased for this task.

Logical checks and safety devices were needed for this device too. Obstruction sensors, which should be on the original garage door system, are used to check the door opening for blockages. Contact limit switches are used to check if the door is in an open or closed state.

Timer circuits in the micro-controller are used for the driveway lighting and door closure timing. Potentiometers are used to make the timers adjustable.

A free Craftsman opener was given to the team for testing purposes. This opener has open and close contacts and a lighting circuit installed.


2.2.4 Detailed Design

The entire system can be visualized by observing the block diagram shown in Figure 1.



Figu

re 1

: Des

ign

Blo

ck D

iagr

am

Door1

Door2

Override1

Override2

Each different block/component was purchased separately. The micro-controller is programmed to take all the device inputs and send an output signal to the open or close contact of the opener unit itself.

Following is a diagram displaying the general layout of the wall-mounted and remote control.

Figure 2: General Controller Layout

The descriptions below describe the functionality of the wireless transmitter/receiver and button control system.

Opening (opening the garage door from a closed position and leaving the door open) – This will be initiated by a push button override. Pressing either “Override 1” for door one, or “Override 2” for door two will open their respective door and override the timer. A signal will be sent from the transmitter unit on the button release. (1 to 2 second delay).

Close (Immediate close from any state) – Close the garage by pressing either one of the two consecutive garage door buttons for the selected garage door.

Open & Close (Automatically) – To operate, the user will need to press one of the Door buttons on the controller (Door 1 or Door 2). This will open the garage door from a closed position and expect it to only stay open for the set amount of time. The time from open to close will be determined by the user (factory default at one minute). After the timer times out, a signal will be present at one of the inputs on the micro-controller and a door closing output signal will be sent to the opener unit.

2.2.4.1 Environmental Inputs to SGDS

Contact Limit Switches – Allows the system to monitor the status of the garage door. Determines whether the garage door is in an open or closed position.


Light Sensor – Allows the system to determine if daylight is present. If daylight is not present then the driveway lighting circuit should not be activated.

Figure 3: Light Detecting Circuit

User Interface Devices to SGDS

Mounted Push Buttons to Interior of Garage – Allows the user to control the system from inside the garage.

Remote Control – Allows the user to control the system from a remote location. Below is a schematic diagram of the receiver that was purchased for the system. A 5V signal is used in conjunction of the relays on the board.



Figu

re 4

- R

ecei

ver

Sche

mat

ic D

iagr

am

2.2.5 Implementation Process

For design implementation, the overall SGDS design was broken into smaller parts, and each of the different components were tested one at a time. Following is a list of results for each of the different components that were tested.

Transmitter/receiver - This unit had very minor assembly requirements. First, a battery terminal had to be soldered to the circuit board of the transmitter. The only other assembly required was to solder an eight-inch wire to the receiver unit, which would act as an antenna. For testing, a battery was placed in the transmitter and power was wired to the receiver board. The output was hooked into a multi-meter, and when the buttons on the transmitter were pushed the 5V signal was present at the output of the board.

Light sensor - Initially a solar cell was purchased from Radio Shack for the detection of light. This piece was not giving off enough voltage and was accidentally destroyed while taking a voltage reading with a multi-meter. The decision was made to go ahead and use a different light detecting circuit using an operational amplifier and a phototransistor. The circuit was assembled and tested. For testing, power to the circuit was applied and an output was present because no incandescent lighting was present. To simulate light, a flashlight was used and the output of the circuit was 0V like it was supposed to be.

Contact limit switches – These were not tested but simply wired into the system after the switches were mounted on the opener rail. They close a 5V DC circuit when contact is made.

Microprocessor – Code was written for the entire system and simulated on the computer using the ICC11 compiler.

Power relay – The power relay was wired to the output of the lighting circuit on the super strip. 120V AC was drawn through a receptacle and plug on the wall and the relay was used as a switch.

Push buttons – These were not tested but simply wired into the circuit in when it was assembled.

2.2.6 End-Product Testing Description

Finding a person who owned a garage door system and was willing to let the group test the design on it was not very practical so design testing was done in a simulated fashion. A 1/3 H.P. Sears Craftsman opening unit was given to the team by The Door Store located in west Ames. The sensors, controllers, and timers are wired into the micro-controller and evaluated so the correct output signal can be sent to the door-opening unit. (Appendix A)

Once the simulation layout was constructed each system component was tested for the correct signal output by taking readings from a multi-meter. After output signals had been verified the system functionality was tested on an individual component basis. The individual component testing is described below. Door timer – The garage door was opened and a stopwatch was started to check

for proper functionality. If the door stayed open too long then the timer would not be functioning properly and need to be re-adjusted.


Lights timer – The garage door was opened after dark to see if the lights were working. After the lights lit up, a stopwatch was initiated to keep track of how long the lights remained on. The lights turned off after the preset time expired.

Four-button controller – Pressing the proper buttons tested each of the different possible scenarios. One of the garage door buttons was pressed and a stopwatch was started to test the scenario where the user desires the door to close automatically. After the preset time had expired the garage door closed. Pressing the proper button and observing the door in an open position for a period longer than the preset timer was used to test the override button.

Figure 5 - Push Button Wiring Diagram

Driveway lighting – A lighting circuit with a switch was wired to a light fixture and tested. This simulated a driveway lighting system that is controlled from a switch in the home. An additional relay controlled lighting circuit was wired in parallel to the switch based circuit. When the relay got a signal from the processor it closed a set of contacts, which will energize the circuit and turned on the driveway lighting circuit. Figure 6 displays a diagram of the lighting circuit.


Power Relay

Lighting Circuit

External Lighting Output Signal from SGDS System

Main Source Power Feed

Wall-Mounted Manual Power Control Switch

Figure 6: Lighting Circuit Diagram

Contact limit switches – The output signal was verified with a multi-meter when the door was in an open and closed position.

Microprocessor – The microprocessor was purchased and worked when it was wired up and all code was correct.

Light detecting circuit – The circuit was placed in a well-lit area to determine that it is able to generate a signal. Then the circuit was covered to verify that the signal disappeared.

2.2.7 Project End Results

The following list gives a brief description of the major completion phases involved in the design project:

Start of project (completed)o Define problems to be solved and document the results.

Problem definition completed (completed) Finalize physical design plan (completed) Acquire all necessary parts for design phase (completed) Completion of implementation phase (completed) Completion of test and verification phase (completed) Completion of technical documentation (completed)

2.3 Resources and Schedules

The following section contains data on project costs and time spent on the project.

2.3.1 Resource RequirementsThis section contains tables with data to view personal effort requirements, resource requirements, and financial requirements.


2.3.1.1 Personnel Effort Budget

This table displays the estimated personal effort for the entire project. The time is sub-divided into different milestones of the project.

Table 2.1 Original Personal Effort Requirements

Table 2.2 Revised Personal Effort Requirements

Table 2.3 Final Personal Effort Requirements

2.3.1.2 Other Required Resources


The following tables will show original, revised, and final data of resources that would best fit in the “other costs” section of the project.

Table 2.4 Other Required Resources

2.3.1.3 Financial Budget

The following table contains a breakdown of estimated project costs and a breakdown of where the money will be spent. The team members will donate extra funds for parts and other unforeseen costs.

Table 2.5 Financial Budget


2.3.2 Schedules

Table 2.6 Original Estimated Project Gantt Chart

Table 2.6 shows in detail the original estimated schedule that was produced to show how the project would progress.


Table 2.7 Final Project Gantt Chart

Table 2.7 shows in detail the final true schedule that was produced to show how the project has progressed. There are minor changes between Table 2.6 and 2.7 mainly due to changes in the deliverables schedule for the project and due to project requirements given by the faculty advisors.


Table 2.8 Deliverables Gantt Chart

Table 2.8 shows in detail the deliverables schedule that was produced by the faculty advisors. This shows when all reports, posters, and any other forms need to be delivered to the faculty advisors and the client.


2.4 Closure Materials

The following section contains closure information. This data is important for re-summarizing the project as a whole.

2.4.1 Project Evaluation

Overall this project was a success. The final problem definition was reached early in the first semester of work. The project design was much easier to accomplish because the problem definition was clear to every member of the group. The design phase could have been slightly more efficient if group procrastination would have been eliminated.

There were no problems acquiring any parts for the SGDS because the group approached more than one source of information on parts in question. Sources of information used were Internet technical documents, faculty advisors, friends and other students, and EE staff.

Implementation, testing, and revisions went rather well despite a few minor changes to the system. A different alternative for light detection was needed after the solar cell did not work and was accidentally broken. Obstruction sensors were eliminated from the SGDS system because none are were compatible with the opening unit acquired. Also, obstruction sensors are required on any garage door opening system manufactured after 1992 so they will already be present. The group was originally going to use magnetic limit switches to place on the rail. Unfortunately, the parts we ordered were incomplete and a better alternative was discovered.

In the end the project turned out as the group foreseen at the beginning of the first semester. A few parts used ended up being different than planned but the final product worked in the same manner as planned.

2.4.2 Commercialization

The SGDS is a system fully capable of being commercialized. The system is adaptable enough to work on most major garage door systems and by designing the system with unique features to be offered at different consumer groups, the SGDS should be a very marketable item. The current estimated production cost of the SGDS is targeted at $100. The street selling price of the SGDS is currently seen to be at $300. At this cost the product would not be very feasible because majority of people will not spend this kind of money to add a feature like this.

However, with more research and time, various components of the SGDS could be custom designed and produced. This would at least cut production costs in half, and make the SGDS more marketable because it could be sold at a lower price.


2.4.3 Recommendations for Additional WorkThe following is a list of possibilities for further work to be done on the SGDS system.

Create an original transmitter/receiver - This would affect the cost of the overall system. If the system was mass-produced, this option might save money on production.

New microprocessor – The goal would be to find the cheapest microprocessor on the market that would be able to carry out all of the functions already in place. The current microprocessor (Motorola HC11) is overkill for the functions it is called to perform. The same functions can be carried out on a cheaper processor. This would help to lower the cost and area taken up by the present microprocessor.

Design for commercial use – This approach would broaden our customer base. This in turn would help sell more of the SGDS.

Design for more than two garage doors – This would allow customers with three or more garage doors, the abilities to operate each one with the luxury of only one remote.

Design for non-rail-type systems – This again will help to broaden the SGDS customer spectrum and bring in more business.

2.4.4 Lessons Learned

One of the major accomplishments that went well for the team was the ability to properly use outside resources. The team was able to secure a Craftsman opening unit from The Door Store, and in doing so lowered the overall costs for this project. The team successfully used the expertise of Jason Boyd and Doug Jacobsen in acquiring and understanding how certain components of the SGDS function and operate. The team also benefited from this project in terms of understanding how hardware and software are dependent upon one another and that having well defined specifications for each is a necessity in order to have them properly communicate to one another.

One of the major issues early on in the project that the team dealt with was project specifications. At times, team members were confused by what types of requirements were needed by each component in the SGDS and which components would work the best for what was needed. To solve this problem, the team sat down at a meeting and listed all the requirements and functionalities the SGDS needed to meet. Once this was accomplished, the team was able to quickly identify what components would meet their needs and satisfy the project requirements.

One of the technical issues that the team faced involved the limitations of taking components from different vendors and attempting to inter-connect them. At times the team struggled in understanding why one component may be operating correctly and the other component, which was to pick up this correct output, would not see it at all. After several hours of Internet research and experimentation, the team eventually found solutions to these types of problems and were able to overcome most of the limitations of the components. Some additional information the team learned throughout the course of this project was the ability to take output given by a piece of hardware and have software correctly interpret the signal and supply the appropriate action to the hardware.


As for non-technical issues, the main points the team learned were teamwork and time management skills. The team discovered what each individual’s strengths and weaknesses might be and then managed the project in such a way that each person on the team was able to contribute equally and significantly. As for the time management skills, the team discovered the importance of communicating meeting times and meeting places. At times, proper documentation of work accomplished saved other team members several hours of figuring out what had been accomplished and what still needed to be done.

In regards to what the team would do differently, the major emphasis would be on doing as much research and planning as possible. In doing so, the team feels that any problems that may occur throughout the project could be dealt with swiftly since time was allocated to have information ready in such an event. Also, the likely-hood of problems occurring would be greatly reduced because proper research had been conducted and looked through thoroughly.

2.4.5 Risk and Risk Management

Budget

Financial aspects of a project are very important to keep track of. The following are some financing areas the team is especially concerned with:

The project is terminated when no remaining budget is available. – The available budget will be checked on a weekly basis.

Personnel

When more than one person is assigned to a project there is always risk that one or more of the members may not perform to what is required. Following are personnel issues the team is concerned with:

Each member fully understands the responsibility of other members – If responsibility is an issue the team leader will address everyone together.

A team member is dismissed or lost for unforeseen circumstances. – Project responsibilities will be reassigned.

Risk Factors

Other factors the team needs to be concerned with are:

Missing deadlines – The team must be organized and keep to a schedule. Not saving project – A habit of emailing the latest version of every document

will be developed. Losing disks – The project will be saved in more than one place. Unexpected equipment failure – The team’s communication skills will be put

to work immediately. Misplaced equipment – The team will take extra care in putting equipment

away and making sure everything is organized before meetings are adjourned.


2.4.6 Project Team Information

Clients:

Senior Design

Faculty Advisors:

Ralph Patterson III John W LamontOffice Phone: (515) 294-2428 Office Phone: (515) 294-3600Home Phone: (515) 232-9933 Home Phone: (515) 292-5541Fax: (515) 294-6760 Fax: (515) [email protected] [email protected] Town Engr. 324 Town Engr.Ames, IA 50011-3230 Ames, IA 50011-3230

Team Members:

Dave Barto Ben Molayal232 Welch Ave. apt. #4 237 Ash Ave.Ames, IA 50014 Ames, IA 50014(515) 290-6695 (515) [email protected] [email protected] EE/Cpr E

Kyle Leinen Brodie PedersonFriley 5574 Bennett 1209 Scholl RdAmes, IA 50012 Ames, IA 50014(515) 572-5271 (515) [email protected] [email protected] E EE


2.4.7 SUMMARY

Technology continues to play a greater role in our everyday lives. As this dependency grows, the probability that human error can significantly affect the performance of these high tech devices increases exponentially. Enter the SGDS system. Revolutionary in its ability to allow the user a peace of mind in no longer worrying whether they have closed the garage door after departing their home. The SGDS utilizes state of the art devices to monitor the status of the garage door and interprets what the user needs may currently be. The SGDS will feature a package that goes beyond the “usual” and will expand into important expected and unexpected features. Once completed, the SGDS will offer homeowners precisely what they have desired in a garage door opening system.


2.4.8 AppendixThis is a diagram which displays approximately where the parts to the garage door and SGDS system are located.

A Garage Layout


Figu

re 5

: Gar

age

Lay

out

B Program Code

// SGDS System Program

// Included Library#include <f1board.h> #include <f1intsvc.h>#include <ram.h>#include <hc11.h>

// Interupt Handler#pragma interrupt_handler ISR_RTI_Timer

// Function Prototypesvoid ISR_RTI_Timer ();void moveDoor (int mode);void lightswitch (void);void ProcessAtoD();

// Inputs to Systemunsigned char *IN = (unsigned char *) 0x1808; // Dipswitch Inputs (IC pins)

// Outputs for Systemunsigned char *OUT = (unsigned char *) 0x1809; // Digital Outputs at the Digital Out port

//A/D Conversionunsigned char *pADR1 = (unsigned char *) 0x1031;char *pOption = (char *) 0x1039;char *pADCTRL = (char *) 0x1030; unsigned char temp=0;

//********** Input Bit Setup **********// Button 1 = (IN & 0x01) CYCLED OPEN/CLOSE// Button 2 = (IN & 0x02) OVERRIDE OPEN/CLOSE// door_open = (IN & 0x04) DOOR OPEN POSITION// door_close = (IN & 0x08) DOOR CLOSED POSITION// light_sensor = (IN & 0x10) LIGHT SENSOR CIRCUIT ON IF NO LIGHT

// ***********Output Bit Setup**********// Door = (OUT & 0x01) Signal to Door Opener// Lighting Relay = (OUT & 0x02) Signal to Close Exterior Lighting Relay

// System Variablesint LSeconds = 0;int DSeconds = 0;int DsSeconds = 0;int door_timer = 0;int door_signal = 0;int light_timer = 0;int door_moving = 0;int prev_door_pos = 0;int User_timer = 1860;

void main (void){

*OUT &= 0x00; // Initializing Output pins to be low*pOption = *pOption | 0x80;*(void (**)()) 0x7e28 = ISR_RTI_Timer; // Place our ISR in the vector table

// Setting up the real time interruptTFLG2 = 0x40; // clear the interrupt flagPACTL |= 0x03; // Setup I/O subsystemTMSK2 |= 0x40; // Turns on Maskable interrupts

while(1){

ProcessAtoD(); //Allows User to adjust timer of Door and Lights

if(temp >=1 && temp <= 10) User_timer = 1860; // 1 minuteelse if(temp >=45 && temp <= 60) User_timer = 3720; // 2 minuteselse if(temp >=130 && temp <= 145) User_timer = 5580; // 3 minuteselse if(temp >=215 && temp <= 230) User_timer = 7440; // 4 minuteselse if(temp >=250 && temp <= 255) User_timer = 9300; // 5 minutes


// CYCLE MODEif(!(*IN & 0x01)) // Button 1 pressed, timer set{

if(!(*IN & 0x04)) // Door1 is open and user wants to CLOSE DOORmoveDoor(0); // Closing door1 WITHOUT timer

if(!(*IN & 0x08)) // Door1 is CLOSED and user wants to OPEN and START TIMER{ moveDoor(1); // Opening door1 and CLOSING WITH timer

lightswitch(); // Turning on the lights with a timer if it is dark out}if(door_moving && prev_door_pos) // If door is opening and button 1 is pressed{

door_timer = 0; // Shutting off door timer DSeconds = 0; // Reset door timer delay time

moveDoor(0); // Closing door without timerprev_door_pos = 0; // Changing previous door position from closed to open

}if(door_moving && !(prev_door_pos)) // If door is closing and button 1 is pressed{

door_timer = 0; // Resetting door timerDSeconds = 0; // Reset door timer delay timemoveDoor(1); // Re-Opening door with timer activatedprev_door_pos = 1; // Changing previous door position from open to closed

}

}

// OVERRIDE MODEif(!(*IN & 0x02)) // Button 2 pressed, no timer set{

if(!(*IN & 0x08)) // Door1 is CLOSED and user wants it to stay OPEN{

moveDoor(0); // Opening door1 and CLOSING WITH timerlightswitch(); // Turning on the lights with a timer if it is dark out

}

if(door_moving && !(prev_door_pos)){

door_timer = 0; // Shutting off door timer DSeconds = 0; // Reset door timer delay time

moveDoor(0); // Closing door without timerprev_door_pos = 1; // Changing previous door position from open to closed

}

}

if(door_signal) door_moving = 1; // Setting Flag to tell when the door is moving

// Determine when the door is done movingif(door_moving && (!(*IN & 0x04) || !(*IN & 0x08))) door_moving = 0;

}return;

}

void ISR_RTI_Timer (){

// Lights have been turned on....waiting 2 mins to turn offif(light_timer) {

LSeconds++; // Incrementing number of times ISR called and light_timer is onif(LSeconds == User_timer) // If 2 mins has passed, turn off lights{

LSeconds = 0; // Resetting number of times ISR is called and light_timer is onlight_timer = 0; // Resetting the light_timer flag*OUT &= 0x0C; // Physically turning off the lights

}}

// Door has been opened with timer activated....waiting 2 mins to re-close the doorif(door_timer){

*OUT &= 0x0E; // Initializing Output pins to be low


DSeconds++; // Incrementing number of times ISR called and door_timer is onif(DSeconds == User_timer) // If 2 mins has passed, close the door{

DSeconds = 0; // Resetting number of times ISR is called and light_timer is on// Counter is reset after each second

door_timer = 0; // Resetting the door_timer flagif(!(*IN & 0x04)) prev_door_pos = 0; // Door in OPEN positionif(!(*IN & 0x08)) prev_door_pos = 1; // Door in CLOSED positiondoor_signal = 1; // Setting flag to hold door closing signal for 2 seconds*OUT &= 0x0F; // Physically closing the door

}}if(door_signal){

DsSeconds++; // Incrementing number of times ISR called and door_signal is onif(DsSeconds == 62) // If 2 seconds has passed, shut off the signal{

DsSeconds = 0; // Resetting number of times ISR is called and door_signal is ondoor_signal = 0; // Resetting the door_signal flag*OUT &= 0x0C; // Physically turning off the signal

}}TFLG2 |= 0x40; // Clearing the interrupt flag

}

void moveDoor (int mode){

// mode => 0 = door timer off// 1 = door timer on

if(mode) // Closing the door WITH door_timer{ door_timer = 1; // Set Flag to start door_timer (will be handled in ISR_RTI_Timer) *OUT = 0x01; // Physically closing the door} else{

if(!(*IN & 0x04)) prev_door_pos = 0; // Door in OPEN positionif(!(*IN & 0x08)) prev_door_pos = 1; // Door in CLOSED positiondoor_signal = 1; // Setting flag to hold door closing signal for 2 seconds *OUT = 0x01; // Physically closing the doorprintf("I am done with moveDoor!");

}}

void lightswitch (void){

// Testing to see if the light sensor detects no lightif(!(*IN & 0x10)){

light_timer = 1; // Setting flag to start light_timer*OUT |= 0x02; // Physically turning on the lights

}}

void ProcessAtoD(){

if(*pADCTRL & 0x80) temp = (*pADR1);*pADCTRL = *pADCTRL & 0x7F;

}


Executive Summary - ECpE Senior Design | General...

Documents

Transcript of Executive Summary - ECpE Senior Design | General...