Lesson video

Hello! my name is Mr. Hogan.

I'm so excited to be learning with you today.

We are going to have such a great time learning all about physical computing.

I will be supporting you with our learning during these lessons, and hopefully helping you out along the way.

I'm so pleased that you have decided to complete your learning with me today.

We are going to do brilliantly.

Welcome to today's lesson from the unit physical computing using the micro bit.

This lesson is called "Developing a Physical Computing Project." I'm really looking forward to this lesson.

It's all about how to build and improve your project.

So the outcome is, I can build and improve a physical computing project based on my plan and feedback.

So you're going to start to build your prototype for your physical computing project.

Keywords for this lesson, we've got prototype.

So this is an early model of a programme or digital system.

And we have audience.

So this is the intended users of the physical computing project.

These are really important words to understand.

So throughout the lesson we'll be referring to these words, so please take some time to read and understand what they mean.

This lesson is split into two.

We've got the first part, which is build a prototype based on a project plan.

And we've got the second part, which is refine and improve the project prototype.

So the first part is building the physical computing project, and then the second part of the lesson is refining it, a bit of self-reflection, and improving the project.

So I'm really looking forward to this lesson.

Let's start by building a prototype based on a project plan.

In this lesson, you'll continue to create your physical computing project.

I'm so excited that you're gonna get really hands-on and continue to create your physical computing project.

I'm really excited about it.

So these are the steps we'll be following while designing and building a prototype for your physical computing project.

So you can see we're at step two now.

So we are going to build a prototype, self-reflective feedback, and then give back to the prototype and hopefully improve it.

A prototype is an early model or version of a project.

It is used to test ideas, demonstrate how something works, and identify potential problems before creating the final version.

Two photos from the Beating Heart project.

The paper heart prototype.

The LEDs that simulate the pulsing effect of the heart.

So you can see I'm starting to create the heart, crafting it, and then also putting the hardware together.

So the LEDs connecting to the resistor and wires.

When working on a physical computing project, it is really useful to do the following things.

So test thoroughly.

Only move on to the next step when you are sure the previous step is complete.

Also keep previous versions and save a numbered copy of every tested programme version before moving on.

That way, you can go back to a previous version if things go wrong.

Let's have a quick check.

When should you test your code? A, at the end of the project; B, only when you think there might be an error; or C, after every small change or addition to the code.

Remember, you can pause the video to have a think about the answer, or you can go back to previous slides and rewind the video.

Should we have a look at the answer? It's C, after every small change or addition to the code.

You need to test your code a lot.

So make sure every small change or addition to the code you make, you make sure it works and you test it.

Self-reflection helps you understand your progress.

It highlights what's working well and areas you might need to improve.

It encourages problem solving and finding creative solutions.

You might want to ask yourself, what task have I completed successfully? Are there any challenges or problems I'm facing? How can I fix these problems? What do I need to adjust in my project plan? Do I need help or advice from others? These are the sorts of questions you can answer to self-reflect.

Let's have a quick check.

Which of these is a benefit of taking time to reflect on your work during a project? A, it helps you understand what you're doing well and what you can improve on.

B, it allows you to take a break from working.

C, it makes the project more complicated.

Remember, you can pause the video to have a think or you can rewind the video.

Shall we take a look at the answer? It is A, it helps you understand what you're doing well and what you can improve on.

Aisha is asking, "The wiring is done and the LED lights up, but the blinking pattern doesn't look right." So she's self-reflecting here and asking, "Maybe the timing in the code needs adjusting.

That could fix it." So that's a good example of Aisha self-reflecting.

Moving on to the first practise of the lesson.

So Task A.

1, build your physical computing project.

So this is the time now maybe that you want to pause the video and do the following.

So gather the hardware for the components.

Use the MakeCode editor to write the code that will make your project work.

If possible, connect your microbit to your computer and download your code onto it.

Assemble your prototype by connecting the microbit to the other hardware components you plan to use.

So, pause the video and build your physical computing project.

Task A.

2, self-reflect about your prototype.

A, does your prototype working the way you planned? B, are there any problems you need to fix? Pause the video, have a think about the answer to these questions.

Shall we have a look at a possible answer? So self-reflect about your prototype.

Does your prototype work the way you planned? So it could be, yes, it does work the way that you planned, although I could make the wings of the firefly larger and more colourful.

B, are there any problems you need to fix? The connections to the LED are not stable.

I could use some crocodile clips instead.

So hopefully your answers are similar to this or it could be completely different, but you've identified things that you can improve on or problem that you've overcome.

Well done on making it this far in the lesson.

Hopefully you've built your prototype based on your project plan.

Now the second part of the lesson is to refine and improve the project prototype.

I'm really looking forward to it.

Hopefully you've had a really good fun time building your prototype, and now hopefully we're going to improve it even further.

So how can we refine and improve the prototype? Well, you can use more built-in hardware on the microbit.

There's lots of different components that we could use.

So for example, we could use radio for communication input and output.

This communicates with microbits and other devices without a cable.

We could use a compass for inputs.

This finds magnetic north or measures the strength of a magnetic field.

We could use a temperature sensor that's inbuilt for input.

This measures how warm the surroundings are.

We could use an accelerometer for input.

This detects gestures and measures movement.

You could also use more GPIO pins.

Through the GPIO pins, your programmes could control the power in a circuit for output.

Also through the GPIO pins, your programmes can detect power in a circuit, input.

Let's have a quick check.

Which component on the microbit would you use to detect if it's being shaken? Is it A, LED display; B, buttons; C, accelerometer? Take your time, think about the correct answer.

You may want to pause this at this point or rewind it to play other slides before.

Shall we take a look at the answer? It's C, accelerometer.

Well done if you got that right, don't worry if you didn't.

But yeah, the accelerometer would be used to detect if the microbit is being shaken.

Aisha is asking, "How could I improve my flashing heart prototype?" So you can see the flashing heart working there on the right-hand side.

You could light another LED and programme it to be always on.

You could use a buzzer to sound when the LED lights up.

You can make the LED flash when the light level is low, or even you could cut a hole in the card so the LED display on the microbit could be seen and then make the heart icon flash on the LED display.

So all of these things could be added to improve Aisha's flashing heart prototype.

Alex is saying, "If you have a microbit version two, you could use the music category to play a sound when the LED lights up, like the sound of a heartbeat." So that's Alex's idea of how to improve the prototype.

So on the right-hand side, you have all the blocks available to you.

Let's have a quick check.

Which of these is a reason to refine or improve your project? A, to fix a problem you found when testing it; B, to add something new or make it more exciting; C, so it can be decomposed more.

Remember to have a think about the answer and you can pause the video at any time or rewind it.

Should we have a look at the answer? It's B, to add something new or make it more exciting.

Yeah, that's the reason why we refine or improve our project.

Task B.

1, how could you use the built-in hardware that we've just seen to refine and improve your physical computing project? Have a think about the answer.

You may want to go back and look at the slide that explains what the built-in hardware components are, and then see how you can add it to your physical computing project.

You can pause the video anytime.

So a possible answer, "So for the firefly project, I could use tilt gestures to change the speed or randomness of the blinking pattern.

I could use the sensor to mimic the natural behaviour of fireflies, as they are more active at night." Two, how could you use external components that connect to the GPIO pins to refine and improve your physical computing project? So have a think about what could you attach now to the GPIO pins to refine and improve your project.

You may want to go back and replay some slides or pause this so that you've got some time to think about the answer.

A possible answer could be, "I can connect a buzzer to play sounds when the firefly blinks." Or, "I could connect several LEDs to different GPIO pins to simulate a group of fireflies." There's two great ideas that can be added to your project prototype of a firefly.

Well done for making it this far.

Hopefully you've got some great ideas of how to refine and improve your project prototype.

That's the end of the lesson.

Well done.

So in summary, microbits can be programmed for a variety of physical computing projects based on a design plan.

A prototype is an early model or version of a project.

It is used to test ideas, then refine and make improvements.

Hardware can be used to refine and improve programmes on the microbit.

For example, the light sensor can be used to turn on an LED when the light levels are low.

Well done for making it to the end of the lesson.

I've really enjoyed it, and I hope you have, too.

Hopefully you've really got to grips with your physical computing project, being a bit self-reflective, and also refined and improved it.

Well done.