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

Second Progress Reports for Prototype II go here.

[Meds] – Progress Report II for Prototype II: [Idea Name]

Goals for the week:

We plan to buy the touchscreens and  get more comfortable with them.  also we want to make a blueprint for the box that holds the arduino and the screen.

Meeting times/dates

several times on Thursday.

Individual Hours:

Fill this out by Thursday eve: Who put in what kind of hours for the week?

What we did:

We bought the screens.  They came in on Wednesday.   We looked at some example code for the screens. There are some examples at adafruit.com. 

What we didn’t do:

We didnt get anything done with the box.  We are assigning one of the group members to The box so we stay on track.  We all will participate in the 3D printer part of the project, because nobody would want to miss that. 

Where we are stuck:

Fill this out by Thursday eve: Logistical or technical questions could go here. Anything you want to remember to ask me when we meet might go here too.

Notes/Misc:

Green Wu – Progress Report II for Prototype II: Bicycle-Powered Generator

Goals for the week:

 Research charge controller and python/code implementation. Research other DC or AC motor options.

Meeting times/dates

Fill this out as soon as you can after class on Friday. List times/dates/length of meetings for the week

Individual Hours:


What we did:

We received our battery and began looking over it’s Powerpack-ness. It’s power-packed.

What we didn’t do:

Didn’t get any physical components created. Need to look into blocking diode and see which components for the charge controller are readily available in the lab.

Where we are stuck:

Fill this out by Thursday eve: Logistical or technical questions could go here. Anything you want to remember to ask me when we meet might go here too.

Notes/Misc:

MAR – Progress Report II for Prototype II: Wireless GPS Tracker

Goals for the week

  • Start making a wrist band for the SMD module
  • Developing the android app
  • Find a suitable switch and a battery for the Bluetooth SMD module

Meeting Times/dates

Friday 4pm to 7pm
sunday 4pm to 7pm
 

Individual Hours

Team members will work on their piece of work as needed.

What we did:

We could develop the app until it detecting the bluetooth signal. 

We could find a wrist band and batteries for the SMD module

What we didn’t do:

* We still couldn’t upgrade the android version of  the phone. 

Where we are stuck:

* Our android phone’s touch screen is not working anymore. We have to try from another one

Electric Chair – Progress Report II for Prototype II: Electric Chair

Goals for the week:

Analog to digital conversion using the Arduino

Joystick x,y, output voltages

Expand Arduino program for multiple output

Meeting times/dates

Thursday 7:00 PM – 9:00 PM

Individual Hours:

All team members put about an hour into research for the project.

What we did:

We did find the upper and lower voltages for the joystick. We did also trying to look for the signal through the oscilloscope.

What we didn’t do:

We didn’t buy the LED lights.

Where we are stuck:

Coding an Arduino program to communicate with the joystick.

Notes/Misc:

After discussion with Greg, we have decided to alter our plan slightly again.  Instead of hacking into the encrypted DX BUS, we have decided to basically disable an unused drive as a motor control and then enable that drive as light control.

Team Glen – Progress Report II for Prototype II: Smart Mailbox

Goals for the week:

Draw a wiring diagram.

Program the mailbox xbees and the RFID system according to the wiring diagram.

Complete program 2 (RFID with softwareSerial that compares assigned mailbox tagID with just scanned RFID tag.

Start program 3 that is the program used in Prototype II.

Meeting times/dates

We met on Friday for 2 hours 12.30 to 2.30.

Individual Hours:

Murtada and Dhreen: We worked collaboratively for 3 hours figuring out the bugs in the existing wiring diagram and creating a new wiring diagram with some necessary additions to it.

Tetteh spent 8 hours working on programming the RFID reader to pick up the key on each of the 4 authorized TAGs  and make a decision if the keys are matched.

Glen – worked on many different things of the project.

  1. About 2.5 hours writing the code for program 2 that compares the just scanned RFID tag with a specific tagID assigned to each mailbox.
  2. About 0.5 hours on program 3 that is the main RFID program used in final project.  The combined program of xbee sender program already done with the RFID program from above.
  3. About 1.5 hours make a sketch (on paper) of the dimensions and rigging of final project for next semester.
  4. About 1.0 hours troubleshooting the program 2 at WSU with no success.
  5. About 1.5 hours of continued troubleshooting of program 2 and RFID at home to test in my C++ program I use that is a step by step debugger which is a great aid to find errors in code like this.  Program 2 RFID program now works.
  6. Note:  Not sure if program 3 works as it has not been tested yet.

What we did:

- The wiring diagram was very important for this week because it will be the foundation for our entire circuit that connects the actual mailbox and the RFID system. There were a few errors in the coordination with the mailbox that we fixed. The errors were because the labeling of the sensors was done wrong but its fixed now. We also added 3 RFID sensors and added new RFID circuit to it as well. 

- Programming the RFID reader to pick up keys and match them to the hard coded keys, allows us to distinctly turn on and off 3 different LEDs with the first 3 tags. Once the master key is scanned, it turns on and off all 3 LEDs at the same time. Our next step will be to replace all 3 LEDs by 3 servos. 

After minimal changes to this currently working code we can simulate the locking and unlocking mechanism of all 3 mailboxes .

What we didn’t do:

Test program 3 for bugs.

Where we are stuck:

We never get stuck.

Notes/Misc:

[S.R.P.R] – Progress Report II for Prototype II: [Dual Mode Table.]

Goals for the week:

  • Make table out of Styrofoam on Saturday with help of Tom
  • Play with Microswitches to control how far actuator can go so it doesn’t reach to its extreme.
  • Start to work on the first movement of the table.

Meeting times/dates

Saturday at 1 pm – 3 pm

Wednesday at 10 am – 11:30am

Individual Hours:

Each member is expected to spend at least 2 to 3 hours.

What we did:

  • Made Styrofoam table on Saturday with help of Tom. Thank you so much Tom.
  • Painted the styrofoam. That was the fun part of the week. Thanks to my teammates that they were better at painting than me.
  • Researched on microswitches with arduino. I found this blog: http://blog.martinperis.com/2010/09/arduino-rkl298-limit-switches.html This is similar to what we were thinking to implement. The main components in this example were 2 DC motors, 4 limit switches, RKL298 (H-bridge) and obviously arduino. The H-bridge that it used is different than what we used for motor shield. If we can use the our H-bridge and able to modify a code a bit, I think this will be a good code.

What we didn’t do:

  • Got 2 microswitches from lab but didn’t get to work with it. More time was spend on research on how to use the microswitches.

Where we are stuck:

  • I am kind of stuck on the understanding of the code on the blog I posted above. I understand what it is doing overall but quite not sure when i went through the coding.

Notes/Misc:

TEAM X – Progress Report II for Prototype II: Wheelchair Curb Sensor

Goals for the week:

Break into the joystick of the wheelchair, map the voltages of the wheel chair between neutral & run position with Oscilloscope & DMM.
Using the relay to cut out the “go” signal of the wheelchair.
Test the RC car in sunlight and a real curb.

Meeting times/dates

Sunday at 4PM
Thusday 1:00PM

Individual Hours:

Sam: 4.5 hours

Nhat: 4.5 hours

Bana: 3.5 hours

What we did:

We were able to map out the voltage of run and neutral position of the joystick. Neutral is 2.4 to 2.6 volts and run is 2.6 volts to 4 volts. Test the system in the sun. It did detect the curb, we didn’t notice any interference but still we got spikes in the readings maybe due to bad ground connect ( we soldered the ground connection after this). We will try to test it again on a different day.

What we didn’t do:

We completed the tasks we set out to do.

Where we are stuck:

We are currently on schedule.

Notes/Misc: