Wednesday, 21 February 2018

Week 1 Introduction






Links:
Code Templates http://artworkprocess.com/makingInteraction/microBIT-code-templates.zip
Micro:Bit Projects https://makecode.microbit.org/projects/
Code editor https://makecode.microbit.org/
How to copy files to the micro:bithttps://makecode.microbit.org/device/usb

Time table for GC 2018

Primary activities


Week 1
Intro to class, PebblePad, micro:bit basics (examples 1 & 2 in Instructors kit)
Week 2
Inputs & outputs, adding components: examples 3 & 4 (if not already).
Week 3
Introducing communication via radio. In-class exercise: create a self-contained handheld interaction.
Week 4
(no in-person class at GC)
Assessment 1 due
SB: Conversation about essays, brainstorming first project
GC (remotely): Comment on at least 2 other students’ assessments, post brainstorming about your own first project
Week 5
(no in-person class at GC)
Brainstorming and development of Assessment 2
GC (remotely): post same
Commonweath Games

No class

Week 6
Dev & troubleshooting for Assessment 2
Week 7
Assessment 2 due: critique
Week 8
Final project ideation and brainstorming
Week 9
Intro to simple fabrication strategies (making cases etc.). Induction on laser cutter, at least, for any students who haven’t gotten it yet.
Week 10
Final project workshop
Week 11
Final project workshop
Week 12
Assessment 3 due: critique


Assessment Items

Assessment 1: Critical Context Review

The student must conduct a critical and contextual review of an existing interaction in the world. This can be of a simple mechanical object (a doorknob) or a more technologically complex experience (motion-sensitive sliding doors); it can be a common object like the above, or an art experience like a motion-sensitive light display. But it should be a single, discrete interaction rather than a complex device like a smartphone.

The context review will be 3-5 pages, and include:

  • its intended use;
  • its history (what need it was designed to meet, what existed before, how it's developed over time);
  • some examples of how the similar interaction has been done (e.g., precedents);
  • its intended audience;
  • a site visit and personal observation, if possible;
  • a concluding analysis discussing its effectiveness.

The context review is due in tutorial of week 4.

Sample topics

You may pick one of these topics for your assessment, or choose your own.
  • Pick a simple interactive experience you have every day: sliding door, light switch, water faucet, camera. Do the research that wouldn’t ordinarily occur to you. What problem is it solving? What kind of interaction did it replace? What are different kinds of solutions for the same interaction (eg outdoor hand pump for water faucet, vs. motion sensor)? What weaknesses does it have?
    • Sliding door
    • Light switch
    • Faucet
    • Camera (not phone)
    • Lock & key
  • Pick a public artwork or design event you admire, and find out all you can about how it worked and what its context is. Concentrate on finding historical precedents. For instance, if you like Craig Walsh’s projections onto trees, you might look at the history of landscaping as art, topiary, follies.
    • Craig Walsh, any
    • Camille Utterbach, Shifting Time
    • Marcel Duchamp’s last work
    • Any water installation (public fountain)
Assessment 2:  Working prototype

Conceive and propose an interaction that transforms the user’s experience of a space, or their behavior in it. The finished project will include both a written explanation of the concept (1-2 pages), and a working proof-of-concept prototype that might be very raw. Example: the concept is a motion-activated nightlight, and the prototype is a simple circuit with a sensor and an LED.

Sample spaces

You may pick one of these topics for your assessment, or choose your own. Be specific—choose a particular bus stop, kitchen, etc.
  • Bus stop
  • Kitchen
  • Bedroom
  • Hotel room (how is this different from your own room?)
  • Backpackers room (how is this different from a hotel?)
  • QCA Cafe
  • An underused space at QCA

Assessment 3: Reinventing interaction

Choose an existing interactive platform (a board game, a revolving door, an artwork, whatever), analyse its interactivity, and develop a way it could be re-imagined, transformed, or enhanced. This will involve some investigation and analysis as well as technical work. The emphasis of the assessment is on experiment, play, and process; the finished project will include both a written explanation of the concept (1-2 pages), and a usable object or space.

You may build on your work in Assessment 2 for this project, but you cannot simply repeat or correct it. The new project must show ample evidence of re-conception, for instance moving from a motion-activated nightlight to a model house with interactive lighting.

Possible topics

You may pick one of these topics for your assessment, or choose your own.

  • Photobooth: Find a new way to take a photo remotely, without the camera operator being present. Be specific about the time and place for this project—taking photos of animals at night is a common real-world example.
  • Sculpture: Make a sculpture or installation that changes shape and/or look with the viewer’s participation. Think both about the physical object itself, and light and shadows.
  • Signage/wayfinding: Design something to help people find their way around a specific area (e.g. level 4, or an office building, or other space). This might be a handheld device, or public signage (e.g. LED screens).
  • Kitchen aid: How could a specific kitchen tool be improved, or is there a kitchen task for which there isn’t a tool? “Improved” might mean making the tool work better, or it might mean making it more fun, or funnier.
  • Playground: Make a game you can play with your eyes closed.



week 1 exercise 4 sound output


Outcome:

Links:
Code editor https://makecode.microbit.org/
How to copy files to the micro:bithttps://makecode.microbit.org/device/usb

Step 1
The code
(as a general rule with the micro:bit, it is recommended to add a show icon to the start function, this will allow you to check if your code has successfully loaded to the micro:bit, and that it is running)

Create a new project. From the Music menu select Play tone , middle C. 

Place the play tone code block into the forever function. You will notice when you do this the icon to the right will show a pair of cables coming off the board to a headphone socket and a tone will begin playing.


Step 2
Now save the file. Select  the text field next to the save button and type in buttonAB. This will be the file name for the project. Go ahead and click the save button to the right of this text field. This will download the code to you computer saving it as a .hex file. Copy this file to the micro:bit, as the data is transfered to the micro:bit a light will flash showing that a transfer is in progress. Visit https://makecode.microbit.org/device/usb for more information on uploading files to the micro bit.

Step 3
using the image as a guide connect two wires either to a headphone plug, OR the speaker supplied in your inventors kit. Feel free to ask your tutor for assistance


Week 1 exercise 3 rock paper scissors for micro:bit

This tutorial will introduce you to making games for the micro:bit , if else statements, adding variables, random number generation and accessing the onboard accelerometer.

Outcome:
Play rock, paper, scissors game with the micro:bit. 


Links:
Code editor https://makecode.microbit.org/
How to copy files to the micro:bithttps://makecode.microbit.org/device/usb

Step 1
Create a new project. We want the micro:bit to choose rock, paper, or scissors when you shake it. Place a on shake  code block so when you shake the micro:bit, it will run part of a program.



Step 2
Adding a variable
Select Variables from the menu then set item to.  
Drag the variable item into the on shake block, your code should now look like the following

now click on the set item code block and select Rename variable
 this will open a popup, go ahead and rename the variable to tool



Step 3
Adding random number generation
Select Math from the menu, then select  pick random 0 to 4.

 Add the pick random code block to the end of the set tool variable. Once in place change the number  to 2.


Now when you shake the micro:bit, it will pick a random number from 0 to 2 and store it in the variable tool.



Step 3 
Adding If else statement
What we want to do now is to show a different image on the LEDs that is matches each possible number (0 , 1 or 2)
Select Logic from the menu and select the if then else block.

Now place it under the set variable code block.


Select a condition check from the logic menu.


and add it to the first if statement

As rock paper scissors has three variables, we need to add another condition check and else if statement to the code to do this click the wheel icon next to the word if, which will open a popup
Select and drag else if from the left/grey panel, to the white panel
You can now close this popup by clicking the wheel icon again. Now add another condition check to the new else if statement so that it looks like the following.


Step 4
Now that the statements and condition checks are in we need to get the code to check for which random number has been generated and then for it to do something.
Select the variable tool from the Variables menu,



And place it into the start of both condition statements as seen below.


Now change the second condition statement check from 0 to 1.
You don’t need to check if tool is 2 because 2 is the only number left out of 0, 1, and 2. That’s why you can use an else instead of an else if.



Step 5
Adding images
Now from the Basic menu select show icon and add icons to each of the statements, select a different image for each statement.

Step 6
Now save the file. Select  the text field next to the save button and type in Rockpaperscissors. This will be the file name for the project. Go ahead and click the save button to the right of this text field. This will download the code to you computer saving it as a .hex file. Copy this file to the micro:bit, as the data is transfered to the micro:bit a light will flash showing that a transfer is in progress. Visit https://makecode.microbit.org/device/usb for more information on uploading files to the micro bit.

Week 1 exercise 2 functions and buttons for micro:bit

This tutorial is an extention of the code introduction tutorial

Outcome:
Changing the image displayed on the micro:bit through pressing the A and B button

Links:
Code editor https://makecode.microbit.org/
How to copy files to the micro:bithttps://makecode.microbit.org/device/usb

Step 1 
Load the previous project by clicking 'projects' in the code block editor.

This will open the project manager interface, select Import file from the menu


Click 'Choose File' which opens your file browser and select the previous tutorial project file 'microbit-getting-started.hex' 


Step 2
Inputs from button A and B
Now that the code from the previous project has been loaded we can add the user input to the code.
Select Inputs from the menu, then 'on button A pressed', repeat this again so that there are two instances of the 'on button A pressed' code block.



Step 6
Now add two 'show icon' code blocks into the 'on button A pressed' code blocks. Make sure that you select two different images for 'show icon' code blocks, in this case a cross and tick were selected. 

Step 7
You can now test your project in the editor by pressing the buttons on the interactive micro:bit to the left of the editor. Pressing the A and B buttons will change the image displayed on the micro:bit


Step 8 
Go ahead and save the project file. Select  the text field next to the save button and type in buttonAB. This will be the file name for the project. Go ahead and click the save button to the right of this text field. This will download the code to you computer saving it as a .hex file. Copy this file to the micro:bit, as the data is transfered to the micro:bit a light will flash showing that a transfer is in progress. Visit https://makecode.microbit.org/device/usb for more information on uploading files to the micro bit.

Step 9
Now that the project has been upload to the micro:bit. Test it out. Pressing the buttons will change the displayed icon

Tuesday, 20 February 2018

Week 1 exercise 1 introduction to code editor for micro:bit

 Introduction to code editor for micro:bit

This introduction covers creating a new project which outputs an image to the led screen of the micro:bit device with the code block editor

Step 1
Connect your micro:bit to the computer via the usb cable and open the code editor which is found at https://makecode.microbit.org/# . 

Step 2 
Click basic and select 'show icon'
The show icon code block will then appear in the editor window



Step 3
Drag the 'show icon' code block into the 'on start' function


Step 6 
Now lets save the file. Select  the text field next to the save button and tupe in getting-started. This will be the file name for the project. Go ahead and click the save button to the right of this text field. This will download the code to you computer saving it as a .hex file. Copy this file to the micro:bit, as the data is transfered to the micro:bit a light will flash showing that a transfer is in progress. Visit https://makecode.microbit.org/device/usb for more information on uploading files to the micro bit.