Archive for the ‘Teacher’ Category
In the previous entry, I shared some of the features of the VEX IQ robots. Also discussed were some ideas on how to get a classroom organized. Now that we have those things established, we can move on to a discussion of how to begin programming the VEX IQ robots.
ROBOTC for VEX IQ has Natural Language commands that will help beginning programmers of the VEX IQ by supplying a set of commands that use “natural” words. For example, the “forward” command will make your robot move forwards for a specified amount of time or distance. The robot will come to a stop after the movement. Here are some examples of the command:
Move the robot forward for 2.5 rotations:
Move the robot forward to 180 degrees:
• forward(180, degrees);
Move the robot forward for 1.5 rotations at 30% speed:
• forward(1.5, rotations, 30);
Move the robot forward for 10 seconds:
• forward(10, seconds);
• forward(10000, milliseconds);
Natural Language also contains other helpful commands; such as, “backward”, “turnLeft”, “turnRight”, and “repeat”. Below is an example of a Natural Language sample program that is located within the Natural Language sample program folder in ROBOTC:
VEX IQ Natural Language – Port Names and Numbers
leftMotor - Port #1
rightMotor – Port #6
armMotor - Port #10
clawMotor - Port #11
touchLEDSensor – Port #3
gyroSensor – Port #4
distanceSensor – Port #7
bumperSensor - Port #8
colorSensor - Port #9
//Configure the Natural Language to use the VEX IQ Clawbot
//Move the robot forward for 1.5 rotations (rotations are the default unit) at 50% speed (default speed)
//Turn the robot right for 1.25 rotations at 50% speed (default speed)
//Move the robot backwards for 720 degrees at 25% speed.
backward(720, degrees, 25);
//Turn the robot left for 2.5 rotations at 50% speed (default speed)
As you can see, there are a couple things that we have to do in order to use the Natural Language functionality. To enable Natural Language, go to “Robot Menu -> Platform Type -> Natural Language”.
The easiest way to get started programming is to open a sample program or to use a template. To open a sample program in ROBOTC, go to File Menu -> Open Sample Program.
To use a Natural Language template in ROBOTC, go to File Menu -> New… -> Natural Language Template.
To make programming easier, Natural Language makes assumptions about the type of robot you are using. To configure your Natural Language program to use our VEX IQ Clawbot, use the following line of code:
More robot models will be supported in future releases.
Finally, you will notice in the sample program that port names and numbers are given specific names and ports. Make sure that your VEX IQ Clawbot’s motors and sensors are configured this way in order to work with the Natural Language commands.
Ok. We are ready to go with programming! What should we do? My suggestion would be to start with the Labyrinth Challenge.
The Labyrinth challenge gives the students an opportunity to engage with the VEX IQ robots and ROBOTC. The students are immediately engaged because they can see and test their robot’s movement as it makes its way through the course. Since this may be the first program that some students write, there are a couple of things worth remembering. First, makes sure the students create a flowchart before they begin programming. For more information on flowcharts, you can look here: VEX Teacher – Engineering.
Second, it is important that the students describe what is going on in their programs with comments. For more information on how to utilize comments, please see here: http://www.robotc.net/vex_full/reference/hp_comment.pdf
Now you are ready to go! Good luck and have fun! Remember, if you have any questions as you are working, please visit the ROBOTC forums.
The VEX IQ robot is a great, new option for middle and high school robotics teachers. With anything new in the classroom, it’s important to have some ideas on how to best implement the new tools in the classroom.
There are some features of the VEX IQ system that teachers will notice initially. The VEX IQ brain has 12 identical ports. This means that any device (either a sensor or a motor) can be plugged into one of the ports. Also, the VEX IQ motors are smart motors; therefore, the motors can hold a position and resist external movements. Some of the sensors for the VEX IQ include a Bumper sensor, a Touch LED sensor, a Gyro Sensor, a Color sensor, and a Sonar sensor. One nice asset of the motors and sensors is the fact that they each have their own upgradeable firmware. As a result, if new features are added, the firmware for the device can be upgraded, as opposed to buying a new sensor and/or motor.
With the VEX IQ Starter Kit, there are over 850 structural and motion components. That many parts allow teachers and students lots of flexibility when it comes to building a robot. But, that’s only if they can find the parts they need. One of the first things that teachers need to do is get their kits organized. The Starter Kit comes with a storage bin and tray that help, but the amount of parts means that different pieces will need to be stored together in the storage bin. If the students know what pieces are located in each section of the storage bin, it will make the building process much easier.
The base robot for the VEX IQ is the Clawbot. The Clawbot include a gripper and a lifter arm. These features immediately grab the attention of most students; they love the idea of being able to lift and grab an object. For teachers, it is a good idea to build the Clawbot before allowing the students the opportunity to do the same. This gives teachers an idea of what problems the students may have as they begin building, and it also allows the teachers to help those students that run into problems. You can’t start anything until all the students have their robot built. Having some groups finish their robot, while other groups lag behind can be an issue. Building a robot first, puts the teacher in the best position to get everyone started off on the right foot.
When it comes time to start building, students can work on different parts of the VEX IQ Clawbot. You can divide the Clawbot into these sections: the Base, the Claw, the Tower, and the Ball Holder. One suggestion to organize a class would be to have two students work on the Base, while one student each works on the Claw, the Tower and the Ball Holder. Or, you could have one student work on each section. It’s important to note that however the class is organized for the building of the Clawbot, there should be a uniform way that the students attach the motors and sensors.
The battery for the VEX IQ robot brain comes charged, so a teacher does not need to worry about doing that preliminarily. So, once the Clawbot is built, the next thing that needs to be done is install the ROBOTC firmware and update the VEX IQ brain, motors, and any sensors that may be on the robot. Click here for directions on how to install the ROBOTC Firmware.
To update the VEX IQ brain, motors, and sensors, the VEX IQ Firmware Update Utility needs to be downloaded to your computer. The Firmware Update Utility and directions on how to utilize it can be found here.
With the next installment, we will take a look at how to set up your first programming lesson. In the meantime, teachers can take advantage of a few readily available resources at Carnegie Mellon’s Robotics Academy VEX Teacher Site and the ROBOTC Wiki to help with questions concerning programming the VEX IQ with ROBOTC.
The ROBOTC Curriculum contains quizzes to help assess what students have learned, or for that matter, what they haven’t learned. However, as we discussed in a previous blog post, one of the great things about teaching ROBOTC is the ability to differentiate instruction to your students. This can present some issues when it comes to assessment. If a student is progressing quickly through the curriculum, he/she cannot have more assessments than another student. Students all have to be assessed equally. This then begs the question of how you can have the students move through the curriculum at different rates while still assessing them equally.
One of the ways I’ve been able to address this is through the use of rubrics, like the one below:
The programmer uses Pseudocode within the comments to display a logical plan to solve the Mission.
Unsatisfactory - No Pseudocode included.
Satisfactory - Pseudocode is included but it does not display a logical plan to solve the mission.
Good - Pseudocode is included and it displays some logical thinking and something of a plan to solve the mission.
Exemplary – Pseudocode displays a logical plan to solve the mission. The plan is well thought out and clear.
The programmer is able to solve the Mission efficiently and repeatedly.
Unsatisfactory - Less than 70% of the mission is completed.
Satisfactory - Between 70 and 80% of the mission is completed.
Good - Between 80-90% of the mission is completed.
Exemplary - All of the mission is completed, and is able to be completed repeatedly.
Unsatisfactory - Code is hard to read and understand.
Satisfactory - Code is readable but is difficult to understand completely.
Good - Code is readable and understandable, but unclear is certain places.
Exemplary - The code is tabbed well and takes good advantage of white space in order to make it very easy to read.
Unsatisfactory - No Comments included.
Satisfactory - Basic Comments are included but some important parts of the code are not explained.
Good - All of the code is commented but explanations could be more complete.
Exemplary - All of the code is commented and the comments are thorough and comprehensive.
The nice thing about this rubric is that the student does not have to complete the programming challenge in order to be assessed. Just like in any other class, students might not learn a concept to mastery on its initial presentation. You never want a student to reach their frustration level, so this gives the teacher an opportunity to clear up misconceptions while still assessing the student.
Another thing that a teacher can do is utilize Exit Slips. Once again, if students are working at different instructional paces, then the Exit Slips can general. You can ask questions like, “What part(s) of the programming challenge were you able to finish today?” This type of metacognition is valuable for students as they complete projects that last several days. Or, the exit slip can be a review of previously learned concepts. Either way, Exit Slips can play an important role in both teaching and assessing.
Fortunately for teachers, robotc.net contains a wealth of information for extension activities. The ROBOTC blog contains a section entitled “Cool ROBOTC Projects.” Here, there is a wealth of ideas that teachers can look at in order to create an interesting activity.
Moreover, the ROBOTC forum contains a section dedicated to projects. This can also be researched in order to find ideas or interesting projects for your class. Also, the forum can be used to ask questions as you begin to plan and implement a project. Here, you really get the best of both worlds: A wealth of ideas and choose from and a dedicated community willing to help you with those ideas.
Have a great school year!
I’ve always been of the opinion that teaching is an art, not a science. Therefore, it’s impossible to devise a scenario that will handle every issue. But, there are some common issues that arise for teachers as they teach robotics and ROBOTC.
Many students come into class familiar with different aspects of technology, but many students will be unfamiliar with some basic things. For example, never assume that students will know how to save a program while using ROBOTC. Secondly, never assume that the students will know where to save their programs. As a teacher, you need to have a plan to cover these things for students. Also, it would be helpful to have a reference for these things for the students. When students return from Christmas Break or a long weekend, sometimes these details escape them.
One things that is very important for teachers who work in classes in which the students are working cooperatively, is for the teachers to identify what is most important and to assess those things. Simply, students get better at things which are measured and assessed. For example, if you want students to use math vocabulary while solving a particular problem involving different wheel sizes, then you need to assess that. If students are working as a group to solve a problem, then each student’s role in that group needs to be defined and assessed.
Additionally, students working cooperatively in groups are always going to be an issue for teachers. The clearer the roles (and how those roles will be assessed) are defined for the students, the better chance you have for success. Still, teachers need to have a plan for those students who just don’t work well in groups. This plan needs to be articulated to the parents and to your administrators at the beginning of the school year.
One of the great things about teaching robotics and ROBOTC is that the first answer is hardly ever correct. This is great because the students are immersed in the problem-solving process. However, some students will become frustrated by this and immediately look to you for the answer. Teachers need to have a plan for these students. How can students work cooperatively to handle these issues? What has been done to prepare for the challenge? Is there a flow chart that the students can review for some ideas? Is there a sample program the students could examine? As teachers gain more experience working through the ROBOTC curriculum, they’ll be able to anticipate these situations more and have an answer for them.
The beginning of class and the end of class oftentimes determine the success, or failure, of a lesson. Teachers should always have a plan for the beginning of class to get the students settled and focused. The more structured this opening activity is, the better. If a routine is developed, the students will respond accordingly. If the students are coming to your class after gym class or lunch, for example, this opening structure will be very important. Examples of class openers could be having the students find errors in code, a review of particular concepts (what is the difference between = and ==), or an Abstraction Bridge.
In much the same way, the closure of the lesson should be used to judge the effectiveness of that day’s lesson. The most popular way to do this is with the use of an exit slip as the students leave the room.
Having a plan allows teachers to work that plan instead of getting frustrated with individual students. Planning your work, and then working your plan will help to allege some of the daily stressors that teachers face.
The challenge for teachers in today’s educational environment is to teach student at their instructional level. Instead of creating an artificial level to instruct the entire class, teachers have to assess each student’s current level and create a plan to ensure that the student has academic growth from that beginning baseline. It’s best to think about this with an example. A sixth grade student has a reading comprehension at a 9th grade level at the beginning of the school year. The student takes assessments during the spring of that school year. When those assessments are scored, it shows that the student is reading at a 9th grade comprehension level. In the past, teachers and parents would be happy with that information, but the recent push towards differentiated instruction has forced educators to look at this information in a new light. What implications does this have for a robotics teacher?
Luckily, teaching robotics seamlessly fits into the demands of differentiated instruction. First, students are encouraged to come up with different solutions to problems. Whether it is a building challenge or a programming exercise, different students are going to come up with different solutions. Students are encouraged to do this in other disciplines also, but robotics is unique because it is so open-ended. There are only so many ways you can solve a math problem, but there is a myriad of different ways to program your robot to accomplish a task.
Secondly, students who are learning robotics are not forced to conform to an artificial ceiling. In another classroom, a teacher has to keep a student’s learning somewhat in line with the rest of the class. When teachers try to differentiate instruction, they create projects or assignments that are open-ended so students can explore those items as much as they can. However, when that assignment/project is completed, students are all brought back to the same point within the curriculum. Teaching robotics revolves around problem-based learning. Therefore, as the students learn how to solve a programming challenge with more sophisticated ROBOTC code, they are accelerating their knowledge both within that project and within the larger curriculum. While some students are mastering the fundamentals of programming their robot to move, other students can be incorporating more complex programming tools, like functions, into their programs. Robotics teachers can point students in the right direction so they can explore different and more intriguing programming concepts to apply to their challenges. It is not necessary that students memorize all of the different programming/building techniques, but that they know how to access the information when they need it. In this way, students are given the tools to create some ownership with their learning. That ownership, combined with the engagement of robotics helps to provide the true key to differentiation: high student interest.
Simply, if students are not interested in what they are doing, they will never develop the intrinsic motivation needed to push their learning. Students will work towards the minimum unless they are engaged and challenged. Teaching robotics provides the perfect platform to accomplish this goal and create a learning environment in which students are receiving individual acceleration and enrichment. Robotics is the perfect means to achieve the end of differentiated instruction.
Now that the physical robot kits are in the classroom and ROBOTC is installed and activated, you should be ready to build the physical robots for your classroom. One of the best features of a LEGO Mindstorms educational robotics kit is that they allow students to create a nearly limitless range of robots; the downside of this, however, is maintaining student-created robots in a classroom. To help with this, ROBOTC and their related Video Trainer Curriculum support several standard models to help keep a baseline in the classroom.
The first of such robots we will look at is the NXT REMbot (which stands for ‘Robotics Education Model), the standard NXT that is used in the ROBOTC Curriculum for TETRIX and LEGO MINDSTORMS. The REMbot utilizes three NXT motors (two for driving, one for the (optional) arm), a Light Sensor mounted below the robot, a Touch Sensor mounted in the front, a Sonar Sensor positioned above the robot, and a Sound Sensor on the side of the REMBot. This model allows for a variety of tasks to be completed and is designed to work with all of the challenges in the ROBOTC Curriculum.
If your classroom will be utilizing the TETRIX kit, the Mantis Robot standard model would be the build of choice. The Mantis Robot utilizes the TETRIX kit to add two TETRIX DC motors (for driving) and a TETRIX Servo (for the arm), as well as the respective motor and servo controllers; all of which are fully programmable in ROBOTC. Sensors can be added using any of the remaining sensor ports (one of which is used by the HiTechnic Motor/Servo controller chain).
Users of the MATRIX kits are not left in the dark however! MATRIX also has several options to use in the classroom, but the Quick Start Rover stands out from the pack. Combined with The Little Gripper, the MATRIX kits can be quickly and effectively set up for a standard robotics classroom. Like the TETRIX bots, the Quick Start Rover can be outfitted with NXT sensors on any of the remaining sensor ports for added versatility. It uses two MATRIX motors for movement and a MATRIX servo for The Little Gripper (all controlled through one MATRIX controller), all of which is fully programmable in ROBOTC.
Visit CMU’s Robotics Academy LEGO site for more information on the different kits available and to find build instructions.
A curriculum pacing guide is something that teachers have to consider whenever they examine their curriculum. This fact does not escape teachers of ROBOTC. Whenever I come across teachers who are just starting to use the ROBOTC curriculum, often their first question revolves around how long the curriculum will take. Once again, teachers are used to having some type of pacing guide that delineates how a subject is to be taught. The ROBOTC curriculum is not organized in that fashion. Instead, the curriculum is organized by topic. The topics include basic programming fundamentals, robot movement, robot sensing, etc. The teacher is then free to spend an appropriate amount of time within each topic.
As teachers, this freedom is welcome. It is welcome because the pacing that comes with most textbooks is an impossible guide to follow. In order to create a true pacing guide, student background knowledge would have to be taken into account. Since every classroom is different (sometimes within the same grade, within the same school), it is impossible to gauge how quickly the students are going to master the concepts as they are presented. Additionally, as the teacher becomes more familiar with ROBOTC, they will find that they spend more time on particular concepts then they did the first time they taught the curriculum. For example, when I first taught ROBOTC, I spent 20 minutes discussing Flowcharts and Pseudocode. Experience has now taught me to spend a significant amount of time on these topics. I also spend much more time talking about Errors. Specifically, what should a student do when they get the dreaded compiler errors in their program? Experience has taught me to spend much more time on thinking about the logic of a program before the writing of ROBOTC and on debugging strategies once the code has been written.
Each of the aforementioned sections of the ROBOTC curriculum contains a programming challenge. The programming challenged is designed to showcase the skills that were emphasized in that section. Each section also contains an assortment of “mini challenges”. These challenges can be used at the teacher’s discretion. They all do not have to be completed. However, they can be very useful. For example, after the students have spent a day or two learning a topic, I will begin the following class with one of these mini challenges. They might not know all of the skills needed to complete the section challenge, but the mini challenge is a good assessment of what has been presented so far in that section. This also serves as a good change of pace for the class. Simply, you can’t learn to program without actually programming. In order to really understand the applications of while loops or if/else statements, students need to apply them. The mini challenges found within the ROBOTC curriculum serve as a great opportunity to scaffold skills toward their more challenging applications.
A beginning teacher of ROBOTC could teach the basic ROBOTC curriculum in one semester. By including many of the mini challenges, the curriculum can be stretched easily over a semester. I often tell teachers who are teaching the class for a year to do this, and then to end the year with a larger programming challenge. After the students have made it through the ROBOTC curriculum, I enjoy introducing them to Multi-Robot Communication. The sensor needed (NXTBee) is inexpensive, and there are a lot of great ideas for activities and programming challenges.
If you have a stronger background in computer science, and maybe you are teaching older students, you may be able to navigate through the curriculum much faster. What then do you do with students if you have them for an entire year? Luckily, there are many great ROBOTC projects on robotc.net. Moreover, the ROBOTC forum is also a wonderful place to look for ideas for projects, in-class competitions, and programming challenges.
Teaching robotics and ROBOTC is a lot of fun. The ability to watch your students apply what they learn in the ROBOTC curriculum in such engaging and open-ended activities is one of the main reasons why.
There is a bevy of materials to help a teacher get started teaching the ROBOTC Curriculum. But what about the teacher that has made it through the curriculum and has a robotics class returning at the beginning of the school year? Whether that teacher is preparing to enter a robotics competition or is planning on creating a cool ROBOTC project, the teacher will still need to determine what the students have retained from the previous year.
Students that have made it through the ROBOTC curriculum should be able to use variables and functions in their programs. A great way to assess this would be to utilize the Robot Virtual Worlds. Students can spend the first week of school trying complete all of the missions within Operation Reset. Working with Operation Reset affords teachers the opportunity to differentiate this beginning diagnostic. Students that have retained more information can work independently, while those students that need more assistance can get the help they need. This is just another great application of Robot Virtual Worlds in the robotics classroom.
If Robot Virtual Worlds is not an option, you can apply the same concept with a physical robot. For students that are already proficient with ROBOTC, a good challenge to begin the year with would be the Chasm Detection.
Another great tool that a teacher can utilize is the debugging of code. This can serve as a good one or two day review of ROBOTC syntax and logic. If a teacher is anxious to get started with a project and wants a quick review, this may be the way to go. One of the nice things about using code is the teacher can get some quick and individual feedback from the students. If time allows, a teacher may use one or two examples of code, see where the students are, and then design a challenge for them. Here is an example of code that the students could troubleshoot.
Hopefully this gives you some ideas of how you can reintroduce ROBOTC to your students. A seamless beginning to the school year will help with all of the projects and activities that you may have planned for the rest of the school year.
Now more than ever, robotics educators are faced with the important question of which kit they should purchase and use. This key question has been made even more intricate in the 2013-2014 school year due to the addition of the new robotics kits, VEX IQ kits. This article will help break down each VEX kit, their capabilities and target audiences, and allow you, the educator, to make an informed decision on which kit is best for your particular classroom.
The VEX IQ system is the brand-new robotics system from Innovation First International (IFI for short, makers of the VEX Robotics Design System). The VEX IQ can be used with any of the all-new hardware and sensors, including a unique plastic snap-fit structural system.
- Sensors include a gyroscope, color sensor, potentiometer, touch LED, and ultrasonic sensor.
- The base kits (either Sensor or Controller kits) are provided with over 650 structural components, 4 plug-and-play ‘smart motors’, at least 2 touch sensors (or more, depending on kit), and the VEX IQ microcontroller (more information on all available kits can be found here).
- The IQ contains 12 smart ports that can be used to control either analog sensors, digital sensors, or servos/motors; the ports are non-typed and can be used to control any piece of VEX IQ compatible hardware that is plugged into it.
- It also includes a micro-USB port for IQ-to-computer communication and a ‘tether’ port for direct connections to an VEX IQ Controller.
- Debugging and programming information can be displayed on the backlit LCD information to increase ease-of-use in real time.
- Wireless communication between the VEX IQ microcontroller and a VEX IQ controller is provided via a set of 900 MHz radio adapters.
- The VEX IQ system will be fully legal in the new VEX IQ Challenge (designed specifically for the VEX IQ system), for students ages 8-14.
- Recommended use: Middle School.
One of the mainstays of the educational robotics world is the VEX Cortex platform. Originally released in 2010 by IFI, the Cortex can be used with the VEX Robotics Design System’s hardware and sensors.
- Includes over 300 metal structural parts, 4 powerful DC motors, the VEX Cortex microcontroller, and a wide variety of fasteners, gears, and other miscellaneous hardware.
- Sensors include touch sensors, an ultrasonic sensor, integrated motor encoders, line following sensors, and a potentiometer; additional sensors are available outside of the base kits.
- Wireless communication between a VEX Cortex and a VEXNet Joystick Controller is possible by using the 802.11b/g VEXNet USB Adapter Keys.
- The VEX Cortex system can be used in the VEX Robotics Challenge (Middle, High School, and College divisions).
- Recommended use: advanced Middle School, High School or College.
We understand that choosing a robotics kit is a tough decision. The number one factor in determining which kit is right for you is the students; depending on the skill level of the students, it may be better to challenge them with a more advanced kit (VEX Cortex) or they made need to start with a simpler kit (VEX IQ.) No matter which kit you decide to use, though, you can rest easy knowing ROBOTC will fully support all of these platforms.
Now more than ever, robotics educators are faced with the important question of which kit they should purchase and use. This key question has been made even more intricate in the 2013-2014 school year due to the addition of the new robotics kit, LEGO MINDSTORMS EV3. This article will help break down LEGO’s kits, their capabilities and target audiences, and allow you, the educator, to make an informed decision on which kit is best for your particular classroom.
The LEGO MINDSTORMS EV3 is the all-new robotics kit from LEGO Education (creators of the LEGO MINDSTORMS NXT system). It is fully compatible with previous NXT hardware (except for the battery), including all plastic structural pieces and sensors.
- Compatibility with the MATRIX and TETRIX metal systems is expected in fall 2013.
- Those starting a classroom from scratch need not worry; the EV3 comes with a total of 541 elements, including a multitude of structural parts (beams, connectors, wheels, gears, etc), 4 different sensor types (color sensor, gyroscopic sensor, ultrasonic sensor, and touch sensor), 3 motors, and the EV3 micocontroller or ‘brain’.
- The EV3 microcontroller sports 4 sensor ports, 4 motor ports, a internal Bluetooth adapter, and a USB slot which can be used with a WiFi adapter for wireless connectivity (as well as microSDHC card slot which supports cards up to 32GB in size).
- It utilizes a Linux-based firmware which allows for on-brick programming and datalogging.
- The EV3 will be legal in the 2013 First Lego League (ages 9-14) and the 2014-2015 First Tech Challenge (High School) competitions.
- Recommended use: Middle School (EV3) or High School (with MATRIX or TETRIX kit).
Now, let’s take a look at the LEGO MINDSTORMS NXT V2.0. Released in 2009, the NXT platform utilizes a plastic snap-fit hardware structure system, with 431 elements included in the base kit.
- These elements consist of both structural pieces (beams, connectors, and axles, to name a few), three interactive servo motors, the NXT microcontroller, and ultrasonic, light, sound, and two touch sensors included.
- There are also many third-party sensors available from sites such as Hitechnic, Dexter Industries, and Mindsensors.
- The NXT is also fully compatible with the MATRIX and TETRIX metal systems.
- Wireless capabilities include built-in Bluetooth and WiFi connectivity (provided by an external Samantha Module adapter).
- The NXT is currently a legal microcontroller for both the First Lego League (FLL, ages 9-14) and First Tech Challenge (High School) challenges.
- Recommended use: Middle School or High School (with MATRIX or TETRIX metal kit).
We understand that choosing a robotics kit is a tough decision. The number one factor in determining which kit is right for you will come down to the students; depending on the skill level of the students, it may be better to challenge them with a more advanced kit (MATRIX or TETRIX kits) or they made need to start with a simpler kit (LEGO NXT or EV3 kits). No matter which kit you decide to use, though, you can rest easy knowing ROBOTC will fully support all of these platforms.