Success! Our first robot program works!

On Wednesday we had another robotics meeting, and were again quite productive. We discussed more designs and strategies and managed to run a program that controlled the chassis and 4 motors of the robot (using RobotC)!

[Since the meeting I have been trying to get a program written that uses the compass to keep the robot in the same direction.]

The motors are very powerful, but we get a message on the NXT controller that the batteries are low, when they obviously aren't (they run seemingly forever on one sliver of battery according to the meter).

I was personally excited about the new opportunity to use polycarbonate to aid in the design and aesthetics. Take a look at this video:

I hope we can use this too, though I wonder where we might get a heat gun.

A Constructive Meeting!

The PolyGnomes had an excellent meeting on Monday, and plan another on Wednesday (our new schedule is Mon/Wed).

We got some ideas about the basic design we could use, and discussed various strategies for our robot. We have a nice crisp engineering notebook with our name engraved upon it neatly which will prove quite useful.

We also took out the parts of our new robotics kit and put together a basic chassis that may or may not be the final robot's chassis. We haven't yet managed to hook the motors up to a computer or power source yet, but will most likely on Wednesday.





Eric and I also installed and began to get used to RobotC, which seems like a very powerful language that we may use for the robot's code (NXT-G is too buggy for my taste). It will be refreshing to have some neat code that is much more malleable than the stuff we've been using so far. Using NXT-G or EasyC is like LEGOs, it's fun and structured. But using text-based coding is more like clay, which you need to understand to work, but once you do gives you easy-to-make, elegant results. I think I'll dive into making the core robot code soon :).

Anyway, we'll probably update the blog with more technical stuff, using the notes we took on that meeting.

New Game Released!

Well, it's out! The game this year will be challenging but very fun. It involves hockey pucks this time instead of rings. Take a look at the video (I uploaded it to youtube, but it is NOT my video. The orignals are here: http://www.usfirst.org/community/ftc/content.aspx?id=962

Meanwhile, we will begin to formulate the optimal strategy to get the most points--before designing the actual robot. It also looks like we will be able to get some CAD software to help with designing. :) I also hope that some parents/students of the team can start building the special parts described in the video so we can test our robot well (they did an excellent job last year!).

PS: in terms of meetings, we haven't had a true "meeting" yet, since we're still organizing the best days for everyone to be able to come. As soon as we start the meetings, expect more posts from all our contributors.

Line Follower (w/ video)

Here's a quick video of the line follower I put together to try out the NXT-G code:



PS: You may want to subscribe on youtube to this username :)

Goodbye Vex Controller, hello Mindstorms!

Today I had a chance to test out the Mindstorms that Mr. Madsen (our teacher/coach) had bought for us to try out before the full FTC kit arrives. It's a amazing improvement!

First of all, the controller has a screen so you can choose the program you wish to run right from there (with the old controller we had to preprogram it with special homemade switches). It also has a bunch of demos to try out the different sensors and get a feel of their range.

The ultrasonic sensor (a sensor to record the distance an object is from the robot) seems to capture differences up to about 2 meters before maxing out. You can sort of play the theremin with it, holding a piece of paper in front of it and waving it closer and farther away (the output in the demo program is sound/pitch).

The light sensor is also neat, with two modes, reflected light and ambient light (the difference is the reflected mode shines a beam out to bounce off objects, while the ambient mode simply captures the light coming into the sensor). I started work on a line follower simply based on this sensor (though it is not as exact as, say, a color sensor might be)--see below.

This basic kit also comes with a microphone sensor that detects the decibels (blowing into it also triggers it) and the demo responds by moving a motor. Finally, the standard pushbutton sensor is also present.

In terms of software, I got to try out the NXTG platform for coding. It's a very simple way of laying out the code, but I somehow find it more clunky than coding by hand. It's something like the difference between the command line and user interfaces--it's just faster to type in a command than to set a bunch of options manually. On the other hand, in terms of learning it is pretty simple. It will probably be an excellent way for me to get the team members who wish to program a head start instead of diving into text code.

I was able to code a simple program that kept the robot from falling off a table, using the ultrasonic sensor. The program simply checks the distance to the floor/table, and drives forward until the distance is more than 3 inches. Then, it stops, reverses, turns, and loops back to the front of the program.

Another really neat part about the robot is the output options. Our old robot could only display terminal output (through a "PRINT" command) when the robot was plugged into the computer, the software was downloaded, and the program was running. With the new kit, I was able to have it display an icon of a street "WALK" sign when it was running, then turning arrows when it was turning. But that doesn't mean it's too simple to display more than images. It can display any value you wish anywhere on the screen, at any time. In addition, sounds are supported, including many humorous recordings of various words and phrases like "Alert" and "You're good!" In the future, when we have the controller, it will be able to output through bluetooth as well (though I don't know much about that).

The program also detects if the robot is connected and displays the various values in real time in a box in the corner--a good way to figure out the optimal defaults to use.

Speaking of programming, the old robot took 40 seconds or more to download code, no matter the complexity. It also only supported one program at a time. Want to change one value? Wait another 40 seconds just to find it doesn't work. But with the new kit, you hit the "play" button in the program, wait for it to compile (2 seconds), it downloads (1.5 seconds) and the robot beeps and begins running the new code. I like that!

In any case, this new kit is already exceeding my expectations, which were very high already. My only gripe would be the flimsiness of the parts, but this is just a temporary problem because the real kit uses metal parts instead of the wiggly LEGO parts that come with this kit.

PS: I spoke with Mr. Madsen and he said the metal parts were very expensive. I hope my plan to design first, build later will help us stop wasting metal like we did last year.

PPS: I got a Wacom tablet today. Perhaps I'll be able to use it to draw out design ideas (I mainly got it for my senior project).