Files
micromelon-website/content/resources/year-7-digital-tech-at-st-peters.mdx
Tim Hadwen ae3ae18585 Major site overhaul: resources hub, content migration, new blog posts, forms
- Redesign /resources as sectioned hub with category pages
- Migrate 645 Squarespace CDN images to local /images/content/
- Create 9 new news/blog posts with event photos
- Fix blog post slugs (rename gibberish filenames)
- Rename Design Blog to Design Blogs across site
- Remove education page, replace with Platform in nav
- Redesign rover repair request form with dynamic rover entries
- Add school search combobox to contact, store, and repair forms
- Extract shared KNOWN_SCHOOLS data
- Make /rover-expansion-3d-printing dynamically pull from MDX
- Add related resources sections to product pages
- Fix homepage broken /quote links to /store
- Store page: sample kit cards, inline quote builder, mailing list opt-in
2026-03-01 17:14:05 +10:00

51 lines
3.6 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Case Study: Year 7 Digital Tech at St Peters Lutheran College"
date: "2021-07-06"
categories: ["All", "Customer Stories"]
tags: []
excerpt: "See how Meg Foley at St Peters conducted a challenge for their Year 7s using Micromelon."
featuredImage: "/images/resources/year-7-digital-tech-at-st-peters.png"
---
![](/images/content/c064e1-cropped-image-4.png)
For the final unit of Digital Technology this Semester, Year 7 students were given a whirlwind tour of physical computing through learning how to code Microbits, Lego Mindstorms EV3 robotic arms and Micromelon Robots (two lessons for each one) before attempting a final activity incorporating all three technologies.
**Building a Knowledge Base**
To familiarize themselves with the technology, students were given basic code (Blocks and Python) and were asked to improve the code by reading the sensors, updating the values and adding any extra functions that they needed. Students were provided with a few activities during the two lessons that they could complete in pairs. These activities allowed the students to get to know the device, understand how it functions, what sensors it uses and how to code it.
**Learning Through Exploring**
Many pairs then went on to create their own activities and build on the code that was provided. For example, for the Micromelon lessons, students were given an activity card with line following, balance board and obstacle avoidance code. A few groups then found they could combine these to complete an obstacle course. Giving students a choice and allowing for exploration and play helped the students to consolidate their learning.
![](/images/content/750a41-image2.jpg)
**Analysing and Understanding**
After each lesson, students were then asked to reflect on their program in a journal, share their code, answer questions and share any new learnings. Students were asked to respond to the following:
- What did you learn during the lesson? - Explain what you created and how it works.
- Was there anything you found hard? -** ** Share how you overcame challenges
- How could this type of technology be used in a Smart City? - Discuss the use of sensors, “codable” technology and autonomous vehicles.
**The Final Activity**
The culminating activity for the Physical Computing unit was getting students to collaborate using the three devices to solve a challenge, in a Smart City style setting. The challenge outline was,
![](/images/content/fad933-image1.jpg)
- Code the EV3 robotic arm to drop a tyre stack onto the Micromelon Rover,
- The Micromelon Rover then needed to follow a line, avoid obstacles and drive onto a balance board.
As an additional challenge, an EV3 rover was programmed to drive around on the black line as a moving obstacle. Students worked in pairs or trios to solve their part of the challenge; these groupings then worked together as a team (e.g. Red, Blue, Yellow teams).
- Once the Micromelon Rover drove over and tipped the balance board, the Microbit would be triggered and light up.
**The Learning Outcomes**
Students seemed to really engage in this activity as it was challenging, but not impossible, with a number of teams able to complete all aspects of the challenge. Some students struggled with the margin of error when reading the Micromelon Rover sensors (the code given used the brightness reading), especially when the line curved or had a corner. A number of students found solving the challenge really exciting; they felt a real sense of achievement when they solved a problem. It was awesome to see students express the feeling of oh I did that, I made the robot move and follow the line!