Rope Climb

The objective of this task was to have the NXT climb up a rope on a 45 degree slope and climb back down in 60 seconds.

My original plan was to use a sort of Batman tool and wind up a seprate rope and have my robot use the othe rope as something to just hang on. But I wasn't too keen on designing that sort of tool, so I just coppied what everyone else was doing and so I ended up having my rope in between two wheels and the wheels just turned and moved my NXT up the rope. And theennnn, my robot made a smashing end with dislocatnig the motor from the NXT and effortlessly slid down the rope.

Some issues I had were the wheels getting a grip on the rope. I had to pry a tiny space between the tires so they could have traction.

Center of gravity... I had to take off my touch sensor because it was messing with my balance. I couldn't go up the rope because one side was heavier. The blance of the robot it important. If the robot is doing a task that requires it to have symmetry then it's important to make sure the balance is equal.

Decisions Assignment #12

The goal of this activity was to Create a program that would randomly select a course of action when it came within 25 cm of an object. I had to change my switch block from 'flat' view to 'tab' view and each tab would perform a different movement.

The random block chooses a number between 0-3.

Pseudo-coding: Move block: go forward
Loop, ultrasonic sensor
Random block connected to a tab switch block.
First tab- go backwards one rotation and then turn left and continue moving.
Second tab- go backwards one rotation and then turn right and continue moving.
Third tab-  turn left and continue moving.
Fourth tab- turn right and continue moving.
All inside one giant loop

I didn't have any problems with this program... probably because It isn't really performing a task.

Counting

The goal of this activity was to have my robot move past a ball placed on a little pipe and have my robot state weather the ball was red or blue. My robot was supposed to keep track of how many red balls it sensed and how many blue balls.
This task was difficult, and when I finally figured it out it just stopped working.
I had to take a light reading of the red ball and a reading of the blue ball and create a range so my robot could tell which color it was sensing.

One problem I had was that the ball counting gods got mad at me and decided to curse me.


The problem with the counting balls lab was reading the balls and displaying what color they were because you either had to pick them up or you had to read them while the robot was running witch was hard because it was never the right thresh hold but if you brought the ball to your robot sometimes missed the ball and just knocked it over i don't think anyone ever did the lab all the way through but people got very close but they had to do it with a very complicated program




Activity/ lab/ project/ name/ date
goal
provide a short description
plan

how are you planning on solving
pseudo-coding of your plan

issues/ problems
what isssues did you encounter and how you solved/ overcame them


Conclusions
Results
What prototypes/ experiments did you try
known problems- how could they be solved
final version of your pseudo-code