The (temporary) sound boxes have been updated so that they can be triggered via littleBits circuits. Each box now has two littleBits connectors at one end – one for input, and one for output. They have been tested using a simple toggle button on the input side, with an LED connected to the output:
As the large playback-only soundboxes worked fine at MERL, and the small size of the last version made it very difficult to get all the components in, the sound recorder has been scaled up.
The old version, the new one, and a quick model of a pint glass I had nearby for scale.
The speaker on the last version was crudely glued to the bottom, and didn’t really fit properly; the new one has a proper piece to hold the speaker with a grill to protect it. The bayonet fitting idea was copied from the top piece of the old design.
The joint between the bottom piece and the main body is less obvious than the top/body joint as the edges aren’t rounded off, but it should still be secured with glue, tape, screws, etc to stop users from undoing it.
It was noted that it would be nice to be able to ‘point’ the device at the desired sound, like a microphone or dictaphone. The previous version had the microphone mounted in the side of the main body. The new one has a socket in the centre of its top, with a small grill to protect the microphone.
As the new case is so much larger, this should allow for more complex electronics (perhaps a microphone preamp to clean up recorded sounds a little), and larger batteries, as well as being easier to construct.
It will take considerably longer on the 3D printer though. It’s unlikely that more than one case could be printed simultaneously.
The pilot workshop at MERL was based upon two main activities, both relating to sound. The first activity involved looking for objects around the museum that could have produced specific sounds that we provided on custom-built sound players (which we informally refer to as the ‘Sound Boxes’):
The Sound Boxes
The sound boxes were designed to be as simple to use as possible: turn the dial to one of the six positions, press the big button and the sound will play. We have used sound recorders/players in previous workshops, but they are often very complicated to operate, and therefore require someone to assist in using them. For this pilot, members of the group were given the sound boxes and asked to try and locate the source of these sounds from around the museum. The activity itself worked very well and engaged the group members. The boxes themselves also performed very well too, and produced good clear sounds. More importantly, everyone could use them.
The sound boxes were also used in the second activity, along with various other sound making objects, to produce a soundtrack to a silent movie clip.
We are planning on extending the capabilities of the sound box to more sounds, and possibly create distinct players for different categories of sound. i.e. one for mechanical noises, one for animal sounds, etc.
Ahead of the Autumn workshops planned with Reading College, Kate, Nick and I have planned a session with a group from Mencap Reading to test out some ideas and Nick and Craigs new sound storing boxes (to be revealed!).
Here is how we have planned the day:
Attendees: 3 researchers (Kate, Nick, Kassie), 6 Mencap co-researchers, 2 support workers.
When: Thursday 5th September – 10.30am – 2.00pm
10.30am: Welcome Talk: Introductions from everyone, explain the day ahead, short tour of MERL.
11am: Recognising Sounds: Scavenger hunt where co-researchers hunt to find objects that make the sounds they can hear from the device.
12pm: LUNCH: Picnic lunch inspired by the collection at MERL.
12.40pm: Making Sounds: Sound making workshop where we will create and record sounds using instruments to accompany video clips from the rural past.
1.50pm: Review: Review of the day. Quick questionnaire for co-researchers.
Nic showed us unit that could trigger smells which connects to Littlebits triggers. The box contained a strawberry its smell wafted by a fan, Nic has developed the box to be used with the Littlebits kit to diffuse various smells.
Demo of Sound Collection Module by Craig, the prototype has been made so a Co-Researcher can hang the unit round their neck, record 6 sounds by pushing the big red button during a tour of an exhibition, hear the recorded sounds by pulling the neck lanyard, choosing each sound by twisting the top segment. The Co-researcher can then experiment triggering sounds using the LittleBits Kit that will add to the development of sensory object museum interpretation. Unit still needs a bit more refinement, but we are hoping one will be ready for our test workhop at MERL Museum of English Rural Life with members of Reading Mencap on Thursday May 5th 2013.
Craig demos sound collector
Sound collector module with different lids that links to littleBits
Faustina tests sound collector linked to Littlebits to trigger recorded sounds
The projects examined in previous posts had a lot of interesting concepts and ideas- this is a condensed list of them, with recommendations for future attempts.
===============================================================
Squishy Circuits:
Tern:
littleBits:
Tangible Programming Bricks:
Electronic Blocks:
Reactable:
StoryRooms:
Cuboino:
GameBlocks:
Dr. Wagon:
Topobo:
===============================================================
PRINCIPLES COMMON TO PREVIOUS PROJECTS:
MODULARITY:
Nearly all tangible programming interfaces use modular components, where a single block, device, or item represents a function or serves a single purpose. Programs are created by putting these components together.
ACTIVE/PASSIVE COMPONENTS:
Some had the components themselves provide power, processing, or effects, whilst others had a dedicated power supply, or offloaded these functions to an external device. Both approaches work well, though self-powered and processing devices tend to be larger and more complex. This may not be a downside- larger components are more easily manipulated.
FLEXIBILITY:
Schemes involving ‘active’ components tend to be less flexible with regards to their connections. They have to be connected in one or two ways, limiting the physical structure of the programs and thus the possibility of incorporating them into other devices.
Many schemes were created to control a specific device, such as a turtle or microwave. Few were able to interface with a variety of sensors and effectors in the same manner as the Arduino.
IDENTIFICATION OF FUNCTION:
Most modules’ functions are indicated to the user by icons. These mean users do not have to be able to read in order to use them. None of them actively used texture to indicate function, but occasionally had surface details as a side-effect of their design. Colours were often used to group modules into categories.
===============================================================
RECOMMENDATIONS:
Modular components are a useful way of providing flexibility whilst still giving users some pre-defined functions to use. Manipulating several small objects, each with a clear individual function, is easier than a “blank canvas” like a word processor.
Active components, being those which provide their own power or processing, are more complex and therefore more likely to cease functioning or malfunction. This may be due to failure of their power supply, damage to their circuitry or mechanisms, or from poor connection to other necessary modules. Modules should be kept as simple as possible.
Passive components, although more robust and simpler, cannot provide some features that active ones can, like the ability to ‘test’ a module without connecting it to a program. Active sensors or outputs could be constructed with a ‘test’ button to trigger their output, or sensors could be given an indicator to show when they have been triggered.
Both approaches would be suitable, though it should be noted that passive components will require an external processor which may introduce complications.
Connectors should be keyed to prevent damage to the components, and to prevent frustration of the users- if a connection is incorrect but this is not indicated to the user, the device may not function as expected, with the fault being difficult to locate.
Ideally, connectors will be able to accommodate several different orientations to permit the programs/devices to fit into other creations more easily.
It should be made possible to interface with a wide variety of sensors and effectors, rather than limiting control to one device- given that the project’s aim is to simulate sensory experiences, limiting the possible types of experience is counterproductive.
The function of a module should be obvious from its features. This should be accomplished using as many senses as possible, rather than simply writing the function of the module onto its casing. Icons should be preferred over text.
External processing does make individual components simpler, but introduces complications as the interface between the program modules and the external processor must be reliable.
It also allows for software upgrades to be applied to the processor, without having to alter the program modules. As these are likely to be embedded systems, compared to an external processor which has fewer restrictions on size and power, upgrading its software is probably simpler.
It can also more easily accommodate new modules, as only the processor must be updated as opposed to all modules.
Reading University has a 3D printer, which we planned to use for this project. It uses ABS, which is durable and despite only being available in one colour,c an be relatively easily painted if necessary.
The printer is compatible with Solidworks (or anything else that produces .STL files), which allows for precisely-made parts to be produced to scale.
The case, littleBits connectors, and the three ‘top’ designs have been printed (still learning to use the camera!):
This is the hex-top. It has had to be extended upwards to accomodate the internal parts.
This is the dome top- it was tall enough already. The shaft of the rotary switch used to select the sound has been cut to fit.
This is the original ‘pie’ top, again, extended to fit.
The current design makes them relatively easy to change, but this does mean that the tops could be removed by a user. Future versions will require bayonet lugs or some similar mechanism to hold the top on.
The littleBits connectors are generally the right size, but the small prong and socket is too fragile in 3D-printed ABS. They are also slightly the wrong size and do not fit cleanly. It has already been noted that they will need holes for magnets and electrical connections, so future versions will incorporate these changes.
Kate and I are planning to hold a preliminary sensory session with a group from Mencap at MERL in September. Hopefully this will be a good time to test out the audio prototype and some ideas planned for the Autumn sessions.
Entrance to MERL
We visited the museum and the archive at MERL
Invisible Horse
Duck Basket
Threshing Machine Working Model
We considered existing objects that could contain sensor and listened for sounds used in the existing collection.
Listening to Crafts
Display with sound
We found that videos are used in the museum although most of the films have no actual sounds of the activity instead a narrator describes the activity. The videos of crafts pictured below do feature sounds of the process.
Harness Making
Here is a compilation of the range of sensors and outputs we can use, or could make ourselves (to be compatible with LittleBits) to get an idea of how much choice we really have! (the ones marked in bold are already available to purchase in LittleBits)
Sensors: light, sound, bend, roll switch, toggle, motion, pressure, slide dimmer, pulse, time sensor, stretch, tilt, accelerometer, blow, proximity
Output: fan, light, sound, buzzer, motor, vibration, rgb LED, bargraph, smell (based on olly factory/aroma company), video
Also, LittleBits supply AND and OR logic gates which add complexity to the circuits.
Just as a log: In our meeting last week, we also talked about practical ways to introduce and demonstrate the co-researchers to the concept of the different sensors overcoming the problem that the sensors don’t look like what they do (e.g proximity sesnsor looks like a phone). Here is a list of some of the ways we discussed:
light sensor in a box, bend sensor in a foam noodle, pressure sensor in a stress ball or shoe, blow sensor in a windmill, motion sensor in a wand, accelerometer in a bottle with oil and water.
Please feel free to edit this post with other ideas or if I have missed anything out!
A circuit has been designed around the ISD1820PY chips which allows up to 12 of them to be used in a single device.
As mentioned in previous posts, the method of selecting which sound ‘file’ to play or record must be kept as simple as possible. We also want to make every action or method of interacting with the device distinct. The main idea has been a rotating section, either a ring or the entire top of the device, which ‘clicks’ round.
Colours, textures, or embossed indicators (numbers, braille, or abstract symbols) will be used on the top section to differentiate between the sections.
The ‘golf ball’ design shown earlier, though it looks a little like a microphone and provides a good surface to grip, does not do this, and so a few other designs have been created.
The first concept was a similar image to a ‘Trivial Pursuit’ counter, with the distinctive pie wedges. This design provides plenty of space on its top surface for indication markers (coloured surfaces are used to indicate the sections here, but can be replaced with other methods later). The grooved lines match up with similar grooves in the body of the device, allowing users to check if the sections are lined up correctly.
This dome-shaped version should provide a more ergonomic gripping surface, at the cost of size. The curved surfaces are also harder to print or emboss indicator markers on.
It should be the same white colour as the other designs- this screenshot is grey.
This hexagonal one was created because I was looking at bolts earlier. It’s similar to the ‘pie wedges’ design in terms of usability and practicality.
Showing the sound quality and methods of recording/playback on the prototype.
Still needs a better speaker and some batteries, as well as the selection method!
