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

First Progress Reports for Prototype I go here.

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

Goals for the week:

Get information re: availability  and types of motors, accelerometers, arduino coding, investigate piano pedal compression parameters

Meeting times/dates

Tuesday and Thursday mornings at 9:00

Individual Hours:

Tom – 2 hrs 

Atul – 2 hrs

What we did:

met with Tom, experimented with various motors, group mtg

Research arduino coding, group mtg

 

What we didn’t do:

Accelerometers, piano pedal compression parameters, wireless receiver for acclerometer, meet with piano players to discuss fine point of pedal movement, talk with potential clients. 

Where we are stuck:

Is the motor going to be fast enough? Exact positioning of cam.

Notes/Misc:

Marz – Progress Report I for Prototype I: Campus App

Goals for the week:

  • Set up server and necessary services
  • Research Google Maps API for Android
  • Develop server and client proto-code
  • Set up development environment for all group members

Meeting times/dates

  • Monday 2:30-3:30

Individual Hours:

  • Zane Sumpter – 2 hours – Looking for web host, creating account, setting up initial web page
  • Mason McCanless – 2.5 hours – campus promotion for app, other campus apps and interfaces

What we did:

  • Found a free web host with PHP and MySQL and created an account.
  • Setup a web page and used the Google Maps API to display a map of the WSU campus.
  • Created functionality to move a marker around on the map given GPS coordinates.
  • Created a list of ways to entice students to download app / help campuses think of ways to promote the app.
  • Researched other campus apps, took notes on their layers, interfaces, depth, originality, and creativity. Took some pictures of the other apps for reference.

YAY WE’RE AHEAD OF SCHEDULE!

What we didn’t do:

  • Most of our energy this week was spent on getting the server up and running; as such, we did not put much effort into the Android client.
  • We did not reach out to Wichita State’s PR people, as we had discussed with John last week. We will be contacting John to follow up on leads within the university.

Where we are stuck:

As mentioned before, we’ll need to try to initiate contact within the university to gauge interest in this project.

Notes/Misc:

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

Goals for the Week

  • Update Code of Conduct to reflect meeting locations
  • Update Prototype I Writeup to reflect addition of use H-bridge for small motor and Arduino microcontroller
  • Purchase alumimum or copper tubing and shape into appropriate metal arcs
  • Learn how to program Arduino microcontroller
  • Learn how to make or purchase H-bridge for small motor
  • Obtain small motors from Shopping Cart Project
  • Make plans to purchase miscellaneous items, if not available in EECS Sr Design inventory

Meeting Times and Dates

  • 10:30AM-12:00PM, 23-SEPT-2012
  • 6:30PM-9:00PM, 24-SEPT-2012

Individual Hours

  • Taylor Russell will attempt to learn how to configure Arduino microncontroller, 2 hours
  • Jenice Duong will purchase aluminum or copper tubing for metal arcs, 2 hours
  • Shital Shrestha and Albert Ogenche will learn how to create or purchase an H-bridge for small motor, 2 hours

What We Did

  • Updated Code of Conduct to reflect meeting locations
  • Updated Prototype I Writeup to reflect addition of use of H-bridge for small motor and Arduino microcontroller
  • Purchased conduit for metal arcs
  • Learned how to program Arduino microcontroller with sample programs
  • Purchased SN754410 Quad Half H-Bridge chip
  • Obtained small motors from Shopping Cart Project, and verified that small motors work
  • Checked EECS Sr Design Lab inventory, found available batteries and electrical wiring

What We Did Not Do

  •  Did not shape conduit into appropriate metal arcs

Where We Are Stuck

  1. How could we add our Entrepreneur to our group on our Team #4 Forum?
  2. How much collaboration should we be doing with our Entrepreneur? Should they be at every Team meeting?
  3. Could we possibly have Wallace Hall opened on Sundays for easy access to EECS Sr Design Lab?
  4. Do we have Arduino motor shields available for use?
  5. Do we have three-way switches for use with Arduinos?
Progress Report I JEL group

Goals for the week:

Develop a better understanding of our respective subjects.

Meeting times/dates

Tuesday at 8pm group meeting with Tom.  (~discuss ubertooth)
Thursday 2:00 (tentative) group meeting: discuss what we know/and should know about bluetooth.  

Individual Hours:

Jerret: Probably around 20
Erika: at least an hour each day reading about bluetooth, and an hour to meet with Dr. …Zaman for direction re bluetooth and microcontrollers

What we did:

Formulated our goals in a more clear way. Came to the conclusion that our goal is to create a relay (bluetooth enabled) in between the switch and communication board referenced in the notes from 9/19/2012. The switch will pair with the relay and not the communication board. We are utilizing this approach because after discussing the problem with Dr. Jadlawali (sp?) we were forced to assume that the switch is hard coded to pair with only one device. With this assumption we have decided to create a relay with (currently) two modes, Chair Mode and Board Mode. In Board mode the relay will simply receive the information from the switch and relay it unchanged to the board utilizing the bluetooth protocol. This will also require us to pair the board with the relay. In Chair Mode the Switch will communicate with the relay which will be connected to the chair motor. The relay will be programed in such a way that it will send information, expected from the chair, to control the forward motion of the chair.

What we didn’t do:

Complete the entire project but we didn’t expect to.  We do now have some direction and expectation so we will have a better idea in future weeks of what is really not done.

Where we are stuck:

Jerret: Reverse Engineering bluetooth is hard.  

Out Of Time – Progress Report I for Prototype I: Electric Cooler/Heater

Goals for the week:

Parts will be arriving soon, allowing us to start testing the effectiveness of our peltier coolers.  We will be outlining our Arduino code requirements, and begin devoloping psuedo code to support it.

Meeting times/dates

Unfortunately, our hours were in conflict this week, so we will only be able to meet on Monday night.  We have all been diligently coming up with ideas for cooling, voltage/temperature regulation, and user interface on our own time.

Individual Hours:

Our group has agreed to put in 2 hours of independant research this week, focusing on Arduino programming, heat dissapation, and methods of integrating our prototype with wheelchair electronics.

What we did:

We have found many credible sources of Arduino code that should give us a head start in developing our own prototype.  We will begin testing cooler dynamics Tuesday.  A topic of discussion that will be focused on immediately is how to dissapate the heat generated by the Peltier cooler without consuming too much power.

What we didn’t do:

We did not get as far on the prototype as we would have liked.  The parts were ordered later than expected, and that pushed back on physical prototype development.

Where we are stuck:

Locating pre-built water cooler heatsinks for such large devices (40mm X 40mm) is a problems thus far.  We might have to create our own heatsinks from scratch.

Notes/Misc:

Our project name could use some finesse…

Team 12- Automation Home Framework

Goals for the week:

 

  1. 1.     Create a mock up of the web interface our users will see
  2. 2.     Research existing technologies that we could implement

 

Meeting times/dates

 

  • Thursday 8 p.m. (see forum for meeting minutes)
  • Sunday 4-5:30 p.m.

 

Individual hours and what we did: (includes some previous work up until 9/23/2012)

 

Trey -  Set up Raspberry Pi OS on SD card

            Plug in RPi to router and power (with ports 22 and 8080 open to internet for ssh/web)

            Install Apache on RPi

            Install mod_wsgi and change permissions to let Apache run Python scripts

            Start work on web interface (HTML/CSS/jQuery)

Write a python script to test control from web interface

Install RPi GPIO port control library for Python

4 hours

 

Olivia – 2 hrs – Attended meetings, took notes (Thu.), contributed research ideas, posted meeting minutes to forum

 

Nena – 0.5 hr – Thu. meeting

                         Wrote some  interview questions for CPRF

                         Working with Mike on market (business) aspects of the research

                         Upload project assignments on cartel web

Jose – 6hrs

            Set up collaboration tools

                        Google Group

                        Evernote

                        GroupMe

                        Google Drive

            Set up group meetings

            Attend group meeting

                        Wrote agenda

                        Lead meeting

                        Took notes

            // Let the dogs out. Yes, it was me.

                                               

What we didn’t do/Upcoming Goals:

 

  • Things are going smoothly.
  • Plan to meet at Trey’s apt. for tech work on Thu. evening at 7:15 p.m.
  • Make apache server have access to IO ports
  • Measure volt usage for the remote control

           

Where we are stuck:

 

  • Ask about decomposing existing devices to learn about their implementation.
  • How much is building on previous groups’ experience with RFID/wireless, etc. okay?
  • Does John have experience building RF communication systems?

 

Notes/Misc:

 

May want to check out the website smarthome.com to see other similar ideas, and get a feel for where the final product needs to be for mass marketing. -Mike

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

Goals for the week:

  • Get parts in
  • Practice with the Arduino
  • Interview prep

Meeting times/dates

  • Monday 7:00 PM

Individual Hours:

  • Tanner bought the GPS module and antenna
  • Ryan is practicing with the Arduino

What we did:

Tanner bought the GPS module and antenna. Ryan practiced with the Arduino.

What we didn’t do:

Haven’t yet met with Sydney to run over project details and questions.

Where we are stuck:

Wondering about how to connect GPS module to Arduino, and parse data. Already found reference material.

Notes/Misc:

N/A

Team Alpha – Progress Report I for Prototype I: Trueview Power Camera System

Goals for the week:

 - Download SDK

- Work with the SDK to work on coding for the next few weeks

- Get some code working with the Kinect (if we can get the coding down).

- Order Kinect

Meeting times/dates

 - Saturday 9/22/12  4pm

Individual Hours:

 _ At least one and 1/2 hour for each person

What we did:

 - Chose Kinect will be used for our project

- Discussed about the Kinect

- Talked about the hardware and software need to be used

What we didn’t do:

-We didn’t get the hardware working with the software yet.

Where we are stuck:

-  C++ or Java will be used to write the code

Notes/Misc:

- Eric Robinson will be ordering Kinect and handling the reimbursement forms. The team is expected to load the SDK on their machines to test example code before getting their hands on the hardware.

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

Goals for the week:

Take apart mechanical grabber. Attach motor to cable controlling gripper.

Identify if Arduino will have sufficient power to drive motor powerful enough to run grabber or if a driver chip will be necessary.

Discuss interface options.

Meeting times/dates

Friday      6:00pm       Senior Design Lab

Individual Hours:

Jeremy Wharton -

Justin Hickey -

Charles Swanson -

Clayton Skaggs -

What we did:

During our meeting on Friday we mounted a 12V Gearhead Motor to a hacked down mechanical gripper. The gripper operated by pulling on a long 1/16th inch steel cable to pull back on the connections of the pincers at the end of the shaft. This was the first big step toward creating our battery assisted grabber. It lacked any type of control other than hooking it up to power to clamp down and removing it from power to release.

What we didn’t do:

We ended up usinig a more powerful motor than was probably necessary due to difficulty mounting our mechanical grabbers steel cable to a smaller one. Even so, it’s very probable we’ll need a driver chip to supply the power we need seeing as an arduino can only supply 5V and 120A. We’re also going to need to clean up the motor assembly at some point.

Where we are stuck:

The current grabber is taking a lot of force to keep closed. We may need to step into the mechanical field and find ways to make the mechanics of the grabber easier on the motor, find a way to increase the amount of force being pulled by our motor using a pulley or gear system, or both. Scaling everything down and is going to be a pretty big challenge as well.

Notes/Misc: