Archive for the 'Progress Reports' Category
Team Bravo Squad- Progress Report for Prototype II: Emergi-Text (4/17/13)

Goals for the week: 4/17/13

Our goals for this week are to finish our box for the Emergi-Text device.  Construction for a box has been started and needs to be completed. A larger button needs to be built for easier access of use.

For the program being used for our device, there needs to be some debugging for the battery disconnect application. When power is lost for the device, the Emergi-Text app should automatically turn on and send out a text to a friend for family member.

Meeting times/dates

Tuesday 1pm – 2pm 

Thursday 11am to 12pm

Individual Hours:

Bryan 1 hours soldering wires together

Tanner 1 to 2 hours debugging programs for the Emergi-Text app. Tanner worked on the program for the power disconnect and continues to fix any problems the program might have.

Danny 1 to 2 hours finishing contacts list for program. Programing the contact list into Emergi-Text app on device.

Ryan 1 to 2 hours designing and building a box for device

What we did:

  • Soldering wires together
  • Soldering wires to circuit board
  • Cut materials for box
  • Finished button setup for device
  • Power disconnect program
  • Emergi-Text contact list was programmed into app
  • Debugging for button program

What we didn’t do:

 

Where we are stuck:

For some reason our Emergi-Text app will work fine when the button is pushed, however when there is a power disconnect to replicated a dead battery the app on our system will crash. Further inspection of this issue is in progress and should be fixed by Monday. 

 

Notes/Misc:

 

Goals for the week: 4/11/13

Our goals for this week are to finish our box and button for the Emergi-Text device.  Construction for a box has been started and needs to be completed. A larger button needs to be built for easier access of use.

For the program being used for our device, there needs to be some debugging for the battery disconnect application. When power is lost for the device, the Emergi-Text app should automatically turn on and send out a text to a friend for family member.

Meeting times/dates

Tuesday 1pm – 2pm 

Individual Hours:

Bryan 2 hours soldering wires together, cutting materials for the box

Tanner 1 to 2 hours debugging programs for the Emergi-Text app. Tanner worked on the program for the power disconnect and continues to fix any problems the program might have.

What we did:

  • Soldering wires together
  • Soldering wires to circuit board
  • Cut materials for box
  • Started building a button
  • Power disconnect program
  • Emergi-Text gps coordinates programmed to be sent when device is on
  • Debugging for button program

What we didn’t do:

Bryan could not get any solder to stick to the pin being used to plug into the phone. The pin is made of a stainless steel and the silver solder will not hold.

Where we are stuck:

 

Notes/Misc:

Team Bravo Squad – Progress Report for Prototype II: Emergi-Text System

Goals for the week: 4/3/12

Bryan’s goals for the week are to get a box built for our Emergi-Text device. He will make a model of the box first and then design the box on the computer and have the laser cutter cut the box to piece together. Once the box is built a button can be installed or made.

Programming goals: For the programming code Danny has been working on the contact list that can be used for our device. Tanner will be doctoring up his section of programming. All the code is now being shared between Tanner, Danny, and Ryan for further collaboration.

Meeting times/dates

Tuesday 1pm to 2pm

Thursday 11am to 12 pm

Individual Hours:

Bryan spent 1 to 2 hours modeling a box out of foam board and then began drawing up the box digitally for the laser cutter

Tanner spent 1 to 2 hours fixing problems with code and creating new features with our system

What we did:

We have begun final stages of our device, so full manufacturing and usability will soon be available. A box with a large easy button is being built and the final strings of code are being written.  

Where we are stuck:

Our app that we are creating will crash every so often, so we have been dealing with that and trying to figure out why the phones program this our app has less priority than other apps. When we use the push button feature the app should automatically come on and send a  message, we are having trouble with this being consistant.

 

Goals for the week:3/27/13

Our goals for this week were basically the same as last week. We are still working on the code for our program.

Tanner is dedicated to the code that responds to the power output of the wheelchair.

 Danny is dedicated to the code for the contact list for the device. 

Ryan is dedicate to the code for the button control that turns our device on.

Bryan is constructing  a larger button for easier use for the  electrical components to the device.

Meeting times/dates

Tuesday 1:00pm to 2:pm

Thursday 11:00am to 12:00pm

Individual Hours:

Tanner spent several hours 2-3 hour on programming his portion of the code

Bryan spent 1 hour setting up electrical components to the device. The usb port that goes into a power socket similar to a car’s power port was tested.

Ryan spent a couple hours getting examples of how to re-program a media button for a phone. He found several examples that may work.

What we did:

Tanner was able to get the app for the Emergi-Text system to actually function. There still needs to be some minor tweaking, but for the most part we have a working app for the device.

Bryan spent some time designing a box for the device as well as constructing a larger button for the device. The button is not completed but should be finished by next week.

What we didn’t do:

We were not able to have our program run continuously for our device. There may be an error in the code, but the app continues to crash after being turned on. The function on the phone put the media button at a higher priority than the function Tanner programed it for.

Bryan was not able to get a box built to hold all the electrical components to our device. The lab has been full this last week so space for work has been hard to find. The design for our box and button have been design, but need to be built now.

 

Where we are stuck:

Not stuck so much as waiting for code to be written. Bryan’s work is dependent upon Ryan’s code and in order for Danny’s code to work Ryan’s code must be written.

Bryan needs to solder a couple wires from our power source to the usb port.

Notes/Misc:

Team Bravo Squad – Progress Report VI for Prototype II: Emergi-Text

Goals for the week:

Tanner- Continue working on his program for the button being used to turn on the Emergi-Text system, which will be sending a text to a contact of choice

Danny- Begin programming the code for the contact list being used in the Emergi-Text app

Ryan- Begin working on a code to read and display to amount power being used or remaining in the wheelchair.

Bryan- to test the stripped down earbud wires to see which wire and ring on the pin  are being used for the button to turn the microphone on and off

Meeting times/dates

Tuesday 1pm to 2pm

Thursday 11am to 12pm

Individual Hours:

Bryan 1 hour of stripping down wires and testing the I/o of each wire to understand how the ear buds worked.

Tanner 1 hour of programming

Danny 1 hour of programming

Ryan 1 hour of programming

What we did:

Bryan spent time this week carefully taking apart a pair of ear phone with a mic button. The button on the ear phone is the main focus of this process. We will be using the wires to the button and the pin that goes in to the phone port. We stripped it down and found out that the first two ring on the bottom of the pin are used for the left and right audio, the third ring appeared to be the ground which were gold wired and the microphone wire was attached to the top ring or sleeve. We are mainly only needing the red and gold ground wire for this project. The audio wires serve no purpose for the system.

 Tanner order more parts for the project. He ordered several usb jack that can be plugged into a cigarette lighter, and ordered a cigarette lighter port that can be wired directly to the wheelchair power source.

Danny began working with the code for the contact list being used for our system. We will be using our own personal phone numbers until a client is set up for this product.

What we didn’t do:

We have still not purchased a test phone, but this is not top priority since the programming is not even ready for the phone yet

We have not worked on designing a way to test the remaining power in the batteries.

Where we are stuck:

Where we are stuck the most is just trying to figure out tedious coding for our program. The program for this project is definitely the hardest part that needs to be designed. We are not even sure yet if we will be able to even re-write new programs into phone or not to turn on the emergitext system through the push of the ear phone button. The app on the users phone should work fine, it is the phone we will have to used for the button that we have concerns with.

Notes/Misc:

Team Bravo Squad- Progress Report V- Emergitext

Goals for the week:

The goals for the Emergi-Text system are primarily set towards programming this week. Tanner, Danny, and Ryan have downloaded git and will be focused on individual projects for the programming. Bryan is focusing on the production of the circuit design.  

Meeting times/dates

Tuesday 1:pm

Due to the weather we mainly communicated through email

Individual Hours:

Tanner 1 Hour

Danny 1 Hour

Ryan 1 Hour

Bryan 1 Hour

What we did:

Danny has began working toward his individual goals toward setting up the program for the contacts list in the Emergi-Text system. Danny made a youtube video for setting up the git account.

Tanner worked on the automated battery monitoring program

Ryan has begun working on the manual functionality of the system, which is basically programming the button functionality which will be turning our device on and off and then sending out emergency text

Bryan setup an initial circuit design which now need to be tested and built on a circuit board.

What we didn’t do:

Due to the weather we were not able to distribute the headphone Tanner purchased to each other. Bryan will be stripping a pair of headphones down to see how to connect the button to the device, and Ryan will be testing the button to see what steps need to be taken to program the button.

 

Team Bravo Squad – Progress Report IV: Emergi-Text

Goals for the week:

Our main focus for this last week was  to  have Git downloaded onto Danny and Ryan’s computers so Tanner could collaborate with them. Once a gitorous account was made then the fine tuning through eclipse could be made to our programming code. Bryan’s goals for the week were to come up with or find a circuit design to step down the 24v from the wheelchair to 5v to the usb cable used for the device we are using.

Meeting times/dates

Tuesday 1pm to 2pm

Individual Hours:

Tanner spent 1hr on programming as well as setting up a tutorial for our group showing steps on how to download Git and eclipse

Danny spent 1hr on creating a gitorous account

Ryan spent 1hr creating a gitorious account

Bryan spent 1hr  searching for circuit designs as well as working with a wiring a bread board for a basic set up of our circuit

What we did:

This week Tanner ordered four sets of headphones which we will be using for the push button function. Bryan checked out a breadboard to begin setting up a circuit that can be used to connect the power from the wheelchair to the Emergi-Text device. Danny and Ryan began setting up their sections of programming. Collaborations between programming is now enabled between Tanner, Danny, and Ryan. Each programmer will now program specific functions of the device.

What we didn’t do:

We have still not been able to buy a smartphone, but that is not really top priority right now. We have not been able to find a way of testing our voltage regulator circuit. We would like to be able to test our circuit without connecting it to someone’s wheelchair.

Notes/Misc:

[Team ALPHA] – Progress Report III for Prototype II: [THE TRUEVIEW CAMERA SYSTEM]

Goals for the week:

- Get the servos.

- Get Hardware and Software working together.

- Get the Kinect mounted on the servos. 

Meeting times/dates

- Saturday at Wallace Hall 4pm – 7pm 

Individual Hours:

- At least two hours per team member .

- Seth spent a lot of time at the lab room.

What we did:

- We got our part for the turbo bot printed.

-  Brady has been testing the accuracy of the measurements of the kinect. He has also been working on trig functions.

- Seth has been researching the new servos and how they communicate with the arduino.

- We finally got the servos arrived in the mail. But unfortunately one of the two servos just didn’t work. Seth, John and Tom have all tested and have decided it’s not functional, they had even rewritten an arduino library, but then Tom pulled out some servos  that are larger versions of the servos we used for prototype I and we got lucky this time, it worked. Since we had to use new servos (from Tom), we couldn’t use the parts we printed from the 3D printer. Seth had to do a new framework, he had to cut some pieces of wood and glued/screwed most of it together.

- We got almost of everything done.

What we didn’t do:

- We haven’t done the tri-fold display for the visual thing. 

Where we are stuck:

Notes/Misc:

[Three Musketeers] – Progress Report III for Prototype II: [Laser tag]

Goals for the week:

Get the GPS in, and wired in.

Get the Magnetometer to output to serial

Meeting times/dates

Monday evening during class time

Friday afternoon 2pm

Individual Hours:

James: 6 Hours debugging Magnetometer, 3-4 hours on GPS.

What we did:

James:

The GPS came in. It had a tiny connector, Instead of cutting it off and trying to solder the wires (Stranded, and never seem to stay) I built a connector to translate between it and the female pin headers I have on the wireless shield. I Did this by using one of the old style IC sockets with the flattish pins, Pulling the pins out whole, I put them in the connector and spread them out. Then I plugged male header pins into the female pins and carefully soldered them together. Covering it with hot glue gives a very nice connector.

The problem with the Magnetometer was finally solved by deleting all of the code and starting over. Something in the old code caused an issue where it would take an initial value, then just repeat the next value ad nausea. Now it is spewing out the proper value, (as rapidly as possible). I added a function to calibrate the sensor with visual feedback via an RGB led I added. Code can be implemented for both the GPS and the WiFly shield. I’ll be updating the pin definitions in the code.

To make access to the code easier I added a github repository available at https://github.com/hipcatcoolcap/LaserTag .


Where we are stuck:

Currently need to bring the data into the wifi function.

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

Goals for the week:

Per timeline: Be able to communicate with the (wireless communication) modules. Send basic Hello World messages back and forth.

Meeting times/dates

Meeting with John – Tuesday 8:20pm
Thu. Nov. 8 – 8 p.m. to 9:30 p.m.

Individual Hours:

Everyone: 3 hour meeting on Thursday

What we did:

We were able to make great progress with the wireless modules we had picked up in the past week. We used ribbon cables to attach Arduinos to two separate wireless communicators. We then loaded “server” code on one Arduino to listen for packets, and “client” code on the other to send packets every few seconds. We designed the server code to send power to a pin for one second whenever it receives a packet. We then connected this output pin to the relay/transistor setup we built last time, which made the relay click on and off (along with an LED “load”) whenever a packet was received from the client. This proved that the wireless communicators are actually capable of wirelessly communicating.

What we didn’t do:

We’ll be meeting with our business colleague next time to map out plans for the Dec. 8 open house. We’ll also continue to investigate building a case for the Raspberry Pi ensemble.

Where we are stuck:

No major issues at this point. Our next technical hurdle is using the ATtinys with the wireless modules rather than the Arduino.

Notes/Misc:

 
Team 9 – Progress Report II for Prototype II: Remote Piano Pedal

Goals for the week:

Make bracket for motor, potentiometer, frame, etc.

Meeting times/dates

Tuesday 9:00 am

Individual Hours:

Tom 6 hours, Design and build bracket

What we did:

A bracket was designed and built out of metal. The product seems to function as hoped. It holds the pieces in place firmly and provides a 1.5″ shaft to shaft distance between the motor shaft and the potentiometer shaft.

Tom spent several hours trying to figure out how to desing the hub and gears using CATIA but was unable to come up with anything usable.

What we didn’t do:

Tom spent several hours trying to figure out how to desing the hub and gears using CATIA but was unable to come up with anything usable. Also downloaded autocad and have spent some time trying to figure it out. Testing on the new h bridge chip .

Where we are stuck:

The hub can be fabricated in the metal shop on campus if a CATIA drawing can be made.

Notes/Misc:

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

Goals for the week:

  • Have a meeting with Tara to discuss how they want to control the LED lighting system remotely and start working on the remote control system.

What we did:

  •  Designed a circuit to control the LEDs as follow:

 

  • Tried to meet with Tara last week but because Tara was out of town, we rescheduled the meeting for this week

 

What we didn’t do:

  • Our plan to meet Tara last week did not happen instead we are going to meet her this week