rhoadley.net   music   research   software   blogs

aru    seminars    m&t    critski    focm1a    cmc    circuit bending    mic2b    sensor technology    comp 3    sonic art    major project
youtube    vimeo    facebook

 
 

Sensor Technology Tasks

Make your own Arduino

Task 8 Triggering and modulating events Set: w5i Due: Monday 19th December 2016 Weighting: assessable (10%) Courses: stech
Prev Task: Investigating sensors - Make your own sensor - Make your own arduino Next Task: Advanced sensors
Task Summary All sTech tasks

Make your Arduino

One of the main reasons for the Arduino's popularity is that it is an open source product. This means that it is relatively easy to acquire the parts and make your own. As a number of articles about this point out, the Arduino is so cheap that it's difficult save money by undertaking such a project, but it's an interesting challenge nevertheless.

Examples




to top of page The Task

  • Make your own Arduino.
  • Test your Arduino.
  • Come up with a creative scenario in which to use your Arduino.
  • Implement and document your experiment(s).

  • Clearly, I don't want you to submit your Arduinos. That means you need to submit some documentary evidence that you've completed your task. The most obvious way to do this is to submit some sort of video of your task working, as well as of the code running. If you can't do this, take photos.

  • Media files
    You must submit media files, such as video, audio or image files, but please ensure that video files are compressed to a reasonable degree. You should never submit dv files, but compress these to mp4. You should submit no file that is greater in size than 25MB/minute.

  • Added value
    By completing the details of the task you will achieve at least a pass mark. By imaginatively and creatively considering how you might implement the task originally you can add value to your submission, and this added value may increase your mark significantly. Even when making videos of short demonstration tasks try to consider musical and performance criteria.

  • Bearing this in mind, try to adapt and make more interesting your files. Simply repeating what we've already done will get minimal marks. So try each patch out in various ways. Even if it's just a blinking LED, try using patterns of colours and/or timings.

  • Compress (zip) your patches, demos, etc. into one file called your_student_number_"myo" (e.g. 0504335_myo.zip), include a readme with your name and student number and, if necessary, how to use or just open the patch.

  • Submit a copy of the files to the i-Centre on Monday 19th December 2016