this weeks blog post was to do an overall reflection. At first I didn’t really know what to say because we do a blog post every week and I share pretty much everything. I’ve realised I haven’t said everything. My group had a lot of problems where one person in the group would get randomly mad at someone and we didn’t know how to fix it but through the end of the term we have all agreed on everything and when we didn’t agree we wouldn’t argue we’d work out a way to make all possible ideas work. Zali, Mallory and I have been much more productive after we talked about how to make our robotics lessons more smooth sailing, we would get any task we were given done in that lesson and if we didn’t we’d do it the morning after. Out of all the tasks we were given my favourite was probably colour sensor and touch sensor because they both such big challenges and so much fun to look back on our robot doing those challenges. I also loved going around and sharing my knowledge with others when they were stuck or didn’t understand because then they would share what I told them with others. I also really appreciated when other groups helped us when we were more confused than ever. I think robotics is important because not only is it so much fun, and something that I look forward too every Friday, It truly did teach me how to not only work in a team but to feel part of a team.
Our challenge for this week was to use colour sensors. Colour sensors are when you robot will move and then as soon as it find the colour you set it to it will stop and either coast which is when you would make your robot stop but it will glide for a few seconds or come to a complete stop. As it was not very clear in the PowerPoint they sent us we weren’t sure how we were suppose to program. Arnav came and helped us and the program he gave us worked but it would coast either way and it was way to complicated so I modified it and completely change the last bit so it was much more simple. We found that it was much easier to use dark bold colours rather than light ones because they are hard for your robot it pick up so we chose the colour red and it worked so our first challenge was completed. The next challenge we were given was loops. We had to make our robot go around square and then stop using the touch sensor. This was much more of a challenge than the first one because I had already practised the loops but it’s just that it was really hard to estimate the exact measurements of the square so I decided the easiest and quickest way was to use port view. Sometimes we’d use port view and the measurement wasn’t the exact one we needed and we had to make it a bigger number. The other struggle was the turn number because we tried to set it to 52 which is a 90 degree turn because of the surface we were on if we set it to 90 it would’ve been way to big. 52 was a little bit too big so we set it to 51 and that was to small. We figured out that the most accurate one was 51 so we went with that and we were successful.
here is the program for coasting:
here is the program for a complete stop:
Here is the videos of our robot coasting using colour sensor:
And this is it coming to a complete stop:
Here is the video of our robot doing the loop around a square and then stopping using the touch sensor:
Here is the program for the loop challenge:
Our next challenge was to use touch sensors. Now this was much more of a challenge than I thought because they gave us a PowerPoint that explained what we had to do but not how to do it. We had to try and use the touch sensor which is a sensor you attach to your robot so that if your robot runs into anything rather then it trying to keep going it will stop. Our challenges was to try and make the robot stop when it hits our hand and then when it hits the wall. It was defiantly a trial and error challenge but we manged to do it with the help of Mrs Malone. When we finally figured out how to do the program our robot wouldn’t stop moving when it ran into something, we tried to see if the cord wasn’t plugged in properly which didn’t work so we tried swapping the sensor which worked but not very well, my group and I decided to swap the sensor one more time and if that didn’t work we’d ask someone who had already completed the challenge to help. The last sensor we tried finally worked and we filmed both of the challenges. I think the first challenge was harder because our hand sometimes didn’t provide enough force for the touch sensor to process that there was something there, where as when it was pushed against the wall it was much easier for it to stop. I think my group and I did really well in being persistent when our sensor wasn’t working
here is the program and the videos of our robot doing both challenges:
This weeks challenge was to figure out how to use the display block. Display block is a action on the program that can put words on your robots screen as it moves. My group and I decided the best way to take on this challenge was to make our robot bud tell a story about how it was built while also doing a range of actions such as: moving forward, pivot turns and multiple spin turns. We found it quite challenging to make a program that made the words easy to read while also making an entertaining routine. My group also had a hard time understanding why the words weren’t coming up on our robots screen, after a lot of testing me managed to figure our it’s because you need to put an action after the display block otherwise the words won’t show up .Next time I would really like to make a program that everyone would enjoy, like make our robot ask everyone questions using the display block setting. I think my group did really well organising the tasks we were going to do and we were on the same page with everything which helped us disagree much less then we did before. The patterns that I started to see during this task was how some people was trying to rush and finish first where as we were taking our time trying to create the best program we could. I think this task helped we realise I am capable for creating an amazing and impressive program where as before I didn’t know I could do something like that. Some people thought that we were trying to show off by making a big program which was defiantly not the case, In order to make our robot tell the story it had to have a big program, not at all because we were trying to be better than everyone else.
When we recorded the video it was quite hard to read so I wrote some subtitles:
Hello World. I’m bud and I’m going to tell you a story about how I was built. I started off as just a brick but now I’m so much more thanks to Mallory Zali and Sophie!
This is the program.
After finally figuring our how to work as a team and finishing my last weeks blog post we were given our next challenge. This weeks challenge was turning, We had to learn how to pivot and do a spin turn. The difference between a spin turn and is pivot is quite simple. A pivot turn is better for larger spaces because it is simple and fast, a pivot turn is where only one wheel moves, where as a spin turn is better for tight spaces because the robot doesn’t actually move very much at all, but in some situations you may need to use a spin turn for large spaces it just depends what exactly you want your robot to do. My group has finished the pivot turn and has finished the spin turn. The spin turn was very difficult because we couldn’t figure our the degrees so I decided to use port view. We started with the number that port view gave us which was 765 but that didn’t make it all the way around, we experimented and ended up with 755 and that worked with our program. The pivot turn didn’t take very long mainly because it also has a simple program. This program only requires one action, although you do have to change the settings to make it move in the exact turn you want it to go it is still overall very simple.
and here is my groups robot doing a pivot turn and a spin turn
This weeks challenge was to use port view. port view is an option on your brick that measures the degrees that you need to put into your program to make your robot go from one space to another without having to estimate anything. My group found this fairly easy because all you need to do is get port view onto your robot, then place you hand on you robot and gently push it to the place you want your robot to go and it will measure the amount of degrees it moved and then you put that number into your program and it will move that amount. another part of the task was using sensors but when my group put sensors on our robot it wouldn’t move and sometimes the cord would get tangled underneath the wheel. We tried to avoid this by get a shorter cord but each cord we tried was too small. My group and I solved this problem by taking the sensors off and our robot would start to move again. Unfortunately the screen snip that we took of our program didn’t save so we do not have a photo of the degrees.
We couldn’t find the materials we needed for a start and finish line so we improvised and used a hat and a student planner as our start and finish line. This is my groups robot using port view:
This week was based around programming our robots that we built last week. Me and my team found it challenging to program our robot while working as a team. our first challenge was to used degrees, rotations and seconds to make our robot move from the start line to the finish line, my group successfully completed that challenge. Our biggest struggle was to connect to Bluetooth, we would’ve used a cord but it wouldn’t connect to our robot so Bluetooth was our only option. if it didn’t connect we would restart our robot and then turn it back on. I think we did pretty well building and programming and I don’t think I could’ve done it without the other people in my team. I think this project is important because it teaches us how to work as team, although my group has had a difficult time working together we managed to get through it in the end. I’m really excited for our next challenge with our robot bud.
This week is our first week of robotics. Zali, Mallory and I first challenge was to build our robot and start to program it on Friday. it was challenging but we manged to finish out robot working as a team. We programmed our robot to go in a straight line for 5 seconds and we are now working on making it turn. it took 4 hours to build and 1 hour to program. We named out Robot Bud although we weren’t able to change the name of our robot because it wasn’t an option in settings on the brick, which is the thing on the robot that makes it function. I’m really proud of me and my team for finishing our robot without anyone feeling left out. I’m so excited to program our robot.
Welcome to your College Digital Portfolio Geelong College Sites!
To get started, simply log in, edit or delete this post and check out all the other options available to you.