Research & Learning
Other Class pages
I'm one of 5 instructors teaching 6 sections for PComp this fall. You can reach me by:
Office hours: Sunday evenings 6:30-8:30pm in the adjunct lounge, and by appointment - email me to set something up. Also, the latest version of Skype has a screen share feature that's great for remote help. My Skype name is dustyn.roberts. By day my office is at the NYU-Poly campus in Brooklyn: 6 Metrotech Center, Rogers Hall 520B. Stop by any time for help (take the A/F train to Jay St, exit at back of train).
Notes from classes:
What is Physical Computing? SixthSense Technology
Can you find out what code is already on an Arduino?
http://www.bareconductive.com/home.html (A video of conductive ink, invented by Royal College of Art students)
Alex's notes in response to reading - The User Illusion:
Intro Pysch / MIT ocw / Jeremy Wolfe - Lecture 5 (Limiting information)
Lecture notes / Lecture slides
Additional lectures here
Internetís effects on cognition and the brain:
Perception of time:
Notes from Alex and Ezer's EMG project:
Below is the link to the lab that we used for the EMG (although it was a ECG schematic). This is the one that seemed to work. Be warned, the background 'pictures' make the lesson almost unreadable.
And the schematic comes from this site that encourages diy EMGs using Arduinos.
1 bit: 0 or 1
It turns out that there's a standard system called ASCII code that can takes any value from 0-255 and assigns it an alphanumeric character (letter, number, or punctuation mark). Here's an example table:
The drawback is that when you send things at text, it takes as many bytes as there are digits. For example: a raw value of 12 only takes up one byte, but an ASCII encoded number 12 takes two bytes: one byte for 1 and one byte for 2. Be careful here. If you're speaking in ASCII-encoded text but listening for a raw value, you might interpret the 1 and 2 as their representative values in ASCII of 49 and 50. And if you're speaking in ASCII and listening in raw, you can get all kinds of garbage characters like ~, +, *, etc. that correspond with the representative ASCII values.
If you're thinking that ASCII encoding is an inefficient way to send numbers from 0-255, you're right. After all, sending the number 12 as two ASCII encoded bytes instead of one raw byte takes twice as much information. However, at the standard baud rate of 9600 that we work with, you're unlikely to feel this efficiency for just a few numbers. And it also gives you the flexibility to agree on one method of encoding for anything you might want to communicate between the speaker and the listener.
One more note about ASCII: the first 32 raw values correspond with control characters, that won't even show up as garbage but stand for things like "carriage return" (ASCII 13).
This serial data is passed byte by byte from one device to another. If you're constantly sending values between 0-255 like with a potentiometer, you don't particularly care how the message starts or stops because it's a constant flow of numbers. But if you want to send a more specific message, or more than one message, the speaker has to give the listener clues as to when the messages start and stop and how to tell the difference between them.
On Arduino's serial monitor, by default, it interprets bytes as ASCII-encoded decimals. So the following lines will print out the same thing:
Final project matchup
Motors - review family tree, pg 6 Finish h-bridge lab
Wireless communication and Bluetooth
Myers-Briggs Personality test link
<object width="512" height="400"><param name="movie" value="http://news.bbc.co.uk/player/emp/external/player.swf"></param><param name="allowFullScreen"