This is a 10 runs tutorial that demonstrates how the accuracy of the robot improves when we use slow acceleration vs fast or default acceleration. Note that the improvement is small. This is not an accurate and consistent robot. No. This is a robot that is all but accurate or consistent. It does not use sensors and you should use sensors. But it is a teaching/demonstration moment for everybody to seen what is it that you can expect if you don't use sensors.
- #1961
- 01 Nov 2022
- 5:34
- LEGO MINDSTORMS Robot Inventor
- FIRST LEGO League, World Robot Olympiad, Scratch, LEGO MINDSTORMS App Word Blocks, Acceleration
English
This is a ten runs tutorial with this LEGO MINDSTORMS robot inventor. And the goal is to reach a mission model from base to almost the other end of the other side of the field. And to do this without the use use of any sensors. And with this ten out of ten runs, we'll explore the accuracy of the robot. First try. We start from bass. Move forward, turn left, move forward, turn. Right, move forward, turn left. And this is where we arrived. So it's a program with six movements, three turns and three move forward. And it's not very accurate, it's not very reliable and it's not very precise. We start the robot from the same place. And again, the point here is not to demonstrate you how to position the robot on the field. The goal here is to discuss, to have the opportunity to discuss and to visualize that even though we are using an acceleration block with slow acceleration, even though they're using this and the robot is small, it's balanced, it doesn't have any attachments. And despite all of this, it is difficult for the robot to arrive same place every time. And you can see how big this difference is like between the second and third run. This is what you can expect from the robots. Not only these robots, not only these, it's not only something in the Robot Inventor or the LEGO Education SPIKE Prime. Most robots will behave in this way. Most robots, something will happen. They will slip, the wheels will slip on the map. Something will not be correct when turning. There will be some inertia and there will be some error. And as we are not using any sensors here, we cannot correct for this error. We cannot prove the behavior of the robot while we are moving on the field. Now, imagine it is like a small child and it's like a human. If you close the eyes of a human and you tell them, move forward, then turn, move forward, then turn. Move forward, then turn, you wouldn't be at the same place every time. And try this with the team, try this with the students. Try to ask them blindfolded like, put something on their eyes and ask them to move forward five steps, third, move. Forward five steps, third, move forward five. Steps, third, move forward. And let's see if they manage to be at the same place every time and what will be the difference. This is a rather fun exercise and we've done it a couple of times, so I definitely recommend it. It's an easy way to demonstrate how difficult it is to even have fun on the competition without the use of any sensors. A few more runs, just to make sure that we demonstrate all the possible cases of the same program running, but the robot behaving in a different way.
It kind of got to the phone, but it's not where it should be. And we just mark the last location where the robot was.
Start. Move, turn, move, turn again. Move.
And we're here where we are supposed to be.
Nothing much more to up here. The only recommendation that I have is download the program to the robot and try to experiment with this program. Try to see how consistent the robot is, and you see for yourself. You see how the robot behaves. And that the program. Even though it is the same program, the robot is behaving in a different way. And it's the same robot with same wheels, same motor, same battery. Everything is the same field. It just works in a different way.
That's it. I hope this was helpful, and I hope I'll see you in the next tutorial.