Archive for the 'Final Project' Category
[DSSP] – Final Project Proposal: [Smart Mailbox for Smart Wheelchair]

Team Members:

  • Dipendra Khatiwada
  • Suman Gautam
  • Santosh Shrestha
  • Pravin Maharjan

Final Project Proposal

           We, “Team DSSP”, will be continuing working in our final project “Smart Mailbox for Smart Wheelchair” in next Spring semester.  Smart Wheelchair will have all functions such as getting notification on mail arrival, obstacle avoidance, and 3-D mapping.   The most important goal for this project will be to design cheap, affordable, and effective obstacle avoidance sensors.  This will help many disabled individuals to drive freely while remaining safe.  We will also be using a cheap android tablet as a display which will have an application containing all the commandsSome of the key points to our project are:

  • User-friendly to disable and handicap individuals
  • Basic and simple interface  
  • Android tablet will be used for display and to control other important functions (getting notifications for mailbox, navigation, etc.)
  • The final project will include our original idea of a smart mailbox 
  • Our product will have user guides included

Team Structure

           Each team mate will work at least 3-5 hrs a week. As a team, we will share our ideas and skills to get our project done throughout the semester. We will meet at least 3 days a week to work together and to keep our project in right track. We will be spending at least 7-9 hrs working together a week.

Project Timeline 

Phase

Date

Acceptable

Good

Excellent

Project Completion

 5/4

Project Completed with some minor bugs that needs to be fixed. Final Report submitted.

Project Completed with almost all parts working fine. Final report submitted.

Project completed completely without any trouble. Everything works perfectly. Final report submitted.

Goal 6

 4/20

Test our project and fix bugs, start writing final report

 Test our project, final wrap up with some tolerance, start writing final report

 Test our project, works perfectly, final wrap up with no errors. Final report written

Goal 5

 4/13

Still working on developing android app

Start putting all components and circuits together 

 Assembling all circuits and components together and in right way, test it

Milestone 2

 3/30

Arduino and android working together

Almost done with our application development, android and arduino working together 

Application developed, android and arduino working together perfectly 

Goal 4

 3/9

 Research on android and arduino working together

 Learning   android application development, connecting android and arduino

 Start developing android application and start making arduino and android work together

Goal 3

 3/2

 Work on obstacle avoidance if we don’t get it done

 Research on other components that we will be adding such as tablet

 Get to know android and research on developing application for our final project

Milestone 1

 2/24

 Obstacle avoidance works but needs attention

 Obstacle avoidance works with some bugs

 Obstacle avoidance works perfectly without any flaws

Goal 2

 1/27

 Arrange all components we get, work on programming, study real wheelchair (if we get any)

 Try to figure out all the components we need, work on programming,  try to hack real wheelchair (if we get any)

 Get all components and start programming, successfully hack real wheelchair (if we get any)

Goal 1

 1/20

 Looking for exact wheelchair, android tablet

 Hopefully find wheelchair to work on, find cheapest android tablet

Get wheelchair to Lab to work on, buy cheap and functioning android tablet. 


[Haymar-Phuong-Giang] – Final Project Proposal: [Motion Controlled RC Car]


Team Members:

  • Haymar Hliang
  • Phuong Nguyen
  • Giang Tran

Final Project Proposal

Our team is really optimistic about the motion controlled RC car. By the end of spring, we hope to have more than just a working car, but an actual marketable electronic toy. We feel that our project is can easily be marketed to consumers of all age group. We envision to have an aesthetically attractive glove that will help market the project. The glove will feature a re-wired circuit to cut down on wires and space. We also want to keep the glove’s weight to a minimum due to the fact of attaching a micro-controller(arduino), xbee, and a power source. We predict to have a couple more functioning RC car with different type of movements if our budget allows.

Team Structure

We are all seniors and expect to graduate sometime next year (spring, summer, or fall). We will be very busy with class, but we have devised a flexible schedule to work on the project:

  • we will meet/communicate daily (we will have at least 2-3 classes together)
  • we work as a team every friday
  • we will assign an individual with a small assignment(usually solving a problem we encounter)

Project Timeline

Phase Date Acceptable Good Excellent
Project Completion  5/4 Everything complete but have minor flaws(cosmetics) Everything works ready to sell Have more than 1 type of RC with motion control
Goal 6  
   
Goal 5  
   
Milestone 2  4/14  Finish rough draft  Finish report  & coding  No errors in code and no errors in essay
Goal 4  4/7  Finish code  Have excellent code with minimum bugs  Code works flawlessly
Goal 3  3/24  Start report (essay)  Have at least a rough draft  ready for final draft
Milestone 1  3/10  Survey consumers  Have actual stats from from 100 ppl  Gathered stats from different age group
Goal 2  2/25  Figure out speed control  Speed control is a function  Have a sensitive speed control code
Goal 1  2/11  Have working glove (can actually wear)  fully built glove with housing  finished glove with tucked wires and hidden micro controller
Steering wheel sensor- Final Project Proposal: Steering wheel sensor

As a team, replace the text in this template to write an initial writeup for your Final Project:

Team Members:

  • Mitchel DeWild
  • David Djobo
  • Kemal Ali

Final Project Proposal

Replace this text with a full description of what you imagine your final project at the end of Spring semester to be. Consider in your proposal that your project should be:

The final project will improve upon the reliability of the capacitance sensing by incorporating a program that continously calibrates the sensor to compensate for temperature and other physical changes in the environment.

 We will move all the wiring to a custom made printed circuit board and cover all circuitry for a cleaner look.

We will also attempt to add a camera that can sense a drivers head drooping when falling asleep.

We will integrate the seat shaker into the drivers seat.

Team Structure

      We expect each member of the team to commit at least 3hrs a week individually and will meet as a group for at least twice a week.

Project Timeline


Phase Date Acceptable Good Excellent
Project Completion  5-4 Working sensor tested in many climates. An efficient reliable product that work with a capacitor sensor and vibrator seat that goes along with the light effect
Be able to set off alarm with multiple sensing devices i.e. touch sensor and head motion detector.
Goal 6   Finish working on any change request(CR), perform additional, and final test, write up the final report, button up the final product.
Finish working on any change request(CR), perform additional, and final test, write up the final report, button up the final product. Finish working on any change request(CR), perform additional, and final test, write up the final report, button up the final product.
Goal 5   Full system operational check, start writing final report
 Full system operational check, start writing final report  Full system operational check, start writing final report
Milestone 2  4-14 All software  complete, report written, head motion optimal working All software  complete, report written, head motion optimal working All software  complete, report written, head motion optimal working
Goal 4  4-7   Install the speedometer   Operational head motion sensor working  Circuit board installed
Goal 3  3-24  Integrated vibrator into the seat  Install the speedometer  Operational head motion sensor working
Milestone 1  3-10  Calibration ready, warning light mounted  Wheel speed installed, accelerator pedal installed, horn loudness fixed  Software for head sensor installed
Goal 2  2-25 Have a working new speed sensor , operational test completed  installation of a camera with motion sensor capability  Have software for continues Calibration of the capacitor sensor
Goal 1  2-11  Replace 10k wheel speed sensor with an accelerator pedal  Replace the speed sensor wheel with reflective paint Start research on the head sensor(pure data)
Samov – Final Project Proposal: The Person Following Shopping Cart

Team Members:

  • Stephen Janzen
  • Mimosa Nguyen
  • Veena Shyam Krishna

Final Project Proposal

Our final project of this semester will be a shopping cart that follows a person around a store. This includes being able to sense the distance of the person it is following and stay within a following distance.

  • Useful for handicap or persons with disabilities, especially those in a wheelchair
  • Easy to use; just activate a switch to start the following
  • Navigates through aisles without running into obstacles
  • Follows the person a set distance away and not lose track of the person

Team Structure

Everyone will give more input toward the advancing of our goals.
As a team, we will work out problems and stay on the same track. We will plan to meet at least twice a week as a group for 4 hours. Individually, we expect at least an hour from everyone a week. More may need to be required to complete individual tasks assigned.

Project Timeline

Phase Date Acceptable Good Excellent
Project Completion 5/4 Project is complete, but still has bugs that need to be worked out. Final report written. Non-aesthetically appealing. Project is complete, but still has some minimal bugs. Final report written. Project is complete in entirely and works flawlessly, final report completed. Project cosmetically appealing.
Goal 6 4/20 Mostly completed project.
Final report beginning to be written.
Project is complete with the exception of aesthetics. Final report beginning to be written Project in near final shape. Final report beginning to be written.
Goal 5 4/13 Systems not cooperating with each other at all times, some bugs to work out. Systems mostly work together, some bugs to work out All systems working together.
Milestone 2 4/30 Shopping cart tries to turn and runs into the corner Shopping cart turns not so gracefully Shopping cart turns a zero point turn at corners to follow the person without hitting obstacles
Goal 4 3/9 Obstacle avoidance with minor bugs n/a Obstacle  avoidance mostly  implemented into design.
Goal 3 2/31 Turning with bugs Turning with minor bugs Turning fully implemented into design.
Milestone 1 2/24 Shopping cart shows signs of following, but not maintaining following Shopping cart follows a person in a straight line Shopping cart follows a person in a straight line and beginnings of turning implementation
Goal 2 2/10 Detection of person working Detection of person working, and resulting ‘then’ statement Detection of person, with subsequent code to stay within a range of that person.
Goal 1 1/27 Basic idea outlined with many components to work out Constructed plan, but with some unknowns left to figure out Fully constructed plan, including specific parts and example working applications
Goal 0 1/20 Determine possible sensor ideas Narrow sensor ideas down Determine exact sensor


The Mind Takers – Final Project Proposal: RC MindControl

Team Members:

  • Kalyn Kovac
  • Ifeanyi Bruno Umeadi
  • Eric Berman

Final Project Proposal

The RC MindControl final project should offer complete control of the RC Vehicle using brainwaves.  This would include forward, reverse, left, right, and speed control.  The big challenge for the final semester will be getting useful data from the Emotiv EPOC headset.   The RC MindControl final project will offer more precise control in two dimensions.  The first prototype only offered control in on dimension.  Another improvement over the prototypes is the speed control.  Prototype one went the stock speed of the RC vehicle, in prototype two we slowed down the RC vehicle. 

Team Structure

  • Each team member is responsible for working at least 2 – 4 hours individually each week on the project unless specified otherwise
  • There will also be  2 – 4 hour joint working sessions during the week to work on the project with as many team members as can make it
  • Every member is responsible for the team’s progress and success
  • Attend as many meetings as possible and try to be on time
    • Let team members know if you’ll be late or miss a meeting

Project Timeline

The biggest issue we are facing for the final project is processing data from the EPOC headset to meaningful data that can be processed by the arduino.  We will be working with Dr. Ying(?) to work on the signal processing of the brainwave data we are receiving from the headset.

Phase Date Acceptable Good Excellent
Project Completion  5/11 Have reliable two axis control  to demonstrate at  the senior open house. Have well tested two axis control, speed control, and signal processing on the arduino to demonstrate at senior open house. Implement a an algorithm similar to the “Wolpaw” research.
Milestone 1
 4/6  Have an idea about how to process the EPOC signals on the arduino without a going through a PC  Have hardware and software to close to being able to process data directly from the EPOC on the arduino  Have the arduino do all the receiving and processing of the EPOC data.
Goal 2  2/24  Be able to process signals from the Epoc headset with a PC.  Be able to process signals from the Epoc headset on a PC and have at least one axis control using the signals.   Be able to process signals from the Epoc headset on a PC and have at least two axis control using the signals.
Goal 1  1/27  Look into adding a second arduino with bluetooth or wifi as a replacement for the RC vehicle radio control.  Order/have bluetooth or wifi components to connect to the arduino  Have the RC vehicle use bluetooth or wifi instead of the built in RC control.
[Team Alpha] – Final Project Proposal: [The Smart Mailbox]

Team Members:

  • Said
  • Festus
  • Kathy
  • Stanley

 

Final Project Proposal

The smart mailbox should get more functions by the end of next Spring, that include sending high resolutions JPG images from inside the mailbox to the user’s e-mail. It is going to abandon the arduino units to more efficient and smaller in size and power consumption alternative (Microcontrollers is  expected to be the substitute). It will also go into the field and the team will imagine every possible situation and scenario that can happen while the project is in use, so that no surprises happen under special conditions.
The project will take further approach to the real market by taking into considerations the cosmetic issues and best ways to make it come in an attractive packaging and design. Safety issues will be taken into consideration during all design and testing processes and any change that is needed will be implemented.

The main goals:

  • Make the device do all functions including sending high resolution JPG image from inside the maibox to the user’s e-mail
  • Make the project more energy efficient.
  • Make the mailbox device comes in a small and easy to install size.

Team Structure

  • Individually: as many as each team member’s schedule allows ( minimum 2 hours)
  • Group: 2x a week, 2 hour/session.

Project Timeline

Phase

Date

Acceptable

Good

Excellent

Project Completion

 April 25

The whole system works under many conditions and many possibilities are took into consideration. The project comes in a small and attractive shape

Everything is working as planned, more than one design are available and all works fine

Everything is working as planned and the multiple designs are tested by real users and they loved it.

Goal 6

 4/2

Assembling the whole project in a small and marketable slim design

The assembly is done and tests takes place

Assembly is done, tests took place, and all is working great.

Goal 5

3 /23

Doing designs for the whole project to be put in a whole smaller size

 Few designs are done

 Few designs are done and investigated well.

Milestone 2

3/16

Testing for the new circuits under the new design are done

testing is completed. Minor issues presented.

 testing is completed. All is ok.

Goal 4

 2/24

 The new circuits for the new devices are designed

 The new circuits are designed and assembled

 The new circuits are working and doing all functions without problems

Goal 3

 2/17

Considering all possible alternatives for the arduino units

Having all information about the practical alternatives and how they can be implemented

 Picking one final choice and start working on it.

Milestone 1

 2/10

  The new functions are working

The new functions works well under many conditions

The new functions are fast and reliable

Goal 2

2/3

  Complete consideration and planning for how to deal with the many use of the devices in one day and resetting it.

 Having clear idea about all needed devices and parts to do such functionality

 Working already on assembling all new parts and testing the fucntions

Goal 1

1/27

Have an outline of the final product.

Have an outline of the final product, with a list of all needed extra parts

Have  algorithms of codes ready


[Team Omega - Final Project Proposal: [Washing Machine Auto-Balancer]

Team Members:

    • James Davis
    • Polina Osipova
    • Ravi Wijesekera

 

Final Project Proposal

Our device will automatically correct balance offsets that are inherent in washing machines which are filled with clothes. The balancing aspect will come into effect during the machine’s spin cycle. Opposing to our prototype, we will  move away from Arduino to a smaller microcontroller and will implement the circuit on a real washing machine with added ballasts. The market for this type of idea includes all appliance purchasing consumers. Specifically, this would likely be an option on mid- to high-end machines as the addition of these parts increases the cost to build.

The main goals:

  • Reach the  minimum time frame for the balancing process.
  • Aim to produce at a reasonable cost.
  • Make applicable to different washing machines.

Team Structure

  • Individually: as many as each team member’s schedule allows ( min 2)
  • Group: 2x a week, 2 hour/session.

Project Timeline

Water is an issue we anticipate might challenge us later on. Initially, the challenge will be keeping the water in the ballasts while in operation. This is a challenge since we’ll be employing a passive system of water retainment. Our current approach will be to use channels to divide the water into manageable portions. Subsequently, once the water is kept in place, the next problem will be removal. At present, the idea is to slow the speed of the machine to a point that facilitates a passive dumping of water from the aforementioned channels.

 

Phase Date Acceptable Good Excellent
Project Completion  April 25 The system automatically corrects balance offsets, some instability is present. Minor cosmetic issues. The final report/documentation is completed. Everything is working as planned (the system automatically corrects balance offsets). Most significant testings are done. The final report/documentation is completed. Everything is working as planned (the system automatically corrects balance offsets). All testings are done, no defects discovered. The code is optimized and looks neat. The final report/documentation is completed.
Goal 6  4/2 The system is mostly working.  The system is working, mostly stable. The system is working properly, no instability or defects. Working on the documentation.
Goal 5 3 /23 Workaround is found and the main test passed.  Minor issues were fixed, less significant tests in consideration.  Less significant tests are completed.
Milestone 2 3/16 Main test is completed. Unexpected issue discovered – workaround in consideration. Main test is completed. Minor issues presented.  Main test is completed. The above-mentioned water issue is not presented.
Goal 4  2/24  The circuit is partially moved onto a washing machine.  The circuit is moved onto a washing machine, ballasts added.  Integrate all the components into one final system.
Goal 3  2/17 The workaround is found and applied.  Parts ordered.  The circuit is prepared to be moved onto a real washing machine. Parts ordered.  Get a washing machine and ballasts.
Milestone 1  2/10   The collected readings might be slightly different from what we expected. Workaround yet to be found.  The collected readings might be slightly different from what we expected. Workaround is found.  The collected readings are expected; the circuit is ready to be moved onto a real washing machine
Goal 2 2/3   Few possible alternatives for arduino, but best one not picked.  Research for an alternative microcontroller is completed, but not ordered yet.  An alternative microcontroller is found and it successfully replaces arduino.
Goal 1 1/27 Have an outline of the final product. Have an outline of the final product, excluding potentially needed extra-parts ( still have them listed). Get a pictorial description of the final product . All the potential extra-parts considered.
[Team ACRA] – Final Project Proposal: [MyHomeAudio]

Team Members:

  • Cameron Porter
  • Ryan Brown
  • Ahmed Abdelaziz
  • Andrew Juby

Final Project Proposal

MyHomeAudio final project should consist of the following:

  • Sensor Nodes: 2 or more units.
    • The units will be fully enclosed in a chassis, the dimension will roughly be 3.5” x 3.5” x 1.75” per unit. The unit will be mountable so it could be mounted in a wall or a ceiling
    • The power supply will be an external brick power source that will be small enough in dimension where it can be mounted beside or on top of the sensor node box.
    • A fully functional Java application that will be able to identify clients nearby
  • Server Software:
    • This piece of software the brains of the project or the main software component is intended to be installed in any PC in the home network that will be designated as the MHA server. A media Center PC will be the optimal host, since it has the media/music library for a home
  • Client Application:
    • A fully functional Android based client application that will reside on a mobile device or a tablet pc. This will allow the client to be detected and located , also will give control functions to the user.

Team Structure

Replace this text by updating your answers from earlier in the semester to the following question: As a team, what do you expect from each other? In answering, consider:

  • Ahmed Abdelaziz, write up progress reports, final reports, responsible for all presentation and the business plan (2 – 4 hours per week)
  • Cameron Porter: (Chief Coding Officer) Implementation of the design and managing the coding team( 2 – 4 hours per week)
  • Ryan Brown: Coding and implementation (server side) ( 2 – 4 hours per week)
  • Andrew Juby: Coding and implementation (client side) ( 2 – 4 hours per week)
  • Team: All members contribute to the design aspect of the project. The team plans on meeting once a week for about 1 – 2 hours to manage the progress and modify design as needed.

Project Timeline

Phase

Date

Acceptable

Good

Excellent

Project Completion

 5/11/2011

Complete Product that works for 2+ nodes and offers support for multiuser.

Complete Product that works for multiple nodes and addresses issues such as multi-user conflict and offers decent precision of identifying the active node

Complete Product with full support for multiple users and precise accuracy for active node, expanded set of features and polished user interface on client application.

Goal 7

 4/27/2011

Final Report

Final Report with a usability study

Final Report with a usability study and a full business / marketing plan.

Goal 6

 4/13/2011

No added features

 Expanded Features

 Full set of features that allows the client to have full control and customization of the MHA network

Goal 5

 3/23/2011

Reduced lag transition and somewhat accurate start and end point of streams (within 5 seconds!)

 No lag and accurate start and end points of stream when switching active nodes.

Seamless and gradual Transition of music streams between different nodes

Goal 4

 3/2/2011

Multi-user support with basic conflict resolution algorithm

 Multi-user support with enhanced conflict resolution

 Multi-user support with enhanced conflict resolution set and allowing user to dynamically set up new rule sets

Goal 3

 2/17/2011

 Using simple one dimensional distance to determine the active node

 Using distance as well as predefined rules to determine active node

 Using triangulation or some other form of detecting the closest node within the same room for complete accuracy.

Goal 2

 2/3/2011

Working prototype for 1 user – not fully completed

Working prototype for  a single user 1 with limited functionalities

 Fully working prototype for a single user a time with full control features.

Goal 1

 1/27/2011

Utilizing Same feature set as PT II

Expand on design of feature set from PTII.

Expand on design o feature set from PTII and allocate a more cost effective hardware platform for the nodes (that will accommodate written modules)

 

 

Team Name – Final Project Proposal: DoorTextChecker


Team Members:

  • Todd Thimmesch
  • Jordan Castillo
  • Matt Price

Final Project Proposal

The overall goal of our project is to make and integrated security system of sorts that can check if windows or doors are open and in the case of the doors be able to open and close them.  Also we would like to be able to check if a device is on or off and shut it off or turn it on as needed.  We would like to be able to have these components in fairly clean looking packages where someone would not mind having them in their home. As far as making it easy to use we would like to have the server run off of an arduino that can take commands from a phone or computer and talk to the other devices via xbees. The point of running the server off of an arduino so that a user doesn’t have to have their computer on at all times. This is an expansion because it moves on from our simple idea of controlling different types of doors by controlling multiple items at the same time and doing it through a simple interface of an app or computer that is more user friendly than memorizing text messages messages as we have done before to control our items.

The main goals are:

  • Make it user friendly and every device is in a clean neat package.
  • Have an android app that can communicate with a server.
  • The server should be on an arduino for the sake of not needing to have a computer on at all times and making communication between xbees simple.
  • Be able to control and manage multiple items at the same time.

Team Structure

As a team we expect each member to spend roughly 4-8 hours a week working on the project. Then as a team we will have meetings once a week for roughly 1 to 3 hours to make sure everything is progressing as it should.

Project Timeline

Phase Date Acceptable Good Excellent
Project Completion  4/27 A paper that is better in theory than what a 6th grader could write An easy to read paper with most of the theory and how it was done written A paper that explains how everything was done and the theory behind it explaining how everything was set up and executed and how it went.
Goal 6  4/20 Android app that can send and recieve messages from server occasionally  Android app that can send and recieve commands from a server reliably that has some sort of security  Fully integrated app that can communicate with a server and has all the bells and whistles of a snappy gui and notifications
Goal 5  4/20 Have a server that can communicate with multiple xbees  Have a server that can receive notifications from an outside program and go back and forth  A multithreaded server that has some sort of security and and can handle multiple requests at once. Also this servo needs to be on an arduino taking dependancy off of a computer
Milestone 2  3/23 Have the two prototypes working together  Have the two prototypes working in fairly clean presentable units.  Have the prototypes in packaging that is user friendly packaging that is intuitive to use. Also to have started work on the final paper
Goal 4  3/16  Have xbee communication between one device.  Have xbee comunication between multiple devices using point to point.  Have xbee communication between every accessory and have a plan devised to link it with the server.
Goal 3  3/9  Have a unit that can monitor an appliance being on and off.  Have the device work as simply as being inbetween the appliance and the outlet.  Have a fool proof clean design that can be used to monitor any device plugged into a 120w outlet.
Milestone 1  2/24  Have the prototypes made.  Have the prototypes improved to what they should fully do.  Have the prototypes and the additional units all working to start working them into the network
Goal 2  2/17  Have a unit that can monitor if a window is opened  Have a unit that can monitor a a widow in a manner that isn’t obvious  Use a small cost chip that can monitor a window cheaply and in a unobvious way, example a random box on a window.
Goal 1  2/10  Have the garage door unit in a clean package to monitor a door  The garage door unit can open and close a garage door also.  Have the garage door unit open and close a garage door with no hassle and easy to set up
[Team GTLE] – Final Project Proposal: [RF signal enhancer]


Team Members:

  • Bart Voegeli
  • Eric Nyaga
  • Guner Yilmaz
  • Shaun Golden

Final Project Proposal

Team GTLE has constructed a system that will allow a user to non-invasively measure different voltages for a standard street lamp. The design currently in place works with a 120V AC system, which has caused our team to rethink some of our earlier expectations. We wanted to be able to use the system on anywhere from a 120V AC to a 480V AC input. However, such a power supply would have to be custom built in order to handle a 480V input. Most power supplies will handle between a 120V and a 277V input, in this case, we should be able to implement our design within a commercial structure. Right now, our design works with a light that has a ballast attached to it. Taking the reading from the input power into the ballast, we are able to get three different outputs that will allow us to tell remotely whether the light is working, the ballast is out, or the light bulb itself is out.

The second phase of our project is where the remote monitoring comes in. Using a signal repeater chip and an RF signal, we hope to allow maintenance crews in various commercial and industrial facilities to monitor light fixtures from a single location. This prevents having to check the lights each night and also allow the user to directly tell which component of the light is not working. The outputs we obtain from our sensor will be recorded and sent back to a main location. If a fault comes through on a light (i.e. has a current reading that indicates open circuit to indicate that the bulb is out or no current reading to indicate the ballast is out), the user will be able to tell directly where the light is and what exactly is wrong with it, making replacement and maintenance much simpler.

Our design will be able t fit in any enclosing that is greater than or equal to four inches in depth, four inches in length and four inches in width. The only two parts of the system can be fitted onto the fixture without having to ever move it or bring it down. One can simply turn off the power and disconnect the power input cable and the ground from the fixture. Our sensor simply slips around the power in, and our power supply can be directly taken from the input to the fixture (this sounds complicated, but anyone who has experience maintaining a light fixture will be able to apply it). This concept of remote fixture monitoring is already in place, but through a wired system. The install time and cost is overwhelming in cases, and this makes a wireless system almost necessary.

Team Structure

Our team has been good so far about being open and putting in their hours. On average, we believe each team member should spend about three hours (at leas) on this project in a given week. This allows different inputs on ideas and helps take care of one person doing everything. As a team, we expect to spend about five hours together weekly in order to share ideas and implement which one we think is best.

Project Timeline

Given our current status, the following table will be a timeline for our success. These dates are subject to change depending on the difficulty of the phase.

Phase Date Acceptable Good Excellent
Project Completion  4/15     When we apply power to our system, we should get a signal that is bounced from the second repeater chip to our third. This signal should be one of three specific values in order to determine what, if anything, is wrong.
Goal 6  3/15 Get our third repeater chip to read a signal.  Get our third repeater chip to read the signal from the second and get actual values.  Get our third repeater chip to read the signal from the second and get the values given by the first.
Goal 5  2/30 Get our third repeater chip.  Get a third repeater chip with the ability to read our second chip.  Get a third repeater chip that can be programmed to only see the second repeater chip, and make sure it does see it.
Milestone 2 2/14  Get a signal from our first repeater chip to our second.  Get a consistent signal with measurable values from the first repeater chip to the second.  Get a consistent signal that correlates with the signal from the arduino in order to make sure the values are being passed along.
Goal 4  1/30  Get our second repeater chip.  Get the second repeater chip powered up.  Get the second repeater chip and make sure the power is consistent and clean.
Goal 3  1/23  Make sure the repeater chip is getting a signal from the arduino.  Make sure the repeater chip is getting a signal from the arduino and getting an output.  Make sure the repeater chip is getting a signal from the arduino and the output is concurrent with what the arduino is outputting.
Milestone 1  1/1  Have the repeater chip connected to the system.  Have the repeater chip connected to the system, and make sure it is getting power and coming on.  Get the repeater chip hooked up and make sure a steady voltage is being inputted and the chip is turning on and not overheating.
Goal 2  12/16  Have ideas of the code we are going to use.  Have specific examples that are relatively close to our project as far as what the code needs to say.  Have a code chosen and we will know exactly what it does and what we want it to do. There of course needs to be room for changes to the code, should we need to make them.
Goal 1  12/9  Have ideas of which signal chip to use.  Have these chips narrowed down to 3 specific choices, all having schematics to hook up to our current system.  We will know exactly which chip we are going to implement and have schematics for the connection to our system.