text:
User:Fissbusta/enes100/CarHack

Link back to team Autoengineers

Give instructor top 3 project choice list
i gave professor forester my top 3 choices,, which were car hack, rubber band gun, remote hack.

Write problem statement
how is it possible for us to not spend any money on any of these projects and use the items we have already to make something brand new?

Assign Task1
i was assigned car hack. i am going to discuss possible ways this could work.I have many options to choose from and some of them include reading the cars data through the OBD (On Board Diagnostics). Getting the car to unlock and lock. Gps location. Car starting. so I have many ways to go about this. Discussing with my team would be best.

Compare actual work done to Task1
We are planning on going for starting a car, but we might go more into it than that.

Week1 Narrative
Look into how a car starting procedure works. I am going to visit my brother shop and see what i can learn about the way a car starts.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
This week its about ordering the neccessary parts for this project. I am going to be searching on some random websites to find the cheapest Wifi OBD reader we can find.

Compare actual work done to Task1
Searched on the internet to find some links to send to the professor forester.

Week2 Narrative
i needed to find some items that we can use to read the data off a car and after some research i found some. I sent some links to the prof forester. I found a couple to go from. here is the links to some i found.

$86.93 http://www.lightinthebox.com/WiFi-OBD-II-Car-Diagnostics-Tool-for-Apple-iPad-iPhone-iPod-Touch--SZC6341-_p172904.html

$79.50 http://www.hoyasource.com/wifi-obd2-auto-scanner-work-for-apple-ipad-iphone-ipod-p-90.html?zenid=jpmiqqk4f4ds42cbjt82bgptb1

$59.50 http://cgi.ebay.com/ebaymotors/Wifi-OBD2-OBD-WLAN-WIRELESS-Diagnostic-Ipad-iPhone-/160639200862?pt=Motors_Automotive_Tools&hash=item2566d7ae5e

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Now we are planning on making a guide for future teams to have a head start on this project.

Compare actual work done to Task3
we have the parts coming in. I got the REV app need for the iphone to work with that obd adapter.

Week3 Narrative
i edited the wikiversity pages for the team. i made the tutorials and i made the next steps for the future teams. we recorded a video of us testing a car solenoid to see what voltage it snaps in and what voltage it goes back. I am going to be uploading the video to youtube

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
i am planning on uploading the video of what we have already. I had performed the test of the car starter solenoid snapping at 8.5 volts

Compare actual work done to Task4
i got the video uploaded

Week4 Narrative
here is the video of the test happening. you can see that at 8.5 volts it snaps and at about .3 volts it goes back. http://www.youtube.com/watch?v=Hsou7Q8VxqQ

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Fissbusta/enes100/CarHack


text:
User:Andyn6361/enes100/CarHack

Link back to team Autoengineers

Give instructor top 3 project choice list
Project Choices: 1. Flat Screen 2. Car Hack 3. Rube Goldberg

Write problem statement
How to gather information about the car through the car's computer (I.E. mileage, fuel range, speed, rpm, etc) outside of the vehicle through a phone, ipod, computer, etc.

Assign Task1
Find several On-board Diagnostic scanners and state their functions and any differences between the tools.

Compare actual work done to Task1
I searched for On-board diagnostic scanners and presented some applicable scanners the group can purchase.

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Assigned to determine what a remote start system requires.

Compare actual work done to Task2
Figured out what wires that a remote start system needs from the car and researched radio-frequency identification tags as a method to start a car up.

Week2 Narrative
Wires include the accessory wire which links to the AC unit, the ignition wire that goes to the ignition switch, the starter wire which goes to the starter solenoid which then starts the starter, and the power wire which is connected to the car's battery. Another wire that is required for the remote start system is the receiver wire that will be connected to a receiver. In any case where there are more than one wire for a single function, a relay is required for any additional wire. All of these wires except for the receiver wire are located under the dashboard, usually right under the ignition key switch. Continued progress with researching about starting a car with a radio frequency identification tag. Commonly used on starting a car and unlocking its doors. radio-frequency identification or RFID uses small antennas and a computer chip to communicate to another RFID. These tags are considered easily hacked just by accessing it through its IP address. Problem though is that the steps to access it is undisclosed to the public. Publicly disclosing how to hack a radio frequency identification is strongly discouraged by major credit card corporations usually threatening with lawsuit. Finding a way to access these RFID tags means being able to hack into a credit card and have access into someone's credit card account.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Research on a central system that will be connected to all wires and transmit the message from the receiver to the other wires to start the vehicle.

Compare actual work done to Task3
Researched about the starter solenoid and the current that activates the solenoid and the current to return the solenoid to its original state.

Week3 Narrative
I connected the starter solenoid to the power supply and started to turn the coarse voltage dial and the current dial. As I turned the dials the voltage meter showed an increase in voltage and ampere. At an average of 8.6 volts and 0.45 amps the starter solenoid is triggered and the spring contracts. Once the solenoid was contracted, I turned both dials down and the spring expanded at an average of 0.5 volts and 0.04 amps. After I recorded the current and ampere of the solenoid, I researched the holding and actuate current on the internet. Once I read some of the documents, it was determined that the holding current and actuate current varies from each manufacturer but the holding current is actually the current that keeps the solenoid on and the actuate current turns off the solenoid.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Revise guide to making a remote start system

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User:Andyn6361/enes100/CarHack


text:
User:Mderrick4950/enes100/CarHack

Link back to team Autoengineers

Write problem statement
I want to design a project with my team that allows a portable electronic device to read diagnostics on a car and be able to start it wirelessly.

Assign Task1
Find out how remote starts work and do research on the topic of OBD ports.

Compare actual work done to Task1
Basically did what I said I would.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Order a Bluetooth receiver to catch a signal from a phone or other portable device that has Bluetooth connectivity.

Compare actual work done to Task2
Ordered bluetooth receiver from online source.

Week2 Narrative
I ordered the Bluetooth receiver from an online source. Also, I did much more online research and decided that Bluettoth was probably the best thing to use for this project.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Test Bluetooth receiver.

Compare actual work done to Task3
Tested Bluetooth device.

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Mderrick4950/enes100/CarHack


text:
Engineering Projects/Bridges/Howard Community College

Howard Community College is going to build model bridges and break them!
 * /fall2011/
 * /spring2012/


text:
User:Zchill/enes100/Ham

Back to Veteran Bacon team page.

Give instructor top 3 project choice list
I gave the Professor the top three choices and out of them he assigned me HAM radio.

Write problem statement
Setup a Ham radio, get licensed and transmit a signal.

Assign Task1
Task one was to find out what we wanted to do with the HAM radio. Due to us all having various experiences in radio we wanted to find out what we could build a project around. Our first task was a little nebulous, but we came in on Monday with a lot of ideas on how to push the project forward.

Compare actual work done to Task1
The work we did was to make a directionless project come into focus. We came in on Monday with ideas on how to proceed and developed a problem statement out of the research we came up with.

Week1 Narrative
We looked at and inspected which radio kits worked and recorded them in our notebooks, and looked at setting up the Jupiter antenna to see if we could set it up and get it attached to a radio.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
I am examining the manual of the radio and finding out if what we want to do on the project can work on that radio. Nick is researching what we will need to answer in the FCC test, and Chuck is looking at the antenna setup.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Zchill is a positive force within the HAM radio project. He is always prepared and always completes the tasks assigned to him from the team. Zchill has continually contributed useful information and materials to the progression of project. CFurby 19:07, 10 October 2011

Assign Task4
Task four is to study for and take the FCC test on Sunday.

Compare actual work done to Task4
Due to scheduling conflicts with homework for other classes we as a group decided not to take the test. It wasn't an easy call to make, but as this class is focused more on documentation than it is accomplishment we decided we needed to focus more on our other classes.

Week4 Narrative
We had gotten the radio working (barely) last week and with the test falling through and having no class Monday apathy took over and we didn't meet and didn't finalize our project.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

10/5/0 ... saw some editing of your page, creation of next team's page, but "we" shows no transparency ... is merely a report 1sfoerster 13:50, 17 October 2011 (UTC)

title: User:Zchill/enes100/Ham


text:
Engineering Projects/Bridges/Howard Community College/fall2011

 * /501_DAS/
 * /501_DAS_2/
 * /501_DAS_3/
 * /550_ESS/


text:
Engineering Projects/Bridges/Howard Community College/fall2011/501 DAS

The goal of this form is to provide a standard project format that practicing engineers can use to compare project documentation with while assessing these projects. It is called the "Team Done Form" because it should be filled out by the end of the project. Starting with this format helps make the done process much easier.

Projects are never "done" or "finished." But time runs out. Classes end. So this form has nothing to do with project success. This "Done" form can simply state "Nothing was done." If the section below does not fit your project, delete everything but still leave in the section header.

Problem Statement
Put the last negotiated problem statement with the instructor or client of the project here.

Team Members
Put each team members name here with links to their personal page here. Real names do not have to be used.

Summary
Put an overall, one paragraph summary here with links to the team weekly reports.

Poster
Put a graphic in wikimedia, include the graphic here or link to it here. The graphic should be suitable for creating a traditional project poster.

Story
Tell a story of the project. Describe how split up, what the obstacles were, what testing was done, what informal decisions were made, what assumptions were made, what the results were. This is a longer version of the summary with links to all the details collected associated with the project. These links could be to software, links to videos, links to project pages with pictures, etc. Think of the story as a summary of the team weekly reports on one long page rather than a short paragraph like the summary.

Decision List
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
Figuring out what to purchase, what to build, what everything costs is a huge part of engineering. Typically there is a list of materials in stock, materials that are ordered, materials that should be ordered next time there is money, materials that have not been fully justified. These issues are part of healthy management of the engineering lab but are associated with a particular college. The detail needs to be published in this "Done" form. However in the project root, just a list of materials is necessary.

Software List
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
Time estimates and actual time consumed measurements helps justify salaries (grades). The only way to gain respect for estimated project time and costs is to practice.

Tutorials
Most projects consist of making instructions to jump start the next team, shrink the learning of tools and software to the minimum, advice on where to purchase materials, how to assemble, etc. Tutorials modified or created are described here with links.

Next Steps
If this is not filled out, the next team may have to repeat each of your steps just to figure out what the next step is. It is best to write this immediately at the end of the project while creating the summary, poster, presentation, and story.

Subjective Critera
While reading these sections, practicing engineers are building up the following impressions about the document. So the following categories are more subjective:

Repeatablitly
Is there enough detail to repeat the work?

Integrity
Proving something doesn't exist or doesn't work usually requires exhaustion. Simply saying "it can not be done" is like challenging a pro basketball player (engineer) to one-on-one basketball (find a solution). It does not inspire respect. All the different ways respect is created can be found throughout the wikibook General Engineering Introduction.


text:
User:Dzhang2680/enes100/bridges

Link to project DAS team page.

Give instructor top 3 project choice list
I chose three top topics from the Engeering Project page. The instructor put me to Bridges Project as my fist option.

Write problem statement
The goal of the project is to build a spaghetti bridge which can be loaded as much weight as possible. What is the basic design for a bridge to load the most weight? How to connect spaghettis?

Assign Task1
I have two teammates. Angele and Syed will do research for the design of bridges and I am responsible for the software of designing bridges. Besides that, we will all do tests on connecting the spaghettis.

Compare actual work done to Task1
We did tests and found out a way to connect the spaghettis. However, we didn't get a chance to practise it. So we just have a basic thought about it but still can't work on actually building the bridge.

Week1 Narrative
I was looking all over the place, trying to find out what software I can use for designing bridges. Since I didn't have any software background and I never had experience of building bridges, it was hard for me to figure out which software was useful. I looked up online, it seems like there are a lot of similar softwares, some of them are free and some are not. It is not really helpful. Then I start looking through the previous reports of bridges project in HCC. I found out one team, they used Dreamweaver software. I talked to my teammates. They had no idea how to use it. Eventually, we decided to use some other software we were familiar with if needed. Then, I tried to find out a way to connect the Manicottis which will be the arch part of the bridge. Manicottis are so hard that they are really hard to shape. So I was thinking of soften them by boiling them. Since we don't have stoves in Engineering room, we decided to use microwave to heat up water. However, the temparature of the water which was heat by microwave was not hot enough. The Manicottis took a really long time to soften and it seeems to be unsafe if I keep on heating it up with microwave. After I went back home that day, I was wondering around in my house, trying to find a better way to heat up water. Then I found it, rice cooker. I did a test to boil water with rice cooker. It was way faster, safer and more effective. It shortened the time we soften the Manicottis. Also, I wanted to see which way to soften the Manicottis was better, boil the whole piece? or just one end of it. I found out that soften the whole piece was better than only soften one end, because it was easier to get broken by softing partly. Since we were thinking of shaping the Manicottis which can be easy to glue. I want to see if they will get harden again once they get boiled. So after the Manicottis got soften, I put them in room temparature for 4 or 5 hours, they were still soft. Then I put them into fridge. They didn't get harden too much the next day and they became very brittle but not as strong as before. Therefore, I think the softern Manicottis can be used to connect the hard ones by being hidden inside of the tubes of the hard ones. I don't know if it is practical. Still need to test when we actually build the bridge.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Actually build the bridge. And wait for more problems expose.

Compare actual work done to Task2
We started working on building the bridge this week. Some problems came up while we were building the bridge. We decided to start over again in order to solve the problems and build a high quality bridge.

Week2 Narrative
This week we were focusing on actually building the bridge. We decided to build a smaller scale bridge first by using skinny straight spaghettis as the arch part. I picked ten spaghettis as one group and cut them the same length. Then I used tape to keep the spaghettis stay and glue both ends of each group of spaghettis. It was hard to cut the spaghettis into the same size since we didn't have exact measurement for the bridge. I just picked one spaghetti as sample and compared it to other spaghettis to make them about the same size.Sometimes I wanted to do it faster, so I cut several spaghettis at the same time which would break the spaghettis. It was not a good way to size the spaghettis like this. We have to have exact measurement. And maybe draw the bridge on a big piece of paper first which is the same size of the bridge we are going to build. Then we can have a better scale to build it. The other problem was when I glue the spaghettis, the epoxy took a long time to dry up and since pieces of spaghettis were not tied to one another, when the glue dried, the spaghettis didn't really glue together. It was just individual spaghetti with glue on it. The bridge would not be strong if we glued it this way. Therefore, we decided to use Ditalini pasta. It is a kind of pasta with short tubes like elbows, but shorter and without a bend. It will be much easier to connect the pasta by using Ditalini type. We did presentation in the class. About the glue part, I thought glue gun might be better then epoxy because it dried faster. However, Professor Foerster suggested us not to use glue gun because it is not strong enough and he said he saw a lot of people tried and failed at the end and epoxy is the best one. It is good to know similar experiences people had in the past, but I still wanted to try out and test on glue gun. Maybe I will do the glue gun to connect and fix the pasta first, and then code epoxy on top to make it stronger. At the same time, like what I mentioned before, I will have an exact measurement and draw the same size bridge on a big piece of paper first, and then follow the paper to build the bridge. It will be more accuate and easier. Also, I went online trying to look for the best proportion of the height and length for an arch bridge. I found this website and it mentioned that the higher the bridge you want to build, the stronger the middle truss member part you want to make. Website referances :Height and length proportion. In the meanwhile, I was looking at bridge test software too. I couldn't find any free testing software.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Sketch a same size bridge on a big piece of paper. Figure out exact measurement for every part of the bridge. Find right type of spaghetti or pasta we are going to use.

Compare actual work done to Task3
We focused on designing the bridge this week instead of drawing on a piece paper.

Week3 Narrative
This week I focused on designing the bridge instead of drawing on a piece of paper, because I have to figure out the best propotion of measure and the design first. Professor Forester suggested us a bridge design software which is from John Hopkins University. I can design bridges on the website and when I load on the bridge, it can calculate how much weight is loaded on each truss on the bridge. Then Syed found another bridge design software called West Point Bridge Design Software. I can an arch bridge and test it how much weight it can actually bear. I will keep explore this software, see if there is more I can find out. The only problem is both softwares are only two dimensionals, and we can't put much bridge detail on it. We decided to use half meter long spaghettis as the truss members in the middle. However, from the internet, the only place I found this length of spaghettis is in UK. I will keep looking, see if I have more found out.

Link to Bridge Designer from John Hopkins

Link to West Point Bridge Designer

Link to Meter long spaghetti

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Have an agreement on how to connect spaghettis and pasta and maybe do tests about using glue guns to connect them. Keep looking for the kind spaghettis we need.

Compare actual work done to Task4
I didn't get a chance to test gluing the spaghettis.

Week4 Narrative
This week, we tried to finish project 1 and prepare for project 2. All of the team members decided to stay on the same team to continue building the spaghetti bridge. Since we will focuse on actually building the bridge in project 2, the materials have to be prepared ahead. I found the meter long spaghetti online. The only website I found which sells more than half meter long spaghetti was one site called Guidetti from UK. They don't have price on the website and I couldn't shop online. So I emailed them to ask the price and let them know we wanted to order. However, I haven't heard from them yet. For the tube pasta of the arch, Angele has some and we will purchase more for future. Since we have the same team for the next project and we are clear about what we are going to do, we didn't spend much time to build up the team.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
I will stay on the spaghetti bridge project.

title: User:Dzhang2680/enes100/bridges


text:
User:Ablomme2125/enes100/glorious

Link back to Glorious

This is where work on my Hover Craft project exists.

Give instructor top 3 project choice list
My 3 choices consist of Gas engines, Electric Car, and Car Hack. I was put into hovercraft because its a combination of car hack and electric car because we have to use electric motors to propel the hovercraft, and car hack because we have to hack the arduino to make it do what we want it to do. Which is we want the arduino to accept a USB remote control.

Write problem statement
Make a HoverCraft that can be controlled with a remote control that is controlled by RF signals and have the arduino on the hovercraft so we can have it host the receiver.

Assign Task1
My assignment for the week is to come up with the overall functionality and design of our hovercraft. The reason i picked this job is because i like anything dealing with mechanics and design.

Compare actual work done to Task1
The work i have done this week consists of drawing a schematic that shows the layout and position of the motors, fans, and skirting. The design i came up with has an oval shaped platform that has a hole in the bottom that houses the induction fan that will be from an old computer. This will push the air down underneath the rubber skirting creating an air cushion. Then on top of the platform/deck it will house one central motor to control the angle of the fans to make the hovercraft turn. Then attached to the central motor, 2 motors with fans on them, these will control the propulsion of the hovercraft. Then the propulsion motors will be connected to the central motor by 90 degree gears that will convert the central motors power from horizontal to vertical. There will be a picture posted later.

Week1 Narrative
Started first initial design concept. Found a flaw in the design upon completion of the design. The way i had the turning mechanism on the hovercraft would not cause it to turn. The way i had it set up is i was going to have it so when you turn it would pivot, the propulsion motors on the back, up or down. I then realized that it would be much simpler if i could just adjust the amount of current going to each motor that way one would be pushing more than the other, causing it to move forward and turn.

Week1 Peer Review
I found that James is doing a great job with the team wiki page, the only thing i think that could be improved is adding more pictures of the parts were using and some links of the resources were using to figure everything out. Other than that everything looks great to me so keep up the work James.

Assign Task2
What i plan on doing over the weekend is refining our design concept, im going to try and come up with a more efficient way to turn the hovercraft and to power its propulsion mechanisms.

Compare actual work done to Task2
What i have done is come up with a more efficient design concept that gets rid of the added weight from the central and the other motors. Ive decided that having a device adjust the current to each motor when we press the direction would be a better route that would allow it to turn easier.

Week2 Hovercraft Project
What i did on this new concept is, i add a different fan for the lift of the Hovercraft, and just have stationary propulsion motors. I found from testing, that the turbine fans work the best for the lift because as the pressure builds up beneath the craft, it wants to escape through where it came. Using a turbine eliminates that because the fan is constantly forcing air into the bottom and there is no where for the air to escape. Then by having the fans on top of the platform to push it stationary, it allows easier turning and maneuverability.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Im going to work with the Arduino to see if I can get it to operate with the Hovercraft.

Compare actual work done to Task3
Instead of using the arduino to control the functions of the hovercraft, I decided that it would be a better idea to use the Curcuit boards off of the RC cars we received in class.

Week3 Narrative
I decided To use 2 Different RC Cars to control the Propulsion and lift motors via remote control. I first disassembled the small green car , then upon doing that i found that the green car used an electromagnet, that would change its polarity (depending on which way the user turned on the remote)that would then repel a magnet that was attached to the front suspension of the car. Causing it to turn.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
What we plan on doing for week 4 is to try out some different power supplies because using regular C 9volt batteries drains them too fast. So we need to explore different alternatives as far as power is concerned. Mr. Forester has some 11.2 V batteries that are lithium Poly, so they should last longer. But we will only know with future tests.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Ablomme2125/enes100/glorious


text:
User:CFurby/enes100/Ham

Link to project Veteran Bacon team page.

Give instructor top 3 project choice list
I submitted 3 selections from the provided project list and was assigned to the HAM Radio project.

Write problem statement
I will set up an operation HAM radio system.

Assign Task1
Our first task, as a group, was to build general knowledge of HAM radios and brainstorm.

Compare actual work done to Task1
We built a general knowledge of HAM radios and their operation. We found that their operation is regulated by the FCC.

Week1 Narrative
This week we started diving into the parts cabinets a bit deeper. We acquired a Radio JOVE antenna assembly kit, six Elenco AM/FM radio sets, and their accompanying manuals. We tested all of the radio sets and found that four of them were fully operational, while the last two would not operate at all.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
I acquired a a copy of the Radio JOVE Assembly Manual to study it's construction and operation. I want to learn whether or not it is feasible to use the JOVE antenna combined with the Elenco AM/FM-108 to build an operation HAM station. I need to learn how it is set up for use, how I can attach it to the Elenco Radio circuit board, and whether or not I will require any other equipment.

Compare actual work done to Task2
I studied the Radio JOVE assembly manual to find out it's compatibility with the ELENCO AM/FM-108 radio.

Week2 Narrative
After doing some studying on our equipment's operating capabilities, we decided that it wasn't quite possible to combine the Elenco AM/FM - 108 Radio Set with the Radio JOVE Antenna Assembly. So we decided to move in a different direction by attempting to build a World War II Foxhole Radio. The first thing we did was assign each member to collect materials. Nick Delaney was to bring in a toilet paper tube to help construct an inductor as well as a pair of headphones to splice into the circuit. Zach Hill was to acquire another pair of headphones and a coat hanger. I purchased a a pack of razor blades, which I blued, for construction of the radio signal detector.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
We assigned to ourselves the task of studying for the upcoming FCC licensing test.

Compare actual work done to Task3
After collecting a wood board, toilet paper tube, paper clips, 24 AWG wire, metal coat hanger, razor blades, pencils, and thumbtacks, we decided it was time to start the construction of our World War II Foxhole radio.

Week3 Narrative
During this week I started to build the WWII Radio. I clipped with head off of the coat hanger and straightened it out to serve as the radio antenna. Then spooled the 24 AWG wire around the toilet paper tube 101 times to build the inductor. Zach Hill broke apart the pencil as to have access to it's lead to use on the blued razor blade to act as the radio detector. Then I stripped different segments of wire to connect all the components and attached them to the wood board using thumbtacks. I attempted to splice Nick Delaney's headphones into the circuit but, it proved to be too difficult because the headphones used a USB connection thus, having far too many internal contacts to utilize. Our first test of the radio was a complete failure. No noise, no reception, no operation.

Since we did not receive any signal, I decided to measure the connectivity between all the components and use a different pair of headphones with a more simple design. Connectivity between all the radio component was measured using the OHM function of a multi-meter. All connections tested positive for connectivity.

After removing the old pair of headphones, we attached a different set that contained only two contact wires after clipping the attachment plug off. I connected one end to a wire leading to the detector and the other I attached to the inductor/ground paperclip. Rather than using metal piping as a ground, this time we used the ground on an electrical component test bench.

We tested the radio after modifying it and came up short once again, although, we did make progress. During the test we received a small amount of static through the headphones. The small static sound insures us of the radio's proper construction but, still needs some tuning. To tune the radio we will have to add more spools in the inductor. We will use a different tube and smaller wire to build a larger conductor in the coming week.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

0/0/0 .. can not see any work anywhere 1sfoerster 13:50, 17 October 2011 (UTC)

title: User:CFurby/enes100/Ham


text:
Wikiversity:Candidates for Custodianship/Abd (full custodian)/crat chat

This subpage is for open and frank discussion among the WV 'crats. If you're not a WV 'crat and would like to comment, please use the talk page.

Roll call

 * I'm here, but still trying to make sense of the nature of the vote. --SB_Johnny talk 17:37, 19 September 2011 (UTC)
 * I've added my 'neutral' comment - but have limited time/net access over next week or so and haven't reviewed the candidacy or comments. Would prefer not to be involved as 'crat mainly because I am a previous mentor and have been involved. -- Jtneill - Talk - c 22:25, 19 September 2011 (UTC)

Ruminations

 * There seems to be one group voting that are new users that have cultivated relationships with Abd, another group that are veterans of past WV dramas, and yet another group that knows Abd from "interwiki" experience. These seem in a certain respect to be 3 entirely different communities, which provides some food for thought. --SB_Johnny talk 17:37, 19 September 2011 (UTC)

Personal opinions

 * Past experience leads me to believe that Abd is prone to going off the rails when he has a personal stake in an issue or conflict, and I simply can't trust him to be responsible when he finds himself out on a limb. --SB_Johnny talk 17:37, 19 September 2011 (UTC)

Opinions on the consensus

 * I'm genuinely and honestly unsure at this time. --SB_Johnny talk 17:37, 19 September 2011 (UTC)


text:
User:Egm6321.f11.team1.zheng.zx/personal place/HW2

= R*2.3 Show that the equation is linear in $${y}'$$ but an N1-ODE in general = Show that (2)p.7-6 is linear in y', and that (2) is in general an N1-ODE. But (2） is not the most general N1-ODE as represented by (1)p.7-6. Give an example of a more general N1-ODE.

Given
General N1-ODEs:
 * {| style="width:100%" border="0"

$$  \displaystyle G({y}',y,x) =0 $$     (3-1) (1)p.7-6 Particular class of N1-ODEs: Linear in y'
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle M(x,y)+N(x,y){y}' =0 $$     (3-2) (2)p.7-6
 * style="width:95%" |
 * style="width:95%" |
 *
 * }

Find
1)Show that (2)p.7-6 is linear in y' 2)that (2) is in general an N1-ODE. 3)Give an example of a more general N1-ODE.

1) Show that (2)p.7-6 is linear in y'
For a operator to be linear, it has to satisfy the following:
 * {| style="width:100%" border="0"

$$  \displaystyle F(\alpha u+\beta v)=\alpha F(u)+\beta F(v) ,\forall \alpha ,\beta \in \mathbb{R} $$     (3-3) Then we begin to check, Let Y = y',thus
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle G(x,y,Y)=\underbrace{M(x,y)}_{(1)}+\underbrace{N(x,y)Y}_{(2)} $$     (3-4) for (1)  We can regard this as a constant M; for (2)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,y,Y)=N(x,y)Y $$     (3-5)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,y,\alpha u+\beta v)=N(x,y)(\alpha u+\beta v)=\alpha N(x,y)u+\beta N(x,y)v $$     (3-6)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle \alpha F(x,y,u)+\beta F(x,y,v)=\alpha N(x,y)u+\beta N(x,y)v $$     (3-7) So, Formula 3-6 is equal to 3-7, i.e.:
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,y,\alpha u+\beta v)=\alpha F(x,y,u)+\beta F(x,y,v) $$     (3-8) Then we can say that 3-2 i.e. (2)p.7-6 is linear in Y = y'
 * style="width:95%" |
 * style="width:95%" |
 *
 * }

2) Show that (2) is in general an N1-ODE
For a operator to be linear, it has to satisfy the following:
 * {| style="width:100%" border="0"

$$  \displaystyle f(\alpha y_1+\beta y_2)=\alpha f(y_1)+\beta f(y_2) ,\forall \alpha ,\beta \in \mathbb{R} $$ Then we begin to check, So,
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle f(x,\alpha y_1+\beta y_2)\neq \alpha f(x,y_1)+\beta f(x,y_2) $$     (3-12) CONCLUSION: (2) is in general an N1-ODE
 * style="width:92%; padding:10px; border:2px solid #8888aa" |
 * style="width:92%; padding:10px; border:2px solid #8888aa" |
 *
 * }

3) Give an example of a more general N1-ODE
(2） is not the most general N1-ODE as represented by (1)p.7-6.
 * {| style="width:100%" border="0"

$$  \displaystyle G(y',y,x)=0 $$     (3-13) A more general N1-ODE example can be:
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle M(x,y)+N(x,y)(y')^n=0 $$     (3-14) n is the power of y' This problem is solved by ourselves Contributed by Zexi
 * style="width:95%" |
 * style="width:95%" |
 *
 * }

= R*2.4 Verify that $$(4x^7+\sin y)+(x^2y^3)y'=0$$ is a N1-ODE =

Given

 * {| style="width:100%" border="0"

$$  \displaystyle (4x^7+\sin y)+(x^2y^3)y'=0 $$     (4-1)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }

Find
Formula 4-1 is a N1-ODE

Solution
1) The highest order of derivative is 1 and there is only one dependent variable in equation so it's a X1-ODE. (X can be L or N) 2) Verify Non-linearity For a operator to be linear, it has to satisfy the following:
 * {| style="width:100%" border="0"

$$  \displaystyle F(\alpha u+\beta v)=\alpha F(u)+\beta F(v) ,\forall \alpha ,\beta \in \mathbb{R} $$     (4-2) Then we begin to check,
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,y)=(4x^7+\sin y)+(x^2y^3)y' $$     (4-3)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,{\alpha}{y_1}+{\beta}{y_2})=4x^7 + sin({\alpha}{y_1}+{\beta}{y_2}) +{x^2}({\alpha}{y_1}+{\beta}{y_2})^3({\alpha}{y_1}+{\beta}{y_2})' $$     (4-4)
 * style="width:95%" |
 * style="width:95%" |
 *
 * }
 * {| style="width:100%" border="0"

$$  \displaystyle {\alpha}F(x,{y_1})+{\beta}F(x,{y_2})={\alpha}(4x^7+sin{y_1}+x^2{y_1}^3{y_1}')+{\beta}(4x^7+sin{y_2}+x^2{y_2}^3{y_2}') $$     (4-5)
 * style="width:95%" |
 * style="width:95%" |
 *

 * }
 * {| style="width:100%" border="0"

$$  \displaystyle F(x,{\alpha}{y_1}+{\beta}{y_2})\neq {\alpha}F(x,{y_1})+{\beta}F(x,{y_2}) $$     (4-6) So, it's nonlinear. CONCLUSION: The equation is a N1-ODE This problem is solved by ourselves Contributed by Zexi
 * style="width:92%; padding:10px; border:2px solid #8888aa" |
 * style="width:92%; padding:10px; border:2px solid #8888aa" |
 *

 * }

= R*2.10 Verify the solution for the N1-ODE =

Given

 * {| style="width:100%" border="0"

$$  \displaystyle y(x)=\sin ^{-1}(k-15x^5) $$     (10-1) (1) p.10-4
 * style="width:95%" |
 * style="width:95%" |
 *

 * }
 * {| style="width:100%" border="0"

$$  \displaystyle \frac{d\phi (x,y(x))}{dx}=75x^4+(\cos y)y'=0 $$     (10-2) (2) p.8-6
 * style="width:95%" |
 * style="width:95%" |
 *

 * }

Find
Verify that 10-1 is the solution for the N1-ODE 10-2

Solution
We just need to put 10-1 into 10-2 and see if the equation is still in effect.
 * {| style="width:100%" border="0"

$$  \displaystyle \frac{d\phi (x,y(x))}{dx}=75x^4+(\cos (\sin ^{-1}(k-15x^5)))(\sin^{-1}(k-15x^{5}))' $$     (10-3) We can easily verify that the equation 10-3 is equal to 0 with the help of Matlab. i.e.
 * style="width:95%" |
 * style="width:95%" |
 *

 * }
 * {| style="width:100%" border="0"

$$  \displaystyle 75x^4+(\cos (\sin ^{-1}(k-15x^5)))(\sin^{-1}(k-15x^{5}))'=0 $$     (10-4) Here are the codes:
 * style="width:95%" |
 * style="width:95%" |
 *

 * }

syms x syms k syms y y=asin(k-15*x^5); dy=diff(y,x); 75*x^4+cos(y)*dy

This problem is solved by ourselves Contributed by Zexi


text: File:Eqn 1.gif

title: File:Eqn 1.gif


text: File:Eqn 2.gif

title: File:Eqn 2.gif


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 tj2

very good 100 points each 1sfoerster 19:08, 19 September 2011 (UTC)


text: File:Eqn 2.11.1.gif

title: File:Eqn 2.11.1.gif


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 qpa

 * Problem Statement can not be understood.
 * 0/10 points

 * Summary
 * What is the task at hand?
 * Popping all of one color first is an approach. Rows first, columns first is another, but no conclusions were drawn from doing this.

10/10 points

 * Poster
 * 0/10 points ... there isn't one

 * Story ... story of interruption by the professor? another random goal of the project?
 * 0/10 points ... there isn't one

0/10 points
 * Poster .. none

 * Decision List
 * how you split the project up is listed, but no results

10/10

10/10
 * Materials

10/10
 * Software

10/10
 * Time

10/10
 * Tutorials

 * Next Steps
 * are none

0/10

 * 60/100 total 1sfoerster 19:24, 19 September 2011 (UTC)


text:
User talk:Epropplerp/enes100/poppit

0/0/0 nothing was done here 1sfoerster 19:27, 19 September 2011 (UTC)

title: User talk:Epropplerp/enes100/poppit


text:
User talk:Qchi8375/enes100/poppit

0/0/0 nothing was done here 1sfoerster 19:27, 19 September 2011 (UTC)

title: User talk:Qchi8375/enes100/poppit


text: Category:Aircraft

title: Category:Aircraft


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 DE

 * Problem Statement 10/10 points

 * Summary 10/10 points

 * Poster 10/10 points

 * Story 10/10 points

 * Poster 10/10 points

 * Decision List 0/10 ... nothing here

 * Materials 10/10

 * Software 10/10

 * Time 10/10

 * Tutorials 10/10

 * Next Steps 10/10

 * 90/100 total 1sfoerster 19:30, 19 September 2011 (UTC)


text:
User talk:Epcole/enes100/poppit

10/10/10 you pushed the project forward a little bit by attempting processing color reading 1sfoerster 19:36, 19 September 2011 (UTC)

title: User talk:Epcole/enes100/poppit


text:
User talk:Truongdat120891/enes100/poppit

10/0/0 ... can not see what you did on this page, no commitments, nothing you claim to have accomplished 1sfoerster 19:37, 19 September 2011 (UTC)


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/502 ZNC

 * Problem Statement 10/10 points

 * Summary 0/10 points .. there is no summary of chunking strategies and success/failure/unsure nature

 * Poster 10/10 points

 * Story 10/10 points

 * Poster 10/10 points

 * Decision List 0/10 ... nothing here other than we are playing the game ... no differentiation or comparison if everyone was doing the same

 * Materials 10/10

 * Software 10/10

 * Time 10/10

 * Tutorials 10/10

 * Next Steps 10/10

 * 80/100 total 1sfoerster 19:43, 19 September 2011 (UTC)


text: File:Eqn 2.17.3.gif

title: File:Eqn 2.17.3.gif


text: File:Plot of y1 and y2.PNG

title: File:Plot of y1 and y2.PNG


text: File:Eqn 2.17.2.gif

title: File:Eqn 2.17.2.gif


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 cjf

 * Problem Statement 10/10 points

 * Summary 5/10 points .. no conclusions, no descriptions of chunks

 * Poster 0/10 points

 * Story 10/10 points

 * Poster 0/10 points

 * Decision List 0/10 ... nothing here

 * Materials 10/10

 * Software 0/10

 * Time 0/10

 * Tutorials 10/10

 * Next Steps 10/10

 * 45/100 total lots of words, no fruit ... chunks top eliminating columns, but no analysis .. team memmbers listed twice

1sfoerster 19:51, 19 September 2011 (UTC)


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 superior 4

 * Problem Statement 10/10 points

 * Summary 0/10 points .. no conclusions, no descriptions of chunks

 * Poster 0/10 points

 * Story 5/10 points .. good story, no details

 * Poster 0/10 points

 * Decision List 0/10 ... nothing here

 * Materials 10/10

 * Software 10/10

 * Time 0/10 ... should be recording time in notebooks, all have to do is add it up

 * Tutorials 0/10

 * Next Steps 10/10

 * 45/100 total

1sfoerster 20:02, 19 September 2011 (UTC)


text:
User talk:Mbaig7172/enes100/poppit

10/10/10 good job 1sfoerster 20:04, 19 September 2011 (UTC)

title: User talk:Mbaig7172/enes100/poppit


text:
User talk:Rhorton4549/enes100/poppit

10/10/30 ... great screen capture ... video upload to youtube 1sfoerster 20:05, 19 September 2011 (UTC)

title: User talk:Rhorton4549/enes100/poppit


text:
User talk:Palluri9407/enes100/poppit

10/10/10 ... good job 1sfoerster 20:07, 19 September 2011 (UTC)

title: User talk:Palluri9407/enes100/poppit


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 prgm

100 points ... excellent job ... glad you included a link to the source code on the first page 1sfoerster 20:14, 19 September 2011 (UTC)


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/550 fke

 * Problem Statement 5/10 points .. don't change to "Going to Do"

 * Summary 0/10 points .. what was the average?

 * Poster 0/10 points .. others have posted graphics that did not get deleted

 * Story 0/10 points .. don't see one .. need longer version of summary

 * Decision List 0/10 ... nothing here

 * Materials 10/10

 * Software 10/10

 * Time 5/10 ... hours, don't force reader to do math in their head

 * Tutorials 10/10

 * Next Steps 10/10

 * 50/100 total

1sfoerster 20:19, 19 September 2011 (UTC)


text:
User talk:Felhariri3680/enes100/poppit

0/0/0 .. nothing done here 1sfoerster 20:21, 19 September 2011 (UTC)

title: User talk:Felhariri3680/enes100/poppit


text:
User talk:Esmith1993/enes100/poppit

10/10/10 ... strange chunking strategy, creative strategy, unusual strategy 1sfoerster 20:23, 19 September 2011 (UTC)

title: User talk:Esmith1993/enes100/poppit


text:
User talk:K.saunders/enes100/poppit

 * using team form instead of user form
 * recording strategies, but not results of strategies .. data, statistics
 * 0/10/0 1sfoerster 20:24, 19 September 2011 (UTC)

title: User talk:K.saunders/enes100/poppit


text:
User talk:Anton1102/enes100/poppit

10/0/0 ... can see nothing personal committed to, nothing personal done 1sfoerster 20:34, 19 September 2011 (UTC)

title: User talk:Anton1102/enes100/poppit


text:
User talk:RyanPak/enes100/poppit

10/5/0 .. can see you agreed to do something, but no discussion of it 1sfoerster 20:35, 19 September 2011 (UTC)

title: User talk:RyanPak/enes100/poppit


text:
User talk:Wfalak/enes100/poppit

10/5/0 ... can see attempt at work .. but no real work 1sfoerster 20:36, 19 September 2011 (UTC)

title: User talk:Wfalak/enes100/poppit


text:
User talk:Esmith1993/enes100/fanwing

10/0/0 nothing for fanwing committed to over the weekend 1sfoerster 20:52, 19 September 2011 (UTC)

10/5/0 no peer review, no narrative, please delete instructions if you are not going to follow them in the future, do not talk about blueprints or drawings without links to them 1sfoerster 18:46, 26 September 2011 (UTC)

Eric really showed keen interest in finding ways to control the fanwing. He got the controller for the fanwing from one of the scrap airplane which could be used to steer the fanwing. W 18:25 26 September 2011

Eric had a great idea to use old computer fans and use them in the squirrel cage to create lift for the fanwing. M 21:07 02 October 2011 (UTC)

0/0/0 ... nothing posted here 1sfoerster 18:40, 3 October 2011 (UTC)

10/10/0 .. good .. get started .. 1sfoerster 17:35, 11 October 2011 (UTC)

Good job explaining how we will be able to maneuver the fanwing and where we will place the electronics. M

18:34, 16 October 2011 (UTC)

10/10/10 ... see me about the motor ... need to control motor with arduino ... I can see the electronic speed control .. need some more documentation ... like name of parts, source of parts, part cost for more pushing project forward points 1sfoerster 20:04, 17 October 2011 (UTC)

Well done and best of luck for building the cage. Waleed 23:00 11/6/2011

Erik worked on the motor and was pretty successful in figuring out its mechanism and how its going to be placed and would work in the Fanwing. Waleed 12:50 23 October, 2011 (UTC)

Erik, brought up the idea to slant the wing at a degree so the wing sticks out more. He also soldered the wire for the electrical wires together for the steering mechanism. DO you think you can get the steering mechanism working by next week? Mirza 20:25 23 October 2011 (UTC)

10/10/5 .. not clear what gathering materials has to do with blueprint .. if you created a drawing, upload it and link to it, shoot a screen shot of it .. create instructions if you are learning something 1sfoerster 18:43, 24 October 2011 (UTC)

Just letting you know that not much was done on Wednesday so you didn't miss anything. We have alot of work to do. Mbaig7172

Good job explaining how the wing would fit and what materials would be needed to create the wing.Mbaig7172 October 30 2011 22:20 (UTC)

Good job for helping us figure out the body shape and its structure.

0/0/0 .. no week 2 to grade 1sfoerster 19:37, 31 October 2011 (UTC)

Good idea to use the old styrofoam plane as the body of our fanwing.

Mbaig7172 22:40 6 November, 2011 (UTC)

Well done and best of luck for building the cage. Waleed 23:00 11/6/2011

10/10/0 .. just see a report on a team decision, but no information to back up the decision 1sfoerster 20:27, 7 November 2011 (UTC)

I know you were absent but all we did was individual assignments. We did not have much time to work on project in class.

Mbaig7172 10:19 13 November 2011 (UTC)

Good job for putting your effort in this project. Waleed 22:10. 13 November, 2011

10/10/5 ... I made ... ?? no drawing, no pictures, nothing physical .. no idea what you are doing 1sfoerster 21:49, 14 November 2011 (UTC)

title: User talk:Esmith1993/enes100/fanwing


text:
User:Epropplerp/enes100

This is where I will list the projects I worked on in ENES-100 HCC fall2011.
 * /PDP/

title: User:Epropplerp/enes100


text:
User:Epropplerp/enes100/PDP

Link to Team page: 550_PDP

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Epropplerp/enes100/PDP


text:
Solar/Howard Community College/Fall2011/550 PDP

Problem Statement
Put the last negotiated problem statement with the instructor or client of the project here.

Team Members
Patel

Summary
Put an overall, one paragraph summary here with links to the team weekly reports.

Poster
Put a graphic in wikimedia, include the graphic here or link to it here. The graphic should be suitable for creating a traditional project poster.

Story
Tell a story of the project. Describe how split up, what the obstacles were, what testing was done, what informal decisions were made, what assumptions were made, what the results were. This is a longer version of the summary with links to all the details collected associated with the project. These links could be to software, links to videos, links to project pages with pictures, etc. Think of the story as a summary of the team weekly reports on one long page rather than a short paragraph like the summary.

Decision List
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
Figuring out what to purchase, what to build, what everything costs is a huge part of engineering. Typically there is a list of materials in stock, materials that are ordered, materials that should be ordered next time there is money, materials that have not been fully justified. These issues are part of healthy management of the engineering lab but are associated with a particular college. The detail needs to be published in this "Done" form. However in the project root, just a list of materials is necessary.

Software List
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
Time estimates and actual time consumed measurements helps justify salaries (grades). The only way to gain respect for estimated project time and costs is to practice.

Tutorials
Most projects consist of making instructions to jump start the next team, shrink the learning of tools and software to the minimum, advice on where to purchase materials, how to assemble, etc. Tutorials modified or created are described here with links.

Next Steps
If this is not filled out, the next team may have to repeat each of your steps just to figure out what the next step is. It is best to write this immediately at the end of the project while creating the summary, poster, presentation, and story.


text:
User:Palluri9407/enes100/Engines

Link to project ARM team page.

Weekend Activities
Research on what type of engine to build for the project.

Write problem statement
Research on what type of engine to build for the project.

Assign Task1
Get a final decisions from teammates on what type of engine to build

Compare actual work done to Task1
Decided to go with the Stirling Engine

Week1 Narrative
Building a internal combustion engine model along with a working stirling engine.

Week1 Peer Review
Peer Review by CR

Assign Task2
Work on the Internal combustion engine

Compare actual work done to Task2
Finished most of the internal combustion engine model. Should be able to complete it this week.

Week2 Narrative
Finishing up with the internal combustion engine model, start on getting the materials to build the stirling engine. Once we are able to obtain all of the materials, we will start building the engine. We are planning on completing more 80% of the stirling engine by the end of week 3.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
finish up the internal combustion engine model and then start working on the stirling engine.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Palluri9407/enes100/Engines


text:
User:Sdk8

Hi I'm Samantha,

I'm studying Business, politics and sport, at the University of Canberra as part of my degree in Sports Media.

Assignments

 * /Change is in order/

title: User:Sdk8


text:
User:Wfalak/enes100/fanwing

Link to project MWE team page.

Link to project Aviators team page.

Give instructor top 3 project choice list
Fanwing, Hovercraft, and Ice Spikes

Write problem statement
Figure out a way to make the squirrel cage.

Assign Task1
Work on the tail of Fanwing.

Compare actual work done to Task1
Over the weekend, I worked on the blueprint of the whole Fanwing. Using 123 D Autodesk is although easy form Google Sketch Up, but it still take time and effort to understand it and be good at it. Although my model does not exactly look like to what it should like, but we can get the idea from it. I also worked on the tail last week and I am almost done with it.

Assign Task2
During the weeks, I am going to take a look at where the motor for Fanwing should be placed and where it would work best.

Compare actual work done to Task2
The motor will be placed at the compartment that we are going to build in the body of the Fanwing.

Assign Task3
Now that we have the concept where the motor should be placed, we will start working on the placement of motor.

Compare actual work done to Task3
Last week, we decided to use a new body for our Fanwing. Last body was not fulfilling the purpose of flying, and it was lacking center of gravity. That probably was the biggest reason we decided to use a different body. So we decided to use the same cage and put it on a different body.

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
This week, I am going to put the cage on the new body, by cutting the shape and fixing it with the help of hot glue. And make the back panel of the fanwing.

Compare actual work done to Task4
During the week, i worked on putting all the pieces together, to wrap up the project. Although we were not able to finish up the project. I still learned lot of things about flying and the ways we can make things fly.

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week, I will try to collect information about the helicopter and consult people who worked previously on this project.

title: User:Wfalak/enes100/fanwing


text:
User:Mbaig7172/enes100/fanwing

Write problem statement
Create a workable fanwing.

Assign Task1
Encase the wings bottom with balsa wood so that the steering mechanism can be secured in it. Make sketch of wing and body.

Compare actual work done to Task1
I cut the balsa wood into congruent sections to match the bottom of the wing using the multi purpose tool. I smoothed the edges with a sander. I helped conjoin the pieces together with hot glue.

Week1 Narrative

Notice the sections of balsa wood that are on the bottom of the body. The unshaded are is the edge of the squirrel cage that connects at the hip of the body.

Assign Task2
Finish the construction of the body of the wing. Decide on whether or not to slant the wing or keep as is..

Compare actual work done to Task2
-The V shaped part is the body. No need to slant wing. I found a way to increase the RPM by increasing the amount of batteries. 1 battery would create a low humming noise. When I aligned three batteries, the motor mad a loud noise and the RPM dramatically increased. ( See video and pictures below)

I applied more glue to the body. Body was separating from the squirrel cage.

Week2 Narrative

http://www.youtube.com/watch?v=nwJI83ekFCA

Video of three batteries

http://www.youtube.com/watch?v=p2kyXZt0ho0 1 battery

Assign Task3
Build wings of the fanwing.

Compare actual work done to Task3
-The goal I made for myself for week 3 has changed. Group met up and refocused and rethought our plans. The new plan for me is to create an entirely new squirrel cage with craftsmanship. This will accommodate a newer body frame.

-I helped take apart the older fanwing and stripped all the tape from the original frame.

-Researched about center of gravity. Our older fanwing was unbalanced. The wings should have the center of gravity.

Assign Task4
Continue to improve the blueprints of the fanwing and begin to build the fanwing.

Compare actual work done to Task4
I wanted to finish the sqirrel cage but I did not have enough time so I created a rough squirell cage. -Got extra balsa wood from project manager

Gathered neccesary tools to make squirrel cage. (Box cutter, sharpie,measuring tape) Measured wood provided to me (90cm)

Cut wood piece in half to 45cm. That piece will be the squirrel cage.

Marked lines with sharpie of about .5cm vertically along the balsa wood.

Used the box cutter to cut thin strips of wood.

Spaced out wood by 1mm apart from each other.

Used three pieces of electric tape and taped the strips together but still leaving a 1mm space between each successive piece. Used sharpie and made a small circle. Cut it out and placed it along one end of the squirrel cage.

Week4 Narrative

Week4 Peer Review
10/10/10 .. pictures of another cage for the fan part, what was wrong with the previous one built? 1sfoerster 21:51, 14 November 2011 (UTC)

Start Next Project Week0 activities
http://en.wikiversity.org/wiki/Engines/Howard_Community_College/Fall2011/550/qjb-eng#Team_Members

title: User:Mbaig7172/enes100/fanwing


text:
Solar/Howard Community College/Fall2011/PD

Problem Statement
Construct a model of an engine.

Team Members
Here is a list of links to the USER pages regarding the Engines project.

 * Patel
 * Samura

Summary
Put an overall, one paragraph summary here with links to the team weekly reports.

Poster
Put a graphic in wikimedia, include the graphic here or link to it here. The graphic should be suitable for creating a traditional project poster.

Story
Tell a story of the project. Describe how tasks were split up, what the obstacles were, what testing was done, what informal decisions were made, what assumptions were made, what the results were. This is a longer version of the summary with links to all the details collected associated with the project. These links could be to software, links to videos, links to project pages with pictures, etc. Think of the story as a summary of the team weekly reports on one long page rather than a short paragraph like the summary.

Decision List
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
Figuring out what to purchase, what to build, what everything costs is a huge part of engineering. Typically there is a list of materials in stock, materials that are ordered, materials that should be ordered next time there is money, materials that have not been fully justified. These issues are part of healthy management of the engineering lab but are associated with a particular college. The detail needs to be published in this "Done" form. However in the project root, just a list of materials is necessary.

Software List
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
Time estimates and actual time consumed measurements helps justify salaries (grades). The only way to gain respect for estimated project time and costs is to practice.

Tutorials
Most projects consist of making instructions to jump start the next team, shrink the learning of tools and software to the minimum, advice on where to purchase materials, how to assemble, etc. Tutorials modified or created are described here with links.

Next Steps
If this is not filled out, the next team may have to repeat each of your steps just to figure out what the next step is. It is best to write this immediately at the end of the project while creating the summary, poster, presentation, and story.


text:
User:RyanPak

Ryan Pak, student at Howard Community College

title: User:RyanPak


text:
User:Epropplerp/enes100/solar

Link to project PD team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Epropplerp/enes100/solar


text:
User:Felhariri3680/enes100/Rube goldberg

Link to project FJK team page.

Give instructor top 3 project choice list

 * Coanda
 * Rube Goldberg
 * Boat

Write problem statement

 * How can the team use parts of a laser printer to create a Rube Goldberg machine?

Assign Task1

 * Over the weekend, I will research and find out which parts of the printer we can use to create a simple machine. Also, I will start dissembling the laser printer.

Compare actual work done to Task1

 * I looked up the parts of the printer and found many parts such as the rollers, gears and the fan that can be used to create a simple machine. Additionally, the dissembling of the printer has begun.

Week1 Narrative
The team was actually able to successfully dissemble the fan, gears, and many roller bars that will be used in our rube goldberg machine.

Assign Task2
Create a successful design in my engineering notebook that will portray what our complete machine might look like.

Compare actual work done to Task2
Two models of the rube goldberg project were created by hand in my engineering notebook.

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Create a mini sailboat using light material and a cube that can hold water for the boat to float on.

Compare actual work done to Task4
Instead of doing the assigned task 4, I decided to take a detour and play with the arduino in order to power the important DC fan for the rube goldberg machine.

Week4 Narrative
Since the DC fan went to around 24 volts, an outside power source was needed in order to power it so I connected a toshiba adapter into the arduino. With lessons on electricity and how simple circuits work, I was successful in powering the arduino fan. The negative wire or the red wire was placed into the "Vin" slot in the arduino while the black wire was placed in the ground slot so it can act like a circuit. The next step is to control the speed of the fan using the PMW side of the arduino.

Complete Project Page

 * Refer to team page for Project summary and analysis


text:
User:Dsamura/enes100/Engines

Link to project PD team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Dsamura/enes100/Engines