Archive for the 'I' Category
Eh Team – Progress Report II for Prototype II: Universal Wheelchair System

Goals for the week:

Try to get the tablet to communicate with the Arduino

Purchase Poster board and begin designing display for Engineering Open House

Meeting times/dates

Sunday 2-4

Individual Hours:

Ali: 5 hours

Cody: 1 hour

Imran: 1 hour

Kishor: 1 hour

What we did:

We finally determined the greatest stumbling block in our communications between the tablet and the Arduino.  We determined that the code we were using would only work with  Arduinos that have with Atmega16U2 or Atmega8U2 programmed as a USB-to-serial converter; however, it appears the Arduino we are using instead uses a FTDI USB-to-serial driver chip.  (However, when we check, it appears as though our Arduino should have the Atmega8U2, at least.)  Once we made this determination, we were able to run a sample app that allowed basic communciation between the tablet and the Arduino, in which the tablet displays the voltage detected at pin 1.  Also, we have purchased the poster board, and have began designing our display for the Engineering Open House.  We were also able to verify the vendor ID and product ID of our Arduino (view screenshot below).

What we didn’t do:

We have not yet been able to send data from the tablet to the arduino.

Where we are stuck:

Why the only app we are able to run on the Arduino is the one meant for an Arduino with FTDI USB-to-serial chip driver; however, when we looked up the Arduino UNO R2, it indicates that it should have an Atmega8U2 USB to serial converter.

Notes/Misc:

 

Blue Team – Progress Report I for Prototype II: Smart Cushion

Goals for the week:

Get the parts that we need ordered and implement a graph into our code that can change color according to input.

Meeting times/dates

Saturday, 11am in the Wallace Workshop ~2 hours

Individual Hours:

There wasn’t much in the way of work to do outside of our meeting this week besides getting the parts ordered which would be negligable.

What we did:

We edited our code to show 4 different squares when the code was run.  The input from the pressure on the cushion would increase a color value on one of the squares which would change its color to show real time changes in pressure.  We have also ordered a couple valve assemblies which should be here soon.  All in all it was not a busy week but when the parts come in there will be work to do.

What we didn’t do:

We haven’t gotten together with Greg yet about using one of his old cushions, he responded to our email and we are going to meet him on Wednesday for all of that.

Where we are stuck:

There hasn’t really been any tough work to be done so far.  This next week will probably show some more difficulty.

Notes/Misc:

N/A

Deliberate Gecko – Progress Report I for Prototype II: RPTC

Goals for the week:

Find/determine stepper motor winding order to operate stepper motor for y-axis movement.

Program basic code for timing sequence from arduino.

Meeting times/dates

TBD

Individual Hours:

All, 5 for the week

What we did:

Solved the 5-phase stepper motor winding sequence by touching wires to each one to find the order in which to use the phases of the stepper motor to run it in either direction.

Ate and drank.

Programmed arduino to run stepper motor, using 1 phase at a time.

Burned an arduino?

Programmed arduino to run stepper motor, using 2 phases at a time.

Programmed arduino to run stepper motor, using 3 phases at a time.

What we didn’t do:

Give the project a cool name, like Project Ghost or something.

Where we are stuck:

Connect USB joystick to arduino for user control input? or use computer?

Notes/Misc:

Video!

YouTube Preview Image
Team 4 – Progress Report I for Prototype II: Easy Opener/Closer

Goals for the week:

Build a solid base for the device and start working on building the top half

Meeting times/dates

Tuesday : After Class

Thursday : 3 :30 to 5: 30

Individual Hours:

Zubair : 1 hour on friday to work on the base which is finally ready

Michael :

Nick :

What we did:

We figured out that a new base was required for the device to work properly which should be bigger in size to support the 4 rods which are to be mounted on it so we built a completely new base and work out a way so the base can support everything. We have successfully built the base. Michael and Nick are working on the Arduino’s and a procedure on how to mount it on top.   

What we didn’t do:

Not anything that I know of

Where we are stuck:

Using sensors to adjust the pressure when the top panel slides down. Also we will be discussing a suitable material to be used on the top of the plate so it can produce a friction and holds the bottle rather than letting it slip away.

3! – Progress Report I for Prototype II: Mechanical Camera Stand for Wheelchairs

Goals for the week:

  • Learn to use laser cutter
  • Work on joysticks
  • Design the rotating platform 

Meeting times/dates

Wednesday and Thursday: Wallace Hall lounge

Individual Hours:

Meet as a team.

What we did:

We learned to operate laser cutter. We have drawn the design of rotating platform on inkscape and cut the styrofoam with new dimensions utilizing new smaller (3″) turntable that we have.

We checked the styrofoam with servos and now we are ready to cut the glass. We went over some vibration absorber that can be placed on the base where camera will rest.

 

What we didn’t do:

We will finish the top part of our design. i.e. to cut the glass and make box where we will put servo for the base and use the same mechanism for pitch control from prototype I. We are working on to build gears for the rotation of our base. 

 

Where we are stuck:

We have discussed some ideas on up and down movement but we are still working on to build it.


Notes/Misc:

A Team – Progress Report I for Prototype II: Micro Cyber Watch Dog

Goals for the week:

1. Get/Order most components.

a. Xbee

b. Arduino Uno

2. Start working with the components, figure out how everything works.

3. Dissamble/Open existing camera and see if it can be used for the project.

4. Research gears manufacturers….

Meeting times/dates

Wednesday 3/27/2013 @7pm Wallace Hall 3rd Floor Electronics Lab.

Monday 4/1/2013 @7pm Wallace Hall 3rd Floor, Computer Lab.

Individual Hours:

Gustavo: Existing camera housing removed (see notes/misc for picture). 30 min. Tested arduino nano @2hr. Practice/test Eagle CAD @2hrs.

Hector: Research small gears on the web, http://www.wmberg.com/ has many, there is also gears for small mechanical watches available on the web, quote asked from wmberg.com. approximately 45 min. 

Brandon:

James: Took measurments of current bot gears. left voice message for Rick Shipman.  Waiting for Response.  Went to his shop, but he left for the day.  Will be ordering and designing gear system based off of Rushgear.com inventory.  (CAD 3D and 2D drawings provided).  First attempt Gears and actual bot gear measurements attached to post. Will be assembling gear files in CATIA before ordering. 1 hour.

What we did:

1. Most of the parts are already in, Xbees, Arduino Nano, camera.

2. Existing camera housing was removed. Camera is small and might be possible to used in the project, will found out next week.

3. Some programming with the Arduino Nano was done but the code written for prototype I needs to be modified to load it in the Arduino Nano. 

4. Some practice with Xbees…

5. Some research with gears…

6. some practice with Eagle CAD to create PCB boards.

What we didn’t do:

1. Program/Load Arduino nano for Prototype II.

2. Order or decide which LiPo batterie(s) we are going to used.

3. See how much space all the components together will occupy.

Where we are stuck:

1. Still deciding if the current camera will work for the project, will know for sure next week. 

1. Waiting on quotes from two websites for gears.

Notes/Misc:

Gear Files CATIA files and PDF datasheets
[Eh team] – Progress Report I for Prototype II: [Universal Wheel Chair System]

Goals for the week:

*  try to work on program and coding part again to see if there is any bugs in our program or not.

* Emailing Greg and will discuss with him about our current status of our project.

 

Meeting times/dates

Sunday : 2-4 pm

Individual Hours:

Kishor – 2 hour

Cody – 2 hour

Ali – 4 hour

Imran – 4 hour

What we did:

We figured out the code which we can load in audrino. We verified the product ID and vender ID  for the audrino using software LS USB for windows and used in our USB code to make communiction between android and audrino. Coding part is almost completed.  We still need to look at the code from audrino communicator and see what else we can add in our codes to make a smooth communication between audrino and android.

What we didn’t do:

Because we were still working on coding part to make good communication between audrino and android, we didn’t get chance to come to lab and see the solution for our problem using oscilloscope as we discussed in last class. 

Where we are stuck:

When we load our USB code in audrino, it don’t do anything . So we think there might be the possible issue of something wrong with baud rate. For that we have to go through code again and see if baud rate is an issue or not.

Notes/Misc:

This week we will look into codes from audrino communicator and see if we can use anything from there in our app.

BitShifters – Progress Report I for Prototype II: Shelf Assist

Goals for the week:

  • Register for the Open House
  • Customize the motor to fit in the shelf.
  • Contact Cessna Lab about shelf modifications.

Meeting times/dates

  • Tuesday – after meeting with Tom – spend more time customizing

Individual Hours

  • Jeff – 3 hrs
  • Shanto – 3 hrs
  • Andrew – 3 hrs

What we did:

  • We registered our project for Engineering Open House.
  • We detached two of the springs to the self and replaced one of the gas shocks with the linear actuator that Gregg provided.  Using a voltage supply, we were able to have the motor lower and raise the shelf.

What we didn’t do:

  • Because the shelf frame was in the way of the motor, we were not able to position the actuator so that it fully lowers the shelf.  We need to either modify the shelf frame so that it won’t be in the way, or we could drill new pin holes into the actuator so that it could flipped with the motor above the actuator instead of below.

Where we are stuck:

  • The shelf bracket is in the way of the motor.
  • The motor was too long – need a motor of appropriate length.

Notes/Misc:

  • Bring extra Mountain Dew for Jeff.