★ 003. advanced bot!
Today, we showcased our robots!
As yesterday's programming didn't go according to plan, we had to quickly programme a set of movements this morning for Mr T to run on. In the span of about 40mins, we programmed in some moves for Mr T, (following our protocol of course), hoping it would reach the final destination. However, we underestimated the distance of each step we programmed and it moved to the right side too much, so Mr T eventually crashed into the wall as soon as it reached the hallway. We didn't realise that the robot sucked up the life of the batteries so fast, so while everyone else's bots went at a steady pace, ours strolled slowly along. (Slow and steady wins the race, right?)
What I particularly liked about today's task was seeing the robot everyone built and designed. Each group had their own way of building the robot, and it really gave us a different perspective of looking at the robot. I particularly liked one group that attached a ball on the end of their robot for support.
After that, we had more programming to do! Rather than planning out a whole route for our bots, we had to make sure it could adapt to it's surroundings. So if it was about to crash into a wall, the bot should automatically sense the wall and then choose a different path to walk.
It was definitely challenging, but because we almost had that figured out yesterday, we focused more on the appearance of Mr T. We rebuilt it, fiddling around with the parts and creating a whole new look. We tried out a lot of different ways to build Mr T so that it would look more intimidating, since Mr T is supposed to intimidate the opponent. Some changes didn't follow through the way we wanted it to -- for example, we added an extra wheel at the back for more support, but the tyre had a hard grip which made it hard for our robot to turn.
In the end we finally decided on something we were all satisfied with. Just a few more tweaks with the programming, and Mr T is ready to go!
As yesterday's programming didn't go according to plan, we had to quickly programme a set of movements this morning for Mr T to run on. In the span of about 40mins, we programmed in some moves for Mr T, (following our protocol of course), hoping it would reach the final destination. However, we underestimated the distance of each step we programmed and it moved to the right side too much, so Mr T eventually crashed into the wall as soon as it reached the hallway. We didn't realise that the robot sucked up the life of the batteries so fast, so while everyone else's bots went at a steady pace, ours strolled slowly along. (Slow and steady wins the race, right?)
What I particularly liked about today's task was seeing the robot everyone built and designed. Each group had their own way of building the robot, and it really gave us a different perspective of looking at the robot. I particularly liked one group that attached a ball on the end of their robot for support.
After that, we had more programming to do! Rather than planning out a whole route for our bots, we had to make sure it could adapt to it's surroundings. So if it was about to crash into a wall, the bot should automatically sense the wall and then choose a different path to walk.
It was definitely challenging, but because we almost had that figured out yesterday, we focused more on the appearance of Mr T. We rebuilt it, fiddling around with the parts and creating a whole new look. We tried out a lot of different ways to build Mr T so that it would look more intimidating, since Mr T is supposed to intimidate the opponent. Some changes didn't follow through the way we wanted it to -- for example, we added an extra wheel at the back for more support, but the tyre had a hard grip which made it hard for our robot to turn.
In the end we finally decided on something we were all satisfied with. Just a few more tweaks with the programming, and Mr T is ready to go!

0 Comments:
Post a Comment
<< Home