text:
User:Dsamura/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:Dsamura/enes100/solar


text:
User:Tfalak3666/enes100/illuminate clothing

Link to project T2C team page.

Give instructor top 3 project choice list
1) Ice Spikes

2) Illuminating clothing

3) Bernoulli Effect

Write problem statement
Finding a dress /shirt and designing the pattern in the way LED bulbs will be plugged in the clothes.

Assign Task1
I ll go to different stores to see what type of dress / shirt will be a good option to this engineering project and then i have bunch of beads and stones sitting in my house, i ll arrange them in a way to get some certain pattern and the one which will be useful for attaching the lily pad with it to.

Compare actual work done to Task1
I planned that my group member will wear the shirt so i bought a boy's size shirt and when i came in my class, in group discussion we decided that no i ll wear the dress in class demonstration. so then i had go back again to buy some thing of my size, as that material is just consider as waste of material while working on the project or you can say FAILURE of the project. Then i started working on the designing part of the shirt,as i got some stuff sitting in my home. I started playing with it, as it is was really hard to think in the way that design should be the one with which we can not only

Week1 Peer Review
Tfalak3666 shows a lot of enthusiasm about this project. It is still early in our planning so its hard to evaluate the work done but right now she shows good planning skills. Epcole 21:46, 25 September 2011 (UTC)

Assign Task2
Going to sow LED s in the way i designed last week and lily pad in the shirt and arranging the pattern of wires, which wont look weird from outside.

Compare actual work done to Task2
Work which was planned to accomplish had faced various abstacles, the sowing part is still pending as the required is not available so far. The designing part of the project is done and as which having trials of working of LED, it comes to point that if positive pole of thethread touches the negative side then it stops working.

Week2 Peer Review
Peer review is down in both of my team mates DICUSS pages. 1sfoerster 13:32, 28 August 2011 (UTC)

Assign Task3
Planning to physically apply the project material and arrange the switch lilly pad and LED on the dress which was picked for final presentation of the project.

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.

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


text:
User talk:Bmart14/enes100/poppit

Good job Bryan! Dpatel5391 19:34, 15 September 2011 (UTC)

Now, all you need to do is to upload the pictures under the Poster section. Dpatel5391 23:59, 16 September 2011 (UTC)

0/0/0 nothing was done on this web page, just blank form. 1sfoerster 11:23, 20 September 2011 (UTC)

title: User talk:Bmart14/enes100/poppit


text:
User:Dpatel5391

Hi! I'm Deep Patel, a student from Howard Community college.

title: User:Dpatel5391


text:
User:Charles Jeffrey Danoff/ACC

N.B. This page is where I want to organize my Accounting studies. My medium-term goal is to earn a CPA. Currently I am taking Financial Accounting, accordingly I have re

CCASANC Resources

 * Flat World Financial Accounting Textbook

title: User:Charles Jeffrey Danoff/ACC


text:
User talk:Inmookchung27/enes100/poppit

Good job Mike! Dpatel5391 19:30, 15 September 2011 (UTC)

Now, all you need to do is to upload the video under the Poster section. Dpatel5391 21:59, 16 September 2011 (UTC)

0/0/0 .. nothing was done on this page to indicate personal work done 1sfoerster 11:25, 20 September 2011 (UTC)

title: User talk:Inmookchung27/enes100/poppit


text: User:EamesA

title: User:EamesA


text:
User talk:EamesA

 Hello EamesA, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! Jtneill - Talk - c 05:14, 20 September 2011 (UTC)

 Hi! My name is WikiversityJack. I am a pumpkin and a Wikiversity mascot. My aunt told me that fun + learning = Wikiversity. Let me know if I can help you out.

Welcome to Motivation and emotion
Hi. Welcome to the unit and to Wikiversity! I look forward to learning with you and I hope that you find the topic and the unit rewarding. Please feel free to let me know if you have any suggestions or would like help at any point along the way. Sincerely, James Neill, -- Jtneill - Talk - c 05:14, 20 September 2011 (UTC)

Thanks for feedback
Hey

Just wanted to say thanks for the feedback on my shame page. Hadn't thought about clip art. --Jeanette 12:15, 20 October 2011 (UTC)

title: User talk:EamesA


text:
Creative Writing and the Author/Reader Relationship

Creative Writing and the Author/Reader Relationship
I intend to explore the bond, expectations, and interactions between an author and their reader.

 * What is an ethical writing process?

 * What does a reader of a book or article expect?

 * What moral obligations exist on either side?

 * How does a author create a real bond with their reader?

 * What have authors said about these questions in the past?

Found blog comments, papers, and references

 * The Journey of Reading

 * The Integrity Partnership Between Author and Reader

 * Textual Discourse and Reader Interaction
 * (Portions of this paper discuss how there is an interactive, not passive role for the reader)

 * Conversation with a Text

 * A plain horse and wagon

 * Nature of Communication between Author and Reader - Tolstoy

 * Dig up 'Raise High the Roof Beam, Carpenters' by Salinger and list what he said about 'the general reader' →'

→StaniStani  05:18, 20 September 2011 (UTC)


title: User:Roald2


text:
User:Egm6321.f11.team4.Renkexin

HW2

title: User:Egm6321.f11.team4.Renkexin


text:
User:Renkexin

http://en.wikiversity.org/wiki/User:Egm6321.f11.team4.Renkexin#

title: User:Renkexin


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

 * Problem Statement 5/10 ... the goal is not to take video and pictures of the game, answer the question "why are you taking video and pictures of the game" and then you will have your problem statement.
 * Summary 5/10 ... video and pictures were taken ... where are they?
 * Poster 0/10 ... video (with no expectations as to what it is, what it is for) links to a website that asks for money, (rapid share) with no obvious way to download the video. Put video on youtube.
 * Story 5/10 ... which audience is this written for? who are you trying to attract to these web pages? someone who has never played a computer game in their life? Good discussion of Wink and HyperCam-2. The purpose of taking the pictures is not to analyze mistakes.
 * Decision List 10/10
 * Material list 10/10
 * Software List 10/10
 * Time 0/10 this is the time in hours, spent by team members on the project, not how long it takes to play the game
 * Tutorials 5/10 .. this strategy guide offers no real advice. You provided no evidence that it helps eliminate the number of balloons.
 * Next Steps 10/10
 * 60/100 1sfoerster 11:21, 20 September 2011 (UTC)


text:
User talk:Dpatel5391/enes100/poppit

0/0/0 .. nothing was done to this blank form 1sfoerster 11:27, 20 September 2011 (UTC)

title: User talk:Dpatel5391/enes100/poppit


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

 * Problem Statement 10/10 ... the word "outcome" confuses me
 * Summary 10/10 ... now it is "out come" .. is this a translation of another language?
 * Poster 0/10 ... no poster
 * Story 10/10 ... good story, need standard deviation so can predict balloon distribution in the game
 * Decision List 10/10
 * Material list 10/10
 * Software List 10/10
 * Time 0/10 this is the time in hours, spent by team members on the project, not how long it takes to play the game
 * Tutorials 0/10 .. do not understand what was written, don't see links to tutorials
 * Next Steps 10/10
 * 70/100 1sfoerster 11:31, 20 September 2011 (UTC)


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

 * Problem Statement 10/10
 * Summary 5/10 ... you played one game each? .. what was the conclusion?
 * Poster 0/10 ... no poster
 * Story 10/10 ... good story, no data to back it up
 * Decision List 0/10
 * Material list 10/10
 * Software List 10/10
 * Time 0/10 this is the time in hours, spent by team members on the project, 20-30 minutes per week is not enough detail
 * Tutorials 10/10 .. do not understand what was written, don't see links to tutorials
 * Next Steps 10/10
 * 55/100 1sfoerster 11:53, 20 September 2011 (UTC)


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

 * Problem Statement 10/10
 * Summary 0/10 ... opinion, no reference to the problem statement
 * Poster 0/10 ... no poster
 * Story 10/10 ... incrediable ... good work
 * Decision List 10/10 ...
 * Material list 10/10
 * Software List 10/10
 * Time 5/10 this is the total time in hours, spent by team members on the project, not an estimation of future time required
 * Tutorials 10/10 .. this is next step advice, not tutorial
 * Next Steps 10/10 .. this would have been good problem statement
 * 80/100 1sfoerster 12:24, 20 September 2011 (UTC)

If user pages were filled out, someone would have gotten 50 points for pushing the project forward. But they were not. Significant work was done here, but can not tell who did it. 1sfoerster 12:50, 20 September 2011 (UTC)


text:
Engineering Projects/Poppit/Math

There is a relevant theorem to this game called the "Four color map theorem." It says with just four colors of balloons, if the game poppit were randomly generated, there would eventually be an impossible poppit game generated. However, the game may have an internal regulator that eliminates impossible games and only displays those that can have all balloons eventually popped. This would have to be determined through statistical analysis or a program written using this theorem (expanded to 5 colors) that identifies impossible games.

Another thought was to make the game linear by looking at each color sequentially and creating a two dimensional spectral wave from the color pattern. Then something like a two dimensional correlation analysis might be done to see if a strategy for popping all the balloons is revealed.

Perhaps the math of the Traveling salesman problem can be used.

title: Engineering Projects/Poppit/Math


text:
Talk:Engineering Projects/Poppit/Howard Community College/Fall2011/502 1+1=11

The code snippet at the end is interesting. Need to define "cropping." Would like to see link to all the code and description of output expected. Right now hopping to find this detail in the user pages. 1sfoerster 13:01, 20 September 2011 (UTC)
 * Problem Statement 10/10 poppit is also an html 5 game .. in addition to being flash
 * Summary 0/10 ... no summary
 * Poster 0/10 ... no poster
 * Story 5/10 ... story implies something was done, but no evidence of this, and no explicit statement
 * Decision List 10/10 ...
 * Material list 0/10
 * Software List 10/10
 * Time 0/10 this is the total time in hours, spent by team members on the project, not an estimation of future time required .. vague reference to time ... not clear whether the combined total or done by each team member
 * Tutorials 10/10 .. this is next step advice, not tutorial
 * Next Steps 10/10 .. this would have been good problem statement
 * 55/100

Looked at user pages, all of them are in the wrong place, but they are in user space, can not tell who did what. Can not find the full processing code. Someone would have earned 50 push points if I could tell who wrote the code and had a link to the full code with descriptions of what to expect from it. 1sfoerster 13:06, 20 September 2011 (UTC)


text:
User talk:Npsweet/ENES100/poppit

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

title: User talk:Npsweet/ENES100/poppit


title: File:Capacitor.1.A.20110920.pdf


text:
User:Lapit kaewkobsin

-Accounting information is like a data system that gives a detail about each company about the transaction such as the transaction about revenue and expense. It also deal with financial because financial have to use the detail to work and deal with supply chain management packet.

-The advantage, it helps to planning the work and forcasting the product in future.

New homework •	What would be your business model and why?

-	First we choose virtual storefront because we will introduce and give the detail of product. Second we choose Information Broker because we have to research about the student needs and the major because it will be easier to advertising our product to each group of student. And we will make a promotion that is free lecture for any items. Next is virtual community by advertise the product in facebook because it is popular in teenager. Last one is portal, we will divide our product such as notebook zone, textbook zone. Because It will be easy the find the product.

Lapit 5302500004 Sarannut 5302500006 Praphat 5302500021

title: User:Lapit kaewkobsin


text:
User:Npsweet/enes100/Rubberband gun

Link to project ZSN team page.

Give instructor top 3 project choice list
Rubber Band Gurn, Hover Craft, Air plane float

Write problem statement
Desing a Rubber band mini gun that is fast and can be loaded automatically.

Make the barrel of the gun and work on hooking up the motor. Attack metal peices down the barrel to hold rubber band.

Compare actual work done to Task1
Bought two 48 inch wood rods and cut them into 5 1 foot sections. Then I cut a v shape into the end of each rod. Then, starting at 7(1/2) inch mark i drilled a small hole every half an inch up to 11 inches. I then cut a small piece of wood from a cabob into 1/2 and inch segments. I placed one of these segments into each of the holes

Week1 Peer Review
This week we mostly brain stormed ideas. Zach had good ideas for the firing mechanism.

Assign Task2
FInish brainstorming ideas for the rubber band gun and desing/make the actuall gun.

Compare actual work done to Task2
Completed the barrel of the gun. Added Two wooden disks and put the wood rods throught the holes. Sanded down u shaped grooves at the end of the circle so rubber band would fit propely

Week2 Narrative
I finished making both the disks and drilling the holes. I had trouble making the disks perfectly circular and one of the holes is not perfectly aligned. I used a saw to cut out the circles. I also cut a u shape into the end or the circle where the barrels are to make it easy for the rubber bands to slide off. I used a sander to do this with a o shaped sanding bit.

Week2 Peer Review
They helped me build the gun barrel and helped come up with ideas of how to make it the disks.

Assign Task3
Make the device to hold the barrel and find a good motor to spin the barrel.

Compare actual work done to Task3
I cut out a piece of pvc which held the middle rod and allowed it to spin freely. then i drilled a hole in the end of the wood rod and drilled a screw into it. I placed a washer before screw to hold pvc in place.

Week3 Narrative
The barrel iws completly finish and know i have to work on attaching it to a handle.

Week3 Peer Review
My temates finished the barrele of the gun by inserting the pegs and putting the peices together.

Assign Task4
Build a device to hold the barrel and attch the motor.

Compare actual work done to Task4
Rationalize differences

Week4 Peer Review
We all pulled together and tried to finish the project. Zach worked the most on the team page and did a good job.

Complete Project Page
Done

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

title: User:Npsweet/enes100/Rubberband gun


text:
User talk:Mkhan4793/enes100/AirPlane Float

10/0/0 .. no committments made to team over the weekend

10/10/10 ... can not get many points doing the wikiversity work for your team ... need to actually do something for the project ... good comments on teammates pages 1sfoerster 20:03, 26 September 2011 (UTC)

Hey man, you got to work on your user page so you can get points.Dkirby7518 21:42, 29 September 2011 (UTC)

10/10/0 ... done with wings is a report to me ... where is a linked up picture? Where is a list of materials? Costs? Where is the rationalization of the materials? This course is about documentation, not doing. 1sfoerster 17:50, 3 October 2011 (UTC)

Hey man did you find any good video about the propeller working? i watched a few, but they are showing the same things.Afayyaz6843 2:09, 8 October 2011 (UTC)

10/10/0 .. still using wikiversity as a reporting tool, no pictures, no list of materials, nothing that could help me retrace your steps or improve me starting from scratch doing the project myself ... 1sfoerster 13:39, 11 October 2011 (UTC)

Hey zohaib i have uploaded our testing video on the team page. can you check and see if there is anything else need to be done especially the summary and the problem statement of the team page.Afayyaz6843 01:06, 15 October 2011 (UTC)

yea im taking a look at it. ill add more details Mkhan4793 20:21, 17 October 2011 (UTC)

10/10/20 .. good photos ... 1sfoerster 13:28, 18 October 2011 (UTC)


text:
User talk:Hsingh8658/enes100/AirPlane Float

10/0/0 didn't make any commitments to team mates over the weekend 1sfoerster 15:04, 20 September 2011 (UTC)

harman i have sent you a text msg.. i hope you got it. want to tell you that i have posted some pictures to our page. Mkhan4793 02:31, 25 September 2011 (UTC)

10/5/10 ... need to list materials purchased and cost ... would have received more push points ... did not comment on team mates discuss pages .. design comes before materials .. what is the design? 1sfoerster 20:05, 26 September 2011 (UTC)

I like how you saying that you putting all your focus on the propeller. We really need that for our project. Learn as much as you can.Dkirby7518 21:46, 29 September 2011 (UTC)

That's true harman, i gues the only thing left now is the propeller itself. We are almost done with everything else.. Lets finish the final part next class. Mkhan4793 17:35, 2 October 2011 (UTC)

10/10/30 .. good job ... looks like you are using pictures uploaded by a team mate ... this is good, I can tell what you are doing and what your team mates are doing .. good 1sfoerster 17:53, 3 October 2011 (UTC)

hey man, we did a nice job making the propeller, but i think making a lighter one would definitely fix our problem... i believe there is too much weight on the front side. Fixing that will help a lot. Mkhan4793 19:53, 8 October 2011 (UTC)

10/10/40 .. good job .. keep up this level of work ... good transparency ..... 1sfoerster 13:42, 11 October 2011 (UTC)

harman, Do you still want to work on the plane or you want to get started with the new one.. Me and Adnan are planing to get the materials. What do u think we would need. Any suggestions....? and i think we did a pretty decent job making the plane... dont u think? Mkhan4793 19:07, 15 October 2011 (UTC)

I think its too early for materials, we first have to understand the concepts, then have to make a design and then we should buy the materialsHsingh8658 23:43, 17 October 2011 (UTC)

10/10/20 ... good job adding words to the photos 1sfoerster 13:29, 18 October 2011 (UTC)


text:
User:Muzzlbock/enes100/R.O.I.T Wheel Bot

This is the link to the team page. CNM

Give instructor top 3 project choice list
R.I.O.T Wheel, Robot arm, Airplane Float.

Write problem statement
Design and Build a functioning R.C. R.I.O.T wheel robot that can balance on its single wheel and is maneuverable. Must be able to fit a motor inside the wheel and create some sort of steering mechanism for the bot.

Assign Task1
Research R.I.O.T wheel vehicles and how they work. Look for possible materials in building a R.I.O.T wheel bot.

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
Begin experimenting functions of the R.I.O.T wheel bot and try to make models to demonstrate them.

Compare actual work done to Task2
We began looking though different parts we could utilize in the mine craft boxes

Week2 Narrative
Looking through the mine craft part i was thinking of using two motor inside the wheel in order to counter the torque coming from each motor and using a series of gears in order for them to still drive the drive shaft in the same direction. Also while doing research I encountered some high tech in wheel motors which shows a very practical application for our R.I.O.T wheel her is a link

http://en.wikipedia.org/wiki/Wheel_hub_motor

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
Search for a larger suitable wheel and rebuild a prototype with a motor strong enough to move the wheel.

Compare actual work done to Task3
We ended up finishing our first prototype RIOT wheel built using an old remote control car motor and RC receiver we were able to get the wheel rolling.

Week3 Narrative
After completing the wheel we noticed it would lean to either side due to the fact that the plastic bowls we were using aren't totally straight and is angled down causing our completed wheel not to go in a straight line so I came up with the idea of glueing strips of a yoga mat to the end of the wheel to level it out. This ended up working very nicely and now for the most part has the wheel rolling straight. see pictures below. http://commons.wikimedia.org/wiki/File:IMAG0149.jpg

http://commons.wikimedia.org/wiki/File:IMAG0152.jpg

http://commons.wikimedia.org/wiki/File:IMAG0159.jpg

http://commons.wikimedia.org/wiki/File:IMAG0160.jpg

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
Currently building a second prototype out of larger remote control car and more sturdy larger plastic peices.

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.


text:
User talk:Afayyaz6843/enes100/AirPlane Float

10/0/0 didn't make any commitments to team mates over the weekend 1sfoerster 15:05, 20 September 2011 (UTC)

Adnan, good job uploading the pictures.. i also have some pictures. I will upload them too.. Mkhan4793 00:58, 25 September 2011 (UTC)

10/0/0 ... used "we" too much when describing your individual commitments, pictures used are on everyone's pages .. with no description of what they are about or why they are on the page ... this doesn't push the project forward ... need to comment on your team mate's discussion pages 1sfoerster 20:07, 26 September 2011 (UTC)

Can you teach me how to put pictures on the website so i can use it for my user page. Also, try filling out more of the categories for your user page.Dkirby7518 21:51, 29 September 2011 (UTC)

You have done really good job with uploading the pictures and i really like you project and what you guys are doing. Good luck with the project and continue the good work. Spatel5040 21:51, 1 October 2011 (UTC)

I have lighter wood (1/4in diameter), tell me if you want me to bring that to the class. I was also thinking of rolling paper and using it instead of wood as it would be lighter than wood.Hsingh8658 03:52, 2 October 2011 (UTC) Hsingh8658

Harman, i think that would be a good idea, and again, the more lighter it is, the better it wold be.... Mkhan4793 17:28, 2 October 2011 (UTC)

10/10/30 .. good uploading of pictures and putting them on your web page ... need to work more on the project .. more points if everyone was working on their own airplane rather than arguing (without a decision process) about the design of this one 1sfoerster 17:56, 3 October 2011 (UTC)

Adnan, the problem with our propeller is that it is a little heavier. If you look closely in the video then you can see that the propeller that they made is very light. I think we should make it a little lighter. We have reached pretty far now and are almost done. I'm sure we will get it finished soon. Mkhan4793 19:30, 8 October 2011 (UTC)

Yeah That is what i was thinking Zohaib. We will try to do it in the class.Afayyaz6843 6:37, 10 September 2011(UTC)

I think we have to make a lighter propeller. Can you please look for those thin strips you brought before, the ones we used for wings, I thing those are lighter than the sticks we used for propeller. Flexible styrene wires can also be an option but I don't know where to buy those. Hsingh8658 00:20, 9 October 2011 (UTC)

That will be a great idea Herman.I dont think i can find some of those, but we can try to look for an alternate material to use Afayyaz6843 6:45, 10 September 2011(UTC)

10/10/40 .. good job documentation ... need to describe the "test" and why the airplane failed the test or was disappointing ... this would really push the project forward 1sfoerster 13:44, 11 October 2011 (UTC)

adnan, maybe we can try to make the plane float with the balloon. nice job with the propeller Mkhan4793 19:10, 15 October 2011 (UTC)

Adnan, can you please update the 'poster' section of project done form as you have all the picturesHsingh8658 23:56, 17 October 2011 (UTC)

10/10/0 .. can not see any original work of your own ... 1sfoerster 13:31, 18 October 2011 (UTC)


text:
User talk:Dkirby7518/enes100/AirPlane Float

10/0/0 didn't make any commitments to team mates over the weekend 1sfoerster 15:05, 20 September 2011 (UTC)

darnelle you have to edit your user page.. Mkhan4793 02:32, 25 September 2011 (UTC)

10/0/0 .. didn't make comments on team mats discuss pages, did not make any commitments over the weekend as to what you are going to do, did not delete stuff you are not going to fill out 1sfoerster 20:09, 26 September 2011 (UTC)

I'm also trying to make sketch on Autodesk123D but I'm having a hard time making the sketch. Also, we decided to make propeller of wood and we started working on it. The length of propeller is 14in, it might be helpful in making sketch Hsingh8658 04:26, 2 October 2011 (UTC)

Dkirby, its better not to skip class these days, we have to Finnish our project... we are done with the wings and are now trying to make the propeller. Mkhan4793 17:33, 2 October 2011 (UTC)

10/5/0 .. no narrative, not sure what you did .. what was your idea on the propeller turning? .. not commenting on team mates discuss pages 1sfoerster 17:57, 3 October 2011 (UTC)

Do you know how to make the sketch of our airplane using auto desk? I am having a hard time making the sketch.Afayyaz6843 12:45, 8 October 2011 (UTC)

Hey, thanks for sharing the idea of hooking propeller, but dont you think now the front part is a littler heavier...? maybe making a lighter one would fix the problem. Mkhan4793 19:57, 8 October 2011 (UTC)

That idea of attaching propeller using those small attachments was really helpful. Hsingh8658 04:32, 10 October 2011 (UTC)

0/0/0 ... don't see any work 1sfoerster 13:45, 11 October 2011 (UTC)

Nice job with the presentation... got to test the balloon Mkhan4793 20:22, 17 October 2011 (UTC)

0/0/0 .. don't see any work 1sfoerster 13:34, 18 October 2011 (UTC)


text:
Engineering Projects/Music projects/Howard Community College

Music projects for Howard Community College.
 * /fall2011/

 * /spring2012/


text:
Engineering Projects/Music projects/Howard Community College/fall2011

/502_MusicTeam/

/502_SynthTeam/

502_The Tin Can Band


text:
Engineering Projects/Music projects/Howard Community College/fall2011/502 MusicTeam

Problem Statement
The idea is to create an instrument, similar to the on in this video. The can has already been mounted by previous teams, and there are references to code that had the hall effect probe recognizing when a magnet passed by it.

Our portion of the project involved playing a note on the keyboard with the arduino and midi shield portion of the code.

PROBLEM STATEMENT:BUILD AND CREATE A PORTABLE SOUNDS FROM ARDUINO.

Team Members

 * Sunny Patel
 * Dominick Moreno
 * User:Tophat

Summary
Over our time with this project, we essentially came up with a way to make sure the arduino is actually talking to your computer to properly upload code. We tried taking apart a "singing" gift card in an attempt to get it to produce sound, but broke the component necessary to actually get anything to play. Additionally, we worked with MIDI protocol and its interactions with the arduino and a keyboard. We managed to play Mary Had a Little Lamb with an arduino program we wrote ourselves. We also managed to write a code that ought to have played a note based on the voltage read on an analogpin (however, it did not actually play these notes). Lastly, we worked on mounting the tin can to the plastic board through which we will mount the Hall Effect Probes.

Team Weekly Reports:
 * Dominick's Week 1 Activities
 * Dominick's Week 2 Activities
 * Dominick's Week 3 Activities
 * Dominick's Week 4 Activities
 * Sunny's Week 1 Activities
 * Sunny's Week 2 Activities
 * Sunny's Week 3 Activities
 * Sunny's Week 4 Activities

Story
Week 1 was spent learning basic arduino interactions with software. The programming environment is similar (essentially identical) to Processing, the environment used in the previous Poppit project. Because of this, dealing with syntax wasn't much of an issue, just learning all of the various functions and their interaction with the arduino ("if", "noteOn", etc.). Difficulties with getting the arduino to work on home PCs impeded any real testing during this time. Most efforts were concentrated on studying components of the arduino environment (details are given in later summaries).

In week 2, we looked at two things. The first was getting the arduino to work on our home computers, the second was tearing apart a "singing" birthday card we bought to see if we could somehow connect it to the arduino to produce sound.

As far as the arduino is concerned, we noticed we had a problem last week when it would not upload code correctly from our home computers, but when we came to class the first day of the week, it uploaded just fine. After a fairly long process of trying several things, including checking to make sure I had the correct arduino drivers, figuring out if the programming environment was "looking" for the right board and in the right COM port, and that I had at least the minimum number of libraries to run the "Hello World" code, we finally loaded the code blinking light code into the arduino. As it turns out, it was a combination of two things:

The arduino environment (what you write code for the arduino in) has to in essence "find" the right board once it's hooked up to your computer. You have to make sure you have the right model of arduino selected (such as arduino Uno, arduino Mini, arduino Fio - in my case, arduino Duemilanove), and that it's "looking" in the correct COM port. The default, I was lead to believe, is that it will always look for the arduino Uno in COM 1. To find this setting and change it, go to tools -> board and select the correct arduino board. The correct COM port is a bit trickier if you don't already know how to find it. First one must find that the arduino is properly recognized in the device manager. On a Windows 7 64 bit operating system, go to the control panel -> system and security -> system -> device manager -> Open the drop-down menu labeled "Ports (COM & LPT)". The arduino Duemilanove was recognized as the "USB Serial Port(COM3)", but other boards are recognized under different names. To change the COM port the arduino environment looks for, go to tools -> Serial Port and select the corresponding COM point.

As far as dissecting the singing card goes, we felt rather successful in taking it apart. It consists of a small dremel board (perhaps 1 x 1 in) that seems to act as a motherboard (supplying power and "holding" code), connected to an round audio device by two wires. This audio device (now referred to as part (b)) is approximately 1 inch in diameter, and a hard green plastic dome top with a flat, thin plastic bottom. We ripped out the underside to find only a copper ring and two EXTREMELY thin copper wires running from the copper ring to the edge of part (b), where they met up with the two external wires that connect the dremel board and part (b). Additionally, we ripped out the circular looking item on the dremel board, and it was in fact a battery - as evidenced by the "3v lithium battery" written on it.

At this point, we figured we had completely destroyed the device. In the first place, it might have been possible to strip the wires connecting part (b) and the dremel board, and somehow connect that so that it can "talk" to the arduino, but when we tore open the plastic underside to part (b), we tore those incredibly thin copper wires, so it's probably broken beyond repair, or just isn't worth the effort trying to connect them back together.

For the Tuesday of Week 3, we tested the sample MIDI code just to see if the basic connection of placing the MIDI shield on the arduino would be enough to provide sound. It was, and the code used to display this can be found below. Additionally, we glued the plexiglass the tin can will be mounted on to the blocks of wood that will support it.

Uploading this code to the arduino, connecting the MIDI shield to said arduino, connecting MIDI out to the MIDI shield, and MIDI in to the keyboard (or any other device with a MIDI in) will result in all notes the device (keyboard) can play (within limits), in ascending sequence. Understanding how this code works requires a basic understanding of arduino environment programming, as well as basic MIDI protocol properties.

All code using MIDI protocol MUST be set to a baud rate of 31250. This is done in the void setup with:

Additionally, this code is written to play a different note after every iteration of the loop, inside of which there is a 100 millisecond delay; in other words, every time the code repeats itself (which occurs every 1 tenth of a second), it plays a different note. To do this, a "for" statement is used. A "base" value is applied to a specified integer, and every time the loop repeats itself another value is added on to that base value, up to a certain point, at which it repeats itself. A simplified way of explaining this is to say that the for function makes the the note one value higher each time the loop repeats itself.

The code "accesses" the MIDI protocol with:

This basically creates the noteOn function that is used in the void loop. It specifies what each of the three values for noteOn do - the MIDI protocol requires at least these three values to play a note, although there are others that can be used to further augment a note. Additionally, the MIDI protocol is written in hexidecimal, which is fairly easy to calculate values for using a hexidecimal calculator. "0x" always precedes any hexidecimal values, so that the code knows to read that value as hexidecimal and not decimal.

 * All MIDI protocol messages MUST start with the command that essentially says "these following values are to be interpreted as MIDI". This value is ALWAYS 0x90.
 * Pitch simply refers to what note is played. All notes have a corresponding hexidecimal value that ranges from 0 to 127/ 0 to 7F (binary/hexidecimal), where 60/3C is middle C. Finally, the third value is velocity - or how long the note is played. This is much harder to find appropriate values for, because, through testing, I found that a velocity value of 120/78 corresponds to approximately 2.88 seconds of play time. According to the previously linked page on MIDI specifications, the actual device interprets how to use velocity values. Guess and check seems to work surprisingly well, as long as the velocity value doesn't interfere with the time delay on a loop - but more on that later.

When this code was first tested, we did not understand all of the things we just examined, but rather all of this information came as a result of several hours of studying MIDI specification, and testing what code would and would not compile in the arduino environment. There were actually no problems with uploading this code, as it worked the very first time I tried connecting it all together.

The following Thursday in class we experimented with creating sound from code based on what we learned. To start, we simply wanted to play middle C over and over on a loop. The following code was written with the information extracted from the last code:

Where the values for velocity and delay are arbitrary. The code worked wonderfully. The next step was significantly harder, as we set out to write Mary Had a Little Lamb. The resulting (and successful) code is as follows:

We encountered several problems writing this code.
 * Figuring out delay values. We wanted to write this song at a certain BPM, not just get whatever BPM resulted from arbitrary delay values. We decided we wanted to see how long a single quarter note at 145 BPM played, in milliseconds. Through dimensional analysis: (145 Beats)/(1 minute) * (1 minute)/(60 seconds) * (1 second)/(1000 milliseconds) = 2.4167x10^(-3) BPMs (beats per milisecond). To calculate the length of a single beat: (1 beat) * (1 millisecond/2.4167x10^(-3) beat) = 413.793 milliseconds. Rounding up, we found that we should use a delay of 414 for quarter notes. A half note is exactly twice as long as a quarter note, and is therefore 828 milliseconds.
 * The biggest problem we had was actually realizing that the pitch value was a single value 0/0-127/7F (binary/hexadecimal). It was our initial belief that 0x3C was to be read as 0x[3rd octave][note C], instead of 60 (decimal). As a result we tried writing Mary Had a Little Lamb with the wrong intervals. It resulted in a "haunting" sound, that I thought to be dissonant. We incorrectly believed this was because our (initially arbitrary) velocity values were causing the notes to play longer than the delay that followed them, causing notes to overlap, and sound dissonant. This was incorrect because of A), the information just given about hexadecimal, and B), the three notes used in Mary Had a Little Lamb are all part of a common chord, and as a result would be/are not dissonant when played over one another (in fact, more "advanced" versions of Mary Had a Little Lamb for piano have the player playing those exact three notes in a different octave together with the left hand).
 * Another problem was dealing with velocity values. Initially, we were using a velocity value of 0x99 (hexadecimal)for the final (whole) note, with a delay of 5000 milliseconds before it would restart the loop. This resulted in the last note just not being played. I'm not sure why, but when I made the velocity value significantly (and arbitrarily) shorter (0x28), it was fine. Our theory was that the velocity value was so much longer than the decimal value, that the loop would have restarted itself before the note was done playing, and so just did not play that note. This was actually fixed by putting in the "silent" note after the final whole note.

For our final week (week 4), We were advised to work on getting a note to play when the switch on the arduino board was pressed. However, that switch turned out to be a reset button, and not necessarily a programmable switch. There is a method for programming a button, but it requires a breadboard, resistor, and separate button to work. So another method of playing a note on command.

Because the Hall Effect Probe runs with analog, we figured researching analog interactions with arduino would be useful. We found the analogRead function.

As a footnote, the arduino page on analogRead said that if nothing is connected to that pin, the analogRead can pick up very random values, based on a massive amount of conditions - the one that we noticed was the closeness of one's hand. I loaded the Analog Input test code that will blink a light for a length of time based on the analogRead (the lower the voltage, the faster it blinks, the higher the voltage, the slower).

We loaded this code and found that the voltage read from pin 0 was fluctuating greatly just sitting there with seemingly no interaction with anything - however, the closeness of a hand did not seem to effect the rate at which the light blinked. We then got the idea that, because the Human brain is basically a massive ball of electrical signals, that might somehow be picked up by the arduino. I held the pin against one of our temples, and actually saw the light begin to blink slower, by my estimates around the 700-1000 millisecond range. We found this to be fairly reliable, as we tested it about fifteen times - it's a strangely reliable way to alter the analogRead input without a potentiometer.

The second part necessary to code a note playing based on conditional statements (preferably the analogRead just used) is understanding the "if" function and comparison operators. Especially when compared to the "for" function previously used in an example code, "if" is fairly simple to understand.

This is a quick example we wrote using the if statement. If the analogRead picks up a voltage approximately 2.5 or greater, the LED pin is on, if it's less, the light is off. The "Serial.begin(9600);" in the voide setup is not actually necessary if the only thing being used is the analogRead (because it's not interacting with an actual analog device); so this code could actually be used in conjunction with MIDI protocol as is. So our next step was to replace the blinking light with a note playing on the keyboard. Our end result was as follows.

It must be noted that this code did not work as intended. It resulted in a "thumping" being played twice, a pause of approximately 4 to 5 seconds, and then repeat. Originally I thought a lack (initially) of a "silent" note to "turn off" the note being played was what was causing it, but that didn't seem to be the case. We have a list of potential things causing this:

 * The "silent" note being within the "if" statements could be the problem. Just taking it out of there and putting it after both if statements could work - similar to factoring in algebra. For example, 2x + 2y = 2(x+y).
 * Using a delay value within the if statements could somehow be causing problems. Because the sensorValue value is so difficult to control with this setup, it is essentially RNG when it is within the delay function, meaning it waits for an arbitrary length of time.
 * It's possible that more precise control of the program is necessary with "If... Else" statement(s) instead of just if. Further research into "If... Else" is necessary.
 * While a value from analogRead of 0 corresponds to 0V and 1023 to 5v, there is a level of uncertainty associated with dealing with how they interact on the interval in between. If 2.5v is not equal to 511.5, and there is some other kind of ratio involved, it is currently unknown, and could be problematic.

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.

Parts necessary to finish this project:
 * Arduino 2009 board - used to write code
 * MIDI shield - used to give code access to the MIDI protocol
 * Keyboard with a MIDI IN attachment - used to play notes
 * Tin can - device used to play notes over time
 * Several dozen magnets - objects used as "notes" in final product
 * 4-7 Hall Effect Probes - used to interpret the magnets as notes
 * Means to mount the tin can - used to hold the tin can in place
 * Legos to operate a hand crank to move the tin can once mounted - rotates the tin can at will to play music

Parts on hand:
 * Arduino 2009 board
 * MIDI shield
 * Keyboard with a MIDI IN attachment
 * Tin can and appropriate mounting/operating devices - Tin can is currently mounted
 * 4-7 Hall Effect Probes

Parts ordered:
 * New keyboard with MIDI IN attachment - one for students to take home, another to keep in class

Possible parts necessary:
 * Arduino Mega board - allows for the usage of 4 different baud rates. MIDI devices such as the keyboard require a rate of 31,250 bytes per second, while analog devices such as the Hall Effect Probe require a rate of 9600.

Software List
Used software:
 * Arduino programming environment

Absolutely essential to programming with an arduino. A link to their site can be found here. It's open source, so free to download.

Time
We would have said we would be able to accomplish what we did in about 8-10 hours before working on the project. However, actual time spent was somewhere close to 20. We didn't actually expect learning all of the coding to take as much time as it did - the goals seemed fairly straight forward.

Tutorials
The story and team pages actually have a fairly good list of explaining everything, however, they are listed here for convenience.
 * The MIDI protocol
 * Hexadecimal Calculator
 * Arduino references
 * For those who need a stronger background in musical theory, this is not a horrible place to start.
 * Blinking Light Code, used throughout this project to test to see if the arduino board was properly talking to the computer.
 * "If" function, used to create conditional statements
 * "If... Else" function, used for greater control over conditional statements than just "if"
 * "Serial.begin" function, explains baud rate used for when the arduino interacts with various other devices
 * "int" function, explains the usage of integers
 * "analogRead" function, elaborates on how to read the voltage input from a device

Next Steps
The next team must get a note to play based on the analogRead function. This should be done more accurately with a potentiometer at first, rather than just holding the arduino to your temple. A good place to start is with breaking down the code I provided, and figuring out why it does not play a note at any given time (which it should - the if statements just have the pitch of the note different from one another, rather than the presence of a note), and then reconstruct it so that it does play a note.

From there, using previous team's knowledge, it should be possible to connect the Hall Effect Probe to the arduino, pass a magnet through its sensor, and through MIDI shield to arduino to keyboard connections, play a note. At that point, it is fairly easy to get six Hall Effect Probes working on one arduino (using the 7 analog pins provided on the arduino board), and then setting up the the actual tin can to play the notes on a hand crank.


text:
User:Panpicha Prukophas

What financial and accounting information does it deal with?

-	Financial and accounting information does it deal with in SCM because, SCM is stategy of management try to make corperation betwwem organization in SCB, for coordinate in units Both inside and outside the organization, work can be connect to the one. Financial is data report of statement that made from the record of time such as cash flow, income statement, balance sheet. Financial can show result of operation. Accounting information is data must to do financial staterment, financial statement can be useful in the decision. That is the reason why financial and accounting information does it deal with based on my understanding.

What are the advantages of using this module?

-	The advantages of using this module is network of connect to inside and outside organization. Can work together, can manage control and improve the flow of cash and the flow of fund, from หuppliers to customer.

u-commerce, due Sept. 27

What would be the best way to market this business on mobile phones? -	Have a new campaign for promote a products on mobile phone, that can make a predisposition to customer buy products. Have a advertise on mobile phone by send SMS to customers, call to customers for introduce the products, tell a promotions, give a sale discount to customer, it’s make customers can decision buy a products. This is a best way to market this business on mobile phone for me.

(Group Member)

5302500001

5302500009

5302500010

title: User:Panpicha Prukophas


text:
User:Spatel5040/enes100/Music Project

Link to project MusicTeam team page.

Give instructor top 3 project choice list
My top three project choices are: Chunk Poppit, music project and Apps. I really like the chunk Poppit project because it is really easy. Our group just have to play the game and come up with the strategy to pop the most balloons.

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
This week task will be to research more information on how arduino works and how to get everything connected. And plan out the whole project week by week so we wont run out of time.

Compare actual work done to Task1
My task 1 was to get all the materials and research on how everything works and have a basic overview of how to connect everything and get the project accomplished. In this week I researched on how to get everything working and make sure that we have all the things we need are there. I also figured out which is the best way to connect the plexiglass to the base.

Week1 Narrative
During this week i just researched on how to connect everything and how to make this project work. I also researched some information about arduino. Here are some links that has more information about arduino: Arduino.cc, Music Code

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 planning to connect the plexiglass with the base and find out more information about arduino so we won't have to do more research later on.

Compare actual work done to Task2
I did exactly what i planned to do last week. First i took of all the glue from the base. Than, I glue the plexiglass to the base. I also did some more research on hall probe and how to connect that to the arduino. I also found out some code about arduino.

Week2 Narrative
During this week i glued the plexiglass to the base. And continue on with some more research. I also looked at older groups information. That really helped me lot with my research. They basically had everything that i need for this project. I did some more research on how to connect hall probe to arduino. Here are some of the websites that i got information from: input/output,Programming,additional information

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
My task 3 is to connect base to plexi glass and connect the hall probe to the arduino

Compare actual work done to Task3
I connected the plexi glass to the base. I also did some work with arduino and hall effect probe.

Week3 Narrative
On tuesday i connected the plexi glass to the base. I also did some research on how to do coding to make arduino and hall effect probe work. I didn't really understand on how to make it work. I am hoping to find some more information next week so i can try my best and make our project successful.

Week3 Peer Review
I commented on my teammates page.

Assign Task4
My task 4 is too continue working on the Arduino and do some more research if i don't get how to code to make the hall effect probe work.

Compare actual work done to Task4
During this week I continued to work on arduino. I am really bad with programming. I just don't understand it. I got several programming code from online and than tried it with hall effect probe and it didn't work. I did some more research on how connect hall effect probe to arduino. Program

Week4 Narrative
During this week i did some programming and connected hall effect probe to arduino and tried really hard to program so the hall effect probe would work with arduino.

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:Spatel5040/enes100/Music Project


text:
User:TFrancis3580/enes100/Model Boat

this link back to project page Model_boat/Howard_Community_College/fall2011/502_bottle

Give instructor top 3 project choice list
Top 3 Engineering Project Choices:

Electric Unicycle

Reactor End Effector

Submarine

Write problem statement
Brainstorm ideas on the mechanics of a of a model boat with the most common items available.

Assign Task1
Timothy Francis: Materials Research

Wesley Rodriguez: Model Boat Remote

Zach Thompson: Motors & Mechanics

Damilola Kukoyi: Boat Design and Mechanics

Compare actual work done to Task1
Timothy Francis: Materials Research Completed- Plastic boat with Styrofoam casing inside to hold mechanisms

Wesley Rodriguez: Model Boat Remote- Still to be completed

Zach Thompson: Motors & Mechanics- 9VDC Motor found online $3.99 due to quantity=6.99

Damilola Kukoyi: Boat Design and Mechanics- Still To Be Completed

Week1 Narrative
Problem #1: Do not know which material to utilize for the boat's mechanics on the exterior

Solution: Asked group members after doing much needed research and we concluded that plastic is the best material for the boats exterior because it is manipulable and possesses and certain sense of balance when on water.

Problem #2: Need to determine the quantity in which is needed to construct a prototype of the model boat.

Solution: Discussed with the group and came to the conclusion that we will determine material quantity when other logistics are completed.

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
Timothy Francis: Materials Collection

Wesley Rodriguez: Model Boat Remote Research Continuation

Zach Thompson: Motors & Mechanics Testing

Damilola Kukoyi: Boat Design and Mechanics Research Continuation

Compare actual work done to Task2
Timothy Francis: Materials Research (Nearly Completed)

Wesley Rodriguez: Model Boat Remote (Nearly Completed)

Zach Thompson: Motors & Mechanics (Nearly Completed)

Damilola Kukoyi: Boat Design and Mechanics (Nearly Completed)

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:TFrancis3580/enes100/Model Boat


text:
User:Dmoreno1899/Poppit

Link to project 1+1=11 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:Dmoreno1899/Poppit


text:
Helicopter/Howard Community College/Fall2011/502 Helicopter

Problem Statement
Build a helicopter from scratch is the main idea of this project. Here's a brief video showing what you can actually do with a Quadcopter after completing the project.

In previous attempts, the Arduino code (C++) used by Masood Muhammad made it easier to add more functionality, including starting the motors with delay or at once. However, they were unsuccessful at writing a code that operates accelerometer and runs all motors at once. Link to their pictures: Previous Arduino Attempts

The following portion of the project involves writing sketches to operate as many as 4 DC-motors through arduino at once. It also involves introduction to Accelerometer ADXL 335, which can be considered to be the next part of this project.

Team Members
Deep Patel

Summary
Matt Scobell was suppose to redesign the previous model of helicopter and I, Deep Patel, was assigned to work with arduino board. Matt took the previously designed helicopter system; however for some reasons he dropped the class and wasn't able to return any of the items. I looked over the previous projects of arduino to see how far did they get, how many motors they were able to run, what sketches did they use, and how efficient were the codes to run each motor differently. After performing various Tasks, I was able to run 4 DC-motors or 3 DC-motors and 1 stepper at once using the Arduino UNO and motor control shield. I also worked with the Prototype shield and Accelerometer ADXL335, but wasn't able to find or write a specific sketch to operate a remote controller.

Poster
Picture of Motor Control Shield attached to the arduino

Picture of Prototype attached to the arduino.

you may hit next to view more images of the project.

Story
In the beginning, we thought of looking over the previous projects since they might be helpful to us in determining what needs to be done next. We split up the work into two, where Matt looked over the previous designs of a helicopter and Deep collected the necessary information related to arduino program and helicopter.

Material List
Computer: to use the arduino-0022 software.

USB cable port: used to connect arduino to a computer.

Arduino UNO: is a micro-controller that is used to code for other devices through sketches.

Motor Control Shield: used to operate and control the power of motors.

White-breadboard: used to supply power from one device to other.

Prototype Shield V.5: to make prototyping on the arduino.

Accelerometer ADXL335: is a 3-axis accelerometer, which measures acceleration.

DC-motors: runs on a direct current(DC), also used to determine the functions programmed by the arduino software.

Stepper motor: used for precise control and exist as Uni-polar and Bi-polar.

LEDs: used to test connection of each port.

Wires: used to supply between power from the arduino board to white-breadboard.

Switches: used for controlling (turning on and off) the motors or LEDs.

Remote Controller: to control the entire system using wireless signals.

Software List
Arduino software (version 0022)- a software that uses programming (C++ coding) language.

Time
Matt didn't document his work at all so no one can tell if he actually took his time to do any of the work related to this project.

Deep Patel took about 5 hours for Week1 Activities, 9 hours for Week2 Activities, 7 hours for Week3 Activities, and 4 hours for Week4 Activities. Total of 23 hours

Tutorials

 * Arduino Development Environment: This is a manual on using Arduino, which explains how to use a text editor for writing code, a message area, a text console, series of menus and toolbars, and also explains how to upload your sketch step by step.

 * Jeremy Blum's video guide: This is a video guide, in which Jeremy explains what an arduino is and goes through the downloading process, materials needed, running the program, writing the code, and uploading it onto the arduino. He has uploaded a total of 13 tutorial videos, in which he guides us through various functionalities of Arduino by writing different, specific codes for each of them. Those videos might be helpful to me in later activities.

 * Jeremy Blum's video guide. This is a video guide, in which Jeremy explains and talks about NPN Transistor and PWM, which allows to run a motor faster through arduino. He also talks about using the different motor libraries, and writing appropriate sketches when using different motors, such as DC-motors, survo and stepping motors.

 * Arduino Troubleshooting, Archive for the ‘Arduino’ Category, and Correcting Arduino Compiler Errors: These tutorials go over many different errors that we might get when trying to program arduino and show how to resolve them.

 * Arduino Hacks: Libraries. This is a manual on using different types of libraries, which basically explains how to install, import, and use the libraries.

 * Motor Shield. This tutorial includes powering the DC motors, voltage and current requirements for the first section. The second section is about how to set up the arduino and the motor control shield for powering motors, and the remaining sections cover Survos, DC-motors, and Steppers. The last two sections include step by step directions on how to run the motors using the sketches they have provided. I have tested those sketches and they seem to work very well.

 * Analog Devices: This is one of the most important guides, which explains everything you need to know about the Accelerometer ADXL335. The link goes through general description of the accelerometer, functional block diagram, specifications, Pin configuration and function description, typical performance characteristics, Mechanical Sensor, Applications information (such as Power Suply Decoupling, Self-Test, Setting the Bandwidth using CX, CY, and CZ), Axes of Acceleration Sensitivity, and Outline its three dimensions (X,Y, and Z).
 * Motor Shield (stepper): This is a guide to learn about stepper motor. It explains how Bi-polar steppers are different from Uni-polar steppers and their differences in writing sketches. There's also a picture of a Bi-polar stepper (4 wires). It also provides a Test-Sketch for it.

 * Circuit for Bipolar Stepper Motor: This is a diagram of how Bi-polar steppers are different from two pins to four pins.

 * Circuits for Unipolar Stepper Motors: This is a diagram of how Unipolar steppers are different from two pins to four pins.

 * Driving a Unipolar Stepper Motor: This tutorial shows how to write a sketch for Unipolar Stepper and run it.

Next Steps

 * Design a new Quadcopter in which all four motors are attached to ends, arduino system is placed in center, including external batteries.

 * Make or purchase a remote controller.

 * Write a sketch to run Survo motors (faster than DC

 * Write or get a sketch for a remote control to work with arduino using Accelerometer ADXL-335 and Prototype shield.


text:
User:Koalex

 * [Poppit]
 * [Escher Project]

title: User:Koalex