Archive for the 'Progress Reports' Category
[SAFE] – Progress Report III for Prototype II: [MEDS]

Prototype 2 plans

Goals for the week:

1. Research for libraries to implement the on-screen keyboard.

2. Decide about the material for the box for our prototype, and begin designing process.

3. Research about the poor sensitivity of the touchscreen, looking for possible solutions.

4. Implement a numeric keyboard on the touchscreen.

Meeting times/dates

Ryan and Ghassan met with Prof. Harrison on Monday 4/16 to work on the programming code and libraries.

Group met on Thursday, as usual, to work and discuss about the project.

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

Individual Hours:

Team members have spent–this week–around 3-4 hours avg on researching/working in the project in an individual fashion.

What we did:

Libraries provided by Prof. Harrison were implemented, with his help, to produce a numeric keyboard on the screen and receive input numeric data.

We asked Tom for help with the 3-D cutter, since we’ve decided to create the box using the 3-d cutter in lieu of a professional look for our prototype.

We found some issues about sensitivity posted by other users (http://www.microcodes.info/2-8-18-bit-lcd-touchscreen-improved-accuracy-20645.html) and also the suggestion that a hard-point stylus will help with the accuracy issue… although we are conscious that this is not an iphone-quality type of screen, we have to produce an alphanumeric keyboard that would require space and high touch accuracy.

What we didn’t do:

We have still to create the CATIA design for the box, and start working with the 3d cutter.

We have to implement an alphanumeric keyboard and record the pulsations on a file.

Produce an output based on the input captured by the same touchscreen.

Where we are stuck:

Libraries and programming… implementing the keyboard have proved to be the biggest challenge at this moment…

Notes/Misc:

We would like to request to meet with Prof. Harrison for a couple of times this coming week with reference to the programming/libraries implementation, and with Tom to work on the box design.

We are discussing possible alternative solutions to be ready with a prototype working with the touchscreen as input/output way to communicate with the customer. Please find attached proposed algorithm to be implemented to present at the Open House.

LIBRARIES:

TESTING FOR PRESSURE, AND THEN PRINTING X AND Y COORDINATES.

#include “TouchScreen.h”
 
#define YP A2 // must be an analog pin, use “An” notation!
#define XM A3 // must be an analog pin, use “An” notation!
#define YM 8 // can be a digital pin
#define XP 9 // can be a digital pin
 
// For better pressure precision, we need to know the resistance
// between X+ and X- Use any multimeter to read it
// For the one we’re using, its 300 ohms across the X plate
TouchScreen ts = TouchScreen(XP, YP, XM, YM, 300);
 
void setup(void) {
  Serial.begin(9600);
}
 
void loop(void) {
  // a point object holds x y and z coordinates
  Point p = ts.getPoint();
  
  // we have some minimum pressure we consider ‘valid’
  // pressure of 0 means no pressing!
  if (p.z > ts.pressureThreshhold) {
     Serial.print(“X = “); Serial.print(p.x);
     Serial.print(“\tY = “); Serial.print(p.y);
     Serial.print(“\tPressure = “); Serial.println(p.z);
  }
 
  delay(100);
}
 
MAR – Progress Report III for Prototype II: Wireless GPS Tracker

Goals for the week:

* We connect the battey whith its holder and the switch. Try attaching it to the circuit.

* Making the structural holder for the wrist band.

* Continue working on the application building.

* Upgrading the phone.

Meeting times/dates

Friday 4p to 7p and Sunday 4p to 7 p

Individual Hours:

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

What we did:

* We were able to collect the battery and holder.

* We are still waiting for ordered parts.

* From the application side, we were able to do coding to get input to an array adapter and show it as a linked list, and still troubleshooting.

* We started upgrading the phone.

What we didn’t do:

* We were unable to make the holder for the circuit since couldn’t figure out the final size of the entire section as we were still waiting for some parts.

* We planned to see the program output as a linked list, we did the coding but unable to see the output as we are still having unknown errors to troubleshoot.

Where we are stuck:

* For some reason our touch pad does not show the desired layout of the application. We can’t use the emulator since it does not support bluetooth packages. 

Notes/Misc:

Green Wu – Progress Report III for Prototype II: Bicycle-powered generator

Goals for the week:

Fix the gearing on the bicycle

Research charge controller and voltage regulator designs

Set up the python environment for the voltage meter.

Start the eagle board design.

Meeting times/dates

Tuesday 8-11pm

Thursday evening from 7-10:30pm

Individual Hours:

Alex – 2 hours of fixing bicycle gears

Adrian – 2 hours of research in charge controller and voltage regulator designs

Eric – 2 hours of research in charge controller and voltage regulator designs

Stephen – 2 hours of research in charge controller and voltage regulator designs

What we did:

We fixed the bicycle gearing so that the user may switch between gears.

We researched the difference between a charge controller and a voltage regulator and realized that we need both for the project to ensure safe battery operation.

The voltage regulator is used to prevent the over-voltage, and the battery charge controller is used to prevent over-charging.

Charger controller: http://ghurd.info/dc_parts.html

General information about charge controller: http://www.mdpub.com/Wind_Turbine/index.html

One of the commercial charge controllers we could have bought: http://www.amazon.com/gp/product/B000C168ZS?ie=UTF8&tag=freewaresharew01&linkCode=as2&camp=1789&creative=390957&creativeASIN=B000C168ZS

IC chip used for our voltage regulator: http://www.reuk.co.uk/LM2941-1A-Low-Dropout-Adjustable-Regulator.htm

How to connect three of the voltage regulators into a parallel connection to allow high-current applications: http://www.reuk.co.uk/High-Current-Voltage-Regulation.htm

Data sheet to the IC chip: http://www.ti.com/lit/ds/symlink/lm2941.pdf

What we didn’t do:

We haven’t set up the python environment.

We haven’t started the eagle board design

Where we are stuck:

Hand-pedal / lever implementation for our individual CPRF resident

Finding 3D software to simulate the hand-pedal design.

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

Goals for the week:

  1. Determine the # of conductors existing in the joystick 3.5mm connector on the MKIV joystick.
  2. Modify the Arduino code to handle two in/out puts.
  3. Ordered LED marker lights, LED flood lights, and Fuse holders.
  4. Building the system.
  5. Test the system.

Meeting times/dates

Thursday 7:00 PM – 9:00 PM

Friday 2:00 PM – 5:00 PM

Individual Hours:

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

What we did:

We found out from Greg that the 3.5mm connector won’t work, because we need 3 conductors and there are only 2 in the joystick that the residents have.  We used a new code for the arduino to receive analog signals ,converts its and sends out a digital signal.   We received enough of the supplies to build the circuit and test it.  We discovered that we may need to alter the code a little more.  The lights only dim, when they should shut off. 

What we didn’t do:

  1. Didn’t receive the flood LED.
  2. Didn’t complete the areas where we are stuck. (below)

Where we are stuck:

  1. Can’t find proper style fuse to protect the controller.
  2. We need to determine an alternate method to connecting to the joystick via a plug vs hardwired.

Notes/Misc:

Team Glen – Progress Report III for Prototype II: Smart mailbox

Goals for the week:

Wrap up everything

Meeting times/dates

Met Friday 12:30 to 3:00. 

Individual Hours:

Murtada and Dhreen: spent 4 hours making catia three dimensional drawings of the mailbox for the final report.

Dhreen: spent 3.5 hours preparing the wiring diagram for the final report on a software with some minor wiring additions to it.

Tetteh: spent 1.5 hours combining and rewiring what we developed in prototype I and the new hardware (RFID system) added to it to make it prototype II.   3.5 hours were also spent testing and debugging the combined code “program3″ for prototype II.

Glen: spent 2 hours completing the code for program 3 and another 4.5 hours getting everything all enclosed inside project boxes to make everything look nice and neat for Open House.  Also spent about 0.5 hours troubleshooting the errors for prototype II that Tetteh was having trouble with “After compiling program 3 and loading, the RFID reader is no more scanning RFID tags that are brought close to it.”  Changes made was first to the wiring for mailbox sensors 1 & 2 that was in pins 8 & 9 to pins 7 & 8 to match our wiring diagram.  Second changed pin 3 “softwareSerial TX” to pin 2 “softwareSerial Rx” for the RFID to match our wiring diagram.  Reload the original code for xbee receiver to match our wiring diagram.  No debugging was needed to program 3 as everything work okay after these changes.

What we did

  1. We completed program 3 that will be used in our in final prototype II project and it works.
  2. We completed the wiring diagram that will be used in our final report and presentations for Open House.
  3. Successfully tested the wiring diagram hookup and the programs that will be used in prototype II final project.
  4. We are making progress on the catia three dimensional drawings of the mailbox for the final report.
  5. We are making progress with getting everything enclosed for presentations.

What we didn’t do:

Still need to finish up on getting everything enclosed, but almost done.  Also need to finish the catia 3D drawing and make a flow chart of the code.

Where we are stuck:

We are doing alright.

Notes/Misc:

We need to start our prototype II final report for next week.

Team X – Progress Report III for Prototype II: Wheelchair Curb Detector

Goals for the week:

Integrate the system onto the wheelchair.

Meeting times/dates

Sunday 4:00, Thursday 1:00

Individual Hours:

Sam 4 hours

Nhat 4 hours

Bana 3 hours

What we did:

We hooked up the arduino to the wheelchair. We interfaced the joystick with the arduino to read the voltage of when the joystick is pressed forward (4 volts). The arduino will reset the system when the joystick is in the neutral position(around 2.5 volts). It seems to be working correctly. The arduino is still powered off the RC car’s 9 volts battery. 

What we didn’t do:

We need to get a 9 voltage regulator to run off the 24V battery of the wheelchair. We also still need to purchase some goose necks to attack the IR sensors to the wheelchair.

Where we are stuck:

We are on schedule.

Notes/Misc:

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

Goals for the week:

  • Make flowchart to illustrate the function of the project.
  • Write code for microswitch and try to design a circuit.
  • Modify the code for H-bridge since we are not going to use motor shield anymore.
  • Combine code for microswitch and H-bridge.
  • Also combine circuit for microswitch and H-bridge.
  • Try to somehow connect Styrofoam with Linear Actuator for the open house.

Meeting times/dates

Saturday at 1 pm – 2 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 flowchart for our project.
  • Played with microswitch by making circuits (burned several LEDs and thanks to John for helping refresh our Circuit I class) and arduino programming
  • Code for actuator with H-bridge has been modified and thanks to Tom for helping us on coding.

What we didn’t do:

  • Didn’t combine code for microswitch and actuator because of trying to figure out the programming for microswitch.
  • Didn’t  work on connecting actuator with Styrofoam.

Where we are stuck:

We need to work on the mechanics part of the project. We should work on how to connect actuator with Styrofoam this coming week. It will be our main focus besides other goal we’ll set for next week.

Notes/Misc:

Prototype II Progress Report III 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: