Monday, February 28, 2011

ಠ_ಠ

RoboPro: Subprograms and Meters

-A concise sentence or two that summarizes the activity

The recent activity that we had wanted us to create subprograms, specifically one that increases the value of a variable. Here are my reults:

-Screenshots of your program that show off the subprogram and metering


-What are the benefits of using subprograms within your team development projects? 

The benefits of these nice little subprograms is that it allows to provide more space to our main code, and create simple little functions that we can use a variable to define rather than recreate the entire code. That would suck. A LOT.

Thursday, February 24, 2011

ಠ_ಠ

Content Is King

Blogging: it has slowly found its way into our school system and is now being used to grade assignments in calss. All I can say (and i quote the Heavy): How did this happen? The internet has not only impacted my social life, it has now effected my school work.

Why u hatin'?
There are other things that I would preferably be blogging about rather than school work. What are these things? Absolutley nothing: I really don't like blogging at all. But if I had to choose a type of blog to run, it would be about he robotics club. It would help make events smoother throughout the year, provide updates on meeting dates, and also show our progress on the robot. I love robotics, and it be something fun to blog about and would also help out the team. It would also help spread the publicity of robotics, much like how blogs spread the popularity of People magazine throughtout the web.

What we should be doing...
I liked the build activities that we had last semester. They were fun, and provided plenty of hands on experience to do. Besides this, I also don't enjoy writing, its one of my weaker acidemic categories. The problem with the build projects is that nobody really participates, but I think these blog posts have increased participation, and gave us a very rude awakening.

Thursday, February 17, 2011

ಠ_ಠ

Machine Control: Project 3.1.7 Machine Control Design - Part I


Here is the first code that was made for the project. This was more of a speculation of what to use rather than "wtf am i doing?"










This second attempt at code worked out really nicely; it just didnt have the abilitty to stop the motor.








The final product! This code stops the motor when touched by a swithc, switches the direction and stops it with the potentiometer, and took forever to make!

1. Requirements: to design a vehicle that drives in a strait line back and forth to deliver batches of parts. Must travel back and forth based on input from a potentiometer. Must include an emergency shutoff in case the vehicle travels too far in either direction.



Components: Engineering kit tools and pieces



Constraints: must travel back and forth (2 ways); must have an emergency shutoff
2&3. Solutions/Sketches:
4. Final design:







5. Actual Design
The hardest part of this project (from my view, anyway) was making the code. It was quite a pain to figure out how to set up the motor to stop and reverse while going to forward. Overall, I found the final product to be very acceptable, and I feel that we met my expectations





















Peeps:
Mia: thanks for the blog posts and the image uploads!
Freddy: you did an awesome job! thanks for the help with the building and programming!
Me: you did well! we make good team!


Sorry about the text background, it wouldn't come off D:

ಠ_ಠ

Activity 3.11 Inputs and Outputs

Answers

Digital Inputs
5. Unchecked and 0
6. Checked and 1
7. It reversed the conditions of pressing and not pressing the switch; so the switch was normally checked and at a value 1 while pressing it caused it to become unchecked with a value of 0

Analog Inputs
9. The potentiometer has a value range of 37 to 5000
11. 1321
12. 1267

Outputs
14. You can switch the wires so they are in the opposite jacks they were originally in.
15. As the reed switch is in contact with the magnet, it's value is considered open.
16. Normally closed
18. Light on = closed
19. More light = more resistance
20. Just reverse the programming
21. Leave it as it is normally

Conclusion
1. When the wires are in 1 and 3, it is always closed; when in 2 and 1, its always open.
2. It could be because measures the time in between the switch going on and off, and considers this measurement as the value for the analog ouput.
3. The heat on the NTC Resistor causes the particles to move faster, allowing them to pass into the resistor faster.

Thursday, February 10, 2011

ಠ_ಠ

Tennis Ball Game post

  • What was the challenge (list criteria and constraints)?

  • Recently (well, not really) we did a team based challenge inside of our second period engineering class. The challenge involved passing a tennis ball around as fast as possible, and everybody had to touch it. Simple enough, and the biggest problem that we had was finding a way to get everyone to the touch the ball before the other team finished.

  • What plan did your team come up with to solve the challenge?

  • Immediately, the team genius Austin, found a way to maximize ball touching and speed into one. His idea was to line up our hands as an inclined slope, rolling the ball down the slope, causing it to go at a decent speed and touch everyone's hands.

  • How did the execution of your plan work out?

  • This idea worked to the utmost perfection; we were able to beat the other team by a ridiculous amount of time. Of course, the second round we lost because the other team had seen our idea and improved it. There was much complaining and accusations going around, and there wasn't much we could do. So, for the final round, we improved our idea: simply drop the ball and brush our hands against it. It seemed like a winning strategy; it was not. The other team simply got everyone to touch the ball at once, and won the last round.

  • What would you do the same?

  • What would you do differently?

  • Honestly, I was happy with the results, and would not try to change anything and would keep all our ideas the same. The only thing that could need changing was the grade of the slop for our ramp (it could have been steeper).

    ಠ_ಠ

    MKS (what does that stand for?)

    l (distance) = m
    t (time) = s
    m (mass) = kg
    a (area) = m squared
    v (velocity) = m/second
    (density) = m cubed
    g (gravity) = m/second squared
    F (force) = kg·m/s²
    E (energy) = m2 kg/s2
    P (power) = m2 kg/s3