# data[].attributes.body
In this first out of 2 lessons we spent building, we were able to successfully assemble the first part of the bot and research and watch videos about cargo connect, we also looked for videos of other previously successfully teams and watched them complete the map and missions for inspo.

# data[].attributes.body
This lesson, we plugged in the wires and familiarize ourselves with the coding interface and create some basic code that we did not end up using, it was just to experiment with connecting the bot to the computer. We used some basic tutorials for this.

# data[].attributes.body
In this lesson we mapped out and planned the missions, we were not able to successfully code the car and you can see us struggling in the photo, but we learned a lot. In the lesson however we were able to still plan it, our small plan is attached below

# data[].attributes.body
I worked during break on 04 Activity

# data[].attributes.body
In this lesson we started straight away, We started doing a full run through of what we had already coded, to jog our memories.

We then made some small adjustments to our previous mission, to make it easier to transition between that mission and our next.

We started brainstorming what we should do next, after looking at other teams and their strengths. We were then able to add "Transportation Journey" as the third and "Air Drop" as the fourth

Making the order so far:

1. M12 Large Delivery - Chicken Part

2. M14 Bridge

3. M04 Transportation Journey

4. M08 Air Drop

This order is fully apt for the process, using information that we gathered ourselves through testing, communicating with classmates and consulting videos available online.

We did more coding and went back and fourth, we ran into a problem between M14 and M04, there is a small hook-like object sticking out on the M14 Piece, more often then not causing the EV3 to spur off slightly in the wrong direction, causing all further commands to be off.

We overcame this by ensuring the EV3 would go by a slightly different angle, although we cannot be certain this will fix it, we do know that 9 times out of 10 this alteration will ensure the EV3 to continue going the right way.

It was hard finding a solution and toying around with it to make it as precise as possible, but we managed in the end.

All of this can be seen on the timelapse which is attached below.

# data[].attributes.body
The first lesson after choir fest, we were informed of what work we had to do and our teams, as me and Matti had both partaken in Choirfest, we were paired up. We each made a presentation on efficiency. We also familiarised ourself with the bricks and with our recourses.

# data[].attributes.body
We got straight to work this lesson, We started by updating padlet and trying to find the exact dates as Mr Turner asked us to. While Matti was continuing to work on this, I decided to build the robot to make the best use of our time. We compiled a list using online resources for the best order to complete tasks in. We tried measuring how long a wheel rotation was but found this quite tedious, instead we took a different approach and found it took 2 seconds to get to the first mission. We extended this to go there and back and coded it.

We thought this lesson was very successful as we had also completed our first mission.

# data[].attributes.body
This is the full lesson (except our success) As A timelapse

# data[].attributes.body
I completed some homework on this day, specifically the "Safety" HW. I completed this task hastily as I had other work in design and in other subjects that I had to complete

# data[].attributes.body
In this single lesson, Me and Matti continued working together to produce separate slides on the current process of transferring and moving cargo, how to make it safer, reducing the costs and efficiency.

# data[].attributes.attachment_caption
Our order of missions, we completed the chicken pen in this lesson.

# data[].attributes.body
OpenAI, ChatGPT: "this is the board, for example i we start with the chicken pen, its hard to do the blue and yellow one, please make a new order" - Accesed 15/11/2024

# data[].attributes.body
This was our final and working attempt where we used seconds to measure the distance.

# data[].attributes.body
This was a failed attempt, we used wheel rotations here, later we changed to seconds.

# data[].attributes.body
This was our code for the successful mission.

# data[].attributes.body
In this lesson we worked on our presentation on transportation infrastructure and created the slides that can be seen below.

# data[].attributes.body
In this lesson we added more code to what we had so far and played with units and what measurement to use, we went from wheel rotations to seconds, after trial and error - me and Matti realised that this is the best idea. We also start coding the start of our next mission.

The "large delivery" mission: It was very frustrating repeatedly getting it slightly wrong but we eventually came somewhat successful, being able to knock over the first half, but not the second. In the next lesson, we aim to reverse the robot and do the other side.

# data[].attributes.body
Attempt 3 - Partial Success:

This is what I would call our most successful missions and transfer between mission yet, we allowed for 4 seconds to quickly set it up and move it again.

# data[].attributes.body
Attempt 2: Fail:

This is what I would call the least successful experiment, when completing our second mission, we got the placement slightly wrong and it tipped over after striking he flap at the wrong angle.

# data[].attributes.body
Attempt 1 - Experiment:

This attempt started with our usual first mission and we experimented with ways to go to the next mission, after speaking to peers, we discovered that the robot did not have to go exactly on the path, so we quickly changed our objective, opting for a more efficient and easier route.

# data[].attributes.body
We started with cross checking our padlet, to avoid any confusion between what we did in the lesson and incase we accidentally mixed up dates.

We were able to successfully complete the first part of the next mission - it took a long time and over 17 attempts but we finally got there!

We toyed around with the coding and the timing - what was most hard was the the angles and finding out the most efficient way to turn

# data[].attributes.body
This was our route half way through the fully planned route, we experimented with the turn, changing units and doing trial and error to get the umbers right.

# data[].attributes.body
Below was our succesful attempt

# data[].attributes.body
Here is the mission grid for the mission that we successfully completed in the lesson.

# data[].attributes.headline
At this time, we were on school holiday, the holiday started just after the Friday on the 18th - finishing on the 1st November - that is why there is a break in the dates.

# data[].attributes.subject
At this time, we were on school holiday, the holiday started just after the Friday on the 18th - finishing on the 1st November - that is why there is a break in the dates.

# data[].attributes.body
Here is a more labelled mission grid. Matti added blue to make it stand out and clearer.

# data[].attributes.body
In design this term, me and Matti were partners for Cargo Connect and over the past few months, we successfully coded over 4 different missions, optimizing their order for efficiency and logic.

We learnt new teamwork skills, were able to approach opportunities with coding in a new way, which we learnt through thinking outside the box and making many adjustments.

We faced many challenges from not being able to get the turn right, to struggling with assembling the vehicle and having difficulties with coding.

We overcame this mostly from a lot of trial and error and consulting YouTube videos and classmates for advice.

We worked well together and achieved a good final product.