Byzantium Sprint 2 - Revision history

ITechGeek at 09:20, 3 April 2012

2012-04-03T09:20:56Z

← Older revision		Revision as of 09:20, 3 April 2012
Line 1:		Line 1:

	Summary: Build at least one long-haul link to bridge two meshes.		Summary: Build at least one long-haul link to bridge two meshes.

Line 101:		Line 100:

	Let's see how much of [http://fabfi.fablab.af/ Project FabFi] we can make use of!		Let's see how much of [http://fabfi.fablab.af/ Project FabFi] we can make use of!

			{{Template:Byzantium}}

Drwho: /* Lessons Learned */

2011-06-22T16:30:20Z

Lessons Learned

← Older revision		Revision as of 16:30, 22 June 2011
Line 99:		Line 99:
	**everything		**everything
	**[http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 There are no experimental failures. There is only more data.]		**[http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 There are no experimental failures. There is only more data.]

			Let's see how much of [http://fabfi.fablab.af/ Project FabFi] we can make use of!

Drwho: /* Lessons Learned */

2011-04-15T03:08:48Z

Lessons Learned

← Older revision		Revision as of 03:08, 15 April 2011
Line 95:		Line 95:
	*"how hard can it be" ... oops :(		*"how hard can it be" ... oops :(
	**very. soundmodem is finicky and creates unstable connections 20% packet loss at best 80-90% avg.		**very. soundmodem is finicky and creates unstable connections 20% packet loss at best 80-90% avg.
			**Don't forget network latency of 35,500ms over a distance of eight feet.
	*"What could possibly go wrong?" ... oops :(		*"What could possibly go wrong?" ... oops :(
	**everything		**everything
			**[http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 There are no experimental failures. There is only more data.]

Haxwithaxe: /* Goals (proposed) */

2011-04-10T05:37:47Z

Goals (proposed)

← Older revision		Revision as of 05:37, 10 April 2011
Line 68:		Line 68:
	===Goals (proposed)===		===Goals (proposed)===
	*Optimize for hackability. Could your average geek build a few of these using junk around zir house and deploy them in an emergency situation?		*Optimize for hackability. Could your average geek build a few of these using junk around zir house and deploy them in an emergency situation?
			**not a chance
	*Determine the optimum speed in bits per second for a mesh-to-mesh link.		*Determine the optimum speed in bits per second for a mesh-to-mesh link.
			**very crazy slow (we didn't bother measuring it was so slow)
	*Measure the bandwidth of a point-to-point long haul connection at a particular distance.		*Measure the bandwidth of a point-to-point long haul connection at a particular distance.
			**again to slow to bother
	*Determine the maximum practical distance for a long haul connection between two meshes in an urban environment.		*Determine the maximum practical distance for a long haul connection between two meshes in an urban environment.
			**didn't get that far
	*Mathematically describe the way to maximize throughput with a minimum number of nodes.		*Mathematically describe the way to maximize throughput with a minimum number of nodes.
			**didn't get that far
	*Run an ssh session over whatever link is established.		*Run an ssh session over whatever link is established.
			**done
	*Interact with a web page over whatever link is established.		*Interact with a web page over whatever link is established.
			**connection was too unstable to get this far
	*Develop methods to minimize latency.		*Develop methods to minimize latency.
			**tweak the source and transmitter volume A LOT until the it's perfect
	*Determine the efficiency of the mesh routing protocol we settle on.		*Determine the efficiency of the mesh routing protocol we settle on.
			**didn't get this far
	**How many active nodes per mesh can be reasonably supported before connectivity breaks down?		**How many active nodes per mesh can be reasonably supported before connectivity breaks down?
			***to be determined

	===Apps running on Windbringer (laptop/node) to prove functionality===		===Apps running on Windbringer (laptop/node) to prove functionality===

Haxwithaxe: /* Lessons Learned */

2011-04-10T05:31:21Z

Lessons Learned

← Older revision		Revision as of 05:31, 10 April 2011
Line 84:		Line 84:
	===Lessons Learned===		===Lessons Learned===
	*"how hard can it be" ... oops :(		*"how hard can it be" ... oops :(
	*What could possibly go wrong?		**very. soundmodem is finicky and creates unstable connections 20% packet loss at best 80-90% avg.
			*"What could possibly go wrong?" ... oops :(
			**everything

Drwho: /* Lessons Learned */

2011-04-03T03:17:18Z

Lessons Learned

← Older revision		Revision as of 03:17, 3 April 2011
Line 84:		Line 84:
	===Lessons Learned===		===Lessons Learned===
	*"how hard can it be" ... oops :(		*"how hard can it be" ... oops :(
			*What could possibly go wrong?

Haxwithaxe: Created page with " Summary: Build at least one long-haul link to bridge two meshes. Planning meeting: Thu Mar 3 2011 after the bike maintenance class (done) Planning meeting #2: Wed Mar 16 2011 a..."

2011-03-28T16:30:53Z

Created page with " Summary: Build at least one long-haul link to bridge two meshes. Planning meeting: Thu Mar 3 2011 after the bike maintenance class (done) Planning meeting #2: Wed Mar 16 2011 a..."

New page

Summary: Build at least one long-haul link to bridge two meshes.

Planning meeting: Thu Mar 3 2011 after the bike maintenance class (done)
Planning meeting #2: Wed Mar 16 2011 after the elements of computing class (doneish)

'''Sprint Date: Fri-Sun March 25-27'''
[[Byzantium Sprint 2 Inventory|Inventory]]

===Schedule===
FRI: 8:00pm Pizza, sprint 1 recap, and prep (mostly ripping thing apart and some assembly)
SAT:
*Noon Brunch and final assembly followed by bench tests and midrange tests depending on speed of success
*Dinner Time: Dinner outside the space. This must occur outside the space.
*9:00pmish? Discussion and general planning for Sunday optionally followed by more testing/making
SUN:
*Noon Brunch prep for long distance tests followed by long distance tests
*Dinner Time: Dinner outside the space. This must occur outside the space.
*9:00pmish? Discussion and planning for the next sprint

===Stuff to bring (proposed)===
*FMRS/GMRS radios that you wouldn't mind hacking.
*Childrens' walkie-talkies. [[User:Drwho]] knows where to buy cheap pairs of them locally.
*Webcams ''that are known to work with Linux''. That's closer to black magick than computer science, so do your homework first (or on your smartphone while at the store). The feature to look for is called [http://en.wikipedia.org/wiki/USB_video_device_class UVC] though webcam boxes still might not mention it.
*Laser pointers (the more exotic the colors the better). Buy them when you find them. When you go looking for them you can never find them.
*Really bright LEDs
*Photocells, photoresistors, photodetectors.
*Microcontrollers. They may come in handy for modulating/demodulating signals.
*Hackable wireless access points. Here are some [http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Order=BESTMATCH&Description=dd+wrt examples] that might work.
*old headphones/headsets/stereo audio cables and phone cords for cutting up and making into modem to radio connectors

===Radio===
*radio shack/hardware store high bandwidth unlicensed spectrum
*Hacked FRS/GMRS radios
**[http://takethingsapart.blogspot.com/2010/07/note-before-constructing-device-such-as.html Text messages over walkie-talkies.]
**[http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1270645507 Forum post with some ideas.]
**Pros:
***cheap
***longish range (35mi allegedly)
**Cons:
***Need an automated PTT switch or two radios per node
*Develop improvised antennae to improve signal quality, distance covered.
**anything + aluminium foil = bouncy bouncy for radio waves
The FCC has designated a number of channels in the 27 MHz band that can be used for signaling and radio control. They are unnumbered and in-between CB channels 1-13 ([http://forum.servomagazine.com/viewtopic.php?f=1&t=2736 source])

===Optical===
*Modified Ronja-like
**with lasers
**with balloon targets
**with lasers and balloon targets
**with lasers and self-adhesive mirrored decals.
*All Electronics Magazine had a couple of articles on building lasercomm devices on the cheap. Somebody remind the Doctor to go through his magazine collection.
*[http://www.make-digital.com/make/vol16/?pg=69#pg69 How to make a simple laser communicator.] (I do have this issue. Have bought parts to build a pair of transceivers. --The Doctor)
*[http://www.imagineeringezine.com/files/air-bk2.html Handbook of Optical Through-the-Air Communications] is a good read on the basics of an LED-based hardware setup, though he's aiming at voice comms. (Elliot)

===Inspiration===
*[[Ronja]]

===Homework===
*read up on [http://ronja.twibright.com/ Ronja]
*read up on FMRS/GMRS
*read up on and talk to the HacDC Spaceblimp team about soundcard modems: like [http://www.baycom.org/~tom/ham/soundmodem/ this] (also available via apt [[Notes on Soundmodem|like so]])
**[http://www.linux-ax25.org/wiki/Soundmodem Howto](go here last it's a bit short on soundmodem specific info)
**[[Notes on Soundmodem]]
**[http://www.qbjnet.com/packet.html#soundmodem Soundmodem in the field.]
*Read up on [[AX.25]].

===Goals (proposed)===
*Optimize for hackability. Could your average geek build a few of these using junk around zir house and deploy them in an emergency situation?
*Determine the optimum speed in bits per second for a mesh-to-mesh link.
*Measure the bandwidth of a point-to-point long haul connection at a particular distance.
*Determine the maximum practical distance for a long haul connection between two meshes in an urban environment.
*Mathematically describe the way to maximize throughput with a minimum number of nodes.
*Run an ssh session over whatever link is established.
*Interact with a web page over whatever link is established.
*Develop methods to minimize latency.
*Determine the efficiency of the mesh routing protocol we settle on.
**How many active nodes per mesh can be reasonably supported before connectivity breaks down?

===Apps running on Windbringer (laptop/node) to prove functionality===
*[http://status.net/open-source status.net v0.9.6]
*[http://www.mediawiki.org/wiki/MediaWiki Mediawiki]

===Lessons Learned===
*"how hard can it be" ... oops :(