# data[].attributes.body
This was the first challenge we tried. It wasn't too difficult, but the chicken had to be pushed in to the square, so we rethought our code. However, we realised we could keep the code, can just push the chicken in from the same starting point!

We had to code the robot forward, and then back as well.

Above is evidence of it working!

# data[].attributes.body
The next step was to properly get started and ready to code. We decided to first start on the ‘Get Started’ tutorials, just to learn the basics first.

# data[].attributes.body
During this exercise, we learnt how to make the robot communicate, and show different moods.

The image above is the code we learnt for this excercise.

# data[].attributes.body
When doing this activity, we learnt how to properly make the robot rotate. This will come in useful when needing to code the robot to rotate and move around the map.

This image above is the code we learnt for this exercise.

# data[].attributes.body
In this next set of exercises, we learnt how to use the brick to express emotions.

# data[].attributes.body
In this task, we learnt how to show simple moods on the brick. The task is to make a wake up face, but I decided to change it a bit into an angry face. At first, it was difficult to download all the code to the brick, but we understood how to do it after a while.

The image above is the code we used.

# data[].attributes.body
During this exercise, we faced a problem. The original exercise was 'Guess the Animal', but we decided to change it to 'Guess the Expression', because we thought that there weren't enough images for animals, so instead we did moods. This is why all of the images are different emotions instead!

The image above is the code we used.

# data[].attributes.body
During this mission, we struggled. Currently, we have not completed the mission, and are still working on the right code to successfully complete it. We struggled with the rotations of the wheels; always putting too many or too less.

The code above is our first failed code. The rotations were correct, but it didn't move forward enough.

Next time, we aim to move it forward a bit more and ensure that our time is kept to a low.

# data[].attributes.body
This was our first mission grid. We attempted to go from the chicken (M12) mission, straight to the unload cargo (M14) mission. Later on, we decided it would be best it we focused on a mission closer towards our first mission, to reduce the time wasted by moving around the map.

# data[].attributes.body
This was the second attempt of the bridge mission. I was so close to finishing the mission, but unfortunately my robot and attachment was not added on correctly, so we just missed the second bridge!

# data[].attributes.body
Finally, after a lot of trial and error, I completed the bridge mission. My attachment was perfect, and really useful to hit over the bridge. It was coded perfectly and I'm very happy with my results!

# data[].attributes.body
This was the successful code!

# data[].attributes.body
This was the second part of the mission worth 10 points. I spent a while making the code, and finished the mission by the end of the lesson. Next, I want to attempt the first part of the mission.

# data[].attributes.body
This is the code that was used for M13. We replicated the code for M14, and adjusted it slightly.

# data[].attributes.headline
M03 - Unload Cargo Plane 28/11/24 ATTEMPT 1

# data[].attributes.subject
M03 - Unload Cargo Plane 28/11/24 ATTEMPT 1

# data[].attributes.body
In this mission, we had to flip down the lever on the cargo plane to unload the cargo. I spent a long time making an attachment to flip the lever, but unfortunately it was not high enough, so it was not successful. However, the code was correct and working very well! The video above is evidence of it almost working!

# data[].attributes.headline
M03 - Unload Cargo Plane CODE 28/11/24 ATTEMPT 1

# data[].attributes.subject
M03 - Unload Cargo Plane CODE 28/11/24 ATTEMPT 1

# data[].attributes.body
This is the code that we used for our most recent mission. The code was perfect, but the height of our attachment did not reach the lever. Next time, I can build one that can reach it!

# data[].attributes.headline
M03 - Unload Cargo Plane MISSION GRID 28/11/24 ATTEMPT 1

# data[].attributes.subject
M03 - Unload Cargo Plane MISSION GRID 28/11/24 ATTEMPT 1

# data[].attributes.body
This was the mission grid where we planned the mission directions.

# data[].attributes.headline
M03 - Unload Cargo Plane ATTACHMENT 28/11/24 ATTEMPT 1

# data[].attributes.subject
M03 - Unload Cargo Plane ATTACHMENT 28/11/24 ATTEMPT 1

# data[].attributes.body
This was the attachment built for this specific mission.

# data[].attributes.body
Firstly, we built the driving base. This was a challenge at first, and we thought it would take us a while to complete. However, as we started to understand how to properly build it, we were able to complete it faster than we thought.

The image above is the finished robot.

# data[].attributes.body
This mission took us a very long time. It took us 2 weeks and 3 attempts to fully complete and correct the code. But luckily, on the second week, will a new perspective, we completed it!

# data[].attributes.body
In order to complete this mission, we had to build an attachment for our robot. We found a tutorial/instructions on how to build it. Unfortunately, the attachment was not tall enough to reach the leaver, so we had to adjust it and build new attachments multiple times in order to finish it.

# data[].attributes.headline
M03 - Unload Cargo Plane 05/12/24 ATTEMPT 2

# data[].attributes.subject
M03 - Unload Cargo Plane 05/12/24 ATTEMPT 2

# data[].attributes.body
This was our second attempt at this mission. I kept trialing again and again, and it did work quite a few times (fully for the 30 points). But unfortunately, I couldn't capture it on camera. So, this was one I did get on camera that would give us 20 points only, because the cargo car door was touching its black frame, but the cargo was not separate, so we couldn't get the full 30. This is video evidence of it working!

# data[].attributes.headline
M03 - Unload Cargo Plane CODE 05/12/24 ATTEMPT 2

# data[].attributes.subject
M03 - Unload Cargo Plane CODE 05/12/24 ATTEMPT 2

# data[].attributes.body
This is the successful code we used for the final trial. I think this code was perfect, but if only I had moved my robot a bit back from its starting point, it would have been just perfect!

# data[].attributes.headline
M03 - Unload Cargo Plane MISSION GRID 05/12/24 ATTEMPT 2

# data[].attributes.subject
M03 - Unload Cargo Plane MISSION GRID 05/12/24 ATTEMPT 2

# data[].attributes.body
After a bit of consideration, we decided to keep the route of the robot the same as our first attempt.

# data[].attributes.headline
M03 - Unload Cargo Plane ATTACHMENT 05/12/24 ATTEMPT 2

# data[].attributes.subject
M03 - Unload Cargo Plane ATTACHMENT 05/12/24 ATTEMPT 2

# data[].attributes.body
Previously, our attachment did not reach the bar, so it was not able to flick it down. Now, after a lot of reconstruction, we were able to built a successful attachment that was able to stay sturdy, and still move freely.