Archive for the 'I' Category
Team 9 – Progress Report I for Prototype II: Remote Piano Pedal

Goals for the week:

Design and build frame to hold motor and pot in place so that gears and cam may be designed.

Get informed input on cam design.

Meeting times/dates

Friday 12:30p, Tuesday 9:00a and 7:00p

Individual Hours:

Tom 6 hours design frame and build a pattern. Find and prepare material for frame.

What we did:

James and Tom met on Friday to speak with cam designer. He was unavailable. Made three sketches and a couple of ‘blueprints’ for the frame design, built one out of cardboard and one out of sheetmetal to serve as a pattern. Found a metal plate that can be formed into a frame.

What we didn’t do:

Plate needs to be sheared, drilled and bent. Cam needs to be designed and built.

Where we are stuck:

We need to get access to the metal shop to have our frame pattern built.

Notes/Misc:

[Three Musketteers] – Progress Report I for Prototype II: [LaserTag]

Goals for the week:

This week we were wanting to get parts ordered and begin hacking together some basic code.

Meeting times/dates

Met Friday afternoon for a few hours.

Individual Hours:

James: 2-3 hours on what the best course of action to take as far as WiFi. 

What we did:

James ordered parts. Started learning the 3D printer that may be used to build a triggering mechanism. Andrew began looking at what kind of code we would need in order to create an interface for the Arduino. Vinosha began familiarizing herself with arduino code.


What we didn’t do:

N/A

Where we are stuck:

Waiting for parts to arrive.

Notes/Misc:

Group 3 – Progress Report I for Prototype II: Battery Range Meter

Goals for the week:

Meeting times/dates

  • Monday @7:00pm

What we did:

We ordered the AttoPilot Voltage and Current Sense Breakout.  We were able to reconnect the circuit and program it in the lab.  The voltmeter is working correctly but we are still unable to get a current reading.  We plan on getting with Tom for help and to see if we are missing something.

What we didn’t do:

We need to get a SD card for the data-logger so we can test it and we have not ordered a GPS yet.  They are shields and we have to make sure we have enough ports to connect it along with our other components.

Where we are stuck:

We really need to figure out why we can’t get a current reading.

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

Goals for the week:

  • Iron out last kinks in GPS module of project
  • Wait for parts to come in
  • Make sure new parts work

Meeting times/dates

  • Monday 7pm

Individual Hours:

  • Tanner – 3 hours

What we did:

  • Tested new antenna, GPS now cold-start fixes in ~30 seconds as advertised
  • Verfied that the GSM at least turns on

     

What we didn’t do:

  • Haven’t yet really programmed GSM board yet

Where we are stuck:

  • Might need a SIM card specifically for project; not sure what kinds of cheap prepaid options there are.

Notes/Misc:

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

Goals for the Week

  • Desolder and resolder 3-position switch with appropriate input and ground wires
  • Mount potentiometer onto Prototype I base
  • Program 3-position switch to control extension and retraction of metal arc
  • Program potentiometer to control motor speed and extension and retraction limits of metal arc

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 performed various housekeeping duties, 3 hours
    • Soldered appropriate input and ground wires to 3-position switch
    • Posted updated meeting minutes up until 5-NOV-2012
    • Wrote Progress Report I for Prototype II
  • Albert Ogenche and Shital Shrestha mounted potentiometer onto Prototype I base, 3 hours
  • Taylor Russell programmed 3-position switch and potentiometer to control extension and retraction of metal arc, 3 hours

What We Did

  • Soldered appropriate input and ground wires to 3-position switch
  • Mounted potentiometer onto Prototype I base
  • Programmed 3-position switch to control extension and retraction of metal arc
  • Programmed potentiometer to control extension and retraction limits of metal arc

What We Did Not Do

  • Program potentiometer to control motor speed

Where We Are Stuck

  • N/A
Out of Time- Progress Report I for Prototype II: Hot/Cold Pad

Goals for the week:

  • Get a power supply circuit drawn up
  • Continue arduino code
  • Figure out PWM problem
  • Fabricate water block for the peltier

Meeting times/dates

Tuesday – 7:00

Thursday – 7:00

Monday – 7:00

Individual Hours:

Ralph – 3 hrs (Power supply development + project vision quest)

Joel – 3 hrs (Arduino Code)

What we did:

We started this week by determining that we couldn’t use the PWM on the arduino to control the peltier unit. So we did some research and found a very small circuit with a cap to eliminate the curve. We also did start some arduino programming to control the relay that will control the power to the peltier.  We have also written code that uses a pot to control the output of a PWM pin that will go to our curve destroyer circuit.

What we didn’t do:

  • Finish arduino program
  • Fabricate water block

Where we are stuck:

Deciding the design for the water block.

Notes/Misc:

http://provideyourown.com/2011/analogwrite-convert-pwm-to-voltage/

http://electronics.stackexchange.com/questions/28634/how-to-drive-a-peltier-element

Marz – Progress Report I for Prototype II: Campus App

Goals for the week:

Complete login/registration system and add building markers and information windows to map page that open up when clicked.

Meeting times/dates

Tuesday, 7:30pm

Individual Hours:

Zane Sumpter – 6 hours, Creating framework and functionality of login/registration system. Added dynamic building location/information to map page.

Mason McCanless – 4 hours. Created rough sketches for the “Classifieds” module and collected information on campus buildings including latitude, longitude, and links to descriptions on WSU’s website.

What we did:

Setup a login and registration framework. Trying to access any of the modules or menu will redirect to the login page. A user can register by clicking “Create an Account” on the login page. The registration page will ask for a valid email, and a password. All input is checked, sanitized, and verified before entered in the database. A confirmation email is sent to the email address with a confirmation link. The confirmation link just contains a 20 character code in the URL that maps to a user account in the database.

Registration page

The login page asks for an email address and password to login. The user cannot login without first confirming their email address by clicking the link. Once the link is clicked, the account can be logged into. If the email is never received, or is somehow lost, a user is prompted with an option to resend the confirmation email upon attempting to login. Upon entering a valid email/password combination, an encrypted cookie is stored on the browser and the user is redirected to the Campus App menu. The system allows for multiple login sessions at the same time, so the user can be both logged in on a computer and on their phone. The stored cookie is the user id in the database appended with a  randomly generated 32 character string. The contents are then hashed, and that hash is appended to the contents of the cookie. The entire cookie is then encrypted with a 256 bit key. This ensures that a cookie cannot be spoofed, nor modified without being detected by the server.

Login page

The user can request a new confirmation email to be sent.

Resend email confirmation page

Building locations, names, and descriptions are stored in the database for each school and automatically loaded into the map. This will allow a single page to concurrently server multiple schools by dynamically loading the correct information as determined by the id in the url.

Map markers to indicate buildings

Clicking the marker on a building will bring up an info window containing the name and description of the building stored in the database. Any content can be added here, including html.

Building info window on map

What we didn’t do:

Need to create a Forgot Password page and a page to change your password. Also need to create an intermediate menu for the Map page to choose what kind of Map to load: Plain Map, Building Information Map, Parking Lot Map, etc.

Need to get latitude and longitude for remaining buildings.

Lucky 13 – Progress Report I for Prototype II: Battery Assisted Grabber

Goals for the week:

We plan on building a “mini” version of our grabber to prepare it for telescoping abilities. It will shorten the grabber rod down to what’s only needed for the clamp. Also, we are going to come up with ways that we could implement the telescoping feature on the grabber, and are going to acquire pressure sensors for further automation of the clamp.

Meeting times/dates

(10/30) Tuesday 5:30-9:00 -Spent time in the senior design lab continuing fabrication of the mini grabber design and brainstormed telescoping solutions.

Individual Hours:

(11/2) Friday – We weren’t able to meet up as a group, and instead worked individually on our assigned tasks (Jeremy and Chuck: fabrication and electronic implementation and Clayton and Justin: pressure sensor and touch screen implementation).

What we did:

We fabricated new parts to act as a clamp, rod, and linear actuator out of aluminum and PVC pipe. We came up with an idea of how to telescope our grabber. The most prominent idea thus far is a partially flexible, plastic rod that will fit inside our PVC pipe rod but will be able to be coiled around a pulley to contract the grabber, and then will be strong enough to push our device’s clamp outwards, or extend our grabber. Also, we have started experimenting with a touch screen feature that may make it easier to control the opening, closing, and extending of the grabber. At this point the Arduino shield that we have been using requires quite a bit of finesse to press the screen. A stylus makes selecting options on the touch screen much easier and may be a sufficient solution if we don’t want to change touch screen models at this point. 

What we didn’t do:

We weren’t able to integrate or combine any of our objectives this week into a single product. We finished with our “mini” prototype, touch screen application tests, and telescoping implementation ideas, but they are still all individual accomplishments, and we plan to combine them next time we meet on Tuesday, 11/6/12.

Where we are stuck:

The pressure sensor has proven far from trivial as to how it will be implemented, and the telescoping concept is still a daunting problem and the only solutions are ideas on paper.

Notes/Misc:

We might try to get with Dr. Whitman to see if he has, or knows how to get a hold of, a plastic track that could coil up and act as our telescoping backbone. I know the BEST robotics kits had a similar item last year that would serve our prototype well.

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

Goals for the week:

Per the timeline:
Receive ATTinies to manage module processing
Receive RF wireless communicators to connect from modules to RPi.

Meeting times/dates

Meeting with John – Tuesday 8:20pm
Sunday, Nov. 4, 2012 – 4-6 p.m.

Individual Hours:

Everyone – 2 hour Meeting on Sunday

What we did:

We did get both the ATTinies and the Wireless Communicators, but the Wireless Communicators weren’t available since when they arrived there was no one to sign for them.
Therefore, we tried to get a leg up on making our own modules.
We met with Tom after our Tuesday meeting and we talked about using the relays. So on our Sunday meeting we were able to program a blink script on an ATTiny to control the relay.

Programming the ATtiny: http://hlt.media.mit.edu/?p=1695

Transistor datasheet: http://www.fairchildsemi.com/ds/2N/2N3904.pdf

Relay datasheet: http://www.sparkfun.com/datasheets/Components/General/JZC-11F-05VDC-1Z%20EN.pdf

YouTube Preview Image

What we didn’t do:

We didn’t get the Wireless communicator. We need to pick up from Post Office and program it.

Where we are stuck:

We are coming to the point where we will need to use the 3D printer soon to make casings. None of us has any experience on that yet, so we will need to do some research or get some guidance.

Notes/Misc:

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

Goals for the week:

1. Meet with Tara to finalize remote access system

2. Hack LED system and begin designing a driver circuit

What we did:

1. Our schedules with Tara didn’t line up this week, so we were unable to meet her. We are planning to meet her on Thursday the 8th.

2. We disassembled the LED and found it operates at a range between 15 to 25 volts, and <1 amp. By using a system of resistors and MOSFETs we will be able to control our LED remotely.

       

What we didn’t do:

Meet with Tara

Where we are stuck:

We need to meet with Tara to find out what type of remote control system we will be using.

Notes/Misc:

We did burn out the red array on the LED during testing