The past few months I was busy learning basics of electronics and coding. I have been randomly going through online courses, books, asking around. I realize that though its easier to get access to learn coding through online modules. The challenge still lies in what you do with it all. I don't see myself as a coder or anything, I wanted to know just enough so I can build stuff. In that way, books are better. There is something for everyone. But its tedious and there is no guarantee that you will get what you want to at the end. It's never all in one. So I started asking people around. That's how I met Saurabh Datta. He actually got me 'acquainted' to electronics. So now I can go through codes, understand circuit and figure out the basics.
I am currently doing the project 'Encoded Texture'. I don't know how good the finishing will be or even if we could execute even half of our ideas. But I am having fun. We are making circuits that will be embedded in textiles to play the stories of the weavers based on the viewer's proximity, and how patterns can get visible on touch. We were hoping to procure some expensive stuff (thermo-chromic ink) for this, but for all sorts of reason its not working out. We are now hacking for alternatives. You can read more on this at storiesinfabric.blogspot.in.
What else? I started work on my final year project this week. Its on the concept of communicating interpersonal awareness discreetly. Imagine yourself in an office and you need some help from a colleague. Based on subtle hints like body language, tone etc and awareness you know when its the right time to talk to your colleague. I am using the same concept of (interpersonal) awareness for family members (like elderly citizens) who are away from their families. The idea is to see how technology could work as a medium through which you can share and decipher meaningful interpretations about loved ones. The challenge is to see if technology could provide enough hints without sharing the details. And if and how will people use these hints in their daily communication. I will be making technological sketches and place it in the homes of the elderly citizens. I will add the details in a separate blog.
And I have recently started painting. After a long sabbatical, one day I randomly picked up the sketchbook and pencil. It felt good. The works seem more personal. I do them as and when I feel like. The only prerogative is that I finish them on the spot.
Saturday, November 23, 2013
Saturday, November 16, 2013
Encoded texture: Interpretation of punch card_punch crad reader
“You are aware that the system of cards which Jacard
invented are the means by which we can communicate to a very ordinary loom
orders to weave any pattern that may be desired.
Availing myself of the same beautiful invention I have by similar means communicated to my Calculating Engine orders to calculate an)' formula however complicated.
But I have also advanced one stage further and without making all the cards, I have communicated through the same means orders to follow certain laws in the use of those cards and thus the Calculating Engine can solve any equations, eliminate between any number of variables and perform the highest operations of analysis.”
-Charles Babbage
The workshop was the first step in helping us understand machines.
We choose to make a simple punch card reader. The idea was to create music from a punch card and also record live music into the cards. While it was technically possible, we had very little time. So we made a simple reader that could read one alphabet at a time.
This was the first time I worked on an Arduino, so it meant some extra work.
Things I discovered:
> Setting up Arduino in windows is better done manually.
> It's better to work with solid materials and fix them well before starting work. (We first used small boxes and wrapped them with Aluminum foil. So the circuit was loose.)
> The final reader still doesn't read the data strip. So the work is still unfinished.
The final model was made with wood and a metal plate to complete the circuit. And it worked...almost! The overall experience was fun.
Me and shrankla worked on the coding. Rectifying the code was bit difficult. As it turned out, the code that we used was old and the Arduino IDE would not recognize it.
I will add one last line. Red Burns, who was the ITP director, laid out two points in working with technology: 1) “consider the technology as a tool which, in itself, could do nothing,” and 2) “treat the technology as something that everyone on the team could learn, understand, and explore freely.”
The circuit diagram was sourced from: http://arduining.com/2012/06/10/arduino-punched-card-reader/#respond
and the updated code can be found at: https://gist.github.com/HashNuke/1b2497e5cf8f82f816e6
Red Burns quote from: http://rhizome.org/editorial/2011/dec/15/technology-not-enough-story-nyus-interactive-telec/
Availing myself of the same beautiful invention I have by similar means communicated to my Calculating Engine orders to calculate an)' formula however complicated.
But I have also advanced one stage further and without making all the cards, I have communicated through the same means orders to follow certain laws in the use of those cards and thus the Calculating Engine can solve any equations, eliminate between any number of variables and perform the highest operations of analysis.”
-Charles Babbage
The workshop was the first step in helping us understand machines.
We choose to make a simple punch card reader. The idea was to create music from a punch card and also record live music into the cards. While it was technically possible, we had very little time. So we made a simple reader that could read one alphabet at a time.
This was the first time I worked on an Arduino, so it meant some extra work.
Things I discovered:
> Setting up Arduino in windows is better done manually.
> It's better to work with solid materials and fix them well before starting work. (We first used small boxes and wrapped them with Aluminum foil. So the circuit was loose.)
> The final reader still doesn't read the data strip. So the work is still unfinished.
 |
| First trial: Checking the code for errors |
The final model was made with wood and a metal plate to complete the circuit. And it worked...almost! The overall experience was fun.
Me and shrankla worked on the coding. Rectifying the code was bit difficult. As it turned out, the code that we used was old and the Arduino IDE would not recognize it.
 |
| The final model |
 |
| Close-up shot: Circuit complete |
I will add one last line. Red Burns, who was the ITP director, laid out two points in working with technology: 1) “consider the technology as a tool which, in itself, could do nothing,” and 2) “treat the technology as something that everyone on the team could learn, understand, and explore freely.”
The circuit diagram was sourced from: http://arduining.com/2012/06/10/arduino-punched-card-reader/#respond
and the updated code can be found at: https://gist.github.com/HashNuke/1b2497e5cf8f82f816e6
Red Burns quote from: http://rhizome.org/editorial/2011/dec/15/technology-not-enough-story-nyus-interactive-telec/
Subscribe to:
Posts (Atom)