Archive for the 'II' Category
Progress Report II Prototype I Assignment

Second Progress Reports for Prototype I go here.

Team 9 – Progress Report II for Prototype I: Remote Piano Piano Controller

Goals for the week:

Assemble arduino, accelerometer, and some LEDs sop that we can explore the parameters of the accelerometer and programming of the arduino. 

Discuss the project with the client to get feedback.

Meeting times/dates

Tuesday mornings at 9:00 and Tuesday evenings at 7:00.

Individual Hours:

Tom – 4 hours

Atul – 4 hours

James - 4 hours

What we did:

We connected the arduino with accelerometer and an LED, and took some preliminary measurements to explore the parameters of the accelerometer. With the accelerometer resting on my leg, the output was 300 ‘units’, with my leg raised 3 inches, the output was 320 units. This gives us 20 increments to work with between our up and down positions. Much better than an on off switch (solenoid). Explored programming of the arduino in controlling the output parameters. Spoke with the client: The solenoid he is currently using is noisy, especially on the up stroke. The solenoid goes up faster than the piano pedal causing pedal noise. He has also had issues with heat. The speed of the motor is definitlely a priority.

What we didn’t do:

Speak with other piano players, get measurements of piano pedal tensions.

Where we are stuck:

Have not yet started on cam or cam/pushrod design.

Notes/Misc:

Infinite Loop – Progress Report II for Prototype I: Hazardous Weather Warning System

Goals for the week:

  • Decide the required materials
  • Buy required LEDs and Switches
  • Do research how to receive  weather signal
  • Do research  how to send wireless signal to turn  LED on/off
  • Have  meetings on Monday and Tuesday

Meeting times/dates

  • Monday 7:00pm – 9: 00pm
  • Tuesday 7:00pm – 9: 00pm
  • Saturday 9:00am – 11:00am (as required)

Individual Hours:

Caleb:  2 hours

Debritu:  2 hours

Edwin:  2 hours

Jeff:  2 hours

What we did:

We are a little bit behind other teams for we changed our first project idea and picked a new project idea. We had a meeting with Tara last week to discuss what the project should look like in order to benefit the CPRF community more. We implemented circuit on Arduino to figure out what possible colors LED would produce on Arduino. So far our trial confirmed that we can get seven different colors blue, green, red, clear, cyan, purple, and yellow from standard RGB LED. We have also researched the type of materials such as LED, switch and controller that we should be using for the project and posted on the group forum.

What we didn’t do:

We have not experimented how to receive and send the weather data

Team 12 – Progress Report II for Prototype I: Home Automation Framework

Goals for the week:

Ask concept test questions to CPRF residents. This way, we can get some feedback on their specific needs and price points they’ll be willing to pay.

Dissect remote control/outlet and see if we can control it via rasperri pi pins

Meeting times/dates

Thursday 7:30pm

Sunday 4pm

Individual Hours:

Jose/Mike: CPRF concept test, 2 hours

Mike: questionnaire development: 1 hour

Trey:                      

Meeting with John, 20 min

Toying with remote outlet: 3 hours

Nena/Olivia/Jose/Trey:

Toying with remote outlet: 3 hours more

What we did:

We did the CPRF Concept Test. It went really well, we got some good ideas (like controlling blinds), and price point ideas ($50 to $100) for a base unit.

We played with a remote control to turn outlets on and off. This was an existing product that already fulfilled one of the functionalities of the project, so we wanted to see how it works.

We took it apart, and activated the inputs in the circuit manually, and we got a very good understanding of it, and we were able to discover its circuits voltages and inputs.

We figured that we could plug it in to the raspberry pi through some kind of interface we would build ourselves.

We managed to solder some wires into it, so we could connect it to the Raspberry Pi’s General IO pins.

What we didn’t do:

We didn’t actually have time to program the raspberry pi to activate pins on the remote. However, it does seem like a simple thing we can accomplish next week.

Where we are stuck:

Everything is going smoothly. We are thinking of getting some tiny microchips to replicate the controllers behavior, but that’s after we get the controller we dissected working with the Pi

Notes/Misc:

Previous version of the report got screwed up because I tried using a cheap app on my iPad to post. Lessons learned! -JC

Pictures/Evidence:

Marz – Progress Report II for Prototype I: Campus App

Goals for the week:

  • Get a basic menu interface up
  • Try out geolocation for pinpointing location on map
  • Survey students
  • Begin work on the android app, have it load the web page

Meeting times/dates

Tuesday 7:30-8:00

Individual Hours:

Zane Sumpter – 2 hours, created an index page to display the main menu, moved map to a separate page and added geolocation to automatically detect a users location

Mason McCanless – 4 hours, created survey, passed it out in classes, tallied results. Also created a Google Doc survey (question 5 is different- better worded to get better feedback) and got people to fill out the survey online via facebook and email.

What we did:

Got a basic menu up using HTML and CSS to display buttons that should tile up correctly on a mobile phone screen. Use geolocation to detect a users GPS coordinates at a 5 second interval and place a marker on the map at that location. Also created a Back to Menu link at the top of the map.

Surveyed students with initial interest questions. Will upload the excel document Monday night.

                           

What we didn’t do:

Need to get Android app up and working.

Shade Technologies – Progress Report II for Prototype I: Motorized Wheelchair Canopy

Goals for the Week

  • Shape metal rods into metal arcs for structure of motorized wheelchair canopy
  • Purchase and create prototype base (1 1/2″ x 2 3/4″ x 20″ wood board,  1 2 3/4″x 3″ x 1/2″ wood block, 1 5/16″ screw eyes)
  • Program Arduino Uno with Adafruit Motor Shield to rotate metal arc 1/2 revolution forward and backward with button
  • Complete Concept Test with Mabel Flores

Meeting Times/Dates

  • 10:30AM-12:00PM, Sunday in EECS Sr Design Lab
  • 6:30PM-9:00PM, Monday in EECS Sr Design Lab

Individual Hours

  • Jenice Duong and Taylor Russell will work on attaching Adafruit Motor Shield to Arduino Uno and applying bi-directional motor code, 4 hours
  • Albert Ogenche and Shital Shrestha will work on shaping metal conduit into metal arcs and finding appropriate electrical attachments to motor, 4 hours

What We Did

  • Shaped metal rods into metal arcs for structure of motorized wheelchair canopy
  • Purchased and created prototype base (1 1/2″ x 2 3/4″ x 20″ wood board,  1 2 3/4″x 3″ x 1/2″ wood block, 1 5/16″ screw eyes)
  • Programmed Arduino Uno with Adafruit Motor Shield to rotate metal arc 1/2 revolution forward and backward with button
  • Completed Concept Test with Mabel Flores

What We Did Not Do

  • N/A

Where We are Stuck

  1. How could we add our Entrepreneur to our group on our Team #4 Forum?
  2. Could we possibly have Wallace Hall opened on Sundays for easy access to EECS Sr Design Lab?
  3. Do we have wire sockets for unused pins on Arduino Uno?
Group 3 – Progress Report II for Prototype I

Goals for the week:

  • Find out if project is viable (done)
  • Get Arduino working on Windows 8 (done)
  • Play with accelerometer
  • Explore Options for filtering accerometer.
  • Research H-Bridge for motor going 2 directions
  • Pneumatics vs gravity or compressed air.
  • Come up with new ideas

Meeting times/dates

  • Tuesday@6:00pm

Individual Hours:

  • All students put in 1-2 hours on the project.

What we did:

  • Merl : Determined to not be a good option by talking with CPRF residents; Had idea to open and close a window automatically.
  • Todd: Got arduino working on Windows 8; Started researching how to filter accelerometer data: http://levonp.blogspot.com/2010/10/how-to-filter-accelerometer-data-from.html, but no longer necessary; Has new idea to do battery monitor and distance calculator.
  • Saed: Researching new ideas; Had idea to create a wind turbine to charge an extra battery. (Maybe add solar power as well)
  • Mido: Researching new ideas; Had idea for a voice controlled wheelchair.

 

What we didn’t do:

We were unable to actually work on the project because the project selected is not going to be something they will really want.

Where we are stuck:

Stuck at picking a new idea.  We will be meeting before class tomorrow and hopefully will have something set in stone by our group spot time.

Notes/Misc:

Out of Time – Progress Report II for Prototype I: Hot/Cold Pad

Goals for the week:

  • Finish sketch outline of prototype.
  • Order last of needed parts.
  • Get psuedocode and actual code written for arduino.
  • Check efficiency/power usage of peltier.

Meeting times/dates

Thursday 7:00, Monday 7:00

Individual Hours:

Joel: 2-3 hours (Arduino code research/psuedocode)

Ralph: 1-2 hours (Construction concepts/part suppliers)

Hammad: 1-2 hours ( Helping in Construction concepts)

Samuel:

What we did:

Researched input/output capabilities of peltiers.

Made decisions on how to keep hot side of peltier cool to achieve best efficiency.

Decided to use a Corsair CPU cooler for the hot side of the peltier. Through research we found out that if the peltier gets over a certain temp it will basically loose all usefulness, and that the best way to keep that from happening is use a self contained reliable unit.

Found a cheap water pump that has a low enough flow rate to be adapted with the water pad we found. The pad we are going to use for the first tests, and possibly adapt to full use, is a water circulation pad used by veterinary facilities to raise animal body temperatures. The given rates that the pad is designed for is what we based our decision on.

We are going to make a copper mount that will circulate the water across the top of the peltiers cold side.

Reviewed concept test results to adjust for what the clients actually wanted.

 

What we didn’t do:

  • Finish arduino code.
  • Actually fabricate the copper mount.

Where we are stuck:

Still having trouble arranging times for all of us to meet at once.

Notes/Misc:

Specs and sources posted in forum (here).

Team#5 – Progress Report II for Prototype I: Rescue Lifter

Goals for the week:

  • Determine why the roomba is not working.
  • Get the roomba working if possible.
  • Get a thermal sensor working with the arduino.
  • Get rough code written to simulate moving the robot on a pre programmed path.
  • Get rough code written to simulate the infrared sensor detecting an obstacle.
  • Work on code to simulate routing the robot around an obstacle.
  • Research how to control a roomba using the serial interface.
  • Do more work writing code for the arduino.

Meeting times/dates

  • We postponed our scheduled meetings.
  • We had one unscheduled meeting Monday afternoon for about 45 minutes to update the team on what we were working on and discuss where we are stuck. Not all team members were able to attend this meeting.

Individual Hours:

Chris –  ~8 hours. Diagnose roomba problem, order battery. Built thermal sensor and wrote code that tracks heat source (person). 

Waleed –

Richard – about 8 hours getting an arduino and having Tom help me hook up two motors and an infrared sensor and writing some basic code for the motors and sensor and working on code to simulate moving the robot on a programmed path, detecting an obstacle and routing the robot around an obstacle.

Kiet – figuring out how to map the house and make the roomba follow the path to get to the room.  But it seems arduino can’t store a map, or make it follow a path.  Still researching what can do that and able to connect to the roomba.

What we did:

  • Determined that the roomba battery was bad.
  • Ordered a replacement battery for the roomba on ebay. It should be here by Thursday.
  • Got the thermal sensor to work with the arduino board and did some testing to see how it works.
  • Put the thermal sensor on a motor to allow it to scan 180 degrees.
  • Completed some rough code to simulate moving the robot on a programmed path.
  • Completed some rough code to simulate detecting an obstacle and running alternate code to move the robot around the obstacle.

What we didn’t do:

  • Get the roomba working. We may have a temporary fix until the replacement battery gets here.
  • We did not research how to control the roomba using the serial port.
  • We did not figure out how to determine the direction to send the robot from the thermal sensor.

Where we are stuck:

  • We need to figure out how to control the roomba.
  • We need to figure out how to make the obstacle avoidance programming work.
  • We need to figure out how to use the thermal sensor to determine a direction to send the robot.
  • We need to figure out how to connect the arduino to the serial input of the roomba.

Notes/Misc:

7. Team Bravo Squad – Progress Report II for Prototype I: Emergency GPS Locator

Goals for the week:

  • Get concept test feedback posted
  • Manage to get basic functionality out of GPS module
  • Working with a switch

Meeting times/dates

Monday 7pm

Individual Hours:

  • Ryan — Arduino and GPS work
  • Sydney & Bryan — Conducted concept test

What we did:

  • Ryan — Successfully recorded a GPS lock, and read correct values from Serial I/P Monitor
  • Ryan — Semi-successful switch functions
  • Bryan & Sydney — Got positive feedback from concept test

What we didn’t do:

  •  Haven’t yet posted up concept test results

Where we are stuck:

  •  Not tested concretely yet, but GPS lock-on latency is too long (up to 30 minutes or even hours)

Notes/Misc: