Actions

Difference between revisions of "Byzantium Sprint 2"

From HacDC Wiki

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

Revision as of 21:31, 9 April 2011

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 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 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 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
  • 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 (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.
  • How to make a simple laser communicator. (I do have this issue. Have bought parts to build a pair of transceivers. --The Doctor)
  • 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

Homework

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

Lessons Learned

  • "how hard can it be" ... oops :(
    • very. soundmodem is finicky and creates unstable connections 20% packet loss at best 80-90% avg.
  • "What could possibly go wrong?" ... oops :(
    • everything