ITPedia - Recent changes [en]

Theory Club

2009-11-23T04:15:20Z

Meetings:

← Older revision		Revision as of 04:15, 23 November 2009
(2 intermediate revisions not shown)
Line 42:		Line 42:

	*'''Meeting 4: Starring Jacques Derrida as Columbo''' (11, 11, 2009) — Led by '''Sonaar Luthra'''<br>Derrida isn't all that different than my favorite detective, and I intend to prove it. Red wine will be served.		*'''Meeting 4: Starring Jacques Derrida as Columbo''' (11, 11, 2009) — Led by '''Sonaar Luthra'''<br>Derrida isn't all that different than my favorite detective, and I intend to prove it. Red wine will be served.
		+
		+	<br>
		+
		+	*'''Meeting 5: Ulysses's landescape''' (11.23.2009) — Led by '''Aiwen'''<br>Bring your mugs to the whiskey sea, all phuns intended in J's oddisee!
		+	**online text: [http://www.online-literature.com/james_joyce/ulysses/]
		+	**basic schemata which we'll be referring to: [http://www.robotwisdom.com/jaj/ulysses/schemata.html]

	<br>		<br>

Monome09

2009-11-20T23:37:48Z

← Older revision		Revision as of 23:37, 20 November 2009
Line 187:		Line 187:
	#Paul Rothman x 2		#Paul Rothman x 2
	#Karla Calderon		#Karla Calderon
-	#Sean Fitzgerald	+	#Sean Fitzgerald
		+	#Marko Manriquez

	1/8" thick 128 buttons		1/8" thick 128 buttons

User:Almoradie

2009-11-20T22:51:11Z

New user account

New page

Future of the Infrastructure Fall '09 with Art Kleiner/class 8 scenario names

2009-11-20T14:34:28Z

← Older revision	Revision as of 14:34, 20 November 2009
(One intermediate revision not shown)
Line 1:	Line 1:
	+	1. THERE GOES EVERYBODY - A couple of pandemics change the game
	+
	+	2. BARBARIANS AT THE GATES - The end of intellectual property law as we know it
	+
	+	3. LITTLE BROTHER IS MICROMANAGING YOU - Data goes superabundant
	+
	+	4. MIGRATION OF PRIVILEGE - China and India eclipse the West
	+
	+	5. LET THEM EAT BROADBAND - Haves and Have-nots in a world of discretionary information
	+
	+
	+

Monome09

2009-11-20T06:34:40Z

Using Windows:

← Older revision		Revision as of 06:34, 20 November 2009
(One intermediate revision not shown)
Line 234:		Line 234:
	# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it (Flash, not EEPROM).		# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it (Flash, not EEPROM).
	# You should see "Flash programming... OK" and you're done!		# You should see "Flash programming... OK" and you're done!
		+
		+	''If you have any troubles with step 6 you can try the following. In the taskbar open up the dialog for connected usb devices. Click on the preferences for the JTAG programmer. Check to see what Serial Port it has been assigned. If it is higher than COM7 or so (which is likely the case if you have a need for these additional instructions), go into the advanced preferences to find an open port with a lower value and assign the device to that port. Once you've done this revert back to step 5 above and keep your fingers crossed.''

	=== Using OSX ===		=== Using OSX ===

Monome09

2009-11-20T03:29:21Z

Talking to Monome:

← Older revision		Revision as of 03:29, 20 November 2009
(One intermediate revision not shown)
Line 251:		Line 251:

	# edit Makefile, 'pro' line with your actual programmer info. then make pro again with everything hooked up and you should be good.		# edit Makefile, 'pro' line with your actual programmer info. then make pro again with everything hooked up and you should be good.
		+
		+	= '''Talking to Monome''' =
		+
		+	# [http://docs.monome.org/doku.php?id=app:monomeserial monome serial] is necessary to start talking to your Monome. Keep it running no matter what application you are using your Momome with. It allows it to communicate via MIDI or OSC.
		+
		+	# [http://docs.monome.org/doku.php?id=app:monomebase Monome Base] has the basic test Max/MSP patches (you need a copy of Max)

	= '''Links''' =		= '''Links''' =

ITP Snow Bunnies: 2010

2009-11-20T00:52:31Z

Sign-Ups:

← Older revision		Revision as of 00:52, 20 November 2009
Line 58:		Line 58:
	#Meredith Hasson		#Meredith Hasson
	#Candice Holmes +1 (my extra person would be driving a zip car. No idea how many could fit)		#Candice Holmes +1 (my extra person would be driving a zip car. No idea how many could fit)
		+	#Nikolas Psaroudakis
	#...you??		#...you??

Monome09

2009-11-20T00:34:43Z

Wood Groups:

← Older revision		Revision as of 00:34, 20 November 2009
Line 186:		Line 186:
	#Alex Vessels		#Alex Vessels
	#Paul Rothman x 2		#Paul Rothman x 2
-	#Karla Calderon	+	#Karla Calderon
		+	#Sean Fitzgerald

	1/8" thick 128 buttons		1/8" thick 128 buttons

TNO

2009-11-19T20:46:05Z

← Older revision		Revision as of 20:46, 19 November 2009
Line 22:		Line 22:


-	<big>''The next TNO will be'' - '''~~October 22th~~, 2009''' -- ~~Haunted House After-Party~~!</big>	+	<big>''The next TNO will be'' - '''November 19th, 2009''' -- Karoake! </big>


Line 32:		Line 32:

	{{TNO		{{TNO
-	\|addedBy=~~Haunted House~~	+	\|addedBy=Emily Ryan
-	~~\|barName=spooky house!~~	+	\|barName=Planet Rose Karaoke
-	\|barName=	+	\|drinkSpecial=$3 Cranberry & vodka
-	\|drinkSpecial=~~spooky drinks!~~	+	\|date=2009/11/19
-	\|date=2009/10/29	+	\|address=219 Avenue A (btwn 13th & 14th ST)
-	\|address=	+
	}}		}}

Monome09

2009-11-19T17:24:33Z

Wood Groups:

← Older revision		Revision as of 17:24, 19 November 2009
Line 186:		Line 186:
	#Alex Vessels		#Alex Vessels
	#Paul Rothman x 2		#Paul Rothman x 2
		+	#Karla Calderon

	1/8" thick 128 buttons		1/8" thick 128 buttons

Version Control using Git & GitHub

2009-11-19T15:16:51Z

← Older revision		Revision as of 15:16, 19 November 2009
Line 61:		Line 61:

	'''File types for version control:'''		'''File types for version control:'''
-	* You can store any file type, text, images, video, etc, however large media will balloon the repository size very quickly.	+	* You can store any file type, text, images, video, etc, however frequently changing large media files (like PSD's) will balloon the repository size very quickly.
	* Typically you would use a '''.gitignore''' file to exclude certain folders and files, making them invisible to git. [http://www.gitready.com/beginner/2009/01/19/ignoring-files.html Tutorial Here]		* Typically you would use a '''.gitignore''' file to exclude certain folders and files, making them invisible to git. [http://www.gitready.com/beginner/2009/01/19/ignoring-files.html Tutorial Here]
	* If your project has a build / compile step, you do not want to include the entire build folder. ''Only include the recipes, not the product.''		* If your project has a build / compile step, you do not want to include the entire build folder. ''Only include the recipes, not the product.''

TNO schedule

2009-11-19T06:32:05Z

Nov 12th:

← Older revision		Revision as of 06:32, 19 November 2009
(2 intermediate revisions not shown)
Line 173:		Line 173:
	'''buy t-shirts for indonesian earthquake relief! and get krrrunk.'''		'''buy t-shirts for indonesian earthquake relief! and get krrrunk.'''

-	====''~~Nov 19th~~''====	+
		+	====''November 19 -- Karaoke TNO!!!''====
		+
	{{TNO		{{TNO
	\|addedBy=Emily Ryan		\|addedBy=Emily Ryan
-	\|barName=~~Magical Surprise~~	+	\|barName=Planet Rose
-	\|invitepage=	+	\|invitepage=http://blip.tv/file/2868259
-	\|drinkSpecial=	+	\|drinkSpecial=$3 Vodka + Cranberry All Night!
-	\|date=2009/10/22	+	\|date=2009/19/11
-	\|address=~~TBD~~	+	\|address=42 E 1st Street, New York NY 10003
-	\|coordinates=~~TBD~~	+	\|coordinates=http://tiny.cc/JM1J1
	}}		}}

Monome09

2009-11-19T06:07:21Z

Wood Groups:

← Older revision		Revision as of 06:07, 19 November 2009
Line 184:		Line 184:
	#Patricia Adler x 1		#Patricia Adler x 1
	#Nate Roth		#Nate Roth
-	Alex Vessels	+	#Alex Vessels
		+	#Paul Rothman x 2

	1/8" thick 128 buttons		1/8" thick 128 buttons

-	#	+	#Paul Rothman x 2

	1/4" thick 64 buttons		1/4" thick 64 buttons

Monome09

2009-11-19T00:28:04Z

Installing Firmware:

← Older revision		Revision as of 00:28, 19 November 2009
Line 219:		Line 219:
	== Installing Firmware ==		== Installing Firmware ==

-	~~Source files (including~~ firmware~~) can be found~~ [http://docs.monome.org/doku.php?id=tech:source_files:40h here]	+	Both methods use the monome firmware downloadable from [http://docs.monome.org/doku.php?id=tech:source_files:40h here]. Grab it!

		+	=== Using Windows ===
	Firmware needs to be booted from AVR STUDIO on a PC.		Firmware needs to be booted from AVR STUDIO on a PC.

Line 228:		Line 229:
	# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.		# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.
	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.		# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.
-	# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it.	+	# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it (Flash, not EEPROM).
		+	# You should see "Flash programming... OK" and you're done!

		+	=== Using OSX ===

		+	[http://post.monome.org/comments.php?DiscussionID=3227 Some background info]

-		+	# Download [http://www.obdev.at/products/crosspack/index.html CrossPack]
-	~~Some words from Brian Crabtree:~~	+	# You'll be using avarice to upload. unpack the firmware file. use terminal and get into that folder. then type
-		+
-	http://www.obdev.at/products/crosspack/index.html	+
-		+
-	~~which programmer did you get?~~	+
-		+
-	~~here's a semi-relevant discussion: http://post.monome.org/comments.php?DiscussionID=3227~~	+
-		+
-	~~download the firmware:~~	+
-		+
-	~~http://docs.monome.org/lib/exe/fetch.php?id=tech%3Asource_files%3A40h&cache=cache&media=tech:source_files:monome40h_firmware.tar.gz~~	+
-		+
-	~~you~~'ll be using avarice to upload. unpack the firmware file. use terminal and get into that folder. then type	+

	make pro		make pro

-	it'll probably give you an error that some file doesn't exist. that's the programmer id. type	+	# it'll probably give you an error that some file doesn't exist. that's the programmer id. type

	ls -lrt /dev		ls -lrt /dev
Line 255:		Line 247:
	and look for something at the bottom similar to the 'missing' filename: /dev/tty.usbserial-0000101D		and look for something at the bottom similar to the 'missing' filename: /dev/tty.usbserial-0000101D

-	edit Makefile, 'pro' line with your actual programmer info. then make pro again with everything hooked up and you should be good.	+	# edit Makefile, 'pro' line with your actual programmer info. then make pro again with everything hooked up and you should be good.

	= '''Links''' =		= '''Links''' =

Monome09

2009-11-19T00:02:35Z

Installing Firmware:

← Older revision		Revision as of 00:02, 19 November 2009
Line 224:		Line 224:

	# Get the JTAG Programmer from the ER and plug it into one of the PCs (right now the one on the right has AVR Studio).		# Get the JTAG Programmer from the ER and plug it into one of the PCs (right now the one on the right has AVR Studio).
-	# Plug in both the JTAG programmer and the FTDI USB cable~~; the red light on the programmer should go on~~.	+	# Plug in both the JTAG programmer and the FTDI USB cable.
-	# Plug the JTAG header onto your board with the ribbon facing away from the Atmega.	+	# Plug the JTAG header onto your board with the ribbon facing away from the Atmega; the red light on the programmer should go on.
	# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.		# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.
	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.		# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.

Monome09

2009-11-18T21:36:08Z

Further Instructions:

← Older revision		Revision as of 21:36, 18 November 2009
(2 intermediate revisions not shown)
Line 202:		Line 202:
	Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]		Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]

-	All you need M-Prog for is changing the serial number on your FTDI chip. The serial server which will sit between your hardware and software looks for this serial number like so:	+	All you need M-Prog for is changing the serial number on your FTDI chip. The serial server which will sit between your hardware and software looks for this serial number like so:

-	* MonomeSerial: m40*	+	MonomeSerial: m40h0001
-	* ArduinomeSerial: a40*	+

-	~~It's~~ up ~~to you but I~~'~~d just~~ do ~~an m40 serial number~~ and ~~use MonomeSerial~~. ~~Weird that there~~'~~d be~~ a ~~distinction in~~ the ~~first place~~.	+
		+	# Open up Mprog, it's on the Desktop.
		+	# Under the Device menu, click on Scan. Let it do it's thing.
		+	# Under Tools, click Read and Parse.
		+	# Press the open file button and open "monome1.ept" from the desktop. Hit the Lightning button.
		+	# That's it.
		+
		+	Now move on to program your Atmeg chip.
		+
		+	For people with a 128, follow the steps above for one of your chips, then connect the second one, and open the "monome2.ept", and lightning that to your chip. The idea is that one monome will be m40h0001 and one m40h0002.

	== Installing Firmware ==		== Installing Firmware ==
Line 221:		Line 229:
	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.		# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.
	# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it.		# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it.
		+
		+
		+

	Some words from Brian Crabtree:		Some words from Brian Crabtree:

Monome09

2009-11-18T19:03:22Z

← Older revision		Revision as of 19:03, 18 November 2009
Line 202:		Line 202:
	Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]		Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]

-	~~Source files (including firmware) can be found [http://docs~~.~~monome.org/doku.php?id=tech:source_files~~:~~40h here]~~	+	All you need M-Prog for is changing the serial number on your FTDI chip. The serial server which will sit between your hardware and software looks for this serial number like so:

-	~~Firmware needs~~ to be ~~booted from AVR STUDIO on~~ a PC.	+	* MonomeSerial: m40*
		+	* ArduinomeSerial: a40*
		+
		+	It's up to you but I'd just do an m40 serial number and use MonomeSerial. Weird that there'd be a distinction in the first place.

	== Installing Firmware ==		== Installing Firmware ==
		+
		+	Source files (including firmware) can be found [http://docs.monome.org/doku.php?id=tech:source_files:40h here]
		+
		+	Firmware needs to be booted from AVR STUDIO on a PC.

	# Get the JTAG Programmer from the ER and plug it into one of the PCs (right now the one on the right has AVR Studio).		# Get the JTAG Programmer from the ER and plug it into one of the PCs (right now the one on the right has AVR Studio).
Line 213:		Line 220:
	# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.		# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.
	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.		# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.
-	# Hit Connect. A new screen should appear	+	# Hit Connect. A new screen should appear with a field to choose a hex file. Select the 40h file from the firmware source and upload it.
-		+

	Some words from Brian Crabtree:		Some words from Brian Crabtree:

ITP Snow Bunnies: 2010

2009-11-18T18:42:41Z

Vote:

← Older revision		Revision as of 18:42, 18 November 2009
Line 43:		Line 43:
	# Candice Holmes +1		# Candice Holmes +1
	# Gloria		# Gloria
		+	# Tim Haynes

	<br>		<br>

Monome09

2009-11-18T15:01:39Z

Installing Firmware:

← Older revision		Revision as of 15:01, 18 November 2009
Line 214:		Line 214:
	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.		# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.
	# Hit Connect. A new screen should appear		# Hit Connect. A new screen should appear
		+
		+
		+	Some words from Brian Crabtree:
		+
		+	http://www.obdev.at/products/crosspack/index.html
		+
		+	which programmer did you get?
		+
		+	here's a semi-relevant discussion: http://post.monome.org/comments.php?DiscussionID=3227
		+
		+	download the firmware:
		+
		+	http://docs.monome.org/lib/exe/fetch.php?id=tech%3Asource_files%3A40h&cache=cache&media=tech:source_files:monome40h_firmware.tar.gz
		+
		+	you'll be using avarice to upload. unpack the firmware file. use terminal and get into that folder. then type
		+
		+	make pro
		+
		+	it'll probably give you an error that some file doesn't exist. that's the programmer id. type
		+
		+	ls -lrt /dev
		+
		+	and look for something at the bottom similar to the 'missing' filename: /dev/tty.usbserial-0000101D
		+
		+	edit Makefile, 'pro' line with your actual programmer info. then make pro again with everything hooked up and you should be good.

	= '''Links''' =		= '''Links''' =

Main Page

2009-11-18T03:48:25Z

← Older revision		Revision as of 03:48, 18 November 2009
Line 24:		Line 24:

	====Current Event: [[Month of FlyBys]]====		====Current Event: [[Month of FlyBys]]====
-	'''Today's FlyBy:''' ~~Martin Ceperley~~, [[~~Version_Control_using_Git_%26_GitHub~~ \| ~~Version Control using Git & GitHub~~]]	+	'''Today's FlyBy:''' Zach Taylor, [[Bitwise_Math \| Bitwise Math Made Exceptionally Easy]]

	<br />		<br />

Month of FlyBys

2009-11-18T03:48:05Z

← Older revision		Revision as of 03:48, 18 November 2009
Line 25:		Line 25:
	#enter your name and topic		#enter your name and topic
	#Martin Ceperley, [[Version Control using Git & GitHub]]		#Martin Ceperley, [[Version Control using Git & GitHub]]
-	#Zach Taylor, Bitwise Math Made Exceptionally Easy	+	#Zach Taylor, [[Bitwise_Math \| Bitwise Math Made Exceptionally Easy]]
	#enter your name and topic		#enter your name and topic
	#enter your name and topic		#enter your name and topic

Bitwise Math

2009-11-18T00:41:32Z

← Older revision		Revision as of 00:41, 18 November 2009
Line 8:		Line 8:
	== What are bitwise operation (and why should I care?) ==		== What are bitwise operation (and why should I care?) ==

-	Bitwise operations are operations that act on numbers at the bit level. Although bitwise operations have many	+	Bitwise operations are operations that act on numbers at the bit level. Although bitwise operations have many potential uses for storing one bit and manipulating numbers, the most frequent use at ITP is probably to interface with a shift register and control many more LEDs than you would be able to if using one digital pin for each LED.
-		+
-	potential uses for storing one bit and manipulating numbers, the most frequent use at ITP is probably to interface	+
-		+
-	with a shift register and control many more LEDs than you would be able to if using one digital pin for each LED.	+

	== Binary ==		== Binary ==

-	Before working with bitwise operators, it's important to understand binary numbers. A binary number is just a	+	Before working with bitwise operators, it's important to understand binary numbers. A binary number is just a number in which each digit represents a power of 2 (as opposed to decimal where each digit represents a power of 10). Sometimes binary numbers will be indicated in code with a zero and a lower-case 'b' before the number, e.g. 0b1001 or 0b001011, but the standard implementation in Arduino is to use a capital 'B' before the number, e.g. B1001 or B001011. This format works up to B11111111, which is 255 in decimal.
-		+
-	number in which each digit represents a power of 2 (as opposed to decimal where each digit represents a power	+
-		+
-	of 10). Sometimes binary numbers will be indicated in code with a zero and a lower-case 'b' before the number,	+
-		+
-	e.g. 0b1001 or 0b001011, but the standard implementation in Arduino is to use a capital 'B' before the number,	+
-		+
-	e.g. B1001 or B001011. This format works up to B11111111, which is 255 in decimal.	+

	More information can be found at [Wikipedia\|http://en.wikipedia.org/wiki/Binary_numeral_system].		More information can be found at [Wikipedia\|http://en.wikipedia.org/wiki/Binary_numeral_system].
Line 33:		Line 21:

	=== AND ===		=== AND ===
-	The AND function takes two inputs and returns one. The output is a high value only when both inputs are high. An implementation of this in Arduino could take two digital inputs, then set a third pin to 5 volts only when both input pins read 5 volts. This function is usually written as an ampersand, e.g. A&B.	+	The AND function takes two inputs and returns one. The output is a high value only when both inputs are high. An implementation of this in Arduino could take two digital inputs, then set a third pin to 5 volts only when both input pins read 5 volts. This function is usually written as an ampersand, e.g. A & B.
	{\| border="1" cellpadding="5" cellspacing="0"		{\| border="1" cellpadding="5" cellspacing="0"
	\|-		\|-
Line 50:		Line 38:

	=== OR ===		=== OR ===
-	The OR function returns a high value when either or both inputs are high. This function is usually written as a pipe, e.g. A\|B.	+	The OR function returns a high value when either or both inputs are high. This function is usually written as a pipe, e.g. A \| B.
	{\| border="1" cellpadding="5" cellspacing="0"		{\| border="1" cellpadding="5" cellspacing="0"
	\|-		\|-
Line 80:		Line 68:

	== Examples on a Byte ==		== Examples on a Byte ==
		+	Applying the AND, OR, or NOT function to a binary number performs the operation bit by bit. For example, using the AND on two 8-bit numbers means using the operation eight times, once for each bit.
		+
		+	~B101001:
		+	NOT B101001
		+	= B010110
		+
		+	B10011001 & B10101011:
		+	B10011001
		+	AND B10101011
		+	= B10001001
		+
		+	B10011001 \| B10101011:
		+	B10011001
		+	OR B10101011
		+	= B10111011
		+
		+	~(B01001011 \| B11011001):
		+	NOT ( B01001011
		+	OR B11011001 )
		+	= NOT B11011011
		+	= B00100100

	== Bit-shifting ==		== Bit-shifting ==
		+	Bit-shifting simply means taking the bits in a binary number and moving them all to the left or right. Moving them to the left is indicated by "<<" followed by the number of places to shift. Moving to the right is indicated by ">>" followed by the number of places to shift.
		+
		+	B00011000 << 2 means to shift the bits twice to the left:
		+	= B01100000
		+
		+	B01000000 >> 5 means to shift the bits five times to the left:
		+	= B00000010
		+
		+	Left-shifting a bit past the highest place sends that bit into oblivion. Right-shifting has some weird features due to the left-most bit being a sign bit in a signed data type. If you need to right-shift a large or negative number, you'll want to read up on how that's implemented, but don't worry about it for the current examples.

	== An example: x &= ~(1 << 2 \| 1 << 4) ==		== An example: x &= ~(1 << 2 \| 1 << 4) ==

		+	ANDing with NOT can be very useful for turning particular bits to 0. Take this example, which hopefully now looks like more than just a random string of characters:
		+	x &= ~(1 << 2 \| 1 << 4)
		+	The purpose of this code is to turn off the second and fourth bits from the right in variable x. Let's look at how that works. For this example, let's assume that our numbers are 8-bit numbers and that x = B11100110
		+	x = B11100110
		+	x & ~((1 << 2) \| (1 << 4)) = ?
		+
		+	(1 << 2) = B00000100
		+	(1 << 4) = B00010000
		+	(1 << 2) \| (1 << 4) = B00010100
		+	~((1 << 2) \| (1 << 4)) = B11101011
		+
		+	x = B11100110
		+	AND ~((1 << 2) \| (1 << 4)) = B11101011
		+	= B11100010
		+	In this example, the final result is the same as x, only the second and fourth digits from the right are now zero (although one of them already was).
		+
		+	To make sure that a digit is high is easier. You just need to \|= with a number:
		+	x = B11100110
		+	(1 << 2) \| (1 << 4) = B00010100
		+	x \| ((1 << 2) \| (1 << 4)) = B11110110
		+
	== An LED Example ==		== An LED Example ==
		+	The Arduino [http://www.arduino.cc/en/Tutorial/ShiftOut ShiftOut] function is a useful one when dealing with shift registers. When using it, you may want to change just one LED at a time. In this case, bitshifting might be useful.
		+	The following example assumes a simple shift register with no latch, but only minor changes to code would be needed if you shift register has a latch:
		+
		+	int leds = B11110000;
		+	// first four LEDs high, last four low
		+
		+	shiftOut(dataPin, clockPin, leds);
		+	// the clock and data pins need to be set as well
		+	// for this example, I'll assume that they were set in setup
		+
		+	delay(1000);
		+
		+	leds \|= (1) \| (1 << 3) \| (1 << 1);
		+	// x = B11111011 (three more leds turn high)
		+	shiftOut(dataPin, clockPin, leds);
		+
		+	delay(1000);
		+
		+	leds &= ~((1 << 2) \| (1 << 3) \| (1 << 6));
		+	// x = 10110011 (two leds turned off, would have been three
		+	but one of the ones set low in the function was already low)
		+	shiftOut(dataPin, clockPin, leds);

Monome09

2009-11-17T23:31:29Z

Further Instructions:

← Older revision		Revision as of 23:31, 17 November 2009
Line 206:		Line 206:
	Firmware needs to be booted from AVR STUDIO on a PC.		Firmware needs to be booted from AVR STUDIO on a PC.

		+	== Installing Firmware ==

		+	# Get the JTAG Programmer from the ER and plug it into one of the PCs (right now the one on the right has AVR Studio).
		+	# Plug in both the JTAG programmer and the FTDI USB cable; the red light on the programmer should go on.
		+	# Plug the JTAG header onto your board with the ribbon facing away from the Atmega.
		+	# Run AVR Studio and choose the Monome file that is listed. If there's no Monome file make a new blank project.
		+	# Find the "Connect" button and choose "JTAG ICE" and "Auto" for port.
		+	# Hit Connect. A new screen should appear

	= '''Links''' =		= '''Links''' =

Bitwise Math

2009-11-17T22:57:31Z

← Older revision		Revision as of 22:57, 17 November 2009
Line 6:		Line 6:
	}}		}}

-	=== What are bitwise operation (and why should I care?) ===	+	== What are bitwise operation (and why should I care?) ==

-	Bitwise operations are operations that act on numbers at the bit level. Although bitwise operations have many potential uses for storing one bit and manipulating numbers, the most frequent use at ITP is probably to interface with a shift register and control many more LEDs than you would be able to if using one digital pin for each LED.	+	Bitwise operations are operations that act on numbers at the bit level. Although bitwise operations have many

-	~~=== Binary ===~~	+	potential uses for storing one bit and manipulating numbers, the most frequent use at ITP is probably to interface

-	Before working with bitwise operators, it's important to understand binary numbers. A binary number is just a number in which each digit represents a power of 2 (as opposed to decimal where each digit represents a power of 10). Sometimes binary numbers will be indicated in code with a zero and a lower-case 'b' before the number (e.g. 0b1001 or 0b001011), but the standard implementation in Arduino is to use a capital 'B' before the number (e.g. B1001 or B001011). This ~~will work for any 8-bit number, so~~ up to B11111111, which is 255 in decimal.	+	with a shift register and control many more LEDs than you would be able to if using one digital pin for each LED.
		+
		+	== Binary ==
		+
		+	Before working with bitwise operators, it's important to understand binary numbers. A binary number is just a
		+
		+	number in which each digit represents a power of 2 (as opposed to decimal where each digit represents a power
		+
		+	of 10). Sometimes binary numbers will be indicated in code with a zero and a lower-case 'b' before the number,
		+
		+	e.g. 0b1001 or 0b001011, but the standard implementation in Arduino is to use a capital 'B' before the number,
		+
		+	e.g. B1001 or B001011. This format works up to B11111111, which is 255 in decimal.

	More information can be found at [Wikipedia\|http://en.wikipedia.org/wiki/Binary_numeral_system].		More information can be found at [Wikipedia\|http://en.wikipedia.org/wiki/Binary_numeral_system].

-	=== AND, OR, NOT ===	+	== AND, OR, NOT ==

-	The next key concept is that of the most basic logic gates, AND, OR, and NOT.	+	The next key concept is that of the most basic logic gates, AND, OR, and NOT. There are other gates, but these are the most essential and the only ones that are necessary for bitwise operations. Both AND and OR take two inputs, while NOT takes only one.

-	== AND ==	+	=== AND ===
		+	The AND function takes two inputs and returns one. The output is a high value only when both inputs are high. An implementation of this in Arduino could take two digital inputs, then set a third pin to 5 volts only when both input pins read 5 volts. This function is usually written as an ampersand, e.g. A&B.
		+	{\| border="1" cellpadding="5" cellspacing="0"
		+	\|-
		+	\| colspan="3" align="center"\| A & B
		+	\|-
		+	\| Input A \|\| Input B \|\| Output
		+	\|-
		+	\| 0\|\|0\|\|0
		+	\|-
		+	\| 0\|\|1\|\|0
		+	\|-
		+	\| 1\|\|0\|\|0
		+	\|-
		+	\| 1\|\|1\|\|1
		+	\|}

-	== OR ==	+	=== OR ===
		+	The OR function returns a high value when either or both inputs are high. This function is usually written as a pipe, e.g. A\|B.
		+	{\| border="1" cellpadding="5" cellspacing="0"
		+	\|-
		+	\| colspan="3" align="center"\| A \| B
		+	\|-
		+	\| Input A \|\| Input B \|\| Output
		+	\|-
		+	\| 0\|\|0\|\|0
		+	\|-
		+	\| 0\|\|1\|\|1
		+	\|-
		+	\| 1\|\|0\|\|1
		+	\|-
		+	\| 1\|\|1\|\|1
		+	\|}

-	== NOT ==	+	=== NOT ===
		+	The not function only had one input. The output is the opposite of that input. This function is usually written as a tilde, e.g. ~A.
		+	{\| border="1" cellpadding="5" cellspacing="0"
		+	\|-
		+	\| colspan="3" align="center"\| ~A
		+	\|-
		+	\| Input A \|\| Output
		+	\|-
		+	\| 0\|\|1
		+	\|-
		+	\| 1\|\|0
		+	\|}

-	=== Examples on a Byte ===	+	== Examples on a Byte ==

-	=== Bit-shifting ===	+	== Bit-shifting ==

-	=== An example: x &= ~(1 << 2 \| 1 << 4) ===	+	== An example: x &= ~(1 << 2 \| 1 << 4) ==

-	=== An LED Example ===	+	== An LED Example ==

Monome09

2009-11-17T22:47:47Z

Acrylic Groups:

← Older revision		Revision as of 22:47, 17 November 2009
Line 138:		Line 138:
	<br> ''1/8" thick 128 buttons''		<br> ''1/8" thick 128 buttons''

-	~~#Xiaoyang Feng, glossy white x 1~~

	<br>		<br>
Line 150:		Line 149:


-	<br>	+	<br>
-		+

	== <br> '''Masonite Groups''' ==		== <br> '''Masonite Groups''' ==

Bitwise Math

2009-11-17T22:27:41Z

New page

{{FlyBy
|addedBy=Zach Taylor
|description=How to Use Bitwise Math
|areaOfFocus=Computation
|keywords=bitwise, math
}}

=== What are bitwise operation (and why should I care?) ===

Bitwise operations are operations that act on numbers at the bit level. Although bitwise operations have many potential uses for storing one bit and manipulating numbers, the most frequent use at ITP is probably to interface with a shift register and control many more LEDs than you would be able to if using one digital pin for each LED.

=== Binary ===

Before working with bitwise operators, it's important to understand binary numbers. A binary number is just a number in which each digit represents a power of 2 (as opposed to decimal where each digit represents a power of 10). Sometimes binary numbers will be indicated in code with a zero and a lower-case 'b' before the number (e.g. 0b1001 or 0b001011), but the standard implementation in Arduino is to use a capital 'B' before the number (e.g. B1001 or B001011). This will work for any 8-bit number, so up to B11111111, which is 255 in decimal.

More information can be found at [Wikipedia|http://en.wikipedia.org/wiki/Binary_numeral_system].

=== AND, OR, NOT ===

The next key concept is that of the most basic logic gates, AND, OR, and NOT.

== AND ==

== OR ==

== NOT ==

=== Examples on a Byte ===

=== Bit-shifting ===

=== An example: x &= ~(1 << 2 | 1 << 4) ===

=== An LED Example ===

ITP Snow Bunnies: 2010

2009-11-17T21:08:52Z

Vote:

← Older revision		Revision as of 21:08, 17 November 2009
Line 27:		Line 27:
	#Sebastian Buys		#Sebastian Buys
	#Candice Holmes +1		#Candice Holmes +1
		+	#Marco Antonio Castro

	'''President's Day weekend'''		'''President's Day weekend'''

ITP Snow Bunnies: 2010

2009-11-17T21:08:15Z

← Older revision		Revision as of 21:08, 17 November 2009
Line 40:		Line 40:
	# Dimitris Makris		# Dimitris Makris
	# Ari L. Joseph		# Ari L. Joseph
-	#Candice Holmes +1	+	# Candice Holmes +1
		+	# Gloria

	<br>		<br>

Monome09

2009-11-17T21:03:40Z

← Older revision		Revision as of 21:03, 17 November 2009
Line 203:		Line 203:

	Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]		Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]
		+
		+	Source files (including firmware) can be found [http://docs.monome.org/doku.php?id=tech:source_files:40h here]
		+
		+	Firmware needs to be booted from AVR STUDIO on a PC.
		+
		+

	= '''Links''' =		= '''Links''' =

Fall 2009 DriveBy Signup

2009-11-17T20:26:59Z

← Older revision		Revision as of 20:26, 17 November 2009
Line 142:		Line 142:
	----		----

-	Date: Last Driveby of Semester, whatever date that is (~~either the 3rd or~~ 17th i think)	+	Date: Last Driveby of Semester, whatever date that is (December 17th i think)

	Host: Jelani John		Host: Jelani John

Canary

2009-11-17T18:45:20Z

← Older revision		Revision as of 18:45, 17 November 2009
Line 19:		Line 19:
	[[Image:Water_cycle.gif\|frame\|right\|An initial diagram of Water Device information flow]]		[[Image:Water_cycle.gif\|frame\|right\|An initial diagram of Water Device information flow]]

-	~~[[Image:UNICEF_Schematic.gif\|thumb\|250px\|right\|Schematic]]~~

-		+	===Travel Blogs===
-	===~~Current~~ Travel Blogs===	+
	[http://watercanary.wordpress.com Ethiopia Blog] - Zoe and Sonaar were researching background in Addis, Ethiopia this summer.		[http://watercanary.wordpress.com Ethiopia Blog] - Zoe and Sonaar were researching background in Addis, Ethiopia this summer.

Line 52:		Line 50:

	===Technical Specifications===		===Technical Specifications===
-
-	~~[http://itp.nyu.edu/~zf213/UNICEF/matterials/Diagrams.zip Device diagrams] - Explanatory diagrams of internal workings of the Canary~~
-
-	~~[http://groups-beta.google.com/group/water-for-unicef/web/UNICEF_Schematic.pdf Device Schematic] - Water tester device technical specifications and wiring~~

	[http://water-for-unicef.googlegroups.com/web/Xenon+flash.pdf Xenon Flash Information] - To replace the expensive UV LED requirement.		[http://water-for-unicef.googlegroups.com/web/Xenon+flash.pdf Xenon Flash Information] - To replace the expensive UV LED requirement.

Version Control using Git & GitHub

2009-11-17T18:13:32Z

← Older revision		Revision as of 18:13, 17 November 2009
(2 intermediate revisions not shown)
Line 59:		Line 59:

	<br>		<br>
		+
		+	'''File types for version control:'''
		+	* You can store any file type, text, images, video, etc, however large media will balloon the repository size very quickly.
		+	* Typically you would use a '''.gitignore''' file to exclude certain folders and files, making them invisible to git. [http://www.gitready.com/beginner/2009/01/19/ignoring-files.html Tutorial Here]
		+	* If your project has a build / compile step, you do not want to include the entire build folder. ''Only include the recipes, not the product.''

	<br>		<br>

Workshop on iPhone Development

2009-11-17T18:00:48Z

Additional Resources:

← Older revision		Revision as of 18:00, 17 November 2009
Line 39:		Line 39:
	====Additional Resources====		====Additional Resources====
	* [http://drop.io/ojbv7ce/asset/iphoneresources-zip Graphics and Interface Demo][ Interface and UI Design Resources]		* [http://drop.io/ojbv7ce/asset/iphoneresources-zip Graphics and Interface Demo][ Interface and UI Design Resources]
		+	* '''''new''''' ITP-iPhone Development Discussion List - anyone can join, just send a blank email to join-itp-iphone@lists.nyu.edu

	====Tentative Schedule====		====Tentative Schedule====

Month of FlyBys

2009-11-17T13:02:18Z

Schedule:

← Older revision		Revision as of 13:02, 17 November 2009
Line 21:		Line 21:
	#Corey Menscher, [[Preparing for the show \| Preparing for the ITP Show]]		#Corey Menscher, [[Preparing for the show \| Preparing for the ITP Show]]
	#Adam Harvey, Arduino + Processing + Flash: Building Flash Displays with Serial Input, OSC and XML Socket		#Adam Harvey, Arduino + Processing + Flash: Building Flash Displays with Serial Input, OSC and XML Socket
-	#~~enter your name and topic~~	+	#Corey Menscher, [[Accessing the student list \| Accessing the Student List]]
	#enter your name and topic		#enter your name and topic
	#enter your name and topic		#enter your name and topic

Month of FlyBys

2009-11-17T07:08:01Z

← Older revision		Revision as of 07:08, 17 November 2009
Line 24:		Line 24:
	#enter your name and topic		#enter your name and topic
	#enter your name and topic		#enter your name and topic
-	#Martin Ceperley, [~~http://itpedia.nyu.edu/wiki/Version_Control_using_Git_%26_GitHub~~ Version Control ~~with~~ Git & GitHub]	+	#Martin Ceperley, [[Version Control using Git & GitHub]]
	#Zach Taylor, Bitwise Math Made Exceptionally Easy		#Zach Taylor, Bitwise Math Made Exceptionally Easy
	#enter your name and topic		#enter your name and topic

Monome09

2009-11-17T05:53:07Z

← Older revision		Revision as of 05:53, 17 November 2009
Line 134:		Line 134:

	#Michael Zick Doherty, white translucent x 1		#Michael Zick Doherty, white translucent x 1
		+	#Andy Doro, white translucent x 1

	<br> ''1/8" thick 128 buttons''		<br> ''1/8" thick 128 buttons''
Line 142:		Line 143:

	''1/4" thick 64 buttons''		''1/4" thick 64 buttons''
-
-	~~#Andy Doro, white translucent x 1~~

Monome09

2009-11-17T00:58:54Z

Further Instructions:

← Older revision		Revision as of 00:58, 17 November 2009
Line 203:		Line 203:
	= Further Instructions =		= Further Instructions =

-	Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t".	+	Done assembling your hardware? [http://flipmu.com/work/arduinome/instructions/ Here's what to do next (starting with part 2)]. You have to install FTDI's M-Prog program which requires the D2XX drivers. For your convenience, T3db0t installed both on the middle Windows computer in the Post Lab, login to the XBee account with password "T3db0t". [FYI: that "0" is a zero.]

	= '''Links''' =		= '''Links''' =