Brain DeCoded with CodeX - Mission 1, Objective 3: Introducing CodeX

📋

Overview

This is the objective where the hardware finally comes out. Students get a look at the CodeX, name its parts, and connect it to a computer with a USB cable. Then they write a short program that displays a series of bitmap images on the CodeX screen with a pause between each one.

Two things carry the whole lesson: careful handling of the device, and careful typing. Punctuation and indenting matter in Python, and this is the first program where students will feel that. When a program won't run, those are the first two things to check.

🎯 Project Goal: Students will write a short Python program that runs on the CodeX.

🎯

Learning Targets

I can name the parts of the CodeX.
I can connect the CodeX to a computer and CodeSpace.
I can type code in a program file and run the code.

💡

Key Concepts

CodeX is a powerful embedded computer with loads of sensors, and input and output capabilities.
Static electricity can harm the device.
The CodeX needs to be connected to a computer and CodeSpace using a USB cable.
When CodeX is connected to the computer, a window will pop up. It can be closed, it is not needed for CodeSpace.
When typing code, punctuation and indenting are VERY important! If a program won't run, check those two things first.

✅

Assessment Opportunities

Complete the program first_program.
Exit ticket: draw a picture of CodeX and label the parts.

☑

Success Criteria

Complete the CodeTrek steps
Program runs correctly without errors

📂

Digital Resources

▸Getting Started with CodeSpace

🧰

Classroom Materials

▸Laptop/computer with Chrome browser
▸CodeX
▸USB cable

🚀

Extensions & Cross-Curricular

ExtensionThe program code has four images being displayed, with 3 seconds in between. Students can program more than four images.

ExtensionHave students vary the amount of time between images, and even have no time between images to see what happens.

MathCalculate the time it should take for the program to run. Then see if the predictions are correct.

Lang ArtsHave students write about one of the topics covered in this objective.

🔤

Vocabulary

▾

Bitmap Image:an image made up of graphics bits.

🐍

New Python Code

▾

from time import sleepAccess to the sleep() function from the time library.

display.show(pics.HEART)Displays a bitmap image from the pics Gallery.

sleep(3)Program code pauses for the amount of seconds indicated.

📐

Standards

▾

Computer Science - Grades 9-12

9-12.CS.2

📝

Preparing for the Lesson

See Getting Started with CodeSpace for help with the steps below.

Connect a CodeX and run the first_program code yourself before class so you know what students will see on the screen.
Have CodeX units and USB cables counted out and ready. Decide now whether students work individually or in pairs.
Open the pics tool in the Toolbox so you can project the gallery of built-in images for the class.
If you use Google Classroom, set up the class in CodeSpace ahead of time so students can submit their programs through it.
Plan how you want to hand out and collect devices, and where students will set them down while typing.

🧑‍🏫

Teacher Notes

If you use Google Classroom, you can set up the class in CodeSpace so that students submit their programs through Google Classroom.
The built-in bitmap images can be found in the pics gallery. Students should click on the pics tool so they can easily see the list of available images from the toolbox.
When displaying a built-in bitmap image, the name must start with pics. in lower case, followed by the name of the image in ALL CAPS.
Static electricity can damage the CodeX. Remind students to handle it by the edges and not to slide it around on carpet or fabric.
Extensions and cross-curricular projects are included to enhance the concepts in the objective. You can use the extensions to extend students' programming experience.

🗺️

Lesson Outline

🗣️Warm-up / Hook

Hold up a CodeX before you hand any out and open with a quick discussion.

Ask: "What do you think this device can do?"
Ask: "What parts do you recognize, and what are you not sure about?"

Teaching tip: Students are eager to grab the hardware, so name the handling rules while you still have their attention. Hold it by the edges, keep it off carpet and fabric, and static electricity can damage it.

📖Introduce the Objective

Walk through the parts of the CodeX and how it connects, then show the pics gallery.

Name the parts of the CodeX and point them out on the device.
Show the USB cable connection to the computer. A window will pop up when it connects, students can close it, CodeSpace does not need it.
Open the pics tool in the Toolbox and project the gallery so students can see the images available to them.

Teaching tip: Image names are picky. pics. is lower case and the image name after it is ALL CAPS. Write one on the board as a model before students start typing.

💻Student Work Time

Students work through Objective 3 in CodeSpace and build the first_program file.

Students connect their CodeX to the computer with the USB cable and close the pop-up window.
Students follow the CodeTrek steps to type the code into first_program.
Students run the program and watch four bitmap images display with 3 seconds in between.
Students debug as needed, then submit the completed program.

Teaching tip: When a program won't run, punctuation and indenting are almost always the cause. Send students to check those two things first before you look at the code with them, it builds the debugging habit early.

Teaching tip: Students who finish early can add more images or change the sleep times. Try no pause at all between images and see what happens.

✏️Wrap-up & Review

Collect devices, then close with the exit ticket.

Exit ticket: draw a picture of CodeX and label the parts.
Quick share: what was the first thing you had to fix in your program?

Teaching tip: The math extension pairs well here. Have students calculate how long their program should take to run, then time it and compare.

Country/region