Cartesian Plane

In maths we had to make a Cartesian Plane. A Cartesian Plane is basically something with four shapes in each corner. You had to use the setpos command with Pen Up to get to each corner and then make the shape with any sort of command. I didn’t know that until later so I made two of the shapes with setpos and I would have been completed earlier but setpos was way more time consuming so when I found out I finished almost immediately. Setpos is really easy to use but making shapes other than a square with them is tricky.

This is my code:

Its very long and the grid thing up near the top is something I used at the start to make a grid.


This is a snip of my Cartesian Plane:

The square and trapezium were both made with setpos entirely so they took about 95% of my time and the other two took about 5 minutes.

Supersonic Sensor Challenge

For this challenge we had two internal challenges. One was to use the ultra sonic sensor to go forward and then stop 20cm from a wall and the second was to stay in a section of four chairs with holes in between and stay in it while still moving around. This challenge was tricky because I wasn’t there when we were told what to do and Euan was the one to attach our supersonic sensor to our robot because I wasn’t there. Abhi helped me by explaining the challenge and telling me the base block to use. He also wasn’t there when it was explained what to do but he got help from someone else.

Challenge 1:

This challenge was simple because all you need to do is make the robot move forward and stop 20cm from a wall form any distance.

This is my code for this challenge:

Ahbi helped me a lot with this one because I didn’t now what block to use yet or how to use it.

This is my video for this challenge:

In this video the robot goes forward until it sees a wall with the supersonic sensor.

Challenge 2:

This challenge was quite hard and confusing to me when Abhi explained it to me but when he showed me his robot doing it I understood. This challenge was hard because I couldn’t get the turn to be good enough easily.


This is my code:

It was quite hard mainly because the turn was hard to get right so it took quite a while.

This is the video:

It shows the robot doing the challenge and has Abhi’s hand in it for some strange reason.

Kite Blog

In Micro Worlds for the past 2 sessions we investigated kites. We made kites out of paper and found out different ways of putting them together to make angles.

Here is one formation we found out.

We found out that in total if you put it together in that way it mad 360 degrees.


Here is an explanation of how a kite is a true kite.

It is a true kite because there is one line of symmetry and if you add two lines from each inner angle when they cross over they should have four right angles. Also the two angles on the sides should be more than 90 and under 180 degrees. The bottom angle is acute angle no matter what.

This is the micro worlds code that I used that made the kite.

My code:

My Picture of the kite that my code created in micro worlds.

I learnt that kites are very specific and I will use this for other things in my learning. if you were wondering how we made the paper kites here is how we made them.


EV3 Follow The Line In An Oval

Our challenge this week was to make the EV3 robot follow a line in the shape of a circle continuously.

This is my code for this challenge:

At first it was tricky because I had it sensing black not white and it was tricky but after Abhi helped me I made it sense white and it won’t stop looking for the line and when it sees the line it goes forward until it can’t see the black line and then it turns until it sees the black line.

This is my video for the challenge:


I still need to add this.

The Switch Block Challenge

Our aim in this challenge was to make a robot go slowly in a continuous pattern on a piece of paper and stay in the barrier.


This is my code snip for this challenge:

It took me a while to do this because it kept turning the wrong amount and was very annoying, but I got it working in the end anyway.


I had two different views for my videos:



I learnt that EV3 is much harder to code in some parts than others and that wheel size makes rotations different lengths according to size. I also learnt that if you use multiple colours you can use the robot on many different sheets.



We did hummingbirds with Mrs Watson and our aim was to finish one module in the outputs and inputs. One module hade 3 or 4 exercises. We worked together with another person, I worked with Abhi.

This is our set:


The first module we did was module 1.  It had 4 challenges. Exercise 1.1, 1.2, 1.3 and 1.4.


Exercise 1.1

Exercise 1.1

Change the 50 to 0 and click on the block again.

This should make the LED turn off. Change the 0 to 100 and click on the block. This is the maximum brightness of the LED. Try out other numbers between 0 and 100 to explore the different levels of brightness that are possible.

We tried 100, 0, 33 and 75.

This our code:

The first number is the port ad the second is the amount of light that goes into the led.

In this snip its at 100 but we have tried different ways.

100 was the max number and if you wrote 1000 it would have the same amount of light as the 100 and 0 means no light, 33 is a bit of light and 75 is quite a lot of light.

This is a picture of the led turned on:

This is a picture of the led at 100 power.

Exercise 1.2

This was our challenge:

Exercise 1.2

You may have already discovered that you can write multiple scripts in the Scripts area. Add a second script that turns the LED off when you press ‘x.’

This was easy because we used a similar program for the last challenge to turn it on and it was space to turn it on or off.

This was our code:

0 was no power which was off and 100 was maximum power which was on and we had the port on 1 because we were still using only 1 led and we needed both programs on the same led so we had the same port on both programs.

This is a video of the program working:


Exercise 1.3

This was our challenge:

Exercise 1.3

Connect a second LED to LED port 2. Write a script that turns the first LED on and then waits 2 seconds. Then the script should turn the second LED on for 2 seconds. Then the program should turn both LEDs off. Remember to save your work!

This was the first bit of code that would’ve taken a while but both Abhi and me have used scratch before and the hummingbird set uses Snap which is similar to scratch so it didn’t take very long.

This is our code:

Again 0 is off and we used 100 as on.

This is our video for this challenge:

We weren’t sure if after the second led turned on if the first one should turn off but then by realising at the end it said turn both of hem off we realised what to do.


Exercise 1.4

This was our challenge:

Exercise 1.4

Write a program that turns two LEDs on at different intensities, waits five seconds, and then turns both LEDs off.


This was our code for this challenge:

This code was quite easy to make and don’t take that long.


This module has 3 challenges and is based around tri colour leds.

Exercise 2.1

This was our challenge:

Exercise 2.1:

 What do you think this script will do? Make a prediction and then try it out. How do you turn the tri-colour LED off?
Our prediction was that the tri-colour-led would change colours every 1 second 3 times and that the last time it would turn off.
This is a video of it working:
It does something strange and we are not sure if are prediction was right or wrong or if we started the video late and the code restarted itself.
Exercise 2.2
This was our challenge:
Exercise 2.2:

Write four scripts to turn the tri-colour LED four different colours. Each script should use a when key pressed block and a Hummingbird TRI-LED block. For example, the ‘a’ key might make the LED aqua.

This is our code for the challenge:

This was quite easy to code and obvious.

This is our video for the challenge:

This video includes Abhi pressing the keys.

Exercise 2.3

This was our challenge:

Exercise 2.3

Make a tri-colour LED blink on and off in your favorite colour at least ten times in five seconds. The tri-colour LED should blink evenly – in other words, it should be off for the same amount of time that it is on. Next, add a single colour LED. The single color LED should be off when the tri-colour is on and on when the tri-colour is off.


This was the hardest to code so far but still not too hard.

This is our code:

This is our video:

This video isn’t that easy to decipher but we’re quite sure we got it right.


Module 5

Here are all the challenges:

Exercise 5.1

Run the script above and watch the value of the distance variable change as you move an object back and forth in front of the sensor.


Exercise 5.2

Write a program that blinks a red light and moves a servo motor when an object is close to the distance sensor. When nothing is near the distance sensor, the light should be off and the servo should not move.


Exercise 5.3

The Boolean block for the if else is checked each time the program repeats the decision. However, the Boolean block is not checked during the statements inside the top or the bottom of the if else block. Try out the script below. In this script, the motor should be on when something is close to the distance sensor. When you run this program, you will notice that the program does not respond quickly when you move an object toward or away from the distance sensor. How can you modify this program to make it respond more quickly to a change in the value of the distance sensor?


We finished all of them except in the last one it didn’t work and we’re not sure why and how because we did the exact same thing as some other people but it still didn’t work and the others worked and on the website it walked us through all the bits really slowly and if you read it all you were sort of an expert for that challenge and you would whizz through it but we’re not sure at all for why the last one didn’t work because we have  no idea whatsoever for what we did wrong.

EV3 Colour Sensor Challenge

The goal of this challenge was to use the colour sensor to move forward until getting to a certain colour, the choices were black, blue, green, yellow, red, white, brown or you could choose no colour at all, you could use more than one colour at the same time. Once you got to the colour(s) you chose you had to make the robot stop turn around move back until getting to another piece of paper and then it was supposed to stop. We also did something so that when it touched the first bit of colour it just backed away instead of turning around.

This is our code for going forward and then backing out:

It was easier and took very little time. It was easier because you didn’t have to turn so it was much more simple, of course it only let you go forwards and backwards not left or right so for some things it is completely useless but for others much more simplistic than turning. We forgot to take a video of it working.


This is our code for moving forwards than turning around:

This was harder and took a lot more time. It took most of the time to make the turn exact so that we could make it do it without it randomly going wonky and end up in the wrong direction. I helped Euan a bit with the turn because he didn’t know how he would write the decimal in. But we both got their in the end. You don’t need the repeat we just used it to see if we could get it going continuously.


This is the video for the part of the challenge for were you go forwards turn and then go back. The video is a bit messy.

By Ishaan




Move Straight Challenge


CHALLENGE: Move your robot forward

from the start line to the finish line and

back to the start. No turns.



What should you do?


  • Move your robot from the first line to the second line and back using seconds, using degrees and using rotations.


1) What did you notice? Differences/Similarities between seconds, degrees and rotations?  Which was most accurate? Least accurate?

Firstly, I think rotations were easiest to code and that degrees were hardest. That was mainly because while coding with degrees it was more time consuming and frustrating because there was a lot of trial and error. Rotations were easiest because they were the first things I coded with and I knew how much 1 rotation was. The most accurate was the easiest which was rotations, and the least accurate were seconds. Seconds weren’t the easiest or hardest to code so it didn’t take to long but wasn’t to fast either.


Seconds were the least accurate and second easiest/hardest to code with here’s a picture to show the code:




Degrees were the hardest to code with and they took most time, here is a screen snip to show the code:





Rotations were the easiest to work with and took least time, here is another snip to show the code:



Turning Challenge



CHALLENGE 1: Your robot is a baseball player. Program the robot to go around the baseball diamond.




What should you do?


  • Program the code
  • Test it out


Explain our code.


What was challenging?

None of it was very hard but some of it took a little bit of trial and error. It didn’t take to long either.


What do you notice about how the robot moves? Which parts? How?

I noticed that the wheel that was closer to the direction you were turning moved by itself, the robot would turn in that direction.

Could it be done a different way?

Yes it could be done a different way but we chose the way we did it, because we found that way most efficient.



CHALLENGE 2: Your robot is a baseball player.

The robot has to run from one base to the next.

Oh no! He’s going to be tagged out.

So he has to turn around and run back to the previous base!










What should you do?


  • Program the code
  • Test it out


Explain our code.


What was challenging?


What do you notice about how the robot moves? Which parts? How?


Could it be done a different way?




I was put in a group with Euan, Hayden and Abhi and we worked together very well. This is a picture of the things in the starter kit. It has a breadboard (the white rectangular prism with holes), a green board which is used in later projects, a wire (to connect the green board with your coding on your computer), some LED’s to light up and use in the project (it is used in nearly all of the projects), some resistors ( the metal things with a brown thing in the middle and there are 4 packets with them all with different Ohm levels), Poteniometers are also there which are blue things which are used as resistors but they are more powerful and there are also the wires which you use with the breadboard and the green board for conections to power the LED’s and different other things like LCD screens.



These two are the picture and video for Abhi, Hayden, Me and Euan’s first challenge it was quite simple and in case you couldn’t tell by the videos the challenge was to make the LED blink.