Archive for July, 2011

Day 18: Thursday, 7/28

by on Jul.28, 2011, under Week 4

Today was our second to last day and thus there wasn’t much to do.  We spent the first half of the day sorting kits: we finished three TETRIX kits and would have finished more but there are many bent or broken or missing pieces.  We finished all of the LEGO kits, however one, which was already in the Botlab when we came, has many missing pieces.  Also, we have many spare pieces, such as 8 extra motors and four extra NXTs.  At lunch we went to the CEEO barbecue, where we discovered someone had made balloons with balloons inside of them, which was pretty mind-bending.  Upon our return, we cleaned for a bit, then spent the rest of the day playing another capture-the-hidden-flag game, which stalemated as neither team could find each others flag.

Daily Thoughts:

Dean: Sorted LEGO kits, I finished a bunch of TETRIX kits.  I made a LEGO airplane but had to take it apart promptly because people needed it to sort kits.  I redesigned the iPad robot to use only one kit and fixed some of the robot’s design flaws.

Lawrence: I wasn’t here today.

Jess: Today was marked by kit sorting. We hardly did much more.

Briyana: All we are doing is rearranging the TETRIX and LEGO kits again.

Sarah: We sorted LEGO kits and played outside.

Comments Off more...

Day 17: Wednesday, 7/27

by on Jul.27, 2011, under Week 4

Today we had our absolutely final demos.  The Axel Rover worked well except during the demo it got tangled in it’s own fishing line, a seemingly common problem now that the spool is attached externally, rather than on the rover.  The Carrier Bot’s ramp was not demonstrable as the program for lowering and raising the ramp does not dynamically adjust for the amount of power left in the battery pack, and thus the amount of power the motor is getting.  Apparently Sarah and Briyana wrote the code for lowering/raising the ramp on a battery pack with low energy, so when a new battery pack was inserted the ramp overextends and thus is unusable, as the over-extension is what caused the motor’s to start smoking in the first place.  Dean’s iPad bot worked flawlessly inside, including on the conference room table, however the fact that one motor starts before the other (rather than both simultaneously – the code says start both at the same time) was made more evident when the ground had more friction; ie. pebbles.  After that hour-long demo, we gave our demos again to the elementary school students having summer camp at the CEEO.  The iPad controller worked perfectly, the Carrier Bot had the same ramp issue, and the Axel Rover went on a grass hill way too steep for it and promptly got tangled in it’s fishing line again, promptly cutting it apart.  After the demos (and a bit before), we sorted LEGO and TETRIX kits; we have 10 and 9, respectively.  So far, 4 LEGO and 2 TETRIX kits are entirely sorted.  The final hour was spent playing an intense capture-the-hidden-flag.  The only reason team Purple (Sarah, Lawrence, Me) won was because team Pink hid their notebook (the flag), under a car; which drove away.

Daily Thoughts:

Dean: Presented to Morgan and Co.  The Thai food was good. Cleaned up the room, no longer such a mess.  CTF fun.

Jess: This day was marked mostly by mediocrity on the part of the robot. We finally tested it outside with the spiral code, and that worked pretty nicely, except for some sort of mysterious spinning in place upon completion of the code, which I could not trace back to the code I wrote at all. I suppose most of the robot actually wasn’t mediocre, in retrospect. The wire/spool apparatus and use were mediocre. Tetrix is mediocre is the point. The wire kept getting wrapped around on things, and at one point it got cut by the robot itself, making us look like we had no idea what we were talking about in front of the elementary schoolers.

Briyana: We presented our project twice, to a few CEEO workers and elementary school students. I also began reorganizing the TETRIX and LEGO kits.

Sarah: I realized in the morning that the ramp for the robot wouldn’t work because when we tested the ramp and it worked, the motor battery level was lower than it was at this moment.  This caused the motor to go much further and the door/ramp would go 180 degrees rather than 90 degrees.

Comments Off more...

Day 16: Tuesday, 7/26

by on Jul.26, 2011, under Week 4

Tomorrow is our final demo to Morgan Hynes (my boss), Ethan Danahy, Merredith Portsmore, and Magee Giarrosso.  From 12:30-1:30 tomorrow we will be doing demonstrations of our completed product, as well as talking about our sources for inspiration, our reasons for doing what we’ve done, what we’ve done, how what we’ve done can be related to middle schoolers, what we plan to do in the future, and what we have learned during this internship.  We wrote down the answers to these questions in anticipation for tomorrow’s lecture as well as finalizing the robots.  The Carrier Robot was having door opening issues and those were worked on.  Dean’s iPad Controller, since it works very well, was left untouched, however, the iPad demo robot was reworked to include a handle for easier transport.  The Axel Rover got a cardboard shell around it (with access points for the NXT and the power switch), but, after assuming a motor was broken, the shell was removed so as to expose the wiring.  After troubleshooting, Lawrence and I eventually managed to pinpoint the cause: we had accidentally switched the spool’s NXT and the rover’s NXT, so the code we were running actually only was turning one motor on at any given time.  After that hiccup, we reattached the shell, this time with convenient flaps for easy access to the wiring.  During this time, Jess wrote a code for examining terrain; the robot travels out from a certain point, then spirals back to the starting location.  However, due to the aforementioned mistake, we had only ten minutes to test the code outside; the Axel Rover runs well on wet grass and mulch, both up and down a shallow hill.  The rover still needs to be tested on concrete, dirt, and up a steeper hill.

Also, at around noon, a prospective student, Alex, from New York came by and we gave another quick demo to him and his mother.  During Lunch, I showed him around the CEEO.  At around 4:30, after all the high school students had already left, I gave a short demo to a summer class teacher who decided she’d like to use a working version of the carrier robot for a two day activity with middle schoolers.  Therefore, I’ll spend next week finishing up and perfecting the carrier bot so we can actually use it in a true class setting.

Daily Thoughts:

Dean: Prepeared for demo on Wednesday.  Fine tuned the iPad robot controller program.

Jess: This morning I wrote a really awesome roomba-esque code for the rover. I’m rather proud of it, and it reminds me of my robotics origins working on iRobot Creates for Botball. It isn’t necessarily an independent program, since it is totally static and doesn’t change at all based on environmental stimuli, but it is significantly more sophisticated than a boring old drive straight program. This one drives to the center of a crater and then spirals back to its mothership. It is my first program utilizing sub-VIs, which allow me to simplify my main code and make it look less cluttered and make more sense at first glance. All day the robot itself has been out of comission due to electrical failure and further improvements. A protective casing had to be removed several times because the robot was being fickle. Only by the end of the day was it anywhere near successfully repaired and able to be tested, leaving no time to actually test my nice code.

Briyana: Today we reattached our ultrasonic sensor for our robot to be a crater robot again but the only difference was now it has a sometimes-working door/ramp.

Sarah: Today I worked on making a mini-robot follow a line.  It didn’t work because the mini-robot’s wheels kept getting stuck at various places on the ramp/Carrier Bot.

Comments Off more...

Day 15: Monday, 7/25

by on Jul.25, 2011, under Week 4

Today we had our final demonstrations at the Dr. Albert F. Argenziano School in Somerville, MA.  Since we had decided on longer, hands-on activities rather than powerpoint presentations and talking, the demos of our TETRIX robots was limited.  Jess and Lawrence just talked about the changes they made to the Axel Rover (external spool, different wheels, different frame) and then spun up the motors.  Sarah and Briyana just showed off the Carrier robot and opened and closed the door.  Dean and I showed the new GUI and the new robot we had built for the iPad controller.  We then divided each class into three groups; each group was assigned to either the Axel Rover Activity, the Carrier Robot Activity, or the iPad Controller Activity.  Each class seemed for the most part interested, with the occasional disinterested student.  In the end, I think providing them with a hands on activity was far more interesting then them listening to us talk.  For future demonstrations the solution is to have a longer period of time to work with the students, rather than just an hour.  That way, we can give our powerpoint demonstrations and let them do the hands-on activities at the same time, without running our of time.  -Nicolas

Axel Rover Activity:
This activity was a simple, hands-on, creativity challenge.  Designed for 6 students, the activity had 6 bags, labeled from A->F, containing a NXT brain, a single motor, an NXT cable, necessary axles and connectors, and then a handful of random LEGO parts, but no wheels (except for one kit with small pulley wheels).  The goal was to build a robot that can go forward, backward, and climb over a set of three NXT bars screwed together, once with the bars facing up and once with the bars facing down.  The NXT had two codes on it: the “forwardbackward” code uses the left and right button to travel backward and forward until the orange enter button is pressed and the “btns” code uses the left and right button to turn left and right until the orange enter button is pressed.  The first code was for the initial activity and the second code was for an extra activity if any two groups accidentally combined their pieces or if there was extra time.  Once the students were shown the pieces, shown how to connect the motor to the NXT, shown how to access and run the code, and given the objective, they enthusiastically jumped on the activity. One of the students in the first class, Pratik, built a really cool walking robot that used the pulley wheels to pull itself along, rather than to spin on them in a traditional wheel-sense.

Carrier Robot Activity:
This activity was a build-it then use-it activity.  Divided into four sets, each group was provided a kit labeled either CA1, CA2, CA3, or CA4 and an instruction booklet for building a simple robot with an attached, downwards-facing light sensor.  Upon completing their robots, the goal became to get their robots up the ramp of the Carrier Bot, which was entirely white except for a strip of blue tape.  Using a pre-programmed line-following code, the students would attempt to get their robots up the ramp.  Every robot failed at the same point: where the robot hit the top of the ramp and the light sensor went off into the air.  This caused a dramatic light sensor value change, in this case causing the robot to verge to the left and get stuck in the gear/motor assembly.  In the future this can be fixed with either a ramp modification, such as having the ramp lift up to 180 degrees with the interior when the robot has climbed to the top of it, or a robot modification, such as adding a ultrasonic detector to read the distance to the ground and compensate for a dropoff.

iPad Controller Activity:

This activity was planned and carried out by Dean.  He set up a path, using tape and various obstacles, that the students would have to make the robot follow by using the iPad controls, as shown in the image above.  He first had them plot out their commands on paper, then allowed them to take turns controlling the robot.  For the last class, due to extra time, he also had one person face away from the robot without being able to see it, then had the other students tell the controller where to go.  The iPad did not work for first class due to connection issues, however it did for the second.  In the future, an LED indicator would be useful for showing whether the robot has received a command, is processing it, or has not received a command (green, orange, red).  Also, occasionally an image wouldn’t load, but that’s not something we can fix, as it has to do with the iPad itself.

Daily Thoughts:

Dean: Met with middle-schoolers again, set up a path that they would have to follow by using the controls that I made for the robot.  First had them plot out their commands then I allowed them to take turns controlling the robot.  The kids seemed very interested and animated about this system.  Also had one person face away from the robot without being able to see it, then had the other students tell the controller where to go.

Lawrence: Today we went back to Somerville to present to the Middle school students again. We just presented our prototypes that we made for the children. Then after that we did activities with the students. Our activity was to have the children to build a robot with 1 lego mindstorms motor. They had to build it so that it could climb over an obstacle that we made out of tetrix. A few of the children were successful so it worked out well.

Jess: Today we went back in to the middle schoolers and demo-ed our revised prototypes to them with some activities. It was entertaining watching them attempt to work through the challenges presented. This time, relative to the last time, they seemed much more engaged overall with what they were doing. They seemed to like building things and playing with them better than just listening to us talk and ask them for feedback, which was entirely predictable. Nobody likes to just have to listen to people talking about things when they could be doing things themself. Some of the kids seemed disinterested, but an overwhelming majority found the activities to be entertaining in some capacity, at least minimally. I also found out that the first class was a seventh grade class, or at least all of the kids I asked said seventh grade, while the other class was mixed grade. Then the rest of the day was relaxing and filled with basically nothing but finalization and writing up these thoughts.

Briyana: We went to the middle school and had them build their mini robots to follow the line in and out of our robot. They needed some help, some more then others, but the final outcome was not too disappointing.

Sarah: Presented to the middle school students again; they had a little trouble building the line following robots.

Comments Off more...

Day 14: Friday, 7/22

by on Jul.22, 2011, under Week 3

Today was our last day before our final demos to the middle schoolers.  Also, Jess and Briyana weren’t here so it was even more hectic.  Dean finished all the xml code by extracting the code from a working robobook file and modifying it. Also, Sarah finally got the door to the carrier bot working, as well as taping down the white paper and green guiding tape inside the robot.  Lawrence finished the mechanized spool and I made modifications to the Axel Rover base: secured the NXT and switched to a two crane design (for stability).

Also, Happy Birthday Jess!

Daily Thoughts:

Dean: Did all the xml coding for the interface but when I tried to run the program on the robot, the Bluetooth would not connect (“Line is Busy” error).

Lawrence: Today Jess wasn’t in so I decided to completely re-design the spool controller I made and made it humungous an attached the spool an the battery pack an everything to it so that it would work. It ended up being very successful. It was able to pick up the robot itself that was connected to the fishing line. Nick helped me get a program for the controller which worked as well. Also today Nick helped me re-design the robot itself which turned out being better than the last prototype that we had built.

Jess: I was not in on this day.

Briyana: Was not here.

Sarah: Finally got the door working!!!

Comments Off more...

Day 13: Thursday, 7/21

by on Jul.21, 2011, under Week 3

More building and coding [and smoking {motors}] today.  Dean made all the icons for the iPad interface; each icon was an image made in Gimp that looked like a button and had corresponding text written on it (like 6″ or 45°).  Then, in order to calibrate the robot so the degree turns were accurate, we used a compass app on my iphone, for which Dean built an ingenious mount for.  Also, Dean did all the VI coding; forgot to add a bluetooth subvi to every .vi he wrote so he had to re-add that to each of his .vis at the end, of which there are a lot.  The Axel Rover also went from being able to move it’s arm to self-right itself to having a stationary arm.  Also, the spool went from being mounted on the Axel Rover to being mounted externally on a handheld controller, since there was no more on the Rover for it.  Briyana and Sarah finished up their line following code for the middle schooler’s activity.  Also, they managed to destroy two DC motors; they accidentally left the motors continuously spinning so when the door was closed the motors would keep trying to spin but were held in place and couldn’t; the motors started pouring out smoke; and are now broken.

Daily Thoughts:

Dean: Made the icons for the iPad interface. Built an iPhone holder on the robot to use its compass to calibrate the turns.  Tedious work, paid off though.  Did all the vi coding.

Lawrence: Today I made the double powered servo pivot an attached it to me and Jess’s rover. Once we attached it we made a program and tried to run it and we couldn’t get it to work so we decided to take the servos off and have a stationary crane. Also I started to make the controller where I attach the spool to and have it run to give the robot slack and to reel it in but I didn’t finish it and it didn’t work so well.

Jess: The wiring seemed less hideous and awful this morning when I looked at it. Yet, out servo problems persisted, despite trying everything we could think of. We got some a new servo controller, hoping that would work, but it didn’t. We got a new battery, and we replaced one of the servos, hoping that perhaps low power or offset servos were causing our problem. That only left two perfectly aligned servos connected to newly redone, flawless wiring that still wouldn’t work. At times they fidget within the upper range or lower range, but the arm is unable to swing completely up and down. I noticed that some of the arm’s fasteners are scraping against the inner servo, but I don’t think that is totally the problem, since I tested it with no scraping/resisitance. In the end, servos needed to be entirely scrapped, with only one more full work day left, on which I would not be present. DC motors, for which hubs are very hard to find, would have to replace the servos. Also, today was the last day of my week before my birthday, so there was cake and everybody sang Happy Birthday. That was fun. Being a July-born person, I was never one of those kids who had cupcakes on their birthday in elementary school or anything.

Briyana: Today we went through two, not one but two, DC motors trying to get the door/ramp to move. We worked on this pretty much the whole day. I also worked on planning out the sensors for the middle school students to follow along a dark line so I placed some white paper with different color electrical tape.

Sarah: First, one of the didn’t work, then two motors burned out because they wanted to keep moving but were being held in place.  It was quite frustrating.

Comments Off more...

Day 12: Wednesday, 7/20

by on Jul.20, 2011, under Week 3

More construction today.  Dean spent the day learning how to setup and use the dc motor encoders so that he could get two motors to travel at constant speed, rather than power, allowing a robot to drive forward in a straight line.  In the end, he succeeded, getting a test robot I built to travel 20 feet down the hall whilst only drifting to the side an inch or two.  The Axel Rover base was fully finished, but there will probably still be future modifications.  Lawrence went to the machine shop and with Jim’s guidance custom machined a piece to mount the fishing spool to a motor.  Sarah and Briyana built a door for their robot that would (theoretically) be opened and closed by two synched servos.  In the end however those servos were too weak to properly open the door, so an encoder-equipped motor was used instead.  Also, I constructed kits for the middle school students; both an activity for the Axel Rover and for the Carrier bot.  For the Axel Rover, I made six kits (A -> F) that each had a motor and NXT, who’s goal would be to drive forward, backward, and travel over objects.  However, the pieces I provided in each kit did not include wheels, so the students would need to make a walking/crawling robot.  The code for it is a simple move forward/backward when the right/left NXT button is pressed, until the middle NXT button is pressed.  For the Carrier bot activity, I started set up four kits with instruction manual and the pieces to build a simple light-sensor controlled robot. -Nicolas

Daily Thoughts:

Dean: Started building the robot for iPad control.  Learned how to use encoders/program using encoders for dc motors.  Frustrating at times.

Lawrence: Today we continued reconstructing our NASA Axel Rover. We have the rover completely built that we know of. Our program for running the rover is not working for some reason and also the servo program isn’t working. We believe it is our wiring but we are not sure so we are going to check it tomorrow because we are out of time. Also me and Nick organized kits for the middle school kids for our presentation coming up. The kits are so that the kids can make smaller and easier robots out of Lego Mindstorms.

Jess: On this morning it seemed somewhat crazy that we had to have completely finished demos for the next Monday. Then I realized that the robot was basically done and I had a six hour period in which to work solely on the robot. Indeed, it turned out that the robot came along rather successfully. It even had a part custom made for it. We solved a lot of problems as far as actual physical construction. When it came to programming, that undid basically everything (in some cases, literally). We couldn’t figure out how to sync the servos, so I undid the zip ties that held all of the electrical parts together, undid all of the connections, and still solved none of the problems, but did succeed in losing my perfect, original configuration.

Briyana: Constructing a door and motorizing it to be a ramp (similar to draw bridge) for the mini robots to deploy from. Servo motor ended up not being strong enough so we switched to DC motors and used encoders instead.

Sarah: We are working on the door for our robot.

Comments Off more...

Day 11: Tuesday, 7/19

by on Jul.19, 2011, under Week 3

Today was the second day of redesigning and rebuilding.  The base of the Axel Rover got a few redesigns as the holes are difficult to line up with Tetrix due to the awkwardness of the provided motor mounts. In the end, two different designs were constructed in order to evaluate which is better.  The Carrier bot started coming together, with the walls being made of cardboard, since it is an easily acquired material and inexpensive.  Originally I was thinking about their robot being made of 1/16″ Lexan (polycarbonate sheeting), however that would defy the purpose of other people being able to easily build this robot.

Daily Thoughts:

Lawrence: Today we still did more reconstructing. We came up with 2 possible ideas for our rover. Both of them are built and we will test them tomorrow to see which of the 2 are better. Also today I made a program to work the double powered servo that I constructed earlier. I made it a double servo so that it would be more powerful. I also synchronized the double powered servo so that it would be better but we ran into technical difficulties that I fixed but it destroyed the synchronizing I did. So my goal for tomorrow is to synchronize the double powered servo so that it works.

Jess: First thing in the morning I had to take apart the base I had spent the entirety of the previous afternoon building. It was growing increasingly unfeasible. The rest of the day was spent constructing two new alternatives to the base, which at times was extremely frustrating, since the holes continue to not match up in ways that have been acceptable to me. In the end, I got the servos/arm mounted in the center of one of the bases as I wished, but continued to be skeptical.

Briyana: My partner and I continued to expand and improve and have got a full base in which the smaller robots (which will be built by the middle school students) will wait to be deployed.

Sarah: We continued building the new robot. We used cardboard for the walls because it is still a prototype and cardboard was easier that using a different material.

Comments Off more...

Day 10: Monday, 7/18

by on Jul.18, 2011, under Week 3

Today was day 1 of rebuilding and modifying our prototypes based on information gleaned from testing and demoing them.  Dean took apart his Tank robot so that the other groups would have more pieces for their own projects, since he used almost every single flat plate and most of the long bars, as well as a ton of screws and nuts.  I used this opportunity to take a SAM animation of him taking it apart, taking a picture every 2 seconds.  We ended up with 2545 pictures for a total of 5090 seconds, or 84.8 minutes.  We decided to run the resulting video at maximum fps, (30.3), resulting in the below video.

Dean taking apart Tank

Also, the two other groups spent today taking apart their prototypes and redesigning them.  The Axel Rover’s base was taken apart and new designs were thought up.  The Carrier bot’s prototype, which was at this point just a simple robot with an arm holding an ultrasonic sensor for finding craters/table edges, was taken apart and an entirely new robot was started.  Using four of the longest Tetrix beams and all the flat pieces Dean took off his tank, the base of the Carrier bot was built.

Daily Thoughts:

Lawrence: Today we took apart our old rover and completely reconstructed it. We did this all day and still didn’t finish it so it got frustrating. We tried many ways to make our rover and we still haven’t solved it.

Jess: After a rather relaxing day on Friday, and then the weekend, we had to buckle down to actual work. We started to take apart our prototype rover, as I wanted to see if I could create a better model by redesigning the base and such. I got it deconstructed within the day, and started brainstorming new ideas. Construction also began on a new base, which was rather frustrating.

Briyana: My partner and I took apart our old robot to expand and improve and have got a new base where the smaller robots (which will be built by the middle school students) will wait to be deployed.

Sarah: We took apart the old robot and built the base of the new robot.

Comments Off more...

Day 9: Friday, 7/15

by on Jul.15, 2011, under Week 2

Today we had our demos for LEGO/TI people (educators and business men/women), who had come to Tufts to discuss the use of the TI Nspire in classrooms.  We used the opportunity of them being here to show our projects, but also to mention some complaints about Tetrix, as one of the Tetrix developers, Andrew, was actually there as well.  From 9:30 to noon, before the demos, we made finishing touches on the powerpoints and finalized the robots.  The Axel Rover had it’s wheel’s redone, from flat bars attached to the large gear, to smaller gears attached to the large gear.  This provided smoother motion and made the wheels large enough to turn without the middle axle hitting the ground:

Right before the demonstrations started, we found out we weren’t going to do powerpoint presentations.  In the end, the presentations went very well as the people we were presenting to seemed genuinely interested and understood what we were saying.  We pointed out our complaints with the TETRIX system: That the one 7/64″ allen wrench that is provided is not enough since it is used so often, that the pieces bend easily even under light pressure, that some screws are improperly machined so that the nut won’t fit on unless forced (with non-provided pliers/nut driver), that some curved pieces would be nice, that pieces with an even amount of connection ports (4 rather than 3, or 6 rather than 5) would be useful, that there should be a variety of axle lengths, and that Servo cables should have a “+” or some kind of sign to show which way is up when inserting them into the Servo controller.  Also, Andrew gave us a personal demo of the TI Nspire, which blew my mind, as I’ve been using a TI 83 for 8 years now.  The Nspire is basically a SAT-legal laptop/calculator hybrid.  At this point, I don’t see how people actually need to learn math for the SAT, they just need to learn this calculator.  My favorite features of the Nspire is not the 10 million things you can do with it, but rather the fact that it has a backlight, (I’m surprised it took so long to add a backlight), is in color, and has a full keyboard (rather than an alpha button activated keyboard).

After those demos we ate pizza and socialized.  Then we did another demo, this time to the other CEEO employees; college interns working on various LEGO projects.  Following our demos, they showed us what they are working on; curricula ideas for LEGO, such as a robotic ice cream making assembly line and robotic puppets, firmware updates for Labview, interactive playground equipment, Arduino-LEGO interfaces, a TETRIX scooter and TETRIX tricycle riding robot, etc.  Other past and ongoing CEEO projects were also shown, such as a LEGO CNC (Computer Numerical Control) machine, a TETRIX Mill, and Mike Mogenson‘s camera controlled quadcopter.

Ben’s TETRIX Mill AR Drone Ball Tracking

After all that, we came back to the Botlab to drop our gear off and headed to the field behind Bromfield-Pearson (the math building) to play some frisbee with Morgan (who’s incredibly good), as we missed the normal game with the CEEO employees.  The final hour we reviewed what happened that day, I gave a game plan for next week, and finally I let the students do what they wanted as the hectic week concluded. -Nicolas

Daily Thoughts:

Dean: Presenting to the tetrix people allowed us to give our opinions on the system which in the long run would be useful to others.  We also presented to the other students working at the CEEO and they showed us their projects.   They are fairly complicated and interesting.

Lawrence: The first thing I did today when I came in is look at the NASA Axel Rover and I did my best to think of a solution to the problem we ran into with the wheels. After a few experiments I finally thought of the idea to put gears on top of the gear to make the wheels bigger so that the wheels will be big enough so that the rover can actually move when you put it on the ground. The only problem with this idea that I came up with was that the screws that were necessary for the wheels were not located in the Tetrix kit so I had to achieve other screws and bolts that worked for this occasion. Also later today we presented our projects to the owners of Tetrix and Lego mindstorms. The presentation went relatively well because this time we could actually run our rover on the ground because I switched the wheels before the presentation. After the presentation we played Frisbee with Morgan because all the other CEEO members already played and then we had pizza.

Jess: In the morning, we found out that all of the work we had done the previous afternoon on advancing our powerpoints into less kiddy, more professional presentations was completely unnecessary, as we wouldn’t even have to use powerpoints to present to the people from Lego and TI. It was significantly easier presenting to adults than to children, and the burritos and pizza afterward were pretty tasty.

Briyana: We just presented our robots to the LEGO people and gave them constructive criticism to improve the next model of TETRIXÒ.

Sarah: We showed people the working version of our robots. We also told them some problems with the TETRIX system like how the pieces are easily bendable. They also ate all of the good burritos.

Comments Off more...

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!


A few highly recommended websites...


    All entries, chronologically...