https://www.tmplab.org/wiki/api.php?action=feedcontributions&user=Kiniou&feedformat=atomTmplab - User contributions [en]2024-03-29T14:53:17ZUser contributionsMediaWiki 1.30.1https://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1955DemoParty Compo with MilkyMist2009-09-07T08:27:05Z<p>Kiniou: /* The compo */</p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists in developing a compo on the [http://www.milkymist.org/ Milkymist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
* From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
* Rules<br />
: We will compete under the Wild Compo rules:<br />
:* playing time: max. 5 min. if it's boring, or if the audience complains, we will stop it.<br />
:* highest resolution: 1280x720 (PAL 720p recommended)<br />
:* AVI, MPG, or DVD format allowed<br />
:* supported video codecs mpeg1, mpeg2, mpeg4 (DiVX, XViD, h264, WMV)<br />
:* supported sound codecs: uncompressed PCM, MP2, MP3<br />
:* Bring the real hardware to proof its working native<br />
<br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the '''"We need you"''' section and put your name under your favorite task(s).<br />
<br />
=Resources=<br />
* Mailing list: http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org<br />
* Repository: http://github.com/lekernel/milkymist-democompo/tree/master<br />
* HOWTO: http://lists.milkymist.org/pipermail/devel-milkymist.org/2009-September/000121.html<br />
<br />
=We need You=<br />
<br />
* Artworks artist<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(I'm not really a true artist but I put my name just in case)''<br />
<br />
* Music composer<br />
** <your name here><br />
**[[User:alban|alban]]<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(mainly 2D/3D)''<br />
<br />
* Coders<br />
** <your name here><br />
** [[User:Lekernel|Lekernel]] ''(FAE)''<br />
<br />
=Ideas=<br />
<br />
''Put your wonderfull ideas/sketch/links here''<br />
<br />
Debriefing on meeting with kiniou --[[User:Alban|Alban]] 08:24, 4 September 2009 (PDT) <br />
<br />
* General Theme : We could use Sanobot.<br />
<br />
* Visual option : 2D plain forms, kind of cartoon / manga (Kiniou : links ?)<br />
:: Still working on it ;) -- [[User:Kiniou|kiniou]]<br />
<br />
* Script proposal : 3 phases<br />
<br />
* Duration : 3 minutes<br />
<br />
===1. Start/Intro===<br />
<br />
* A . Sanobot data as raw / random numbers flowing on the screen<br />
<br />
Graphics : monochromous, greenish<br />
Visuals : Numbers retrieved randomly from csv and scrolling / zooming<br />
Sound : gloomy and experimental synths pads<br />
Idea : start with something strange that will make sense only later<br />
<br />
:* '' Question : Can we modulate rythm of numbers apparition and their scrolling speed with music analysis ? Ex: no music, no number. Loud : larger font. Bass : slow scroll. ''<br />
:* '' Question : Can we define a length for such a sequence, have it render to screen randomly for a given duration ? ''<br />
<br />
* B. Sanobot as a technical system<br />
<br />
Graphics : colourful, fresh<br />
Visuals : illustrations of sanobot character, manga style animations<br />
Sound : rythmic, funky, acid<br />
Idea : Present sanobot, what it does / how it's built<br />
<br />
===2. Sanobot in action ===<br />
<br />
A. Sanobot data : from random to graphics<br />
<br />
Graphics : fresh illustration in front of monochrome background<br />
Visuals : sanobot character dancing in front of the csv numbers now showing the date : proves they're organized<br />
Sound : mix of both preceding style<br />
Idea : show the numbers seen in 1.A. are not random but organised<br />
<br />
B. Sanobot in its environment<br />
<br />
Graphics : colourful, fresh<br />
Visuals : illustrations of sanobot character, manga style animations<br />
Sound : rythmic, funky, acid ( harder than before )<br />
Idea : why it's called sanobot and presents its enemy : the mighty Sanofi monster, Master of All Toxical Wastes <br />
<br />
===3. Finale===<br />
<br />
* A. Sanobot data : from graphics to communication<br />
<br />
Graphics : fresh cartoon style<br />
Visuals : sanobot character dances as we see the data being distributed on a network<br />
Sound : rythmic music at full pace<br />
Idea : show the numbers seen in 1.A. are being distributed worldwide in a meaningful objective<br />
'' Note : this part should use modulation of visuals depending on graphics as every other A. parts''<br />
<br />
* B. Sanobot in the future <br />
<br />
Visuals : Many sanobots appearing.<br />
Sound : Cool synth pads, atmospheric<br />
Idea : Show how we'll see more sensor systems built by people in the future</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1954DemoParty Compo with MilkyMist2009-09-06T14:49:21Z<p>Kiniou: /* Ideas */</p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists in developing a compo on the [http://www.milkymist.org/ Milkymist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the '''"We need you"''' section and put your name under your favorite task(s).<br />
<br />
=Resources=<br />
* Mailing list: http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org<br />
* Repository: http://github.com/lekernel/milkymist-democompo/tree/master<br />
* HOWTO: http://lists.milkymist.org/pipermail/devel-milkymist.org/2009-September/000121.html<br />
<br />
=We need You=<br />
<br />
* Artworks artist<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(I'm not really a true artist but I put my name just in case)''<br />
<br />
* Music composer<br />
** <your name here><br />
**[[User:alban|alban]]<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(mainly 2D/3D)''<br />
<br />
* Coders<br />
** <your name here><br />
** [[User:Lekernel|Lekernel]] ''(FAE)''<br />
<br />
=Ideas=<br />
<br />
''Put your wonderfull ideas/sketch/links here''<br />
<br />
Debriefing on meeting with kiniou --[[User:Alban|Alban]] 08:24, 4 September 2009 (PDT) <br />
<br />
* General Theme : We could use Sanobot.<br />
<br />
* Visual option : 2D plain forms, kind of cartoon / manga (Kiniou : links ?)<br />
:: Still working on it ;) -- [[User:Kiniou|kiniou]]<br />
<br />
* Script proposal : 3 phases<br />
<br />
* Duration : 3 minutes<br />
<br />
===1. Start/Intro===<br />
<br />
* A . Sanobot data as raw / random numbers flowing on the screen<br />
<br />
Graphics : monochromous, greenish<br />
Visuals : Numbers retrieved randomly from csv and scrolling / zooming<br />
Sound : gloomy and experimental synths pads<br />
Idea : start with something strange that will make sense only later<br />
<br />
:* '' Question : Can we modulate rythm of numbers apparition and their scrolling speed with music analysis ? Ex: no music, no number. Loud : larger font. Bass : slow scroll. ''<br />
:* '' Question : Can we define a length for such a sequence, have it render to screen randomly for a given duration ? ''<br />
<br />
* B. Sanobot as a technical system<br />
<br />
Graphics : colourful, fresh<br />
Visuals : illustrations of sanobot character, manga style animations<br />
Sound : rythmic, funky, acid<br />
Idea : Present sanobot, what it does / how it's built<br />
<br />
===2. Sanobot in action ===<br />
<br />
A. Sanobot data : from random to graphics<br />
<br />
Graphics : fresh illustration in front of monochrome background<br />
Visuals : sanobot character dancing in front of the csv numbers now showing the date : proves they're organized<br />
Sound : mix of both preceding style<br />
Idea : show the numbers seen in 1.A. are not random but organised<br />
<br />
B. Sanobot in its environment<br />
<br />
Graphics : colourful, fresh<br />
Visuals : illustrations of sanobot character, manga style animations<br />
Sound : rythmic, funky, acid ( harder than before )<br />
Idea : why it's called sanobot and presents its enemy : the mighty Sanofi monster, Master of All Toxical Wastes <br />
<br />
===3. Finale===<br />
<br />
* A. Sanobot data : from graphics to communication<br />
<br />
Graphics : fresh cartoon style<br />
Visuals : sanobot character dances as we see the data being distributed on a network<br />
Sound : rythmic music at full pace<br />
Idea : show the numbers seen in 1.A. are being distributed worldwide in a meaningful objective<br />
'' Note : this part should use modulation of visuals depending on graphics as every other A. parts''<br />
<br />
* B. Sanobot in the future <br />
<br />
Visuals : Many sanobots appearing.<br />
Sound : Cool synth pads, atmospheric<br />
Idea : Show how we'll see more sensor systems built by people in the future</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Talk:Blender_:_An_Open_3D_Content_Creation_Suite&diff=1951Talk:Blender : An Open 3D Content Creation Suite2009-09-02T10:55:42Z<p>Kiniou: New section: Ressources à synthétiser pour l'intro</p>
<hr />
<div>Kevin, are you here :) ?<br />
<br />
== Ressources à synthétiser pour l'intro ==<br />
<br />
Yep je suis vivant ;) et voilà quelques sources dont on pourrait s'inpirer<br /><br />
* http://fr.wikipedia.org/wiki/Projection_(géométrie)<br />
* http://fr.wikipedia.org/wiki/OpenGL<br />
* http://fr.wikipedia.org/wiki/Blender<br />
-- Kiniou</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1938DemoParty Compo with MilkyMist2009-08-31T10:59:42Z<p>Kiniou: </p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists to develop a compo on the [http://www.milkymist.org/ Milkymist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the '''"We need you"''' section and put your name under your favorite task(s).<br />
<br />
=We need You=<br />
<br />
* Artworks artist<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(I'm not really a true artist but I put my name just in case)''<br />
<br />
* Music composer<br />
** <your name here><br />
**<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(mainly 2D/3D)''<br />
<br />
<br />
=Ideas=<br />
<br />
''Put your wonderfull ideas/sketch/links here''</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1937DemoParty Compo with MilkyMist2009-08-31T10:53:28Z<p>Kiniou: /* The compo */</p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists to develop a compo on the [http://www.milkymist.org/ Milkymist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the '''"We need you"''' section and put your name under your favorite task(s).<br />
<br />
=We need You=<br />
<br />
* Artworks artist<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(I'm not really a true artist but I put my name just in case)''<br />
<br />
* Music composer<br />
** <your name here><br />
**<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(mainly 2D/3D)''</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1936DemoParty Compo with MilkyMist2009-08-30T17:52:41Z<p>Kiniou: /* What we need */</p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists to develop a compo on the [http://www.milkymist.org/ Milkymist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the "What we need" section and put your name under your favorite task(s).<br />
<br />
=We need You=<br />
<br />
* Artworks artist<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(I'm not really a true artist but I put my name just in case)''<br />
<br />
* Music composer<br />
** <your name here><br />
**<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
** [[User:Kiniou|Kiniou]] ''(mainly 2D/3D)''</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Main_Page&diff=1934Main Page2009-08-29T10:52:50Z<p>Kiniou: /* Projects */</p>
<hr />
<div>This is the Wiki from [http://www.tmplab.org/ /tmp/lab]. You can freely edit this, you just need to register and validate your account with your email address to prevent spam. Thanks!<br />
<br />
<div style="float:left; width:48%;"> <!-- This width adds to the margin below to equal 100 %--> <br />
= Intro =<br />
* [http://www.tmplab.org/about/ About /tmp/lab & FAQ]<br />
* [http://www.tmplab.org/contact/ Coming to /tmp/lab & contact information]<br />
* [http://www.tmplab.org/ Blog & news]<br />
* /tmp/lab is located near a [http://ec.europa.eu/environment/seveso/index.htm Seveso] classified pharmaceutical plant ([http://www.portalanglais.com/spip.php?article132 lire l'article en français])<br />
* [[A little history of /tmp/lab]] (en) ([http://www.tmplab.org/wiki/index.php/A_little_history_of_/tmp/lab#Fran.C3.A7ais Un petit historique du /tmp/lab])<br />
* [[Press]]<br />
* [[Administratif]]<br />
* [http://www.tmplab.org/2009/07/31/stages-au-tmplab-internships/ Stages / Internships]<br />
<br />
= Living =<br />
* [http://www.tmplab.org/wiki/index.php//tmp/lab_How_To How To]<br />
* [[Borrowed things]]<br />
* [[KineKlub]]<br />
* [[Conferences]]<br />
* [[Workshops]]<br />
* [[D&Co]]<br />
<br />
= Events =<br />
* [[Wireless Battle Mesh]]<br />
* [[HackerSpaceEuroTour|HackerSpace Euro Tour, May 2009]] see [[HackerSpaceEuroTours]]<br />
* [[HackerSpaceEuroTour2|HackerSpace Euro Tour 2, June 2009]] see [[HackerSpaceEuroTours]]<br />
* [[HackerSpaceEurasianTour|HackerSpace Eurasian Tour]]<br />
* [http://www.hackerspace.net/ Hacker Space Fest 2009]<br />
* /tmp/lab hors les murs au Palais de Tokyo (4, 11 et 18 Juin 2009)<br />
<br />
</div><br />
<br />
<div style="float:right; width:48%;"> <!-- This width adds to the margin above to equal 100 %--><br />
<br />
= Projects =<br />
* [[OLPC France]]<br />
** [[OLPC Emulation]]<br />
** [[Backtrack3 on EEE]]<br />
** [[OLPC Live]]<br />
** [[Sugar Xubuntu on EEE]]<br />
** [[FlashEEE]]<br />
* [[Hacker Space Fest]]<br />
** [[HSF Organization]]<br />
** [[HSF Task List]]<br />
** [[HSF Spaces]]<br />
* BioEco<br />
** [[Toxic Gas Sensor]]<br />
** [[/tmp/flower]]<br />
* [[/tmp/van]]<br />
* [[Chip Reverse Engineering]]<br />
* [[FreeTvPerso video relay]]<br />
* [[Domoverse platform]]<br />
* [http://dev.tmplab.org/wiki/tmp-usine /tmp/usine: RepRap @ /tmp/lab]<br />
** [[Dream Devices]]<br />
* [[Freedom Not Fear]]<br />
* [[Math Playground]]<br />
* [[esonoclaste upgrade]]<br />
* [[/tmp/net dn42]]<br />
* '''/tmp/demoscene'''<br />
** [[DemoParty Compo with MilkyMist]]<br />
<br />
= Documentation =<br />
<br />
* [[MediaWikiLinks]]<br />
* [[Information Design]]<br />
* [[GIT Cheat Sheet]]<br />
* [[BackTrack]]<br />
* [[RFID]]<br />
* [[Pure Data]]<br />
* [[Mobile Phone Chargers]]<br />
* [[Ruby on Rails]]<br />
* [[Business Methods]]<br />
</div></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DemoParty_Compo_with_MilkyMist&diff=1933DemoParty Compo with MilkyMist2009-08-29T10:34:02Z<p>Kiniou: New page: =Intro= This mini-project consists to develop a compo on the [http://www.milkymist.org/ MilkyMist] platform.<br /> It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demo...</p>
<hr />
<div>=Intro=<br />
<br />
This mini-project consists to develop a compo on the [http://www.milkymist.org/ MilkyMist] platform.<br /><br />
It will be presented at [http://www.mainparty.net/ Main#4 ADA 2009] demoparty which runs from October 2 to October 4 in Arles (France).<br />
<br />
=The compo=<br />
From Main Demoparty site:<br />
<blockquote>''The challenge: create, alone or in teams, a digital work according to aesthetic, technology and platforms, pushing the boundaries of programming to make it the lightest possible.''</blockquote><br />
<br />
For now there is no artwork, nor ideas but if you want to be part of this, fell free to edit the "What we need" section and put your name under your favorite task(s).<br />
<br />
=What we need=<br />
<br />
* Artworks artist<br />
** <your name here><br />
**<br />
<br />
* Music composer<br />
** <your name here><br />
**<br />
<br />
* Multimedia (2D/3D/Sound) developper<br />
** <your name here><br />
**</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1931User:Kiniou2009-08-29T09:19:44Z<p>Kiniou: </p>
<hr />
<div>=Info=<br />
[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p><br />
<br /><br />
<br />
=Projects=<br />
<br />
* [http://dev.knokorpo.fr/repositories/show/blender-scripts|Blender ODP Importer]<br />
* [[DemoParty Compo with MilkyMist]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1930User:Kiniou2009-08-29T09:15:05Z<p>Kiniou: </p>
<hr />
<div>=Info=<br />
[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p><br />
<br /><br />
<br />
=Projects=<br />
<br />
* [http://dev.knokorpo.fr/repositories/show/blender-scripts|Blender ODP Importer]<br />
* [[demoparty-main4-milkymist|DemoParty Main#4 : Compo with MilkyMist]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1929User:Kiniou2009-08-29T09:06:21Z<p>Kiniou: </p>
<hr />
<div>=Info=<br />
[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p><br />
<br /><br />
<br />
=Projects=<br />
<br />
* [[Blender ODP Importer]]<br />
* [[Main#4 Composition with MilkyMist]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=FPGA_Workshop&diff=1834FPGA Workshop2009-07-17T16:08:36Z<p>Kiniou: /* Attendees */</p>
<hr />
<div>{{Workshop<br />
|title=FPGA Workshop #3: Computer Architecture<br />
|when=Saturday, August 29th, 2009 ; 14:00 - 23:00<br />
|where=/tmp/lab<br />
|by=[[User:lekernel|lekernel]]<br />
|intro=Practical computer architecture made possible for individuals<br />
}}<br />
= Introduction =<br />
<b>Computer architecture</b> is the science and art of selecting and interconnecting hardware components to create computers that meet functional, performance and cost goals ([http://en.wikipedia.org/wiki/Computer_architecture Wikipedia]).<br />
<br />
With the invasion of digital devices during the last decade (cellphones, wireless routers, digital TV...), it has become more than ever ubiquitous.<br />
<br />
However, it is still a poorly known subject for most people. Even among the self-proclaimed hardware hacking community, most fanatics of the Arduino <s>development board</s> [http://gizmodo.com/5104149/arduino-+-the-open-source-physical-computing-platform-for-artists-and-engineers open source physical computing platform] do not know that all the functionality of their much-hyped toy comes from an [http://www.atmel.com/products/AVR/ AVR microcontroller chip] that has been being manufactured for years by Atmel. And among those who know, yet fewer people are knowledgeable about the inner working of the AVR microchip; in which <b>computer architecture</b> plays an important role.<br />
<br />
The reason behind this might be that during decades, computer architecture was reserved to academic lectures and companies who had enough cash to build integrated circuits costing several hundreds of thousands of dollars. This left little room for the individuals, except those who had the guts to [http://www.stevechamberlin.com/cpu/category/bmow1/ wire together hundreds of logic ICs] together. But these amateur systems lag well behind commercial solutions in terms of performance, size, and power consumption.<br />
<br />
But today's falling costs of powerful FPGAs make it possible for individuals to build complete high-performance computer systems ([http://en.wikipedia.org/wiki/System-on-a-chip System-on-Chips]) from scratch.<br />
<br />
This workshop will explore this possibility. After introducing basic computer architecture concepts and practices, we will load a simplified version of the [http://www.milkymist.org Milkymist System-on-Chip design] in the development boards and execute basic programs on it. Then, using Verilog HDL, we will design a simple peripheral for the system-on-chip, integrate it, and test it on the board.<br />
<br />
This workshop is for people who want to discover practical computer architecture, and at the same time for those who already know about architecture and want to get an introduction about how to add a peripheral to the open source Milkymist System-on-Chip.<br />
<br />
= Prerequisites =<br />
* Basic knowledge of Verilog HDL (equivalent to the 2 previous workshops)<br />
* Basic programming practice (knowing how to write a for loop in your favorite language is enough)<br />
<br />
= Hardware requirements =<br />
* Come with your laptop<br />
* Bring a development board, preferably a [http://www.em.avnet.com/spartan3a-evl Spartan 3A Evaluation Kit ($49)]<br />
* If you bring another board, you must make sure that:<br />
*# it has a NOR flash chip<br />
*# you have a tool for writing a raw binary image to that flash chip<br />
*# it has a serial port that you can use (bring any required null-modem cable, serial adapter, etc.)<br />
*# you can program the FPGA (bring any required JTAG cable)<br />
* If you are unsure if your board is appropriate or not, feel free to send an email to sebastien dot bourdeauducq at lekernel dahht net<br />
* ISE Webpack software and programming tools for your board must be installed before. Installations take a long time that we cannot afford to waste during the workshop. See previous workshop pages for instructions.<br />
<br />
= Attendees =<br />
Please register yourself by editing this page if you plan to attend.<br />
<br />
# Lekernel<br />
# Yann<br />
# Laura<br />
# Kiniou</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1738User:Kiniou2009-06-18T00:32:56Z<p>Kiniou: </p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p><br />
<br /></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1737User:Kiniou2009-06-17T23:36:56Z<p>Kiniou: </p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p><br />
<br />
[[HSF2009 Organisation]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Workshop_hacking_et_grand_public&diff=1542Workshop hacking et grand public2009-05-14T12:28:52Z<p>Kiniou: Je pensais venir ce soir mais en fait non ...</p>
<hr />
<div>= Summary =<br />
* Titre: Hacking et Grand Public<br />
* Par: Phil<br />
* Date: 14 Mai 2009<br />
* Lieu: /tmp/lab<br />
<br />
= Theme =<br />
Table ronde et workshop: <br />
* Quels sont les avantages et inconvénients de présenter le hacking au grand public?<br />
* Est-ce le rôle d'un hacker space comme le /tmp/lab?<br />
* Quel est le role du /tmp/lab et des hackerspaces dans des combats comme celui de HADOPI?<br />
* Quels sont les enseignements à tirer des expériences médias précédentes?<br />
* Quelles sont les futures actions a mettre en oeuvre?<br />
* Qu'en est il du respect de la vie privée des membres du /tmp/lab?<br />
<br />
== Inscrits/Attendees ==<br />
Steering : [[User:Phil|Phil]]<br />
* Hellekin<br />
* Nico<br />
<br />
[[Category:Workshop]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=1541User:Kiniou2009-05-14T09:53:39Z<p>Kiniou: </p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou CHEZ gmail POINT com</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Workshop_hacking_et_grand_public&diff=1540Workshop hacking et grand public2009-05-14T09:52:30Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>= Summary =<br />
* Titre: Hacking et Grand Public<br />
* Par: Phil<br />
* Date: 14 Mai 2009<br />
* Lieu: /tmp/lab<br />
<br />
= Theme =<br />
Table ronde et workshop: <br />
* Quels sont les avantages et inconvénients de présenter le hacking au grand public?<br />
* Est-ce le rôle d'un hacker space comme le /tmp/lab?<br />
* Quel est le role du /tmp/lab et des hackerspaces dans des combats comme celui de HADOPI?<br />
* Quels sont les enseignements à tirer des expériences médias précédentes?<br />
* Quelles sont les futures actions a mettre en oeuvre?<br />
* Qu'en est il du respect de la vie privée des membres du /tmp/lab?<br />
<br />
== Inscrits/Attendees ==<br />
Steering : [[User:Phil|Phil]]<br />
* Hellekin<br />
* Nico<br />
* [[User:Kiniou|Kiniou]]<br />
<br />
[[Category:Workshop]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=D%26Co&diff=1455D&Co2009-04-14T14:09:50Z<p>Kiniou: </p>
<hr />
<div>[[Image:Dco.jpg]]<br />
<br />
----<br />
== PROPOSITION 1 ==<br />
<br />
Inscrire sur un mur un gros "tmp lab" en ascii avec pourquoi pas des couleurs differentes pour les lettres.<br />
<br />
----<br />
<br />
Materiel requis :<br />
* projecteur + laptop (pour faire comme un calque sur le mur)<br />
* Peinture (autre ?)<br />
* Pinceau (plutot gros)<br />
<br />
_ _ _ _ _ <br />
/ | | / | | | | <br />
/ /| |_ _ __ ___ _ __ / /| | __ _| |__ <br />
/ / | __| '_ ` _ \| '_ \ / / | |/ _` | '_ \ <br />
/ / | |_| | | | | | |_) )/ / | ( (_| | |_) )<br />
\/ \__|_| |_| |_| .__/ \/ |_|\__,_|_.__/ <br />
| | <br />
|_|<br />
<br />
(Louis : je me propose de faire la peinture)<br />
<br />
== PROPOSITION 2 ==<br />
[http://dev.knokorpo.fr/attachments/download/6/test.swf Logo animé pour le tmplab]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Main_Page&diff=1398Main Page2009-04-11T20:28:20Z<p>Kiniou: </p>
<hr />
<div>[[Image:Quadrature_black-out_HADOPI_728x90px.gif|link={http://www.laquadrature.net/HADOPI}]]<br />
<br />
[http://www.laquadrature.net/HADOPI blackout campaign against HADOPI]<br />
<br />
<br />
This is the Wiki from [http://www.tmplab.org/ /tmp/lab]. You can freely edit this, you just need to register and validate your account with your email address to prevent spam. Thanks!<br />
<br />
<div style="float:left; width:48%;"> <!-- This width adds to the margin below to equal 100 %--> <br />
= Intro =<br />
* [http://www.tmplab.org/about/ About /tmp/lab & FAQ]<br />
* [http://www.tmplab.org/contact/ Coming to /tmp/lab & contact information]<br />
* [http://www.tmplab.org/ Blog & news]<br />
* /tmp/lab is located near a [http://ec.europa.eu/environment/seveso/index.htm Seveso] classified pharmaceutical plant ([http://www.portalanglais.com/spip.php?article132 lire l'article en français])<br />
* [[A little history of /tmp/lab]] (en) ([http://www.tmplab.org/wiki/index.php/A_little_history_of_/tmp/lab#Fran.C3.A7ais Un petit historique du /tmp/lab])<br />
* [[Press]]<br />
<br />
= Living =<br />
* [http://www.tmplab.org/wiki/index.php//tmp/lab_How_To How To]<br />
* [[Borrowed things]]<br />
* [[KineKlub]]<br />
* [[Conferences]]<br />
* [[Workshops]]<br />
* [[D&Co]]<br />
<br />
= Events =<br />
* [[Wireless Battle Mesh]]<br />
</div><br />
<br />
<div style="float:right; width:48%;"> <!-- This width adds to the margin above to equal 100 %--><br />
<br />
= Projects =<br />
* [[OLPC France]]<br />
** [[OLPC Emulation]]<br />
** [[Backtrack3 on EEE]]<br />
** [[OLPC Live]]<br />
** [[Sugar Xubuntu on EEE]]<br />
** [[FlashEEE]]<br />
* [[Hacker Space Fest]]<br />
** [[HSF Organization]]<br />
** [[HSF Task List]]<br />
** [[HSF Spaces]]<br />
* BioEco<br />
** [[Toxic Gas Sensor]]<br />
** [[/tmp/flower]]<br />
* [[/tmp/van]]<br />
* [[Chip Reverse Engineering]]<br />
* [[FreeTvPerso video relay]]<br />
* [[Domoverse platform]]<br />
* [http://dev.tmplab.org/wiki/tmp-usine /tmp/usine: RepRap @ /tmp/lab]<br />
** [[Dream Devices]]<br />
* [[Freedom Not Fear]]<br />
* [[Math Playground]]<br />
<br />
= Documentation =<br />
<br />
* [[MediaWikiLinks]]<br />
* [[Information Design]]<br />
* [[GIT Cheat Sheet]]<br />
* [[BackTrack]]<br />
* [[RFID]]<br />
* [[Pure Data]]<br />
* [[Mobile Phone Chargers]]<br />
* [[Ruby on Rails]]<br />
</div></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&diff=1375Wireless Battle Mesh2009-04-11T17:04:37Z<p>Kiniou: </p>
<hr />
<div>[[Image:DSC00007.JPG|400px]]<br />
hackers preparing<br />
<br />
[[Image:DSC00008.JPG|400px]] and flashing linksyses<br />
<br />
== Call for Participants ==<br />
<br />
We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.<br />
<br />
The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.<br />
<br />
OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :<br />
* VLANs<br />
* Captive portal<br />
* Authentication<br />
* Admin portal<br />
<br />
Concerning the mesh-protocols, selected targeted protocols are :<br />
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)<br />
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt<br />
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)<br />
<br />
Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).<br />
<br />
The TMPLAB core team.<br />
<br />
== Agenda ==<br />
<br />
* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes<br />
* Sat, April 11th : <br />
** Morning : setting up the nodes on-site and validation of the different subnets<br />
** Afternoon : first series of tests and measurements with fixed nodes<br />
* Sun 12th : <br />
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)<br />
** Afternoon : Optimization of the protocols and Conclusion<br />
<br />
== Evaluation ==<br />
<br />
=== Criterion ===<br />
We will evaluate the routing protocols using the following criterion :<br />
<br />
* time to setup a node<br />
* CPU activity<br />
* network activity<br />
* convergence time<br />
* scalability<br />
* mobile devices handling<br />
<br />
=== Platform ===<br />
<br />
The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.<br />
<br />
== Hardware platforms ==<br />
<br />
We managed to get sponsoring for such hardware :<br />
<br />
* Linksys WRT54G/GS<br />
* Asus WL500G Deluxe/Premium<br />
* Fon Fonera<br />
<br />
For each protocol 25 nodes will be setup, with the following quantities :<br />
<br />
* FON : 25 nodes<br />
* HSB : 32 nodes<br />
* Wireless-fr : 6 nodes<br />
* Tmplab : 15 nodes<br />
* BATMAN : 10 nodes<br />
* Thus0 : 5 nodes<br />
<br />
Total : 93 nodes. In case of problems, spare nodes are highly wanted.<br />
<br />
=== Identification ===<br />
<br />
For each and every single node in the network, please prepare stickers containing the following informations :<br />
<br />
* routing protocol in use<br />
* MAC address of the Wi-Fi interface<br />
* IP address in the management network<br />
* Owner<br />
* hostname (e.g: node 1-babel)<br />
<br />
=== Node parts ===<br />
<br />
Each and every single node consists of the following physical parts:<br />
<br />
* A wireless router (Linksys, Fon, Asus ...)<br />
* Antennas screwed on the router (no external unless specified)<br />
* Power supply unit<br />
* (Battery)<br />
<br />
== Software platform ==<br />
<br />
The different software versions in use during the Wireless Battle Mesh are :<br />
<br />
* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]<br />
* olsrd-0.5.6-r4<br />
* batman-adv-r1220<br />
<br />
OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.<br />
<br />
=== Software configuration ===<br />
<br />
Every node should be configured with the following settings :<br />
<br />
* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)<br />
* user: root<br />
* password: wbm2009<br />
<br />
We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :<br />
<br />
* version: 2<br />
* community: wbm2009<br />
* permissions: ro<br />
* allow graph disk/flash activity (e.g: disk /)<br />
<br />
=== Package list and repositories ===<br />
<br />
A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :<br />
<br />
* ntpclient (or busybox's rdate)<br />
* wprobe<br />
* snmpd<br />
<br />
== Wireless configuration ==<br />
<br />
Each node will be working in '''Ad-hoc''' mode using the following settings.<br />
<br />
=== For babel ===<br />
<br />
* SSID: babel<br />
* Channel: 1<br />
* Encryption: none<br />
<br />
=== For Batman ===<br />
<br />
* SSID: batman<br />
* Channel: 5<br />
* Encryption: none<br />
<br />
=== For OLSR ===<br />
<br />
* SSID: olsr<br />
* Channel: 11<br />
* Encryption: none<br />
<br />
The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:<br />
<br />
<pre><br />
config wifi-device wl0<br />
option type broadcom<br />
option channel 1<br />
<br />
config wifi-iface<br />
option device wl0<br />
option network wifi<br />
option mode adhoc<br />
option ssid babel<br />
option encryption none<br />
</pre><br />
<br />
For an OLSR node on an Atheros board:<br />
<br />
<pre><br />
config wifi-device wifi0<br />
option type atheros<br />
option channel 11<br />
<br />
config wifi-iface<br />
option device wifi0<br />
option network wifi<br />
option mode sta<br />
option ssid olsr<br />
option encryption none<br />
</pre><br />
<br />
Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.<br />
<br />
== Network topology ==<br />
<br />
There will be different subnets corresponding to different purposes.<br />
<br />
=== Protocol wide subnet ===<br />
<br />
This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:<br />
<br />
* Babel: 192.168.40.0/24<br />
* Batman: 192.168.30.0/24<br />
* OLSR: 192.168.20.0/24<br />
<br />
An '''/etc/config/network''' file for a Babel node looks like this:<br />
<br />
<pre><br />
#### VLAN configuration<br />
config switch eth0<br />
option vlan0 "1 2 3 4 5*"<br />
option vlan1 "0 5"<br />
<br />
<br />
#### Loopback configuration<br />
config interface loopback<br />
option ifname "lo"<br />
option proto static<br />
option ipaddr 127.0.0.1<br />
option netmask 255.0.0.0<br />
<br />
<br />
#### LAN configuration<br />
config interface lan<br />
option type bridge<br />
option ifname "eth0.0"<br />
option proto static<br />
option ipaddr 192.168.2.1<br />
option netmask 255.255.255.0<br />
<br />
#### Wi-Fi configuration<br />
config interface wifi<br />
option ifname "wl0"<br />
option proto static<br />
option ipaddr 192.168.40.1<br />
option netmask 255.255.255.0<br />
</pre><br />
<br />
== Setup ==<br />
<br />
Nodes have been flashed with custom firmware images:<br />
- root password is set to 'wbm2009'<br />
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/<br />
- LAN configuration was not changed and default to 192.168.1.1/24<br />
- Default wireless configuration is:<br />
- ssid: wbm2009<br />
- mode: adhoc<br />
- encryption: none<br />
<br />
When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:<br />
<pre><br />
StrictHostKeyChecking no<br />
UserKnownHostsFile /dev/null<br />
</pre><br />
<br />
=== Wireless IP adresses ===<br />
<br />
you can set the addres this way:<br />
<pre><br />
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit<br />
</pre><br />
00:18:84:21:6B:8C<br />
(LAN MAC, WiFi MAC, WiFi IP)<br />
<br />
==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====<br />
<br />
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.20.14, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.20.15, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.20.16, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL<br />
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.20.18, WRT54GL<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.20.20, WRT54GS<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.20.22, WRT54GL<br />
<br />
==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 ====<br />
<br />
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2<br />
<br />
==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====<br />
<br />
==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====<br />
<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS<br />
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL<br />
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL<br />
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL<br />
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL<br />
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL<br />
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL<br />
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL<br />
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL<br />
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL<br />
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4<br />
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS<br />
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1<br />
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1<br />
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1<br />
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2<br />
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera<br />
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera<br />
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera<br />
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera<br />
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera<br />
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera<br />
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera<br />
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera<br />
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera<br />
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera<br />
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera<br />
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera<br />
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD<br />
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD<br />
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&diff=1374Wireless Battle Mesh2009-04-11T17:02:55Z<p>Kiniou: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 */</p>
<hr />
<div>[[Image:DSC00007.JPG|400px]]<br />
hackers preparing<br />
<br />
[[Image:DSC00008.JPG|400px]] and flashing linksyses<br />
<br />
== Call for Participants ==<br />
<br />
We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.<br />
<br />
The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.<br />
<br />
OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :<br />
* VLANs<br />
* Captive portal<br />
* Authentication<br />
* Admin portal<br />
<br />
Concerning the mesh-protocols, selected targeted protocols are :<br />
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)<br />
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt<br />
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)<br />
<br />
Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).<br />
<br />
The TMPLAB core team.<br />
<br />
== Agenda ==<br />
<br />
* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes<br />
* Sat, April 11th : <br />
** Morning : setting up the nodes on-site and validation of the different subnets<br />
** Afternoon : first series of tests and measurements with fixed nodes<br />
* Sun 12th : <br />
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)<br />
** Afternoon : Optimization of the protocols and Conclusion<br />
<br />
== Evaluation ==<br />
<br />
=== Criterion ===<br />
We will evaluate the routing protocols using the following criterion :<br />
<br />
* time to setup a node<br />
* CPU activity<br />
* network activity<br />
* convergence time<br />
* scalability<br />
* mobile devices handling<br />
<br />
=== Platform ===<br />
<br />
The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.<br />
<br />
== Hardware platforms ==<br />
<br />
We managed to get sponsoring for such hardware :<br />
<br />
* Linksys WRT54G/GS<br />
* Asus WL500G Deluxe/Premium<br />
* Fon Fonera<br />
<br />
For each protocol 25 nodes will be setup, with the following quantities :<br />
<br />
* FON : 25 nodes<br />
* HSB : 32 nodes<br />
* Wireless-fr : 6 nodes<br />
* Tmplab : 15 nodes<br />
* BATMAN : 10 nodes<br />
* Thus0 : 5 nodes<br />
<br />
Total : 93 nodes. In case of problems, spare nodes are highly wanted.<br />
<br />
=== Identification ===<br />
<br />
For each and every single node in the network, please prepare stickers containing the following informations :<br />
<br />
* routing protocol in use<br />
* MAC address of the Wi-Fi interface<br />
* IP address in the management network<br />
* Owner<br />
* hostname (e.g: node 1-babel)<br />
<br />
=== Node parts ===<br />
<br />
Each and every single node consists of the following physical parts:<br />
<br />
* A wireless router (Linksys, Fon, Asus ...)<br />
* Antennas screwed on the router (no external unless specified)<br />
* Power supply unit<br />
* (Battery)<br />
<br />
== Software platform ==<br />
<br />
The different software versions in use during the Wireless Battle Mesh are :<br />
<br />
* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]<br />
* olsrd-0.5.6-r4<br />
* batman-adv-r1220<br />
<br />
OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.<br />
<br />
=== Software configuration ===<br />
<br />
Every node should be configured with the following settings :<br />
<br />
* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)<br />
* user: root<br />
* password: wbm2009<br />
<br />
We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :<br />
<br />
* version: 2<br />
* community: wbm2009<br />
* permissions: ro<br />
* allow graph disk/flash activity (e.g: disk /)<br />
<br />
=== Package list and repositories ===<br />
<br />
A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :<br />
<br />
* ntpclient (or busybox's rdate)<br />
* wprobe<br />
* snmpd<br />
<br />
== Wireless configuration ==<br />
<br />
Each node will be working in '''Ad-hoc''' mode using the following settings.<br />
<br />
=== For babel ===<br />
<br />
* SSID: babel<br />
* Channel: 1<br />
* Encryption: none<br />
<br />
=== For Batman ===<br />
<br />
* SSID: batman<br />
* Channel: 5<br />
* Encryption: none<br />
<br />
=== For OLSR ===<br />
<br />
* SSID: olsr<br />
* Channel: 11<br />
* Encryption: none<br />
<br />
The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:<br />
<br />
<pre><br />
config wifi-device wl0<br />
option type broadcom<br />
option channel 1<br />
<br />
config wifi-iface<br />
option device wl0<br />
option network wifi<br />
option mode adhoc<br />
option ssid babel<br />
option encryption none<br />
</pre><br />
<br />
For an OLSR node on an Atheros board:<br />
<br />
<pre><br />
config wifi-device wifi0<br />
option type atheros<br />
option channel 11<br />
<br />
config wifi-iface<br />
option device wifi0<br />
option network wifi<br />
option mode sta<br />
option ssid olsr<br />
option encryption none<br />
</pre><br />
<br />
Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.<br />
<br />
== Network topology ==<br />
<br />
There will be different subnets corresponding to different purposes.<br />
<br />
=== Protocol wide subnet ===<br />
<br />
This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:<br />
<br />
* Babel: 192.168.40.0/24<br />
* Batman: 192.168.30.0/24<br />
* OLSR: 192.168.20.0/24<br />
<br />
An '''/etc/config/network''' file for a Babel node looks like this:<br />
<br />
<pre><br />
#### VLAN configuration<br />
config switch eth0<br />
option vlan0 "1 2 3 4 5*"<br />
option vlan1 "0 5"<br />
<br />
<br />
#### Loopback configuration<br />
config interface loopback<br />
option ifname "lo"<br />
option proto static<br />
option ipaddr 127.0.0.1<br />
option netmask 255.0.0.0<br />
<br />
<br />
#### LAN configuration<br />
config interface lan<br />
option type bridge<br />
option ifname "eth0.0"<br />
option proto static<br />
option ipaddr 192.168.2.1<br />
option netmask 255.255.255.0<br />
<br />
#### Wi-Fi configuration<br />
config interface wifi<br />
option ifname "wl0"<br />
option proto static<br />
option ipaddr 192.168.40.1<br />
option netmask 255.255.255.0<br />
</pre><br />
<br />
== Setup ==<br />
<br />
Nodes have been flashed with custom firmware images:<br />
- root password is set to 'wbm2009'<br />
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/<br />
- LAN configuration was not changed and default to 192.168.1.1/24<br />
- Default wireless configuration is:<br />
- ssid: wbm2009<br />
- mode: adhoc<br />
- encryption: none<br />
<br />
When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:<br />
<pre><br />
StrictHostKeyChecking no<br />
UserKnownHostsFile /dev/null<br />
</pre><br />
<br />
=== Wireless IP adresses ===<br />
<br />
you can set the addres this way:<br />
<pre><br />
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit<br />
</pre><br />
00:18:84:21:6B:8C<br />
(LAN MAC, WiFi MAC, WiFi IP)<br />
<br />
==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====<br />
<br />
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.20.14, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.20.15, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.20.16, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL<br />
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.20.18, WRT54GL<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.20.20, WRT54GS<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.20.22, WRT54GL<br />
<br />
==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 <br />
====<br />
<br />
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2<br />
<br />
==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====<br />
<br />
==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====<br />
<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS<br />
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL<br />
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL<br />
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL<br />
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL<br />
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL<br />
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL<br />
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL<br />
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL<br />
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL<br />
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4<br />
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS<br />
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1<br />
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1<br />
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1<br />
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2<br />
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera<br />
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera<br />
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera<br />
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera<br />
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera<br />
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera<br />
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera<br />
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera<br />
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera<br />
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera<br />
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera<br />
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera<br />
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD<br />
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD<br />
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Wireless_Battle_Mesh&diff=1372Wireless Battle Mesh2009-04-11T17:02:05Z<p>Kiniou: /* Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 */</p>
<hr />
<div>[[Image:DSC00007.JPG|400px]]<br />
hackers preparing<br />
<br />
[[Image:DSC00008.JPG|400px]] and flashing linksyses<br />
<br />
== Call for Participants ==<br />
<br />
We are pleased to announce that the /tmp/lab will be organizing a Spring Wireless OpenWrt Mesh Contest called “Wireless Battle Mesh” during 2 days (April 11-12th) with the goal of building 3 wireless mesh networks based on embedded hardware running OpenWrt and different concurrent mesh routing protocols.<br />
<br />
The targeted architecture will be 3 networks of 25nodes + 1 wireless management network (10-20 nodes) to achieve realistic size of nodes number, data traffic, configuration problems. The architecture will be set-up indoor and outdoor around the building of the /tmp/lab.<br />
<br />
OpenWrt will be the selected for the BoardSupportPackage running on the different hardware nodes and a core network configuration will be built on Linux servers with user-friendly features such as :<br />
* VLANs<br />
* Captive portal<br />
* Authentication<br />
* Admin portal<br />
<br />
Concerning the mesh-protocols, selected targeted protocols are :<br />
* OLSR : IP-based mesh routing platform (http://olsr.org and OpenWrt package available)<br />
* BATMAN : Layer2-based mesh protocol (http://open-mesh.org) and available as a kernel module for Linux and packaged in OpenWrt<br />
* BABEL : Layer-3 mesh protocol developed by University Paris 6, available for Linux and packaged in OpenWrt (http://www.pps.jussieu.fr/~jch/software/babel/)<br />
<br />
Concerning the hardware node, we are looking for hardware sponsors that could enjoy this “real-case” contest by providing 50-100 nodes to the event. This sponsor will be actually displayed on the organization website as well as during the event. The feedbacks for the hardware manufacturers can be not only from the users but also from the network community running real-case test (academic- or community-wide).<br />
<br />
The TMPLAB core team.<br />
<br />
== Agenda ==<br />
<br />
* Friday, April 10th, 8 pm : welcoming of the first people coming and flashing of the node and configuration of the nodes<br />
* Sat, April 11th : <br />
** Morning : setting up the nodes on-site and validation of the different subnets<br />
** Afternoon : first series of tests and measurements with fixed nodes<br />
* Sun 12th : <br />
** Morning : second series of tests and measurement with fixed and mobile nodes (laptops)<br />
** Afternoon : Optimization of the protocols and Conclusion<br />
<br />
== Evaluation ==<br />
<br />
=== Criterion ===<br />
We will evaluate the routing protocols using the following criterion :<br />
<br />
* time to setup a node<br />
* CPU activity<br />
* network activity<br />
* convergence time<br />
* scalability<br />
* mobile devices handling<br />
<br />
=== Platform ===<br />
<br />
The evaluation platform consits of a SNMP agent which collects graphs from the different nodes using Cacti.<br />
<br />
== Hardware platforms ==<br />
<br />
We managed to get sponsoring for such hardware :<br />
<br />
* Linksys WRT54G/GS<br />
* Asus WL500G Deluxe/Premium<br />
* Fon Fonera<br />
<br />
For each protocol 25 nodes will be setup, with the following quantities :<br />
<br />
* FON : 25 nodes<br />
* HSB : 32 nodes<br />
* Wireless-fr : 6 nodes<br />
* Tmplab : 15 nodes<br />
* BATMAN : 10 nodes<br />
* Thus0 : 5 nodes<br />
<br />
Total : 93 nodes. In case of problems, spare nodes are highly wanted.<br />
<br />
=== Identification ===<br />
<br />
For each and every single node in the network, please prepare stickers containing the following informations :<br />
<br />
* routing protocol in use<br />
* MAC address of the Wi-Fi interface<br />
* IP address in the management network<br />
* Owner<br />
* hostname (e.g: node 1-babel)<br />
<br />
=== Node parts ===<br />
<br />
Each and every single node consists of the following physical parts:<br />
<br />
* A wireless router (Linksys, Fon, Asus ...)<br />
* Antennas screwed on the router (no external unless specified)<br />
* Power supply unit<br />
* (Battery)<br />
<br />
== Software platform ==<br />
<br />
The different software versions in use during the Wireless Battle Mesh are :<br />
<br />
* babel-0.94 (and not 0.93 as previously announced), there's also a page about [[Babel]]<br />
* olsrd-0.5.6-r4<br />
* batman-adv-r1220<br />
<br />
OpenWrt should be Kamikaze 8.09. Broadcom-based hardware should be using the '''brcm-2.4''' image while Atheros-based hardware should be using the '''atheros''' target. If you need help flashing your devices do not hesitate to poke Florian and Nico about this.<br />
<br />
=== Software configuration ===<br />
<br />
Every node should be configured with the following settings :<br />
<br />
* hostname: node<N>-<routing protocol> (where N can be found using the plan/map and the routing protocol is babel, olsr or batman)<br />
* user: root<br />
* password: wbm2009<br />
<br />
We would like to be able to monitor the activity of every node, therefore an aditional SNMP configuration should be done with the following settings :<br />
<br />
* version: 2<br />
* community: wbm2009<br />
* permissions: ro<br />
* allow graph disk/flash activity (e.g: disk /)<br />
<br />
=== Package list and repositories ===<br />
<br />
A mirror of the OpenWrt kamikaze 8.09 package repository will be available during the WBM2009. Additionnal packages that we recommend to install are :<br />
<br />
* ntpclient (or busybox's rdate)<br />
* wprobe<br />
* snmpd<br />
<br />
== Wireless configuration ==<br />
<br />
Each node will be working in '''Ad-hoc''' mode using the following settings.<br />
<br />
=== For babel ===<br />
<br />
* SSID: babel<br />
* Channel: 1<br />
* Encryption: none<br />
<br />
=== For Batman ===<br />
<br />
* SSID: batman<br />
* Channel: 5<br />
* Encryption: none<br />
<br />
=== For OLSR ===<br />
<br />
* SSID: olsr<br />
* Channel: 11<br />
* Encryption: none<br />
<br />
The resulting '''/etc/config/wireless''' is then for Broadcom devices and for a Babel node:<br />
<br />
<pre><br />
config wifi-device wl0<br />
option type broadcom<br />
option channel 1<br />
<br />
config wifi-iface<br />
option device wl0<br />
option network wifi<br />
option mode adhoc<br />
option ssid babel<br />
option encryption none<br />
</pre><br />
<br />
For an OLSR node on an Atheros board:<br />
<br />
<pre><br />
config wifi-device wifi0<br />
option type atheros<br />
option channel 11<br />
<br />
config wifi-iface<br />
option device wifi0<br />
option network wifi<br />
option mode sta<br />
option ssid olsr<br />
option encryption none<br />
</pre><br />
<br />
Note: we unbridge the LAN interface with the Wi-Fi interface in order to be able to define specific networks on the LAN interface.<br />
<br />
== Network topology ==<br />
<br />
There will be different subnets corresponding to different purposes.<br />
<br />
=== Protocol wide subnet ===<br />
<br />
This subnet is required for the nodes running a given protocol to work, meaning that the wireless interface in ad-hoc mode must be configured with an address falling within the range defined below:<br />
<br />
* Babel: 192.168.40.0/24<br />
* Batman: 192.168.30.0/24<br />
* OLSR: 192.168.20.0/24<br />
<br />
An '''/etc/config/network''' file for a Babel node looks like this:<br />
<br />
<pre><br />
#### VLAN configuration<br />
config switch eth0<br />
option vlan0 "1 2 3 4 5*"<br />
option vlan1 "0 5"<br />
<br />
<br />
#### Loopback configuration<br />
config interface loopback<br />
option ifname "lo"<br />
option proto static<br />
option ipaddr 127.0.0.1<br />
option netmask 255.0.0.0<br />
<br />
<br />
#### LAN configuration<br />
config interface lan<br />
option type bridge<br />
option ifname "eth0.0"<br />
option proto static<br />
option ipaddr 192.168.2.1<br />
option netmask 255.255.255.0<br />
<br />
#### Wi-Fi configuration<br />
config interface wifi<br />
option ifname "wl0"<br />
option proto static<br />
option ipaddr 192.168.40.1<br />
option netmask 255.255.255.0<br />
</pre><br />
<br />
== Setup ==<br />
<br />
Nodes have been flashed with custom firmware images:<br />
- root password is set to 'wbm2009'<br />
- pubkey ssh authentication is enabled, keys are available here: http://ska.lan.tmplab.org/ssh/<br />
- LAN configuration was not changed and default to 192.168.1.1/24<br />
- Default wireless configuration is:<br />
- ssid: wbm2009<br />
- mode: adhoc<br />
- encryption: none<br />
<br />
When using ssh with same key and different hosts, it might be convenient to add the following in /etc/ssh/ssh_config:<br />
<pre><br />
StrictHostKeyChecking no<br />
UserKnownHostsFile /dev/null<br />
</pre><br />
<br />
=== Wireless IP adresses ===<br />
<br />
you can set the addres this way:<br />
<pre><br />
root@OpenWrt:~# uci set network.wifi.ipaddr="192.168.44.x"; uci commit<br />
</pre><br />
00:18:84:21:6B:8C<br />
(LAN MAC, WiFi MAC, WiFi IP)<br />
<br />
==== Channel: 1, ESSID: wbm2009-olsr, BSSID: CA:CA:FE:CA:CA:20, IP: 192.168.20.0/24 ====<br />
<br />
* 00:0F:66:24:E9:D0, 00:0F:66:24:E9:D2, 192.168.20.1, WRT54G v1.1<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.20.2, WRT54GL v1.1<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.20.3, WRT54GL v1.1<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.20.4, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.20.5, WRT54GS v4<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.20.6, WRT54GS v4<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.20.7, WRT54GS v1.1<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.20.8, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.20.9, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.20.10, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.20.11, WRT54GS v4<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.20.12, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.20.13, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.20.14, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.20.15, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.20.16, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.20.17, WRT54GL<br />
<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.20.20, WRT54GS<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.20.21, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.20.22, WRT54GL<br />
<br />
==== Channel: 6, ESSID: wbm2009-babel, BSSID: CA:CA:FE:CA:CA:230, IP: 192.168.30.0/24 ====<br />
<br />
* 00:1F:C6:62:28:0F, 00:1F:C6:62:28:0F, 192.168.30.25, Asus WL-500Gpv2<br />
<br />
==== Channel: 11, ESSID: wbm2009-batman, BSSID: CA:CA:FE:CA:CA:40, IP: 192.168.40.0/24 ====<br />
<br />
==== Channel: 1, ESSID: wbm2009, IP: 192.168.44.x/24 ====<br />
<br />
* 00:0F:66:C7:C0:AD, 00:0F:66:C7:C0:AF, 192.168.44.101, WRT54GS<br />
* 00:16:B6:40:F2:C6, 00:16:B6:40:F2:C8, 192.168.44.102, WRT54GL<br />
* 00:14:BF:D2:65:A1, 00:14:BF:D2:65:A3, 192.168.44.103, WRT54GL<br />
* 00:16:B6:D9:25:B7, 00:16:B6:D9:25:B9, 192.168.44.104, WRT54GL<br />
* 00:16:B6:40:F2:D5, 00:16:B6:40:F2:D7, 192.168.44.105, WRT54GL<br />
* 00:16:B6:40:F2:DB, 00:16:B6:40:F2:DD, 192.168.44.106, WRT54GL<br />
* 00:16:B6:40:F2:C0, 00:16:B6:40:F2:C2, 192.168.44.107, WRT54GL<br />
* 00:16:B6:40:F9:F2, 00:16:B6:40:F9:F4, 192.168.44.108, WRT54GL<br />
* 00:16:B6:40:F2:CF, 00:16:B6:40:F2:D1, 192.168.44.109, WRT54GL<br />
* 00:14:BF:D2:6C:04, 00:14:BF:D2:6C:06, 192.168.44.110, WRT54GL<br />
* 00:16:B6:40:F2:D2, 00:16:B6:40:F2:D4, 192.168.44.111, WRT54GL<br />
* 00:16:B6:40:F2:D8, 00:16:B6:40:F2:DA, 192.168.44.112, WRT54GL<br />
* 00:16:B6:40:F2:CC, 00:16:B6:40:F2:CE, 192.168.44.113, WRT54GL<br />
* 00:16:B6:40:F2:C3, 00:16:B6:40:F2:C5, 192.168.44.114, WRT54GL<br />
* 00:14:BF:D2:65:86, 00:14:BF:D2:65:88, 192.168.44.115, WRT54GL<br />
* 00:14:BF:D2:65:9E, 00:14:BF:D2:65:A0, 192.168.44.116, WRT54GL<br />
* 00:18:39:BC:39:54, 00:18:39:BC:39:56, 192.168.44.117, WRT54GL<br />
* 00:16:B6:41:02:8C, 00:16:B6:41:02:8E, 192.168.44.118, WRT54GL<br />
* 00:16:B6:40:DE:3E, 00:16:B6:40:DE:40, 192.168.44.119, WRT54GL<br />
* 00:1A:70:FD:4B:03, 00:1A:70:FD:4B:05, 192.168.44.120, WRT54GL<br />
* 00:14:BF:E2:B5:3F, 00:14:BF:E2:B5:41, 192.168.44.121, WRT54GS v4<br />
* 00:16:B6:01:66:87, 00:16:B6:01:66:89, 192.168.44.122, WRT54GS v4<br />
* 00:16:B6:01:5F:E5, 00:16:B6:01:5F:E7, 192.168.44.123, WRT54GS v4<br />
* 00:16:B6:01:5F:DF, 00:16:B6:01:5F:E1, 192.168.44.124, WRT54GS v4<br />
* 00:16:B6:01:5F:E8, 00:16:B6:01:5F:EA, 192.168.44.125, WRT54GS v4<br />
* 00:16:B6:01:57:CF, 00:16:B6:01:57:D1, 192.168.44.126, WRT54GS v4<br />
* 00:16:B6:01:5F:DC, 00:16:B6:01:5F:DE, 192.168.44.127, WRT54GS v4<br />
* 00:14:BF:A5:B9:4C, 00:14:BF:A5:B9:4E, 192.168.44.128, WRT54GS v4<br />
* 00:0F:66:C7:B9:6F, 00:0F:66:C7:B9:71, 192.168.44.129, WRT54GS<br />
* 00:13:10:07:EE:FC, 00:13:10:07:EE:FE, 192.168.44.130, WRT54GS v1.1<br />
* 00:12:17:DF:A7:28, 00:12:17:DF:A7:2A, 192.168.44.131, WRT54GS v1.1<br />
* 00:0F:66:24:EE:2F, 00:0F:66:24:EE:31, 192.168.44.133, WRT54G v1.1<br />
* 00:14:BF:BF:E6:5A, 00:14:BF:BF:E6:5C, 192.168.44.134, WRT54G v3.1<br />
* 00:12:17:26:EB:84, 00:12:17:26:EB:86, 192.168.44.135, WRT54G v2<br />
* 00:18:84:25:69:50, 00:18:84:25:69:51, 192.168.44.136, Fonera<br />
* 00:18:84:10:2F:7C, 00:18:84:10:2F:7D, 192.168.44.137, Fonera<br />
* 00:18:84:1C:EB:28, 00:18:84:1C:EB:29, 192.168.44.138, Fonera<br />
* 00:18:84:13:A5:50, 00:18:84:13:A5:51, 192.168.44.139, Fonera<br />
* 00:18:84:12:F7:2C, 00:18:84:12:F7:2D, 192.168.44.140, Fonera<br />
* 00:18:84:21:6B:8C, 00:18:84:21:6B:8D, 192.168.44.141, Fonera<br />
* 00:18:84:27:19:5C, 00:18:84:27:19:5D, 192.168.44.142, Fonera<br />
* 00:18:84:1C:F7:4C, 00:18:84:1C:F7:4D, 192.168.44.143, Fonera<br />
* 00:18:84:25:28:E4, 00:18:84:25:28:E5, 192.168.44.144, Fonera<br />
* 00:18:84:28:90:78, 00:18:84:28:90:79, 192.168.44.145, Fonera<br />
* 00:18:84:25:DF:50, 00:18:84:25:DF:51, 192.168.44.146, Fonera<br />
* 00:18:84:27:7E:E0, 00:18:84:27:7E:E1, 192.168.44.147, Fonera<br />
* 00:11:2F:9D:15:86, 00:11:2F:9D:15:86, 192.168.44.148, WL500GD<br />
* 00:11:2F:9D:15:98, 00:11:2F:9D:15:98, 192.168.44.149, WL500GD<br />
* 00:11:2F:9D:15:43, 00:11:2F:9D:15:43, 192.168.44.150, WL500GD</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=SuperCollider_Part_I&diff=1244SuperCollider Part I2009-04-02T19:48:47Z<p>Kiniou: </p>
<hr />
<div>{{Workshop<br />
|title=SuperCollider Part I<br />
|when=Thursday 02 April 2009<br />
|where=/tmp/lab<br />
|intro=Beginning to program in SuperCollider, understanding structures ...<br />
|by=[[User:Artheist|Artheist]]<br />
}}<br />
<br />
== Les Possibilités ==<br />
Après discussion avec Nico, nous allons essayer de commencer à 19h30. <br />
Il est possible de faire plusieurs choses, suivant les souhaits des participants. Sachant que l'on pourra tout traiter au fur et à mesure des workshops.<br />
Le but serait dans l'idéal d'aboutir (si cela vous intéresse, bien sûr) à une performance collaborative en réseau, si possible pour le HSF (date à définir).<br />
Il sera également envisageable de coupler l'utilisation de SC3 avec les Workshops DIY Audio pour intégrer micro, effets, enceintes ... Les sujets :<br />
<br />
* 1 - Architecture, Serveurs, Syntaxe, Fonctions, Help ... (Indispensable, à mon avis pour pouvoir se débrouiller tout seul)<br />
* 2 - Synthèse : AM, FM, Additive, Soustractive, Granulaire, Modélisation Physique<br />
* 3 - Les effets : Delais, Fréquence (Phaser, Flanger, FFT ...), Amplitude (Compresseur ...)<br />
* 4 - Les Patterns : Créer des rythmes et mélodies (nécessite des notions/rappels en solfège)<br />
* 5 - Les interfaces : MIDI, OSC, Wii, HID, GUI et Cie.<br />
* 6 - Les librairies externes : Installation, utilisation du cvs, svn, quarks.<br />
* 7 - Les classes et la programmation (en dernier, pour les utilisateurs experts) ; permet de créer ses propres fonctions.<br />
<br />
Si vous avez d'autres idées, n'hésitez pas à les rajouter ci-dessous en continuant la numérotation.<br />
<br />
== Les Devoirs ==<br />
Pour ce Workshop, il serait BIEN que chacun ait au minimum téléchargé, et si possible installé le logiciel SuperCollider 3.2. Pour cela, veuillez utiliser l'url suivante :<br />
* http://supercollider.sourceforge.net/<br />
Vous y trouverez le package correspondant à votre système d'exploitation préféré. Le système idéal est Mac OSX, certaines fonctionnalités étant limitées pour Windows, et dans une moindre mesure Linux.<br />
Vous trouverez également à cette adresse, un certain nombre d'information utiles, que vous pouvez lire pour améliorez l'interaction du workshop. <br />
* Note Importante : Le package vient sous une version zippée avec le logiciel et un certain nombre de librairies externes au logiciel. Je vous déconseille d'installer toutes ces librairies dès le départ, cela risque de créer des conflits de classes et empêcher le serveur de se lancer. Il vaut mieux installer ces librairies au fur et à mesure des besoins pour limiter et corriger les conflits éventuels.<br />
* Note moins importante : pour vérifier que le logiciel fonctionne, lorsque vous le lancez, une (ou deux suivant l'OS) fenêtres doivent apparaître avec le nom "Internal server" (et "localhost server"). Si ces fenêtres apparaissent tout est ok, sinon ...<br />
<br />
== Participants ==<br />
* Le Mono : [[User:Artheist|Artheist]]<br />
* Inscrivez-vous ici, en classant par ordre de préférence les sujets proposés dans la section "Possibilités", identifiés par leurs numéros (ndlr : sauf 1 et 7). Pour toute question, cf. mailing list. Merci.<br />
*Ursula (1-2-5-3-4 ) beau programme!!<br />
* Trop Rance :[[User:toyoto|Toyoto]](1-5-2-3) un petit faible pour les contrôleurs HID...<br />
* Nico (la totale)<br />
* Louis (2-5-3-6) (arrivera vers 20h00)<br />
* Atrus (2-3-5-6)<br />
* [[User:Kiniou|Kiniou]] (1-3-5-2-4-6-7)<br />
<br />
== Fichiers du workshop ==<br />
<br />
[[Image:SC_Partone.zip|SC_Partone.zip]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=File:SC_Partone.zip&diff=1243File:SC Partone.zip2009-04-02T19:45:36Z<p>Kiniou: </p>
<hr />
<div></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=SuperCollider_Part_I&diff=1242SuperCollider Part I2009-04-02T15:52:04Z<p>Kiniou: /* Participants */</p>
<hr />
<div>{{Workshop<br />
|title=SuperCollider Part I<br />
|when=Thursday 02 April 2009<br />
|where=/tmp/lab<br />
|intro=Beginning to program in SuperCollider, understanding structures ...<br />
|by=[[User:Artheist|Artheist]]<br />
}}<br />
<br />
== Les Possibilités ==<br />
Après discussion avec Nico, nous allons essayer de commencer à 19h30. <br />
Il est possible de faire plusieurs choses, suivant les souhaits des participants. Sachant que l'on pourra tout traiter au fur et à mesure des workshops.<br />
Le but serait dans l'idéal d'aboutir (si cela vous intéresse, bien sûr) à une performance collaborative en réseau, si possible pour le HSF (date à définir).<br />
Il sera également envisageable de coupler l'utilisation de SC3 avec les Workshops DIY Audio pour intégrer micro, effets, enceintes ... Les sujets :<br />
<br />
* 1 - Architecture, Serveurs, Syntaxe, Fonctions, Help ... (Indispensable, à mon avis pour pouvoir se débrouiller tout seul)<br />
* 2 - Synthèse : AM, FM, Additive, Soustractive, Granulaire, Modélisation Physique<br />
* 3 - Les effets : Delais, Fréquence (Phaser, Flanger, FFT ...), Amplitude (Compresseur ...)<br />
* 4 - Les Patterns : Créer des rythmes et mélodies (nécessite des notions/rappels en solfège)<br />
* 5 - Les interfaces : MIDI, OSC, Wii, HID, GUI et Cie.<br />
* 6 - Les librairies externes : Installation, utilisation du cvs, svn, quarks.<br />
* 7 - Les classes et la programmation (en dernier, pour les utilisateurs experts) ; permet de créer ses propres fonctions.<br />
<br />
Si vous avez d'autres idées, n'hésitez pas à les rajouter ci-dessous en continuant la numérotation.<br />
<br />
== Les Devoirs ==<br />
Pour ce Workshop, il serait BIEN que chacun ait au minimum téléchargé, et si possible installé le logiciel SuperCollider 3.2. Pour cela, veuillez utiliser l'url suivante :<br />
* http://supercollider.sourceforge.net/<br />
Vous y trouverez le package correspondant à votre système d'exploitation préféré. Le système idéal est Mac OSX, certaines fonctionnalités étant limitées pour Windows, et dans une moindre mesure Linux.<br />
Vous trouverez également à cette adresse, un certain nombre d'information utiles, que vous pouvez lire pour améliorez l'interaction du workshop. <br />
* Note Importante : Le package vient sous une version zippée avec le logiciel et un certain nombre de librairies externes au logiciel. Je vous déconseille d'installer toutes ces librairies dès le départ, cela risque de créer des conflits de classes et empêcher le serveur de se lancer. Il vaut mieux installer ces librairies au fur et à mesure des besoins pour limiter et corriger les conflits éventuels.<br />
* Note moins importante : pour vérifier que le logiciel fonctionne, lorsque vous le lancez, une (ou deux suivant l'OS) fenêtres doivent apparaître avec le nom "Internal server" (et "localhost server"). Si ces fenêtres apparaissent tout est ok, sinon ...<br />
<br />
== Participants ==<br />
* Le Mono : [[User:Artheist|Artheist]]<br />
* Inscrivez-vous ici, en classant par ordre de préférence les sujets proposés dans la section "Possibilités", identifiés par leurs numéros (ndlr : sauf 1 et 7). Pour toute question, cf. mailing list. Merci.<br />
*Ursula (1-2-5-3-4 ) beau programme!!<br />
* Trop Rance :[[User:toyoto|Toyoto]](1-5-2-3) un petit faible pour les contrôleurs HID...<br />
* Nico (la totale)<br />
* Louis (2-5-3-6) (arrivera vers 20h00)<br />
* Atrus (2-3-5-6)<br />
* [[User:Kiniou|Kiniou]] (1-3-5-2-4-6-7)</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_:_Taste_the_code&diff=1141Python : Taste the code2009-03-24T14:32:35Z<p>Kiniou: New page: {{Workshop |title=Python : Taste the code :P |when= |where=/tmp/lab |intro=Now we learn a little about Python and basic coding, it's time to put your hands into it! |by=[[User:Kiniou|kinio...</p>
<hr />
<div>{{Workshop<br />
|title=Python : Taste the code :P<br />
|when=<br />
|where=/tmp/lab<br />
|intro=Now we learn a little about Python and basic coding, it's time to put your hands into it!<br />
|by=[[User:Kiniou|kiniou]]<br />
}}</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Blender_:_An_Open_3D_Content_Creation_Suite&diff=1140Blender : An Open 3D Content Creation Suite2009-03-24T14:26:00Z<p>Kiniou: New page: {{Workshop |title=Blender : Open 3D Content Creation Suite |when= |where=/tmp/lab |intro=An introduction to modeling and animating 3D, but also scripting. |by=kiniou }}</p>
<hr />
<div>{{Workshop<br />
|title=Blender : Open 3D Content Creation Suite<br />
|when=<br />
|where=/tmp/lab<br />
|intro=An introduction to modeling and animating 3D, but also scripting.<br />
|by=[[User:Kiniou|kiniou]]<br />
}}</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Workshops&diff=1139Workshops2009-03-24T14:22:43Z<p>Kiniou: /* Wanted Workshops */</p>
<hr />
<div>Here are the Workshops happening @ /tmp/lab<br />
<br />
== Workshops Schedule ==<br />
* 26/03/2009 - [[Présentation Livecoding]]<br />
* 27/03/2009 ou 28/03/2009 - [[FPGA: la suite]]<br />
* 28/03/2009 - [[Workshop SuperCollider pour le livecode]]<br />
* 04/04/2009 - [[Workshop OpenWrt]]<br />
<br />
== Wanted Workshops ==<br />
So, you want to give or take a workshop, but it's not scheduled yet? Open a page for it :)<br />
<br />
* [[Awesome Window Manager]]<br />
* [[Ruby for beginners]]<br />
* [[Ruby On Rails]]<br />
* [[Linux Virtualization]] (KVM, Linux-Vserver, OpenVZ)<br />
* [[Vacuum tubes]]<br />
* [[puredata]]<br />
* [[Python : Taste the code]]<br />
* [[Blender : An Open 3D Content Creation Suite]]<br />
<br />
== Past Workshops ==<br />
* 19/02/2009 - [[Python for beginners]]<br />
* 26/02/2009 - [[DIY audio]]<br />
* 12/03/2009 - [[La soudure pour les nuls]]<br />
* 20/03/2009 - [[DIY audio 2]] la suite!<br />
* 21/03/2009 - [[Workshop Introduction aux FPGA]]<br />
<br />
== Adding a Workshop ==<br />
Anybody can create a workshop, this is auto-organization.<br />
<br />
# Create a new page on the wiki prefixed with your workshop's keyword, such as "MediaWiki : Why It Doesn't Suck That Much"<br />
## Use the [[Template:Workshop]] :)<br />
## Make sure you add an Attendees section before saving, so that nobody will edit the template itself!<br />
# Add your workshop link on this page with its date<br />
# Add a link in /tmp/lab shared calendar on G00gle Gr0ups<br />
# Announce it on the /tmp/lab mailing list<br />
# Announce it on the #frlab IRC channel and optionnally add it to the topic if it's the next workshop.<br />
# If your workshop involve handling of chemical products, check [http://www.inchem.org/ IPCS (International Programme on Chemical Safety)] for proper handling/disposal instructions</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Awesome_Window_Manager&diff=1105Awesome Window Manager2009-03-19T15:34:08Z<p>Kiniou: /* Participants */</p>
<hr />
<div>{{Workshop<br />
|title=Awesome Window Manager<br />
|when=Not Scheduled Yet<br />
|where=/tmp/lab<br />
|intro=Discover a light and original WM for GNU/Linux, written in Lua by a French Guy (and others)<br />
|by=[[User:Hellekin|hellekin]]<br />
}}<br />
<br />
http://awesome.naquadah.org/<br />
<br />
== Participants ==<br />
<br />
* Merci d'ajouter votre <nowiki>[[User:UserName|nickname]]</nowiki> dans la liste si vous souhaitez participer.<br />
<br />
* [[User:Kiniou|Kiniou]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DIY_audio_2&diff=1030DIY audio 22009-03-11T17:28:26Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>DIY Audio 2 : <br />
<br />
Jeudi 19 Mars à 19H30, Tmplab.<br />
<br />
Nous avons réalisé (c'est à dire insolé, révélé et gravé au perchlorure de fer) le 26 Février dernier, la carte d'un circuit électronique d'une pédale d'effet Octave up fuzz et commencé à implanter les premiers composants.<br />
<br />
Il nous reste à terminer cette implantation et surtout le plus palpitant, à réaliser le câblage du boîtier comprenant l'entrée jack et la sortie jack ainsi que le "bypass" de l'effet et enfin à tester les sonorités qui en résultent!!<br />
<br />
N'oubliez pas votre montage!!<br />
<br />
Et si possible, apporter :<br />
<br />
un fer à souder et de l'étain<br />
<br />
un boîtier pour y installer votre montage<br />
<br />
une pince dénude-fil<br />
<br />
une pince coupante<br />
<br />
un multimètre<br />
<br />
une mini-perceuse<br />
<br />
et du fil.<br />
<br />
Au plaisir de vous y retrouver!<br />
<br />
Urs.<br />
<br />
== Inscrits/Attendees ==<br />
<br />
* Animator : [[Ursula]]<br />
* Lekernel<br />
* [[User:Kiniou|Kiniou]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=OpenWrt_:_une_introduction&diff=1026OpenWrt : une introduction2009-03-10T16:09:24Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>== Workshop OpenWrt ==<br />
<br />
[[Image:Openwrt-logo.png|right]] Samedi 4 avril 2009 au /tmp/lab ; de 14h30 à 20h30.<br />
<br />
Voici les différents points qui seront abordés:<br />
Sur OpenWrt :<br />
<br />
* de comprendre la structure générale d'OpenWrt<br />
* de construire votre propre image du firmware pour votre cible matérielle<br />
* de porter un logiciel de votre choix et de le tester<br />
* de le flasher depuis le firmware original ou depuis une ancienne version <br />
d'OpenWrt<br />
<br />
Sur le Wi-Fi :<br />
<br />
* de faire un petit rappel sur les différents modes de fonctionnement <br />
possibles : Master, Managed, Mesh, Ad-hoc, Monitor<br />
* de tester ces différents modes de fonctionnement (suivant le matériel) et <br />
les configurations correspondantes dans OpenWrt<br />
<br />
Sur les protocoles de routage :<br />
<br />
* quelques réseaux de tests simples utilisants OLSR, 802.11s et Babel.<br />
<br />
== Connaissances nécessaires ==<br />
Ce workshop s'addresse principalement aux débutants. Il est cependant recommandé de savoir :<br />
* utiliser les commandes de base du shell Linux (cd, ls, rm...).<br />
* d'être familier avec la configuration d'une carte Wi-Fi sous Linux<br />
<br />
== Inscrits/Attendees ==<br />
* Animator : [[User:Florian|Florian]]<br />
* Animator : [[User:Nico|Nico]]<br />
* [[User:Phil|Philpraxis]]<br />
* [[User:Loloster|Loloster]]<br />
* [[User:Kiniou|Kiniou]]<br />
<br />
Merci de vous inscrire ici afin d'avoir une estimation du nombre de participants. Vous pouvez aussi envoyer un mail à florian at openwrt.org et nico at openwrt.org<br />
<br />
== Recommandé ==<br />
* Amener votre laptop<br />
* Installer les outils de de développement preréquis par OpenWrt (build-essential, flex, bison ...)<br />
* Votre équipement à flasher<br />
* Des adaptateurs USB série et des convertisseurs TTL (3.3V - 12V)<br />
<br />
== Equipements ==<br />
Dispo :<br />
* 3 cartes Compex WP54G-WRT (3 Florian)<br />
* 3 Linksys WRT54GS (2 Florian + 1 Nico)<br />
* 1 Linksys WRT54G (1 Nico)<br />
* 1 Atmel AVR32 ATNGW100 (1 Nico)<br />
* 1 Fonera2 (1 Nico)<br />
* 1 Ubiquiti LiteStation2 (1 Nico)<br />
* 1 Belkin F5D8231-4 v2 (1 Nico)<br />
<br />
<br />
Wanted :<br />
* Vidéoprojecteur.<br />
<br />
[[Category:Workshop]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=FPGA_:_une_introduction&diff=961FPGA : une introduction2009-03-02T16:35:42Z<p>Kiniou: /* Equipement */</p>
<hr />
<div>== Workshop FPGA ==<br />
<br />
[[Image:180px-Fpga_xilinx_spartan.jpg|right]] Samedi 21 mars 2009 au /tmp/lab ; de 14h30 à 23h30.<br />
<br />
Voici les différents points qui seront abordés:<br />
# Présentation de la technologie [http://fr.wikipedia.org/wiki/FPGA FPGA]<br />
# Exemples de projets<br />
# Bases des circuits logiques synchrones<br />
# Hands-on: implémentation d'un générateur sonore simple (du style http://www.fpga4fun.com/MusicBox.html)<br />
# S'il reste du temps: introduction à Verilog<br />
# Implémentation du générateur sonore en utilisant Verilog<br />
<br />
== Connaissances nécessaires ==<br />
Ce workshop s'addresse principalement aux débutants. Il est cependant recommandé de savoir :<br />
* utiliser les commandes de base du shell Linux (cd, ls, rm...).<br />
* compter en binaire (addition et multiplication). Pour les personnes qui prennent peur : cela se fait exactement comme en base 10 (en posant l'opération !), et il y aura quelques rappels au début du workshop.<br />
* des bases de programmation sur ordinateur (ou mieux, sur microcontroleur/Arduino) sont utiles mais pas nécessaires.<br />
<br />
== Inscrits/Attendees ==<br />
* Animator : [[User:lekernel|lekernel]]<br />
* Philpraxis<br />
* Ladislas<br />
* Louis<br />
* [[User:Hellekin|hellekin]]<br />
* Babydock<br />
* Laurent<br />
* Nico<br />
* [[User:Kiniou|kiniou]]<br />
<br />
Merci de vous inscrire ici afin d'avoir une estimation du nombre de participants. Vous pouvez aussi envoyer un mail à sebastien point bourdeauducq at lekernel point net.<br />
<br />
== Recommandé ==<br />
* Amener votre laptop (et de la bière)<br />
* Installer la dev suite Xilinx ISE Webpack (http://www.xilinx.com/ise/logic_design_prod/webpack.htm)<br />
* Pour Linux 64bit, choisir l'installeur web (le gros bouton download) sinon c'est cuit.<br />
* Attention ! Le zip se décompresse dans le répertoire courant ! Donc mkdir webpack; cd webpack; unzip ../10.1_Webinstall.zip<br />
* Notez bien le numéro d'enregistrement inscrit sur la page de download :)<br />
* Lancer l'installeur en root: sudo ./setup (l'installation se fait dans /opt/)<br />
* Optionnel (pour Verilog): Installer GTKwave, Icarus Verilog et GPL Cver, inclus dans les BSD et les bonnes distrib Linux<br />
<br />
== Equipement ==<br />
Dispo :<br />
* Une carte ML401 (http://www.xilinx.com/products/devkits/HW-V4-ML401-UNI-G.htm) pour les démonstrations<br />
* Un Spartan 3E Sample Pack (http://www.xilinx.com/products/boards/s3esamplepack/files/S3Euserguide.pdf) pour les essais des participants<br />
* Un câble JTAG (2 si je retrouve mon câble parallèle)<br />
* Il y aura peut être d'autres cartes mais ce n'est pas garanti. Si vous voulez être sûr de pouvoir participer, venez avec votre matériel.<br />
<br />
Wanted :<br />
* Vidéoprojecteur.<br />
* Cartes de développement FPGA et câbles JTAG compatibles (seuls les câbles Xilinx semblent utilisables).<br />
* Petits haut-parleurs (HP seuls) ou prises Jack pour casques (femelles), et résistances 220 Ohm non CMS.<br />
* Barrettes HE10.<br />
<br />
Cartes recommandées pour débuter :<br />
* Spartan 3E Sample Pack (?) : http://www.nuhorizons.com/products/xilinx/spartan3e/samplepack.html / Câble JTAG nécessaire<br />
* Spartan 3E Starter Kit ($149) : http://www.xilinx.com/products/devkits/HW-SPAR3E-SK-US-G.htm / Câble JTAG non nécessaire<br />
* Spartan 3A Starter Kit ($189) : http://www.xilinx.com/products/devkits/HW-SPAR3A-SK-UNI-G.htm / Câble JTAG inclus<br />
* Spartan 3A Evaluation Kit ($49) with PSoC : http://www.em.avnet.com/spartan3a-evl / Câble JTAG non nécessaire<br />
<br />
Ceux qui veulent acheter un kit mettent leur nom ici pour faire éventuellement un achat groupé, avec le modèle de kit voulu:<br />
* Philpraxis: Spartan 3A Evaluation Kit ($49)<br />
* babydock: Spartan 3A Evaluation Kit ($49)<br />
* Laurent: Spartan 3A Evaluation Kit ($49)<br />
* Ladislas: Spartan 3A Evaluation Kit ($49)<br />
* Louis: Spartan 3A Evaluation Kit ($49) <br />
* Manu: Spartan 3A Evaluation Kit ($49) <br />
* Pierre-Alain: Spartan 3A Evaluation Kit ($49) <br />
* Nico: Spartan 3A Evaluation Kit ($49) <br />
* Kiniou : Spartan 3A Evaluation Kit ($49) <br />
<br />
[[Category:Workshop]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=FPGA_:_une_introduction&diff=960FPGA : une introduction2009-03-02T16:32:22Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>== Workshop FPGA ==<br />
<br />
[[Image:180px-Fpga_xilinx_spartan.jpg|right]] Samedi 21 mars 2009 au /tmp/lab ; de 14h30 à 23h30.<br />
<br />
Voici les différents points qui seront abordés:<br />
# Présentation de la technologie [http://fr.wikipedia.org/wiki/FPGA FPGA]<br />
# Exemples de projets<br />
# Bases des circuits logiques synchrones<br />
# Hands-on: implémentation d'un générateur sonore simple (du style http://www.fpga4fun.com/MusicBox.html)<br />
# S'il reste du temps: introduction à Verilog<br />
# Implémentation du générateur sonore en utilisant Verilog<br />
<br />
== Connaissances nécessaires ==<br />
Ce workshop s'addresse principalement aux débutants. Il est cependant recommandé de savoir :<br />
* utiliser les commandes de base du shell Linux (cd, ls, rm...).<br />
* compter en binaire (addition et multiplication). Pour les personnes qui prennent peur : cela se fait exactement comme en base 10 (en posant l'opération !), et il y aura quelques rappels au début du workshop.<br />
* des bases de programmation sur ordinateur (ou mieux, sur microcontroleur/Arduino) sont utiles mais pas nécessaires.<br />
<br />
== Inscrits/Attendees ==<br />
* Animator : [[User:lekernel|lekernel]]<br />
* Philpraxis<br />
* Ladislas<br />
* Louis<br />
* [[User:Hellekin|hellekin]]<br />
* Babydock<br />
* Laurent<br />
* Nico<br />
* [[User:Kiniou|kiniou]]<br />
<br />
Merci de vous inscrire ici afin d'avoir une estimation du nombre de participants. Vous pouvez aussi envoyer un mail à sebastien point bourdeauducq at lekernel point net.<br />
<br />
== Recommandé ==<br />
* Amener votre laptop (et de la bière)<br />
* Installer la dev suite Xilinx ISE Webpack (http://www.xilinx.com/ise/logic_design_prod/webpack.htm)<br />
* Pour Linux 64bit, choisir l'installeur web (le gros bouton download) sinon c'est cuit.<br />
* Attention ! Le zip se décompresse dans le répertoire courant ! Donc mkdir webpack; cd webpack; unzip ../10.1_Webinstall.zip<br />
* Notez bien le numéro d'enregistrement inscrit sur la page de download :)<br />
* Lancer l'installeur en root: sudo ./setup (l'installation se fait dans /opt/)<br />
* Optionnel (pour Verilog): Installer GTKwave, Icarus Verilog et GPL Cver, inclus dans les BSD et les bonnes distrib Linux<br />
<br />
== Equipement ==<br />
Dispo :<br />
* Une carte ML401 (http://www.xilinx.com/products/devkits/HW-V4-ML401-UNI-G.htm) pour les démonstrations<br />
* Un Spartan 3E Sample Pack (http://www.xilinx.com/products/boards/s3esamplepack/files/S3Euserguide.pdf) pour les essais des participants<br />
* Un câble JTAG (2 si je retrouve mon câble parallèle)<br />
* Il y aura peut être d'autres cartes mais ce n'est pas garanti. Si vous voulez être sûr de pouvoir participer, venez avec votre matériel.<br />
<br />
Wanted :<br />
* Vidéoprojecteur.<br />
* Cartes de développement FPGA et câbles JTAG compatibles (seuls les câbles Xilinx semblent utilisables).<br />
* Petits haut-parleurs (HP seuls) ou prises Jack pour casques (femelles), et résistances 220 Ohm non CMS.<br />
* Barrettes HE10.<br />
<br />
Cartes recommandées pour débuter :<br />
* Spartan 3E Sample Pack (?) : http://www.nuhorizons.com/products/xilinx/spartan3e/samplepack.html / Câble JTAG nécessaire<br />
* Spartan 3E Starter Kit ($149) : http://www.xilinx.com/products/devkits/HW-SPAR3E-SK-US-G.htm / Câble JTAG non nécessaire<br />
* Spartan 3A Starter Kit ($189) : http://www.xilinx.com/products/devkits/HW-SPAR3A-SK-UNI-G.htm / Câble JTAG inclus<br />
* Spartan 3A Evaluation Kit ($49) with PSoC : http://www.em.avnet.com/spartan3a-evl / Câble JTAG non nécessaire<br />
<br />
Ceux qui veulent achter un kit mettent leur nom ici pour faire eventuellement un achat groupé, avec le modèle de kit voulu:<br />
* Philpraxis: Spartan 3A Evaluation Kit ($49)<br />
* babydock: Spartan 3A Evaluation Kit ($49)<br />
* Laurent: Spartan 3A Evaluation Kit ($49)<br />
* Ladislas: Spartan 3A Evaluation Kit ($49)<br />
* Louis: Spartan 3A Evaluation Kit ($49) <br />
* Manu: Spartan 3A Evaluation Kit ($49) <br />
* Pierre-Alain: Spartan 3A Evaluation Kit ($49) <br />
* Nico: Spartan 3A Evaluation Kit ($49) <br />
<br />
[[Category:Workshop]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=DIY_audio&diff=833DIY audio2009-02-24T19:40:35Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>DIY Audio :<br />
<br />
Réalisation d'un schéma électronique simple: pédale d'effet Octave up fuzz ou pédale disto.<br />
<br />
Si possible, apporter :<br />
* un fer à souder et de l'étain<br />
* une plaque de cuivre<br />
* une pince coupante<br />
* un multimètre<br />
* mini-perceuse<br />
* du fil<br />
<br />
Merci de vous inscrire ci-dessous pour que je puisse prévoir les composants... (coût environ 12 euros par personne)<br />
<br />
== Inscrits/Attendees ==<br />
<br />
* Animator : [[Ursula]]<br />
* louis<br />
* Ladislas<br />
* [[User:Hellekin|hellekin]]<br />
* Ced23<br />
* Atrus<br />
* [[User:Kiniou|Kiniou]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_for_beginners&diff=761Python for beginners2009-02-20T01:18:27Z<p>Kiniou: /* Workshop Python */</p>
<hr />
<div>== Workshop Python ==<br />
<br />
Voici les différents points qui seront abordés:<br />
#Qu'est ce que Python ''(origine, applications...)''<br />
#Comment utiliser l'interpréteur ''(ou comment exécuter du code Python)''<br />
#Petite introduction ''(les bases du Python)''<br />
#Les contrôles de flux ''(d'autres bases...)''<br />
#Les entrées/sorties ''(lire ou écrire dans un fichier, afficher du texte sur un écran)''<br />
#Les structures de données ''(tableaux,dictionnaires,)''<br />
#Les modules/librairies<br />
#La gestion des erreurs<br />
#MyFirstPythonScript<br />
<br />
Note : La version de python couverte par ce workshop sera la '''2.5.2''' car c'est la dernière (en moyenne) supporté par beaucoup de distribs linux, Mac et Windows<br />
<br />
<br />
[http://www.tmplab.org/wiki/images/a/ae/Workshop_python_for_beginners.odp Présentation OpenOffice du workshop]<br />
<br />
== Inscrits/Attendees ==<br />
Animator : [[User:Kiniou|Kiniou]]<br />
* Alexandre Korber<br />
* PhilPraxis<br />
* Nico<br />
* taziden<br />
* Ursula<br />
<br />
== Equipment ==<br />
* Ursula will bring a Videoprojector.<br />
* Optional : a laptop with python installed</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=File:Workshop_python_for_beginners.odp&diff=758File:Workshop python for beginners.odp2009-02-20T01:09:26Z<p>Kiniou: </p>
<hr />
<div></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Soudure_pour_les_nuls&diff=743Soudure pour les nuls2009-02-18T17:32:04Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>== Workshop La soudure pour les nuls ==<br />
Initiation à la soudure pour la petite électronique.<br />
<br />
Le 12 mars 2009, au tmplab de Vitry, de 20h à 23h.<br />
<br />
* matériel: quel matériel pour quel usage ? Présentation du matériel de base. Tour d'horizon des gadgets utiles.<br />
* préparer une session de soudure. Lire un schéma, gribouiller un schéma.<br />
* processus: comment la soudure fonctionne ? Pourquoi celle du voisin est mieux ?<br />
* et pratique: applications courantes: 7-8 montages simples<br />
<br />
== Matériel à apporter ==<br />
Si vous avez, apportez donc, en plusieurs exemplaires si possible :<br />
* un fer à souder et de l'étain<br />
* un bout de circuit imprimé cassé<br />
* une troisième main (genre de pinces orientables avec une loupe)<br />
* une pincette<br />
* une petite pince coupante<br />
* des piles<br />
* un multimètre<br />
* tout ce qui vous semble utile à priori pour l'atelier<br />
<br />
== Inscrits/Attendees ==<br />
<br />
* Charlot (dirlo)<br />
* PhilPraxis<br />
* pascale<br />
* [[User:Kiniou|Kiniou]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_for_beginners&diff=742Python for beginners2009-02-18T17:30:13Z<p>Kiniou: /* Inscrits/Attendees */</p>
<hr />
<div>== Workshop Python ==<br />
<br />
Voici les différents points qui seront abordés:<br />
#Qu'est ce que Python ''(origine, applications...)''<br />
#Comment utiliser l'interpréteur ''(ou comment exécuter du code Python)''<br />
#Petite introduction ''(les bases du Python)''<br />
#Les contrôles de flux ''(d'autres bases...)''<br />
#Les entrées/sorties ''(lire ou écrire dans un fichier, afficher du texte sur un écran)''<br />
#Les structures de données ''(tableaux,dictionnaires,)''<br />
#Les modules/librairies<br />
#La gestion des erreurs<br />
#MyFirstPythonScript<br />
<br />
Note : La version de python couverte par ce workshop sera la '''2.5.2''' car c'est la dernière (en moyenne) supporté par beaucoup de distribs linux, Mac et Windows<br />
<br />
== Inscrits/Attendees ==<br />
Animator : [[User:Kiniou|Kiniou]]<br />
* Alexandre Korber<br />
* PhilPraxis<br />
* Nico<br />
* taziden<br />
<br />
== Equipment ==<br />
* Ursula will bring a Videoprojector.<br />
* Optional : a laptop with python installed</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_for_beginners&diff=741Python for beginners2009-02-18T17:24:51Z<p>Kiniou: /* Equipment */</p>
<hr />
<div>== Workshop Python ==<br />
<br />
Voici les différents points qui seront abordés:<br />
#Qu'est ce que Python ''(origine, applications...)''<br />
#Comment utiliser l'interpréteur ''(ou comment exécuter du code Python)''<br />
#Petite introduction ''(les bases du Python)''<br />
#Les contrôles de flux ''(d'autres bases...)''<br />
#Les entrées/sorties ''(lire ou écrire dans un fichier, afficher du texte sur un écran)''<br />
#Les structures de données ''(tableaux,dictionnaires,)''<br />
#Les modules/librairies<br />
#La gestion des erreurs<br />
#MyFirstPythonScript<br />
<br />
Note : La version de python couverte par ce workshop sera la '''2.5.2''' car c'est la dernière (en moyenne) supporté par beaucoup de distribs linux, Mac et Windows<br />
<br />
== Inscrits/Attendees ==<br />
<br />
* Alexandre Korber<br />
* PhilPraxis<br />
* Nico<br />
* taziden<br />
<br />
== Equipment ==<br />
* Ursula will bring a Videoprojector.<br />
* Optional : a laptop with python installed</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_for_beginners&diff=740Python for beginners2009-02-18T17:22:28Z<p>Kiniou: /* Workshop Python */</p>
<hr />
<div>== Workshop Python ==<br />
<br />
Voici les différents points qui seront abordés:<br />
#Qu'est ce que Python ''(origine, applications...)''<br />
#Comment utiliser l'interpréteur ''(ou comment exécuter du code Python)''<br />
#Petite introduction ''(les bases du Python)''<br />
#Les contrôles de flux ''(d'autres bases...)''<br />
#Les entrées/sorties ''(lire ou écrire dans un fichier, afficher du texte sur un écran)''<br />
#Les structures de données ''(tableaux,dictionnaires,)''<br />
#Les modules/librairies<br />
#La gestion des erreurs<br />
#MyFirstPythonScript<br />
<br />
Note : La version de python couverte par ce workshop sera la '''2.5.2''' car c'est la dernière (en moyenne) supporté par beaucoup de distribs linux, Mac et Windows<br />
<br />
== Inscrits/Attendees ==<br />
<br />
* Alexandre Korber<br />
* PhilPraxis<br />
* Nico<br />
* taziden<br />
<br />
== Equipment ==<br />
* Ursula will bring a Videoprojector.</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=739User:Kiniou2009-02-18T14:42:31Z<p>Kiniou: </p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|95px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou AT gmail POINT com</tt><br /><br />
<tt>Location : [http://maps.google.fr/maps?f=q&source=s_q&hl=fr&geocode=&q=LES+LILAS&sll=47.15984,2.988281&sspn=20.154282,39.550781&ie=UTF8&z=14&iwloc=addr Les Lilas (93) - France]</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=738User:Kiniou2009-02-18T14:42:03Z<p>Kiniou: </p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|75px]]<br />
<p><br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Contact : kiniou AT gmail POINT com</tt><br /><br />
<tt>Location : [http://maps.google.fr/maps?f=q&source=s_q&hl=fr&geocode=&q=LES+LILAS&sll=47.15984,2.988281&sspn=20.154282,39.550781&ie=UTF8&z=14&iwloc=addr Les Lilas (93) - France]</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /><br />
</p></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Python_for_beginners&diff=710Python for beginners2009-02-17T16:54:33Z<p>Kiniou: New page: == Workshop Python == ''<Description here>'' == Inscrits/Attendees ==</p>
<hr />
<div>== Workshop Python ==<br />
''<Description here>''<br />
<br />
<br />
== Inscrits/Attendees ==</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Workshops&diff=709Workshops2009-02-17T16:50:39Z<p>Kiniou: New page: == Workshops Schedule == * 19/02/2009 - Python for beginners</p>
<hr />
<div>== Workshops Schedule ==<br />
* 19/02/2009 - [[Python for beginners]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=Main_Page&diff=708Main Page2009-02-17T16:45:31Z<p>Kiniou: /* Living */</p>
<hr />
<div>This is the Wiki from /tmp/lab. You can freely edit this, you just need to register and validate your account with your email address to prevent spam. Thanks!<br />
<br />
= Intro =<br />
* [http://www.tmplab.org/about/ About /tmp/lab & FAQ]<br />
* [http://www.tmplab.org/contact/ Coming to /tmp/lab & contact information]<br />
* [http://www.tmplab.org/ Blog & news]<br />
* /tmp/lab is located near a [http://ec.europa.eu/environment/seveso/index.htm Seveso] classified pharmaceutical plant ([http://www.portalanglais.com/article.php3?id_article=132 lire l'article en français])<br />
* [http://irc.netsplit.de/webchat/?net=freenode&room=%23frlab&nick=tmplab Chat (IRC) on the web]<br />
* [[A little history of /tmp/lab]]<br />
<br />
= Living =<br />
* [http://www.tmplab.org/wiki/index.php//tmp/lab_How_To How To]<br />
* [[Borrowed things]]<br />
* [[KineKlub]]<br />
* [[Conferences]]<br />
* [[Workshops]]<br />
<br />
= Projects =<br />
* <STRIKE>[[Ecole Bleue]] design project</STRIKE><br />
* [[OLPC France]]<br />
** [[OLPC Emulation]]<br />
** [[Backtrack3 on EEE]]<br />
** [[OLPC Live]]<br />
** [[Sugar Xubuntu on EEE]]<br />
** [[FlashEEE]]<br />
* [[Hacker Space Fest]]<br />
** [[HSF Organization]]<br />
** [[HSF Task List]]<br />
** [[HSF Spaces]]<br />
* [[Toxic Gas Sensor]]<br />
* [[/tmp/van]]<br />
* [[Chip Reverse Engineering]]<br />
* [[FreeTvPerso video relay]]<br />
* [[Domoverse platform]]<br />
* [http://dev.tmplab.org/wiki/tmp-usine /tmp/usine: RepRap @ /tmp/lab]<br />
* [[Freedom Not Fear]]<br />
* [[Math Playground]]<br />
<br />
= Documentation =<br />
<br />
* [[MediaWikiLinks]]<br />
* [[Information Design]]<br />
* [[GIT Cheat Sheet]]<br />
* [[BackTrack]]<br />
* [[RFID]]<br />
* [[Pure Data]]<br />
* [[Mobile Phone Chargers]]<br />
* [[Ruby on Rails]]</div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=User:Kiniou&diff=707User:Kiniou2009-02-17T14:31:32Z<p>Kiniou: New page: 75px <tt>RealName : Kevin Roy</tt><br /> <tt>Location : [http://maps.google.fr/maps?f=q&source=s_q&hl=fr&geocode=&q=LES+LILAS&sll=47.15984,2.988281&ssp...</p>
<hr />
<div>[[Image:Eye-kno.png|left|frameless|75px]]<br />
<tt>RealName : Kevin Roy</tt><br /><br />
<tt>Location : [http://maps.google.fr/maps?f=q&source=s_q&hl=fr&geocode=&q=LES+LILAS&sll=47.15984,2.988281&sspn=20.154282,39.550781&ie=UTF8&z=14&iwloc=addr Les Lilas (93) - France]</tt><br /><br />
<tt>Website : [http://blog.knokorpo.fr Personnal Weblog], [http://dev.knokorpo.fr Personnal Dev Repository]</tt><br /><br />
<tt>Profile : 3D Coder, Python Coder, NintendoDS Hacker, Blender Lover</tt><br /></div>Kiniouhttps://www.tmplab.org/wiki/index.php?title=File:Eye-kno.png&diff=706File:Eye-kno.png2009-02-17T13:48:57Z<p>Kiniou: </p>
<hr />
<div></div>Kiniou