The EV3 Starter Robots
Let’s go over the basic builds. All the starter robots substitute a 3 for an e somewhere in the name, and all of the bots’ instructions are broken up into separate missions to either build the bots in stages or add program features.
These pauses between missions allow you to test your robot as you go, since sometimes building a robot from someone else’s roadmap can make it confusing to troubleshoot mistakes. The smaller missions also enable you to see how small changes can make big differences in the purpose and function of different robots.
Track3r
The Track3r robot instructions ship with your EV3 Home Edition, and the program to drive your Track3r is already installed on your bot, whether it’s the home edition or LEGO Education version. It is the demo program. You can take advantage of that in later chapters by building tanks you can test out before doing any of your own programming. You can also follow along and program your bot to complete the other missions. The programs are relatively simple at this stage and teach you how the programming interface works.
You can build the Track3r in five stages (missions), running the demo software after each build to see how it reacts differently.
Mission 1
You can see the end-build of Mission 1 in Figure 4.2. The Track3r has blades on one side that spin and an infrared head that doesn’t do much other than provide it with good looks. If you launch the demo, you’ll see the bot look from side to side by showing different eye graphics, make noise, and drive by itself.
FIGURE 4.2 The completed Mission 1 robot.
It doesn’t go very far. This demo program really is just designed to show you that you made a robot that can run. Hold onto that thought, though. I like to use this same demo program to test other robots I build. It doesn’t have to just be a tank bot. I’ll show you how this works in Chapter 7, “Make Your First EV3 Program.”
If you unfold the cardboard test track from your EV3 box (see Figure 4.3), you can actually use this blade and driving motion for a demonstration on your track. Place a tire on the marked area of the track, and the blades will knock the tire around. The robot is self-propelled in this case, and it doesn’t vary in its pattern. This is the “mission” part of the first mission. As you build each mission, you’ll see a new action you can complete on your test track.
FIGURE 4.3 Use your test track for this mission.
Mission 2
The blades go away for Mission 2, and the Track3r gets a ball shooter, as shown in Figure 4.4. You can place stacked tires on the indicated areas at the end of your test track, and the Track3r will shoot them. It will only shoot them if you put both the tires and the bot in the spots indicated for them on the test track. There is no attempt to sense where things are or compensate for placement differences.
FIGURE 4.4 The Mission 2 robot with ball shooter.
Mission 3
For Mission 3 you take off the ball shooter and add a gripper, as shown in Figure 4.5. If you place the Track3r and tires on the designated spot on the test track, the bot will grab the tires and place them on another spot.
FIGURE 4.5 The gripping style of Mission 3.
Again, the bot makes no attempt to compensate for different conditions, so you must place everything exactly as instructed.
By this point, you should be seeing some real possibilities for your EV3 with just a few variations in engineering and programming. If you can make a tank bot that knocks down items, why not change the “blades” into a broom and make a robot that cleans your floor? If you can program a robot to hit a target, you could tweak the same program to make a robot that avoids those targets.
Sometimes engineering changes necessitate programming changes and vice versa, but not always. As you build a robot, you might go through several iterations to find the most efficient design.
Mission 4
Figure 4.6 shows the end result of Mission 4. At this stage, you can get rid of the test track and use your bot on a flat surface. A hammer replaces the gripper. This Track3r variation uses the infrared sensor to detect objects, turn around, and try to crush them with the hammer. Not only is this mission a great example of programming with the infrared sensor, it shows you just how versatile the medium motor is. It has now powered a ball shooter, a spinning blade, a gripper, and the hammer.
FIGURE 4.6 The Mission 4 robot gets fancy with its hammer.
Mission 5
Mission 5 brings the Track3r full circle and it gets the whirling blades back, as shown in Figure 4.7, but this mission also adds in the use of the remote control. You now control where the tank goes and whether the blades spin. You could use the Track3r on the test track or on any flat surface.
You might be building to see how the engineering works this time around, but pay attention to the differences in coding, too.
FIGURE 4.7 The Mission 5 robot adds in some whirling blades.
R3ptar
The R3ptar, a robotic snake, is one of my favorite core builds. There are only two building stages for this mission, so it’s relatively fast.
Three programs come with the R3ptar instructions:
- Program 1 plays rattling sound effects and moves the bot. It is meant to test your connections on Mission 1, and it’s the only program you can run with Mission 1.
- Program 2 uses the infrared sensor to detect and strike at objects near the snake-bot.
- Program 3 enables you to use the remote control to manually control noise and movement.
Mission 1
Mission 1, as shown in Figure 4.8, builds the snake without a head. This is a good time to test your bot, just to make sure you’ve plugged in everything correctly. Run Program 1 and double-check that the sound effects play and that the robot moves a bit like a snake. If nothing happens, you know you have to go back and troubleshoot your connections and build.
FIGURE 4.8 The headless R3ptar.
Mission 2
Mission 2 completes the bot’s look with a head that uses the infrared sensor as eyes and the spiked decorative bushings as teeth (see Figure 4.9).
FIGURE 4.9 The completed R3ptor.
Make sure you put your robot on a surface with plenty of room, and be sure that you only try Program 2 with people who will appreciate the surprise of having a robot snake strike at them.
When you run Program 3, you are relying completely on the beacon/remote, so it will no longer strike at anyone unless you press the button to make it happen.
Spik3r
Spik3r is a spikey spider or scorpion. The bot works best on large, clean floors, because it moves around and shoots balls. You build this complex bot over five missions, so budget extra time for this one.
Mission 1
Mission 1, shown in Figure 4.10, is just to build and shoot the ball-shooting scorpion tail. This gives you the chance to troubleshoot the shooter before you complete the rest of the build. That’s probably a good idea whenever you’re building any project, but these demo robots make the concept more concrete.
FIGURE 4.10 The completed first mission.
Mission 2
In Mission 2, you add six legs to the bot, as shown in Figure 4.11. The programming mission tests the leg movement along with the ball shooting.
FIGURE 4.11 Mission 2 adds the legs.
Check out the way the leg build works at this point. There are six legs and only two large motors, so the leg motion has to be divided up in a way that still looks mostly like insect movements and yet allows for the same motor to control multiple legs.
Mission 3
In Mission 3, you add pincers to the front of the Spik3r, shown in Figure 4.12. The program uses those pincers to “attack,” although at this point the attack is not intelligently guided.
FIGURE 4.12 Mission 3 adds the pincers.
Mission 4
Mission 4 adds infrared sensor control, which searches for objects to attack with the pincers and ball shooting tail. This is an independent action. Figure 4.13 shows the build. Eventually it will search for and attack the beacon.
FIGURE 4.13 Missions 4 and 5 are both pictured here.
Mission 5
Mission 5 adds a cute “bug” created from the remote control, which is also shown in Figure 4.13. The remote in the accompanying programming mission is used as a beacon, so the bot will search for the bug beacon and then shoot it with balls and attack it with pincers. This is the robot all of those missions were working to create.
Ev3rstorm
Ev3rstorm is a punk-rock skating bot built in six missions. Rather than using the usual tank driving motion for treads, this bot has legs that skate along on those treads. This bot is also the most humanoid of the core builds and features prominently on the cover of the EV3 box. You’ll use most of the beams with this set, so make sure you don’t lose any parts before you start and set aside several hours of building time.
There are six missions in the Ev3rstorm build, which indicates a long build.
Mission 1
Mission 1, as shown in Figure 4.14, is just putting together the legs and tank treads. The program tests the gliding and skating motion in a partial figure-eight pattern. This lets you know if you’ve hooked everything up correctly.
FIGURE 4.14 The skates and not much else.
Mission 2
In Mission 2, your bot starts to look more humanoid (see Figure 4.15) because of the addition of arms and a pincer. The program uses the touch sensor to activate an abbreviated skating pattern. It’s no longer the figure eight pattern from the first mission. The arms and pincer are just there for show. You would need an extra motor to make those parts move as well.
FIGURE 4.15 The build starts to look more humanoid.
Mission 3
In Mission 3, you add a blade hand, as shown in Figure 4.16, and this mission enables the use of both the touch sensor and the color sensor to control the bot’s motions. The remote will be used later, but this bot does not yet have the infrared sensor in place.
FIGURE 4.16 This robot skates and can be controlled.
Mission 4
Mission 4 adds the infrared sensor as an additional set of eyes (see Figure 4.17). The program uses the infrared sensor, along with the touch or color sensor, to sense and avoid objects in front of it, so you can wave your hand in front of the bot to change its direction.
FIGURE 4.17 Now your robot is mostly assembled.
Mission 5
Now, on Mission 5, you swap out the blade hand for a ball shooter and attempt to shoot targets. I suggest lining up plastic dinosaurs or other toys to see whether your Ev3rstorm can sense and shoot them.
Mission 6
Mission 6, shown in Figure 4.18, is the same build as in Mission 5 but you add a decorated remote beacon, like you did in Mission 5 of Spik3r. The Ev3rstorm will attempt to find and shoot the infrared beacon.
FIGURE 4.18 The robot is the same for Missions 5 and 6. The only difference is the beacon.
Many EV3 fans find this build both incredibly cool and a little frustrating, as it involves building a lot of parts that were swapped out or removed across each of the missions.
Gripp3r
As its name suggests, Gripp3r is a gripping robot. It is humanoid looking with a spikey head and infrared sensor eyes. There’s also a slight problem with the build, in that the plastic wing catches on the treads when Gripp3r has lifted an object, meaning that it makes a ratcheting, clicking noise. Fortunately, this is an issue you can safely ignore, as it doesn’t seem to damage the robot.
Mission 1
Like the other builds’ first missions, you build and test a single part—in this case, the grip handle (see Figure 4.19).
FIGURE 4.19 Test your grip handle before you build the rest of the bot.
Mission 2
In Mission 2, shown in Figure 4.20, you combine the grip you made in Mission 1 with tank treads and add a stacked tire target object for the Gripp3r to grasp.
FIGURE 4.20 Here is both the grip handle and the object it will grip.
Mission 3
In Mission 3 you basically complete the Gripp3r build with an infrared sensor and spiked hairdo (see Figure 4.21).
FIGURE 4.21 In this case, the Intelligent Brick actually faces the back of the robot.
Mission 4
Mission 4 adds in remote control (see Figure 4.22). Try having the bot pick up tomato cans or other objects to see how the grip and lift action work.
FIGURE 4.22 After you have built this mission, you can control it by infrared remote.
Bonus Bots
MINDSTORMS beta testers and power users have also created plenty of bonus building instructions. These instructions are available at http://www.lego.com/en-us/mindstorms/products/ev3/31313. These are user submissions. You can download them with your browser or use the More Robots button in the lobby of the EV3 home edition software. I cover this in more detail in Chapter 12, “Extending Play.”
Here’s a list of the bonus builds available at the time I wrote this book. The list and pictures are available in the appendix in the back of this book.
- Banner Print3r
- Bobb3e
- Dinor3x
- El3ctric Guitar
- Ev304
- Ev3game
- Ev3meg
- Kraz3
- MrB3am
- Rac3truck
- Robodoz3r
- Wack3m