FLL 2022: Push and collect with Kriket - How to accomplish M08, M07, M15 - FIRST LEGO League 2022-2023 SUPERPOWERED Challenge Pro Preview

In this video tutorial, we again accomplish three missions. First - the Television, from FIRST LEGO League 2022-2023, the SUPERPOWERED. Then, the Energy Unit. We must collect this energy unit and bring it back to base. And lastly turn the wind turbine where we must push, and energy units are dropping from the wind turbine. This is our first tutorial with the Kriket robot. It's a new box robot, LEGO Education Spike Prime, and it's quite cool. It's really interesting. We've built a small attachment that we put on the front of the robot, and we use this attachment to collect, push and collect. Let's see. Start a single run. Three missions in a row.

Move, push the television. Television is up. Collect three energy units from the wind turbine. Push and collect are the actions for this mission. And we return the energy unit back to base. Now, let's look at the individual missions. These are the same three missions, but from another angle. And we have the television. We must push slightly on the television so that it is up and the energy unit does not fall. And we'll see this when we explain the mission in details. But now from another angle. This is how the robot moves. First mission. Then we have to collect, push and collect three energy units. Finally, we have to collect the last energy unit, and return back to base. That's it. Kriket robot. Interesting attachment from another angle. Now, we have to enter into how we align the robot, and into the individual missions. Aligning the robot when starting from base is always interesting. This here is the Kriket. We position it right here on this black line. This is our starting position. And on the right, the other black line, we need to attach the attachment. It's a pinless attachment, and you can see how it's attaching without pins. Quite interesting. We put the robot on the attachment. Then, we align the robot to the black lines in the base. And this way we have the same starting position. The television is the first mission in this run, and it has an energy unit. The goal is to push, but to push slightly so that the energy unit does not fall. It has to be like this. And the energy unit should be in this green container there. It shouldn't go further. This is how the robot does this mission. The second mission in this robot run is the Turbine mission, Wind Turbine, where we have to push, we have to push. And then we have to collect the energy units that are falling from the wind turbine. This is how the robot accomplishes this mission. A close view, so that you can see all the details. The last mission of this three-mission run is this energy unit. We must collect this energy unit with the robot. The robot comes, accomplishes the first mission, and the second, and then, as it turns, you can see how it collects the energy unit. That's it. Next tutorial - Programming. This here is the program for the robot. On the right, as always, we have the recording. On the left, we have the program. There are a couple of interesting things about this program. First, as you can see them, just put this to be always on top. As we can see them, these blocks are all purple, which means that we use the movement blocks, but we don't use any sensors. And there is a reason for this. First, we decided to experiment. We decided to have some fun with it. But more importantly, this program is implemented with these blocks because it follows a certain pattern. And the pattern is the following: every time we reach a mission model, we kind of like align to the mission model because we push on this mission model. And as we push, we know that the robot will be aligned. For example, if we start the robot right here for the television mission, we want to start it. And as it moves forward, it will align to the mission model right here. Move. And at the end you see how the robot is almost perfectly aligned because the mission model is aligned to the whole field, and the robot is aligned to the mission model. And we know where the robot is on the field. And at the start you see how it is slightly to the left, then to the right. No sensors here, then to the left. But because we push on this television, we go again to the right and we are aligned. So, let's look at the program. The program is the following: We set movement motors to E and F. These are movement motors. Speed is 50 and we move forward for 660 degrees. This is the move forward right here. So, as we start from base, if we go forward, these are the 660 degrees. Then, what we do, we stop right around here and we set movement speed to 20. Because if we are too fast, we wouldn't be able to accomplish the mission and we wouldn't get all the points. And we move forward for 180 degrees. This is the move forward 180 degrees and right here we wait. We wait for 0.5 seconds just for the inertia to calm down the robot, and for the robot to be aligned, and for the mission to be accomplished. We can experiment with this value. I'm not sure whether 0.5 is the only value that we can set here. Probably, 0.6 will work also. 0.4 will work. So, it's just a way for us to wait for the inertia to cool down. Then, we move, set movement speed to 50, and we move back. We move back for 200 degrees. Let's see, 200 degrees. And we stop right here. We move left 90 and forward with rotations. Here we decide to use rotations left and forward, left and forward. Then, we move right, which is right about here. And you can see that we haven't used any sensors for this. Now, that's a bad practice. It's definitely a bad practice. And we should always try to use sensors, especially if we want to get a more consistent and reliable behavior of the robot. But here it's a way of us demonstrating that for some missions you can get away without using a sensor. But there is a risk. It is possible that some of the missions will be not that consistent and reliable. Then, right as we are here, we set speed to 50 and we move forward. As we move forward, right here, we again align to the mission model. We can afford not to use sensors because the robot aligns to the mission model and we know where the robot is. And then we start this forward-backward, forward-backward, forward-backward, until we get all the three energy units. Now, we will return back. This is the return back. No, this is the return back. 180 degrees back. 270 forward, 180 back. Now, it's the same distance, but we want to really push on the mission model in order for us to align with it. That's why there is this difference. 2nd, 3rd time. We get all the energy units. We move back 300 degrees, turn, let's see the turn. We turn left, move back, and we turn left. That's the left turn. As we turn, we take the last energy unit. Just move slightly forward. Turn left again. This block right here. Movement speed to 50, but you can go 100 at this point, and just return back to base. Not a very complex program. It's a program where we do not use any sensors. But there is a reason we don't use sensors, because the mission models that we've selected to accomplish with this run from the base, allow us to align to them. And because they allow us to align to them, we know - kind of like - where the robot is. This wouldn't scale for the whole competition. It will be applicable only for certain missions. So, if you want to have a more consistent and reliable behavior, you should definitely use sensors. Again, a nice example and experiment: can we get without the use of the sensors and what are the prerequisites we need to have in order to do this. Hope this is helpful and I'll see you in the next tutorial.