Tangible Embedded Linux
Workshop at TEI 2013 by Edgar Berdahl and Quim Llimona
(Some portions of the teaching materials may have been contributed by other authors such as Wendy Ju, Bill Verplank, Michael Gurevich, Spencer Salazar, Matt Wright, etc.)
This workshop consists of a condensed version of the material from labs 1 and 2 for the course Music 250A at Stanford University. For this workshop you need your Satellite CCRMA kit, a laptop computer with Ethernet adaptor to program it, and some headphones with a mini 1/8" (2.54mm) stereo jack.
You are also invited to bring the following optional items, but they are by no means required:
- Some of your favorite breadboardable sensors and LEDs.
- A set of small, battery powered speakers with 1/8" (2.54mm) jack.
- A pico projector with cable to HDMI connector.
- 1 Introductions
- 2 Powering Up For The First Time
- 3 Connect To Satellite CCRMA
- 4 Prepare Arduino
- 5 Stop Default Patch and Run Pd
- 6 Learn A Little More About Pd
- 7 Routing Power On The Breadboard
- 8 Connect Your Analog Sensor To Pin A0
- 9 Make Your Tangible Embedded Prototype
- 10 Appendix A. Transferring Files To and From Your Kit
- 11 Appendix B. Learn A Lot More About Pd
- 12 Epilogue I. Protect The Flash Memory
- 13 Epilogue II. End Of Studio
- Participants explain their backgrounds and what they would like to get out of the studio.
- Show some videos of prior projects
- Construct Satellite CCRMA kits
Powering Up For The First Time
Plug the Ethernet port of the Satellite CCRMA into your laptop. Then use the USB micro cable to connect your laptop to the Raspberry Pi--this provides the power. You should see some lights turn on, flickering every now and then. This means that Satellite CCRMA is booting up.
Connect To Satellite CCRMA
In order to see what your Satellite CCRMA kit is doing and program it, you need to log in to it. To do so, follow these instructions.
After you login, you will see the prompt ccrma@satellite:~$ This means that you are logged into a computer named "satellite" as the user "ccrma", and you are currently in the directory ~, which is the shortcut for your home directory.
- The next step is to install some default firmware onto the Arduino so that it knows what we want it to do. First make sure that the Arduino Nano is connected to the Raspberry Pi via the retractable USB cable.
- Then, start the Arduino software in the terminal by typing the following command. The ampersand (&) is there to indicate that even though you are opening a new window, you should still be able to keep typing at the old terminal.
- Open StandardFirmata from the Arduino software pull-down menus File|Examples|Firmata. Look at the program. This is what will control the Arduino.
- Select Arduino Nano w/ ATMega328 under Tools->Board and /dev/ttyUSB0 under Tools->Serial Port. Then hit the Play button to verify and compile the program.
- Upload the Firmata firmware to your Arduino Nano using upload button, the fourth square button from the left (the one with the sideways arrow). If you watch the RX and TX lights on the Arduino carefully, you will "see" the data flow over the serial USB link into the Arduino as the firmware is uploaded.
- Close the Arduino program by closing all of the Arduino windows. (This is important!)
Stop Default Patch and Run Pd
- In order to be able to hear audio, you will need to plug a pair of ear buds, headphones, or loudspeakers into the 1/8" (2.54mm) jack labeled AUDIO OUT on the Raspberry Pi. Be careful when plugging the headphones in and not to pull too hard on the headphone cable!
- A default pd patch starts running automatically when your kit finishes booting up. To stop the default patch, run the command
- Start pd now with the following command:
- To start audio, click on the Compute audio checkbox.
- Now to test audio, go to the media pull-down menu and choose Test Audio and MIDI. If you still do not here any sound, then probably you missed one of the steps so far. If you look at the messages in the main pd window, you might find a clue.
- Once you have audio working, close the window test audio and MIDI window.
Learn A Little More About Pd
If you get stuck at some point while learning about pd, remember that you can right-click on an object to get help information about the object.
- The patch ~/pd/examples/just-play-WAV-files/play-WAV-file.pd shows the easiest way to play a WAV file.
- Look at the pd lecture patches stored in ~/pd/pd-lecture
- By default, the patch ~/on-startup/default-patch.pd runs right when the kit finishes booting up. Open this patch manually from within pd.
- Look at the lower, right-hand corner of the patch. You will see that this patch automatically enables audio 8 seconds (i.e. 8000 milliseconds) after the patch is opened.
- Now, if you touch the A0 pin or the Arduino with your hand, you should be able to hear the sound of a windy day. (If you still don't hear anything, try touching a grounded object with your other hand.)
- The patch works by filtering white noise (from noise~) with a bandpass filter with a high quality factor. The output of the highpass filter is then scaled by a gain controlled from A0.
- Look inside the subpatches that are named pd <name> by double-clicking on them.
- You will notice that this kind of sensing is not very reliable. In the next parts of the lab, you will learn how to connect a sensor to A0 to improve the quality of the sensing.
Routing Power On The Breadboard
- Remind yourself about how the sockets on the breadboard are wired together:
- Now you are going to start putting jumper wires into your breadboard. Try to be careful to build the circuit correctly. (If you create a short circuit (one kind of wiring mistake), then the lights will instantly all go off on the Arduino. If this happens, please try to undo the short circuit right away.)
- Now connect jumper wires as shown in the image below so that the upper and lower long columns can serve as a power supply for your future circuits.
- Connect a short jumper from the GND pin of the Arduino to the blue column.
- Connect a short jumper from the 5V pin of the Arduino to the red column.
- Finally, use two longer jumpers to connect together the blue columns and the red columns as shown below:
- Check your wires again to make sure that you did it correctly!
Connect Your Analog Sensor To Pin A0
Each participant should have one analog sensor in his or her kit. Optionally go to one of the following links to learn more about electronics or sensors. Ask one of the staff for help if you feel uncomfortable with electronics. We will help you.
If you have a force-sensing resistor, you can hook it up to an analog input of the Arduino by building a voltage divider out of it with a 33k fixed resistor. The idea is that you put two resistors in series between power and ground: one that changes resistance (your sensor), and one of a known, fixed resistance. At the point in between the two resistors, you can measure how much the voltage has dropped through the first resistor. This value changes as the ratio of resistances between variable and fixed resistors change.
- force-sensitive resistor (FSR):
- If instead you have a soft-pot or a standard potentiometer, then you can wire it up this way:
- If you have an infra-red range sensor, then connect the black wire to ground, the red wire to 5V (power), and connect the other wire directly to an analog input on the Arduino.
Optimizing The Patch
You might want to speed up the lowpass filter so that your pd patch responds more quickly to your sensor. To do so, go inside the pd lowpass subpatch and increase the cutoff frequency of onepole~ from 0.4 Hz to something more like 10 Hz.
Make Your Tangible Embedded Prototype
- Now use these tools to make a completed prototype by editing ~/on-startup/default-patch.pd
- This way, each time you power up your kit (whether or not a laptop is connected), it will run your modified patch.
- For additional exercises or things to think about, you may want to look at the Further Reading or down below also.
Appendix A. Transferring Files To and From Your Kit
You can use CyberDuck to get files
- Choose Open from the File menu and select the patch 4_algorithmic_music.pd. In the main pd-extended window, click on the compute audio button. Then go back to the patch, move the speed and width sliders slightly to the right, and bring up the volume. You should now hear some sound in your headphones. Play around with the parameters to see what new sounds you can discover.
Appendix B. Learn A Lot More About Pd
- Here are some lists of pd objects that you can use to discover new object names: http://protman.com/content/list-puredata-objects-and-extended-objects http://www.umatic.nl/workshop/objects.txt
- Go to the Help pull-down menu, choose Browser, go into Pure Data (near the top), and then look through the demonstration pd patches that are organized into chapters.
- For even more further learning, see the labs from the Music 250A course, which are stored in ~/pd/labs-Music-250a-2012
Advanced demo patches for users who have a monitor or pico projector connected:
- The pd patches in ~/pd/examples/SimpleGraphicsOSC can be used to send OSC messages to the SimpleGraphics executable to render hardware-accelerated graphics.
- OR, the patch ~/pd/examples/just-play-video/trigger-omxplayer.pd can be used to trigger the playback of H.264 or MPEG2-encoded video clips.
Epilogue I. Protect The Flash Memory
- Once you are completely done making your prototype, then run the command disable-flash-writes
- After this, any changes you make to your memory card will not be persistent. This means that you can power down your kit at any time without any warning (for instance if it is in a museum), and you do not have to worry about the disk integrity (as you would with your laptop for instance if its power were suddenly cut). If you change your mind later, you can always run the command enable-flash-writes to undo this step.
- (If you prefer not to protect the memory of your kit, then when you are finished and before you power it down, kindly remember to run the command sudo halt, enter the password, and then wait 20 seconds before removing the power.)
Epilogue II. End Of Studio
We will evaluate each others’ interactions in pairs and then share the results in a concluding roundtable discussion. There has been some discussion about also presenting to a wider audience.