Fixme.ch - User contributions [en]

DVPWM

2014-10-31T07:12:45Z

Petaflot: photos

[[File:Dvpwm photo top.jpg|200px|thumb|right|Top view, yes it's small]]
[[File:Dvpwm photo bottom.jpg|200px|thumb|right|Bottom view]]

DVPWM is a PWM driver/dimmer originally designed for very simple LED lighting. It is built to be small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, the circuitry is completely offline.

* '''Input''': 6-15 VDC. With input voltage polarity inversion protection, suitable for dirty or noisy power supplies
* '''Output''': "high" frequency [? kHz] PWM with duty cycle ranging from almost zero to almost 100%
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors because there is a beefy free wheel diode protection.
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common VCC''')

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain [I may have a relationship with Homer Simpson, who is actually my idol -[[User:Jhu]]]

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to an absolute minimum [zero !!!]. The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

File:Dvpwm photo top.jpg

2014-10-31T07:08:43Z

Petaflot:

File:Dvpwm photo bottom.jpg

2014-10-31T07:08:02Z

Petaflot:

DVPWM

2014-10-29T18:03:10Z

Petaflot: oops

DVPWM is a PWM driver/dimmer originally designed for very simple LED lighting. It is built to be small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, the circuitry is completely offline.

* '''Input''': 6-15 VDC. With input voltage polarity inversion protection, suitable for dirty or noisy power supplies
* '''Output''': "high" frequency [? kHz] PWM with duty cycle ranging from almost zero to almost 100%
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors because there is a beefy free wheel diode protection.
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common VCC''')

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain [I may have a relationship with Homer Simpson, who is actually my idol -Jo]

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to an absolute minimum [zero !!!]. The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

DVPWM

2014-10-23T13:17:26Z

Petaflot: merge commentaires Jo

DVPWM is a PWM driver/dimmer originally designed for very simple LED lighting. It is built to be small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, the circuitry is completely offline.

* '''Input''': 6-15 VDC. With input voltage polarity inversion protection, suitable for dirty or noisy power supplies
* '''Output''': "high" frequency [? kHz] PWM with duty cycle ranging from almost zero to almost 100%
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors because there is a beefy free wheel diode protection.
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common ground''')

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain [I may have a relationship with Homer Simpson, who is actually my idol -Jo]

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to an absolute minimum [zero !!!]. The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

Resources

2014-10-23T10:38:33Z

Petaflot: /* PCB Fabrication */ Eurocircuits

A list of local (Romandie, Switzerland) and international ressources.

=Local Ressources in Switzerland=
== Events ==
* [http://zigobot.ch/concour.html PicStar workshop] on alternate Thursdays, 19h-21h
* [http://2012.rmll.info/ RMLL 2012] in Geneva
* [http://liftconference.com/ LIFT Conférences]
* [http://www.espace-des-inventions.ch/index.php/activitee/club-des-petits-inventeurs Club des petits inventeurs]
* [http://www.node-rdv.ch/ Node, rendez-vous des curiosités sonores]
* [https://tech.ebu.ch/events/drs2013/radiohack2013 RadioHack 2013]
* [http://gwenstival.com Gwenstival] (radio, ...)
* [http://librelist.com/browser/cryptoch/ CryptoCH]: Cryptoparties in Switzerland
* [http://lemanmake.com/ Leman Make] (Maker Fair in Arc lémanique)
* [http://nipconf.com/ NipConf] (innovation)

=== Robotique ===
* [http://www.fribot.org/ Fribot]: Autonomous robot contest in Lego Mindstorm
* [http://festivalrobotique.epfl.ch/ Festival Robotique EPFL]
* [https://aseba.wikidot.com/fr:thymiorobotsenclasse Robots en Classe] (formation à la robotique pour les enseignants)

=== Sécurité ===
* http://dahucon.ch // https://twitter.com/DahuCon
* [http://insomnihack.ch Insomni'Hack]
* [http://www.bimo.ch/fr/Jura-Security-Days/Jurackerfestch.html JurackerFest]
* [http://www.isc2chapter-switzerland.ch/index.php/events ISC² Chapter Switzerland]

== Associations/Foundations ==
=== Electronic/Hardware/Robotic ===
* [http://microclub.ch/ MicroClub]
* [http://site.cvra.ch/ Club Vaudois de Robotique Autonome (Renens)]
* [http://robopoly.epfl.ch/ Robotpoly] [http://wiki.robopoly.ch/w/Main_Page wiki]
* [http://lara.heig-vd.ch/robot-ch/home.php Robot-CH (Association Suisse pour la Promotion de la Robotique)]
* [http://www.mobsya.org/ Mobsya]
* [http://bricobot.ch/ Bricobot], Club de robotique pour les débutants (12-16ans)
* [http://www.ader.ch/ ADER] (énergie renouvellable)
* [http://www.creative-studio.ch CreativeStudio] (atelier/cours de robotique)
* [http://roberta.epfl.ch/ Promotion de la robotique à l'EPFL (bureau de l'égalité des chances)]
* [http://www.brainybiz.com/ BrainyBiz] (internet of things/domotique)
* [http://www.swissraspberry.ch Swiss Raspberry UG] (and Wiki)
* [https://abcm.ch/ Les Amis du Musée Bolo] (old school hardware)
* [http://www.nccr-robotics.ch/ NCCR Robotics] (Swiss National Centre of Compentence in Research)

=== Radio amateurs (RF, wifi, électronique) ===
* http://www.radioamateur.ch/
*[http://www.iapc.ch/ International Amateur Packet Club (IAPC)] (Genève)
*http://www.hb9mm.com/ (Vaud)
*http://www.hb9g.ch/ (Radio club Genève)
*http://home.swissatv.ch/ (http://hb9tv.ch/, Transmissions de télévision radioamateur, exemple avec http://www.hb9ibc.org/ )
*http://www.hb9xc.ch/ (Moutier et région)
*http://hb9lc.cq-dx.org/ (Montagnes neuchâteloises)
*http://www.hb9fg.ch/ (Fribourg)
*http://www.hb9ww.org/ (Neuchâtel)
*http://www.hb9y.ch/ (Valais)

=== OpenSource ===
* [http://linux-gull.ch GULL]
* [http://swisslinux.org SwissLinux]
* [http://free-it-foundation.org/ Free IT Foundation]
* [http://www.opensourcecommunity.ch/ Fribourg Open-Source Community (FROSC)]
* [http://gnugeneration.epfl.ch/ GNU Generation (EPFL)]

=== Hackerspaces ===
* Hackerspaces in CH: [http://hackerspaces.ch/] [http://hackerspaces.org/wiki/Switzerland]
* [http://www.posttenebraslab.ch/ Post Tenebras Lab (PTL) Genève]
* [http://www.hackburg.ch/ Hackburg Fribourg]
* [http://www.ccczh.ch/ CCCZH]
* [http://www.chaostreff.ch/ Chaostreff Basel]
* [http://computerlabor.kire.ch/ Computerlabor@KuZeB]
* [http://www.coredump.ch/ Coredump]
* [http://www.dock18.ch/ Dock18]
* [http://www.eastermundigen.ch/ Eastermundigen]
* [http://www.laborluzern.org/ LABOR Luzern]
* [http://www.mechatronicart.ch/ MechArtLab]
* [http://odenwilusenz.ch/ Odenwilusenz]
* [http://www.projektlabor.ch/ Projektlabor]
* [https://www.chaostreff.ch/ RAIF HQ]
* [http://ruum42.ch/ Ruum42]
* [http://www.bastli.ch/ Bastli]
* [http://www.starship-factory.ch/ Starship Factory]
* [https://fixme.ch FIXME]

==== Bio DIY ====
* [http://biodesign.cc/category/where/switzerland/ BioDesign] (EPFL collaboration)
* [http://hackteria.org/ Hackteria]
* [http://hackuarium.strikingly.com/ Hackarium] Bio-hackerspace in Renens (at UniverCité)
* [http://www.bioscope.ch/ Bioscope] (UNIGE open bio-lab)

=== Fablab ===
* [http://fablab.ch/official-register-of-fab-labs-in-switzerland/ Fablabs in Switzerland]
* [http://www.fablab-ge.ch/ Fablan Genève]
* [http://fablab-fribourg.ch/ Fablab Fribourg]
* [http://fablab-neuch.ch/ Fablab Neuchatel]
* [http://luzern.fablab.ch/ Fablab Lucerne]
* [http://www.net-village.org/fablab/ Fablab Jura francais]
* [http://fablab-lacote.ch/ Fablab La Côte]
* [http://www.fablab-chene20.ch/ Fablab Renens (Chêne 20)] [https://www.facebook.com/FabLabRenens facebook]

=== Art-Technology ===
* http://www.sinlab.ch/ Collaboration entre la HETSR et l'EPFL (Arts, Architecture, Science, Engineering and Philosophy)
* [http://www.tskz.ch/ TSKZ liaison artiste-techno]
* [http://www.epfl-ecal-lab.ch/ EPFL+ECAL Lab]

=== Divers ===
* [http://www.espace-des-inventions.ch/ Espace des inventions]
* [http://thebootstrap.ch/ The Bootstrap]
* [http://hackepfl.com HackEPFL]
* [http://www.unil.ch/interface/page18617.html L'Eprouvette (ateliers scientifiques) à l'UNIL]
* [http://www.futurekids-romandie.ch/ Futurekids Romandie] (formation des jeunes à la technologie)
* [http://educatec.ch educaTEC] (Formation à la techologie, informatique, robotique)
* [http://www.thinkdata.ch/ ThinkData: Service de sensibilisation à la protection des données et à la transparence]
* [http://www.ot-lab.ch/ Observatoire Technologique (OT-Lab)]
* [http://nearfuturelaboratory.com/ Near Future Lab] (Geneva)
* [http://opendata.admin.ch/ Swiss Open Government Data portal]
* [http://www.isoc.ch/ Internet Society Switzerland Chapter (ISOC)]
* [http://sti-ateliers.epfl.ch/afa Atelier de fabrication additive] at EPFL (3d printing, etc)
* [http://www.unige.ch/fapse/actualites/2014/lundi-video.html Lundis du jeu video]
* [http://univercite.ch/ UniverCité] Espace communautaire (coworking, hackerspaces)

=== Coworking ===
* [http://g-60.net/ G60] (bio-hs, coworking, art, events, ...) (Lausanne)
* [http://num3.ch/ Numéro 3] (Lausanne)
* [http://www.la-muse.ch/coworking/lausanne/ La Muse] (Lausanne)
* [http://eclau.ch/ Eclau] (Lausanne)
* [http://rainbowlab.ch/ Rainbow Lab] (Lausanne)
* [https://www.facebook.com/blablawork.ch BlaBlaWork] (Genève)

== Ecoles/Enseignement ==
* [http://www.cpln.ch/ CPLN]
* [http://www.edurobot.ch/ Edurobot, Ressources pédagogique pour la robotique]
* [http://edutic.ch EduTIC] (informatique pédagogique)
* [http://codeclubch.wordpress.com/ Code Club] (teach children how to program)
* [http://piclass.org/index.fr.html PiClass] Teaching with the raspi in romandie school

== Shops/Companies ==
=== Electronic/Computer ===
* [http://zigobot.ch/ ZigoBot]
* [http://www.didel.com/ Didel SA]
* [http://boxtec.ch Boxtec]
* [http://thinkembedded.ch/ ThinkEmbedded]
* [http://www.dshop.ch/ dshop]
* [http://www.itopie.ch/lesoccasions/ Itopie] (Informatique d'occasion)
* [http://www.labonnecombine.ch/ La bonne combine] (électronique, électroménager, ...)
* [http://www.toppreise.ch/index.php Toppreise] (Trouver les meilleurs prix pour électronique, électroménager, DVD/BD, pneus, vins, bref tout, en suisse.)
* [http://iPhoneCasse.ch/ iPhone Cassé] (Reparation d'iPhone, iPod et iPad en Suisse)
* [http://www.chipandlove.ch/ Chip & love] electronic components
* [http://www.dupertuis.com/ Dupertuis Electronique] (sono, light, dj, eclairage, video, informatique, electronique, ...)
* [http://www.play-zone.ch/ PlayZone] (electronic components, kits, arduino, rpi, ...)

=== 3D Printer ===
* https://swissreprap.com/en
* [http://www.fabberworld.com/ FabberWorld (The Swiss 3D Printing Shop)]
* [http://3dfunlab.com/ 3D funlab] 3d printing/scanning services in Geneva
* [http://www.oblong-boutique.ch/Vos-creations-3D 3d printing]
* [http://shop.deltatower.ch/ DeltaTower]

=== OpenSource/OpenHardware ===
* http://bytecode.ch/
* http://camptocamp.com
* http://whyopencomputing.ch/ (Computers shipped with Ubuntu, with local support)

=== PCB Fabrication ===
* [http://http://eurocircuits.com/ EuroCircuits] good quality at reasonable prices. excellent service and support.
* [http://dirtypcbs.com/ Dirty PCBs] Dirt cheap PCBs with free shipping (from $1.2/5x5 pcb for 10 units)
* [http://imall.iteadstudio.com/open-pcb/pcb-prototyping.html Itead] Slightly more expensive PCBs with shipping extra
* Fritzing - really expensive PCBs

== Association support ==
* http://www.lausanne-usl.ch/ Union des sociétés lausannoises
* http://www.benevolat-vaud.ch/ Aide aux associations, plateforme, ...
* http://www.lebureauculturel.ch/ informations et conseils aux artistes/créateurs
* http://www.article60.com/ Journal des associations romandes (+ annuaire des associations)

= [[International_resources]] =

DVPWM

2014-10-23T10:33:43Z

Petaflot: Created page with "DVPWM is a PWM driver originally designed for very simple LED lighting. It is built to small, robust and convenient. It has one single control: a rotating knob with on/off switc..."

DVPWM is a PWM driver originally designed for very simple LED lighting. It is built to small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, circuitry is completely offline.

* '''Input''': 6-15 VDC. Inversion protected, suitable for dirty or noisy power supplies.
* '''Output''': "high" frequency PWM with duty cycle ranging from almost zero to almost 100%
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors.
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common ground''')

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain.

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to zero. The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

File:DVPWM ComponentsList105.pdf

2014-10-23T08:21:45Z

Petaflot:

File:DVPWM render bottom.png

2014-10-23T08:01:32Z

Petaflot:

File:DVPWM render top.png

2014-10-23T08:01:06Z

Petaflot:

File:DVPWM Schematic.pdf

2014-10-23T08:00:31Z

Petaflot:

3d printer

2014-05-07T12:06:37Z

Petaflot: /* 3D Software */ Nervous System

{| style="width:80%"
| __TOC__
|[[File:Ultimaker2.JPG|650px]]
|}

== Usage ==
# '''Prepare a 3D model to print'''. You can [[#Find model online|find a model online]] with sites such as [http://thingiverse.com Thingiverse], or [[#Make your own|create your own]] in software such as Sketchup or OpenSCAD. You will need to save the model as a .STL file, however .DAE can also be used for direct exports from Sketchup.
# '''Import your model onto the print computer'''. It is easiest if you print using our dedicated print computer (Fixme-SPM) which is located next to the printer. You can import the model by dragging it into the [https://foo.fixme.ch/marcha/ drag and drop service], using a USB key, using IRC, or using a cloud hosting service such as [http://ge.tt/ Ge.tt] or [https://mega.co.nz/# Mega].
# '''Open Cura and open your model(s)'''. Open Cura from the sidebar, and click on the [https://fixme.ch/w/images/d/dd/Cura-load.png Load button]. Select one or more .STL or .DAE files that you would like to print. Please note that prints that reach near the limits of the print volume (21 x 21 x 20.5 cm) will fail.
# '''Configure your desired print parameters'''. The print parameters will depend on what you are printing and the quality that you're looking for. Here are some guidelines:
## '''Layer height''': the Ultimaker can print between 0.1mm and 0.25mm. 0.1mm should only be used for high precision, high detail prints; 0.15mm should be used for normal prints; 0.2-0.25mm should be used for fast prints where you don't mind the quality (e.g. holder, internal component, etc).
## '''Shell thickness''': this value should be a multiple of 0.4mm (the width of the nozzle). With 0.4mm you'll get 1 solid layer, with 0.8mm you'll get 2 solid layers, etc. 0.8mm is fine for most prints.
## '''Enable retraction''': this retracts the filament when the nozzle moves from one area to another whilst not printing. It is best to leave this enabled.
## '''Bottom/top thickness''': the bottom and top thickness of the solid layer. This value should be a multiple of the layer height - a value between 0.2mm and 1mm is best for most prints, with 1mm used for very delicate models.
## '''Fill density''': this is the density of the fill inside your model. Due to an excellent calibration of our Ultimaker, almost all prints will require less than 30% fill. 10% for just structural support, 24% for an average print (after 25% Cura slices your model differently), 30% for a solid print of an average sized object. For objects that require superior structural strength, up to 60% is recommended. 80% can be used for very small complex objects, and 100% is used on a case-by-case basis.
## '''Print speed''': this is the speed at which the Ultimaker will print. 100mm/s is recommended for detailed prints, 120mm/s for average prints, and up to 150mm/s for fast, lower quality prints.
## '''Printing temperature''': we have tested and 235°C works best. Leave it as is.
## '''Support type''': only use for prints with significant overhangs.
## '''Platform adhesion type''': not required for PLA prints.
## '''Diameter''': the diameter of the filament (currently 2.89mm). Do not touch this unless you are changing the filament and have remeasured it (sometimes the value does not match the specification).
## '''Flow''': I have no clue what this does. If it ain't broke, don't touch it.

== 3D models ==
=== Find model online ===
{| class="wikitable"
|-
! Name
! Description
! align="center" | Requires registration?
|-
|[http://repables.com/ Repables]
|Fully open repository backed by non profit
| align="center" style="background:#90EE90;" | No
|-
|[http://www.thingiverse.com/ Thingiverse]
|Largest go to source for 3D models
| align="center" style="background:#90EE90;" | No
|-
|[https://cubehero.com/ Cubehero]
|Open source source based on git
| align="center" style="background:#90EE90;" |No
|-
|[https://www.youmagine.com/ YouMagine]
|New repository for 3D models
| align="center" style="background:#90EE90;" |No
|-
|[http://www.shapeking.com/ Shapeking]
|Excellent alternative to thingiverse
| align="center" style="background:#90EE90;" |No
|-
|[https://thepiratebay.sx/browse/605 The Pirate Bay]
|Torrents of miscellaneous 3D models
| align="center" style="background:#90EE90;" |No
|-
|[http://defcad.com/ Defcad]
|Controversial thingiverse clone
| align="center" style="background:#FFFFE0;" |?
|-
|[http://makerlove.com/ Makerlove]
|3D printed sex toys
| align="center" style="background:#90EE90;" |No
|-
|[http://www.3dcontentcentral.com/Browse.aspx 3DCC]
|Technical models
| align="center" style="background:#FFFFE0;" | ?
|-
|[http://grabcad.com/library GrabCAD]
|Models mostly for CNC and design
| align="center" style="background:#F08080;" | Yes
|-
|[http://www.shapeways.com/3d_parts_database Shapeways]
|Shapeways tested 3D models
| align="center" style="background:#F08080;" |Yes
|-
|[https://www.3dagogo.com/ 3dagogo]
|'Tested' parts 'guaranteed' to print
| align="center" style="background:#FFFFE0;" |?
|-
|[http://3dr.adlnet.gov/ US .gov repository]
|Backed by the NSA
| align="center" style="background:#FFFFE0;" |?
|}

[http://www.yeggi.com/ Yeggi] is a search engine that shows results from several of the sites listed above.

=== Make your own ===
==== 3D Software ====
* [http://www.sketchup.com/ Sketchup] is a free, popular and most importantly, easy to use software which allows for the quick creation of 3D models (requires [http://rhin.crai.archi.fr/rld/plugin_details.php?id=429 su2stl plugin] for STL export/import)
** [ftp://fixme:fixme@ftp.fixme.ch/incoming/SketchUp%202013%20(Mac).dmg Sketchup 2013 Mac]
** [ftp://fixme:fixme@ftp.fixme.ch/incoming/SketchUp%202013%20(Windows).exe Sketchup 2013 Windows]
** [ftp://fixme:fixme@ftp.fixme.ch/incoming/Sketchup%208%20(Wine).zip Sketchup 8 Windows] (This version [http://wiki.winehq.org/Sketchup works with wine])
* [http://openscad.org OpenSCAD] is a script-based 3D editor, which can make use of parameters, conditions, for and while loops, etc... This is currently Petaflot's choice
* [http://www.3dtin.com/ 3DTin] is an online WebGL 3D modeling web-app
* [http://www.netfabb.com/download.php Netfabb] (Linux version)
* http://n-e-r-v-o-u-s.com/cellCycle/ un outil web marant pour designer (puis commander le cas échéant) des bagues, bracelets.. d'autres ressources sur le site.

==== Printing software ====
* https://print.fixme.ch web interface to replace Printrun/Cura (still need Slic3r to create the gcode)
** Currently not connected to the printer and the service is down
** run as unprivlilegied user please sudo su -c /home/francois/OctoPrint/run francois
** Used for the webcam: http://webcam.fixme.ch
* [http://slic3r.org/ Slic3r] and [http://reprap.org/wiki/Printrun Printrun]
** [https://github.com/daid/Cura Cura]
* To check, http://projectsilkworm.com/
* Check STL files for printability: http://cloud.netfabb.com/
* Buy material in switzerland: [[Resources#3D_Printer]]
* There's a dedicated machine to print: spm.fixme.ch

== Printing ==
=== Software Installation ===
* http://daid.github.com/Cura/
* it's the only software worth it
* Yes, you will need PyOpenGL for it to run. Displaying nice 3d images is not that trivial.

* Recommended: Use the dev version on github: https://github.com/daid/Cura.git (12.10 when I'm writing)
* Required packages: wxPython and PyOpenGL.
* You can use a python virtualenv.

=== First use ===
* On first Cura start, you don't need to upgrade to Marlin firmware because it's already done.
* You should run the checks, at least to check if USB connection between PC and the printer is working. For temperature check, the printer need to cool down (to ~30) before heating and check, it can take looong time.
* Now you can use Cura to print objects.

=== Printing ===
'''Maximum length/width: 180mm'''
* Load a .stl model.
* Change orientation, size, etc...
* Check settings on the left (and in the different tabs)
* Click on the Prepare print button.
* Software will slice the object into GCode. The more you choose a large scale object, the longer the execution time is.
* When it done, click on Print button to open the Printing dialog.
* Wait the software connect with the printer, Connection button will turn from clickable to readonly and Print button will turn from readonly to clickable.
* Set the temperature with the arrows (yeah it's not working by putting the number directly)
* Wait a bit so the hot end is distributively warmed
* Extrude before printing, so the wire is at the start of the hot end
* Make sure the wire is extruding correctly (the output wire is regular)
* Click the Print button.

==== Settings ====
* Walls: 0.4 (1 wall) is good
* Print speed: 80mm/s is clean (you may increase temperature for more speed)
* Infill:
** strong material, 80-100%
** Light print, 10-15%
* Temparatures: ~230-240°
* Support type:
** Exterior when there's a big overhang (we made a 10cm overhang without support, but generally it's >1cm)
** None in general
* Raft: needed when there are small pieces at the bottom (so they stick to the bed)
* Experiment !

=== Important points ===
* '''[https://webcam.fixme.ch/ KEEP YOUR EYES] ON THE PRINTER THROUGHOUT THE PRINTING PROCESS!!!''' And clean what could interfere with the printing.
* BE carefull with the end stops, [http://www.youtube.com/watch_popup?feature=player_embedded&v=IYXnxllWcyc if they don't work], turn OFF the printer immediatly and fix them (by bending the metal part a little bit for instance)

=== After printing ===
* If a pile of plastic has formed in the extruder, remove the wire complitely and cut it
* Put the leftover in the box, maybe one day we'll be able to [http://www.filabot.com/ recycle it!]

== Finance ==
* To buy new PLA filament and upgrade parts, there's a piggy bank next to the printer
* The cost in filament is indicated by Cura, just take a guess to add general maintenance cost of the printer
[[File:piggy.png|300px]]

== Files ==
You can find 3D models to print from [[#Find model online|this list of websites]]. There is also a folder full of previously printed STL's on the machine attached to the Ultimaker.

* FIXME keychain: [[File:fixme-key.stl]]
* Tablet support: [[File:tablet-support.stl]]
* Pincette: [[File:pincette-led.stl]] [[File:pincette-piles.stl]]

== Photos ==

<gallery>
File:Ultimaker.jpg|Ultimaker 3D printer
File:2012-11-04_20.39.49.jpg
File:ulti1.png
File:ulti2.png
File:raspi-ultimaker.png|Raspberry Pi case
File:Cells_Ball.jpg|Cells Ball
File:heart-8bit.png|8bit Heart
File:companion-cube.png|Companion Cube (Portal)
File:pickaxe.jpg|Pickaxe
File:fixme-keychain.jpg|Keychain
File:fixme-keychain2.jpg|Keychain 2
File:Mcad metric fastners.png|Metric bolts
File:pincettes.jpg|Pincette aimantée
File:creepers.jpg|Creepers
File:chain.png|Chaine
File:Ultimaker_Closeup.mp4|Closeup Video
</gallery>

== Webcam ==
* An AXIS webcam is deployed on the printer and accessible by IP: http://62.220.135.212
* There's a service for viewing the webcam
** https://webcam.fixme.ch
** Repo is in github: https://github.com/fixme-lausanne/fixme-webcam
** [[Gitolite#Deploy|Auto-deploy]] by pushing on the <code>live</code> branch in <code>ssh://gitolite@git.fixme.ch:1337/fixme-webcam</code>

== Maintenance ==
==== Issues to fix ====
* End stops are getting crapy
* Belt tension is bad
* Y alignement problems
* Fan can't be turned off (electrical problem?)
* Fan duct melts and scrapes the print/print surface
** Needs to be re-printed more often or made in a more heat-resistant material
* Prints fail if they reach near the edges of the print surface
* The current green filament is shitty and breaks ''all the time''

==== Fixed Issues ====
* <s>http://wiki.ultimaker.com/Jamming</s>
* <s>Needs a new tube and fixation</s>
* <s>One of the nozzle is loose. When the extrusion begins, the pipe move</s>
** <s>[[Media:ultimaker-fix1.png|Nemen has printed a piece for fixin']]</s>
** <s>http://www.thingiverse.com/thing:27376</s>
* <s>Belt tension: https://www.youtube.com/watch?v=grHmmmSoOfc&</s>
* <s>Thermocoupler and the heater are stuck in the head</s>

==== Todo ====
Stuff to print
* New fan: http://www.thingiverse.com/thing:25611
* <strike>Buy a wood chisel set</strike> - done

==== New parts ====
* Ordered and installed May 2013
* Advices from FabLab Munchen: https://plus.google.com/u/0/118147898615631299121/posts/Kckxn1ssgUt
** http://wiki.ultimaker.com/Upgrade:_Extruder_drive_v2 - [https://shop.ultimaker.com/en/parts-and-upgrades/extruder-drive-upgrade.html 22 Euro]
** http://wiki.ultimaker.com/Hot_end_v2 - [https://shop.ultimaker.com/en/parts-and-upgrades/v2-hot-end-upgrade.html 56 Euro]
** http://wiki.ultimaker.com/Knurled_Drive_Bolt_Pack - [https://shop.ultimaker.com/en/parts-and-upgrades/knurled-bolt-kit-version-3.html 16 Euro]
* Self-printer alternatives
** http://www.thingiverse.com/thing:26094 Extruder upgrade

== Other resources ==
* Filabot (recycling): [http://www.filabot.com/collections/filabot-systems buy] [http://www.kickstarter.com/projects/rocknail/filabot-plastic-filament-maker kickstarter]
* [http://www.metaingegneria.com/scanner-laser-3d/ 3D scanner with Camera + Laser + MatLab + MeshLab]
* http://themartinlab.tumblr.com/post/51803765008/10-things-i-wish-i-wouldve-known-before-owning-a-3d
* http://spiderbot.eu/
* [http://www.protoparadigm.com/blog/2013/06/vapor-smoothing-and-polishing-pla-with-tetrahydrofuran-thf/ Smoothing PLA]
* Drag&Drop page to easily transfert a .stl file to the server [http://foo.fixme.ch/marcha/]
* http://reprap.org/wiki/Print_Troubleshooting_Pictorial_Guide
* [http://nothinglabs.blogspot.ch/2013/11/3d-printed-hook-loop-fasteners.html 3D printed 'velcro']
* [http://www.kickstarter.com/projects/172237528/improved-3d-printer-extruder-allows-more-plastic-o Improved 3D printer extruder (for PVC and other plastics)]
* http://hackaday.com/2014/01/13/fastening-3d-printed-parts/
* http://hackaday.com/2014/01/28/fabrickation-combining-lego-and-3d-printing/
* http://hackaday.com/2014/03/19/ask-hackaday-auto-bed-leveling-and-high-temperature-force-sensitive-resistors/

== See also ==
* [[Plastic_recycling]]

30C3

2013-12-14T20:41:47Z

Petaflot: /* People coming */

__NOTOC__
[[Category:Ongoing_Projects]][[Category:Conferences]]
= Information =
* http://www.hamburg.ccc.de/
* Tickets: https://tickets.events.ccc.de/tickets/
* Schedule: https://events.ccc.de/congress/2013/Fahrplan/
* This year, the CCC takes place at Hamburg in the [http://www.cch.de/en/visit/travel-and-accommodation/ CCH]
* 27-30 december 2013
* [http://events.ccc.de/2013/07/18/30c3-call-for-participation-en/ Call for partitipation]

= People coming =

{| class="wikitable"
|+
! Name !! Ticket? !! Transport to HAM? !! Transport from HAM? !! Hotel?
|-
| [[User:Noskill|n0skill]] || (pre)ordered || Train || Train || Yes
|-
| Francois || || Train || Train || Radisson Blue
|-
| Fred || (pre)ordered || Train || Train || Radisson Blue
|-
| Sasha || || || ||
|-
| Jonas || paid ||Night Train (Booked) ||Plane (Germanwings 4U7744) ||Yes (1 double rooms from 27-30.12)
|-
| Gcmalloc || ||Plane ||Plane ||Not yet
|-
| Rorist || (pre)ordered ||Train ||Train ||Radisson Blue
|-
| MC || ||Plane (train sucks) ||Plane (use petrol before it's over) ||Radisson Blue
|-
| David+Chr || ||car (two seats available) ||car (another driver would be nice) ||Dunno...
|-
|+
! Total
!
!
!
!
|}

= Tickets =
Available at
https://tickets.events.ccc.de/tickets/

= Transport =

== By plane ==
{| class="wikitable"
|+
! !! GVA - HAM !! HAM - GVA
|-
| '''Company''' || GermanWings || GermanWings
|-
| '''Flight no''' || 4U7745 || 4U7744
|-
| '''Date''' || 26.12 || 30.12
|-
| '''Departure''' || 20:25 || 22:05
|-
| '''Arrival''' || 18:15 || 19:50
|-
| '''Changes''' || 0 || 0
|}
* For return flight you can get a great rate by booking over lidl-reisen.de http://www.lidl-reisen.de/germanwings

== By Train ==
=== CNL478 ===
{| class="wikitable"
|+
! !! LSN - HAM !! HAM - BSL
|-
| '''Company''' || City Night Line (DB) || City Night Line (DB)
|-
| '''Train no''' || CNL 478 || CNL 479
|-
| '''Date''' || 26.12 || 30.12
|-
| '''Departure''' || 18:45 || 19:11
|-
| '''Arrival''' || 08:42 || 06:36
|-
| '''Changes''' || 1 (BSL 22h13) || 0
|}

=== Proposition ===
From 108€ (~132 CHF) with demi-tarif Suisse for seat, and 118€ (~145 CHF) with bunk.
*[[:Image:Trainto.png]]
*[[:Image:Trainprice.png]]
*[[:Image:Online3.png]]

''Note: train prices are now available.''

= Hotels =
== Radisson Blue ==
<b>The Radisson Blue is FULL!</b>
<s>
*http://www.radissonblu.com/hotel-hamburg 90Eur/night for some ppl
**(119€ night/2)*3=178.5€ or 220 CHF per person for refundable version
**(106€ night/2)*3=159€ or 196.2 CHF per person for non-refundable version
*Promo code : '''30C3'''
</s>

== Other hotels ==
* https://events.ccc.de/congress/2013/wiki/Static:Accommodation
* http://www.generatorhostels.com/en/hamburg/ CHF 25.-/night for some other ppl
** From ~23 to ~85 CHF per person per night
* Gym - 5€/night
** Bartelsstr. 69, 20357 Hamburg and Haubachstr. 55, 22765 Hamburg

= Phone numbers =
Phone number registering: https://www.eventphone.de

== Phone list ==
{| class="wikitable"
|+
! Name
! Extension
! Type
|}

= No nerd left behind =
* TBD

= Projects =
* [[SpaceAPI#Components|MyHackerspace]]

= See also =
* [[28C3]]
* [[29C3]]

Parts Order

2013-10-18T17:23:09Z

Petaflot:

= China =

We can also order parts from China at a very low sales price. However, such orders should be high volume for each part. [[TaoBao Order]]

= International Distributors =

We usually order from [http://digikey.com DigiKey] (free shipping, fairly cheap) or [http://www.futureelectronics.com Future Electronics] ($50 shipping, very cheap). [http://mouser.com Mouser] also ships free above 80 CHF.

Because DigiKey and Future carry different parts, it is not easy to do a cheap order with exactly one part, because sometimes alternative parts exist in the other store that are cheaper.
List alternative parts in the ''Article Number'' field. Let's see how that works out.


== October 2013 - (Pending) ==
how about july/aug? stil pending?

<pre>976-1077-ND, 10, Hi-Power LED BXRA-50C5300-H-00 # DL parce qu'on veut de la luce
XXXXXX-ND, 20, Hi-speed optocoupler # DL, faut encore choisir le composant....
</pre>

== January 2013 - Farnell - (Closed) ==

<pre>
2191863, 17, RASPBERRY PI MODEL B #Prosouth(6) + Sasha(2) + Chris + _gcmalloc(2) + rorist + Noskill + Florian(2) + Ale
1229687, 2, BULGIN - PX0447 - CONNECTEUR MINI USB B MONT PANNEAU #Damien
1280789, 2, PRO SIGNAL - PSG01500 - FICHE MALE JACK 3.5MM 4 BROCHES METAL #Sasha
1280665, 2, PRO SIGNAL - PSG01497 - FICHE FEMELLE JACK 3.5MM STEREO #Sasha
2113799, 1, BOITIER POUR RASPBERRY PI TRANSPARENT #Ale
</pre>

Commande passée le 12 mars par François, livraison mercredi 13 si tout va bien!

== January - Farnell - (Close) ==
<pre>
2113799, 5, BOITIER POUR RASPBERRY PI TRANSPARENT #Fred + Ol1v + Sasha + Nemen(2x)
2113798, 1, BOITIER POUR RASPBERRY PI BLACK #Fred
2095867, 1, BRIDGE USB TO 1-FIL RJ11 #Fred
8750025, 1, CABLE DVI VERS HDMI 1M #Rorist
2115733, 5, CABLE USB A M - MICRO B M 1.8M #Rorist(2x) + Nemen(3x)
1079903, 20, CONTACT A SERTIR 24-30 AWG #Fred (FIXME?)
1668591, 10, EMBASE 2.54MM SINGLE 9VOIES #Fred
1568025, 2, FEMELLE MICRO USB B MID MOUNT #Sasha
2191863, 2, RASPBERRY PI MODEL B #Nemen
1568398, 1, DC STECKER 5, 5/2, 1 MM #Nemen
8365830, 2, FICHE 3 VOIES 4MM AVEC LEVIERS #Nemen
</pre>

Frais de livraison : SFr. 15.00
TVA SFr. 18.40

Prix final : https://docs.google.com/spreadsheet/ccc?key=0AuoAcKD1j_atdFBYWDM3NFE0b21IeW5fTExsQ0FMNXc

== July/August (pending) ==

<pre>
nemen, 5, 568-1484-5-ND # IC SHIFT REGISTER 8BIT 16DIP, $0.50
nemen, 5, ATTINY2313-20PU-ND # AT TINY 2313, $2.67
nemen, 5, ED60011-ND # 20DIP SUPPORT, $2.75
nemen, 10, 497-3186-5-ND # MOSFET N-CH 60V 30A TO-220, $1.02
simon, 20, SE3327-ND # CRYSTAL 77.5000KHZ 11PF CYL, $0.754
simon, 100, DMG3420U-7DICT-ND # MOSFET N-CH 20V 5.47A SOT23, $0.18560
</pre>

== August boxtec.ch (completed) ==

<pre>
3 x Ultrasonic Ranging Module HC-SR04 (47054) = CHF 37.20
4 x Mini 5V DC Power Relay SRD-5VDC-SL-C (48183) = CHF 12.80
1 x Duinomite MINI Basic Computer in small, compact form (31906) = CHF 27.20
5 x Shrouded Header 2x3pin (m) (48168) = CHF 7.50
5 x Shrouded Header 2x5pin (m) (48150) = CHF 8.00
5 x Ribbon Crimp Connector 2x5pin (f) (48151) = CHF 5.00
5 x Ribbon Crimp Connector 2x3pin (f) (48152) = CHF 4.25
4 x Stepper Motor with Cable (47923) = CHF 73.20
3 x USB Cable Mini USB (110cm) black (30306) = CHF 10.80
1 x 8x8 Dot Matrix 3mm dia. Bicolor LED Display (45006) = CHF 4.50
</pre>

==5 April 2012 (completed)==
''il me faut aussi des borniers à visser, pour du fil normal (max 2mm²) par 2 (15pc), 3 (15pc) et 12 (10pc)? je trouve pas sur digikey :-( si quelqu'un sait où trouver..'' [[User:Petaflot|Petaflot]] 15:52, 4 April 2012 (CEST)

<pre>
DL, 10, 360-1816-ND # on-off-on switches
DL, 3, 432-1257-ND # off-on-mom switches
DL, 3, 360-2073-ND # on-on-on switches
DL, 10, EG2394-ND # mom-off-on SPDT switches
DL, 3, 360-2080-ND # mom-off-on DPDT switches
DL, 1, 27931-ND # CO detector will make ND happy ;-)
DL, 4, LM2596S-ADJ-ND # to fix DC converters..
DL, 10, 568-1047-5-ND # I²C 8-bit LED driver with linux userspace utilities :-)
DL, 10, Z995-ND # relay socket, 5 pos through-hole
DL, 6, Z855-ND # relay socket, 5 pos DIN
DL, 2, Z2605-ND #relay socket, 8 pos
DL, 2, Z207-ND # relay socket 8 pos DIN
DL, 2 Z1637-ND # DPDT relay, 5A
DL, 10, Z1633-ND # 24V SPDT relay, 10A
DL, 15, 751-1129-ND #LEDs
DL, 15, 751-1114-ND #LEDs
DL, 15, 751-1153-ND #LEDs
DL, 5, 568-1416-5-ND #demux, active high output
DL, 5, 296-1600-5-ND #ShiftRegisters
DL, 5, 296-9217-5-ND # dual analog mux/demux
DL, 10, ED3114-ND # 14 pin DIP socket
DL, 10, 3M5463-ND # 16 pin DIP socket
DL, 10, 3M5476-ND # 18 pin DIP socket

337,78 Euros

NEM, 5, CP3-1000-ND # 2.1mm plug
NEM, 5 ATTINY13A-PU-ND # ATtiny13
NEM, 1, LM386N-1-ND # LM386 AMP Audio
NEM, 3, BH9V-PC-ND # Battery holder
NEM, 2, 3352T-104LF-ND # 100k variable resistor
NEM, 2, CP-3536-ND # 3.5mm jack
NEM, 1, RNF364K-ND # Heat shrink tube
NEM, 1, RNF012K-ND # Heat shrink tube
NEM, 5, A100204-ND # 8 pins DIP socket

362,89 Euros, delta = 25.11 Euros

JB, 5, 568-1416-5-ND #demux, active high output
JB, 5, 296-1600-5-ND #ShiftRegisters
JB, 20, 751-1129-ND #LEDs
JB, 20, 751-1114-ND #LEDs
JB, 20, 751-1153-ND #LEDs
JB, 10, A32870-ND #16 pins DIP socket
JB, 1, 438-1022-ND #prototype board
JB, 1, 299/1 SV005-ND #non insulated wire

443,24 Euros, delta = 80.35 Euros

ND, to many things, I make the order of my items + the current list on wednesday April 4

Order sent 5th of april @ 00:15

</pre>

File:Mcad metric fastners.png

2012-11-13T18:47:02Z

Petaflot: hmm not quite right yet

currently fixing MCAD library for metric nuts, bolts and the like - pictures show counter-clockwise threads and the pitch is incorrect. I will keep on working on it until I get bolts and nuts that are compatible with
standard "metal" metric bolts. until then, shut up or wait.. or contribute! ask Petaflot about it.

3d printer

2012-11-13T18:37:11Z

Petaflot: openscad

== Information ==
* http://wiki.ultimaker.com/Newcomer_guide_to_your_first_3D_print
* 3D Software:
** [http://openscad.org OpenSCAD] is a script-based 3D editor. it can make use of parameters, conditions, for and while loops, etc... This is currently Petaflot's choice
** http://www.3dtin.com/ Online in the browser
** http://www.netfabb.com/download.php (Linux version)
* Printing software:
** http://slic3r.org/
** https://github.com/daid/Cura

== Issues to fix ==
* The heater may be blocked inside
** Needs to be removed and cleaned
** Head may be replaced by the new one
* Needs a new tube and fixation
* One of the nozzle is loose. When the extrusion begins, the pipe move
** [[Media:ultimaker-fix1.png|Nemen has printed a piece for fixin']]
** http://www.thingiverse.com/thing:27376
* Software is kind of crappy
* Belt tension: https://www.youtube.com/watch?v=grHmmmSoOfc&

== Cura for printing ==
=== Installation ===
* http://daid.github.com/Cura/
* it's the only software worth it
* Yes, you will need PyOpenGL for it to run. Displaying nice 3d images is not that trivial.

* Recommended: Use the dev version on github: https://github.com/daid/Cura.git (12.10 when I'm writing)
* Required packages: wxPython and PyOpenGL.
* You can use a python virtualenv.

=== First use ===
* On first Cura start, you don't need to upgrade to Marlin firmware because it's already done.
* You should run the checks, at least to check if USB connection between PC and the printer is working. For temperature check, the printer need to cool down (to ~30) before heating and check, it can take looong time.
* Now you can use Cura to print objects.

=== Printing ===
* Load a .stl model.
* Change orientation, size, etc...
* Click on the Prepare print button.
* Software will slice the object into GCode. The more you choose a large scale object, the longer the execution time is.
* When it done, click on Print button to open the Printing dialog.
* Wait the software connect with the printer, Connection button will turn from clickable to readonly and Print button will turn from readonly to clickable.
* Set the temperature with the arrows (yeah it's not working by putting the number directly)
* Wait a bit so the hot end is distributively warmed
* Extrude before printing, so the wire is at the start of the hot end
* Make sure the wire is extruding correctly (the output wire is regular)
* Click the Print button.
* '''KEEP YOUR EYES ON THE PRINTER THROUGHOUT THE PRINTING PROCESS!!!''' And clean which could interfere the printing.

== Todo ==
Stuff to print
* New fan: http://www.thingiverse.com/thing:25611

== Files ==
* FIXME keychain: [[File:fixme-key.stl]]
* Tablet support: [[File:tablet-support.stl]]

== Photos ==

<gallery>
File:Ultimaker.jpg|Ultimaker 3D printer
File:2012-11-04_20.39.49.jpg
File:ulti1.png
File:ulti2.png
File:raspi-ultimaker.png|Raspberry Pi case
File:Cells_Ball.jpg|Cells Ball
File:heart-8bit.png|8bit Heart
File:companion-cube.png|Companion Cube (Portal)
File:pickaxe.jpg|Pickaxe
File:fixme-keychain.jpg|Keychain
File:fixme-keychain2.jpg|Keychain 2
File:Mcad metric fastners.png|Metric bolts
</gallery>

3d printer

2012-11-11T21:30:37Z

Petaflot: /* Photos */

== Information ==
* http://wiki.ultimaker.com/Newcomer_guide_to_your_first_3D_print
* 3D Software:
** http://www.3dtin.com/ Online in the browser

== Issues to fix ==
* The heater may be blocked inside
** Needs to be removed and cleaned
** Head may be replaced by the new one
* Needs a new tube and fixation
* One of the nozzle is loose. When the extrusion begins, the pipe move
** [[Media:ultimaker-fix1.png|Nemen has printed a piece for fixin']]
** http://www.thingiverse.com/thing:27376
* Software is kind of crappy
* Belt tension: https://www.youtube.com/watch?v=grHmmmSoOfc&

== Cura for printing ==
=== Installation ===
* http://daid.github.com/Cura/
* it's the only software worth it
* Yes, you will need PyOpenGL for it to run. Displaying nice 3d images is not that trivial.

* Recommended: Use the dev version on github: https://github.com/daid/Cura.git (12.10 when I'm writing)
* Required packages: wxPython and PyOpenGL.
* You can use a python virtualenv.

=== First use ===
* On first Cura start, you don't need to upgrade to Marlin firmware because it's already done.
* You should run the checks, at least to check if USB connection between PC and the printer is working. For temperature check, the printer need to cool down (to ~30) before heating and check, it can take looong time.
* Now you can use Cura to print objects.

=== Printing ===
* Load a .stl model.
* Change orientation, size, etc...
* Click on the Prepare print button.
* Software will slice the object into GCode. The more you choose a large scale object, the longer the execution time is.
* When it done, click on Print button to open the Printing dialog.
* Wait the software connect with the printer, Connection button will turn from clickable to readonly and Print button will turn from readonly to clickable.
* Click the Print button.
* '''KEEP YOUR EYES ON THE PRINTER THROUGHOUT THE PRINTING PROCESS!!!''' And clean which could interfere the printing.

== Todo ==
Stuff to print
* New fan: http://www.thingiverse.com/thing:25611

== Files ==
[[File:fixme-key.stl]]

== Photos ==

<gallery>
File:Ultimaker.jpg|Ultimaker 3D printer
File:2012-11-04_20.39.49.jpg
File:ulti1.png
File:ulti2.png
File:raspi-ultimaker.png|Raspberry Pi case
File:Cells_Ball.jpg|Cells Ball
File:heart-8bit.png|8bit Heart
File:companion-cube.png|Companion Cube (Portal)
File:pickaxe.jpg|Pickaxe
File:fixme-keychain.jpg|Keychain
File:fixme-keychain2.jpg|Keychain 2
File:Mcad metric fastners.png|Metric bolts
</gallery>

File:Mcad metric fastners.png

2012-11-11T21:29:11Z

Petaflot: fixed MCAD library for metric nuts, bolts and the like

fixed MCAD library for metric nuts, bolts and the like

Vim-plugin

2012-10-14T17:19:19Z

Petaflot: git plugins

Here is a non-exhausive list of really great vim plugin:
= General =
== git ==
* Vim-Fugitive - work on your commits from within GIT! https://github.com/tpope/vim-fugitive
* Git.vim is a plugin that allows the user to perform a lot more Git operations from within the Vim environment. http://github.com/motemen/git-vim/tree/master
* This plugin was designed to display the current branch info in the vim status line. http://github.com/taq/vim-git-branch-info/tree/master
== pathogen ==
For plugin management, after installing you can keep all your plugin in a ~/.vim/bundle. You can keep every plugin as a git depot for git-submodule management or similar.
http://www.vim.org/scripts/script.php?script_id=2332
== conque ==
A shell wrapper you can open a shell in a vim buffer simply with
:ConqueTerm ipython
or
:ConqueTerm zsh
http://code.google.com/p/conque/
== ack ==
A simple shortcut to the ack command, a grep alternative specially designed for programmers.
To search for all the source code for a word with some grep option by default.
https://github.com/mileszs/ack.vim
== surround ==
add or remove surrounding, it support parenthesis opening and closing.
For example:
"hello" to 'hello' with cs"'
https://github.com/tpope/vim-surround
== The-NERD-Tree ==
A file browser in vim, much better than the default one.
https://github.com/scrooloose/nerdtree
== auto-mkdir ==
Automatically create the directory that doesn't exist yet when editing a new file.
== minibufexplorer ==
always see all opened buffer, change between them, see wich one are selected.
https://github.com/fholgado/minibufexpl.vim
== snipmate ==
Very good snipet utility, very easily scriptable.
== superTab ==
tab make the completion for everything, snipet completion too if you have snipmate
== vim-powerline ==
status-bar on cocaine, with svn, git status, encoding, end of line, and more
== speedating ==
Increment/Decrement date with ctrl+a/ctrl+x, works so well you will loose your calendar.
Very handy to build macro on top of it.
== ZoomWin ==
Maximize one window, then go back to the original layout

= javascript =
== jslint ==
a simple linter with the quick fix window support

= css =
== css-color==
add the color of every color tag as the background for example:
html {
color: blue
}
the background of blue will be blue

= Python =
== Pydoc ==
Works very well for the default cpython lib. will open a new buffer in a new window with the corresponding doc when completing.
== Rope ==
Renaming at project scope, changing element and moving code around. Works really great
== Pyflake ==
A simple linter with quick fix window support

= Erlang =
== Vimerl ==
The best plugin around for programming in erlang with vim
https://github.com/oscarh/vimerl

Parts Order

2012-04-04T15:26:03Z

Petaflot: /* Electronics Parts Order */

= Electronics Parts Order =

We usually order from [http://digikey.com DigiKey] (free shipping, fairly cheap) or [http://www.futureelectronics.com Future Electronics] ($50 shipping, very cheap).

Because DigiKey and Future carry different parts, it is not easy to do a cheap order with exactly one part, because sometimes alternative parts exist in the other store that are cheaper.
List alternative parts in the ''Article Number'' field. Let's see how that works out.



''il me faut aussi des borniers à visser, pour du fil normal (max 2mm²) par 2 (15pc), 3 (15pc) et 12 (10pc)? je trouve pas sur digikey :-( si quelqu'un sait où trouver..'' [[User:Petaflot|Petaflot]] 15:52, 4 April 2012 (CEST)

<pre>
DL, 10, 360-1816-ND # on-off-on switches
DL, 3, 432-1257-ND # off-on-mom switches
DL, 3, 360-2073-ND # on-on-on switches
DL, 10, EG2394-ND # mom-off-on SPDT switches
DL, 3, 360-2080-ND # mom-off-on DPDT switches
DL, 1, 27931-ND # CO detector will make ND happy ;-)
DL, 4, LM2596S-ADJ-ND # to fix DC converters..
DL, 10, 568-1047-5-ND # I²C 8-bit LED driver with linux userspace utilities :-)
DL, 10, Z995-ND # relay socket, 5 pos through-hole
DL, 6, Z855-ND # relay socket, 5 pos DIN
DL, 2, Z2605-ND #relay socket, 8 pos
DL, 2, Z207-ND # relay socket 8 pos DIN
DL, 2 Z1637-ND # DPDT relay, 5A
DL, 10, Z1633-ND # 24V SPDT relay, 10A
DL, 15, 751-1129-ND #LEDs
DL, 15, 751-1114-ND #LEDs
DL, 15, 751-1153-ND #LEDs
DL, 5, 568-1416-5-ND #demux, active high output
DL, 5, 296-1600-5-ND #ShiftRegisters
DL, 5, 296-9217-5-ND # dual analog mux/demux
DL, 10, ED3114-ND # 14 pin DIP socket
DL, 10, 3M5463-ND # 16 pin DIP socket
DL, 10, 3M5476-ND # 18 pin DIP socket
JB, 5, 568-1416-5-ND #demux, active high output
JB, 5, 296-1600-5-ND #ShiftRegisters
JB, 20, 751-1129-ND #LEDs
JB, 20, 751-1114-ND #LEDs
JB, 20, 751-1153-ND #LEDs
JB, 10, A32870-ND #16 pins DIP socket
JB, 1, 438-1022-ND #prototype board
JB, 1, 299/1 SV005-ND #non insulated wire
ND, to many things, I make the order of my items + the current list on wednesday April 4
NEM, 5, CP3-1000-ND # 2.1mm plug
NEM, 5 ATTINY13A-PU-ND # ATtiny13
NEM, 1, LM386N-1-ND # LM386 AMP Audio
NEM, 3, BH9V-PC-ND # Battery holder
NEM, 2, 3352T-104LF-ND # 100k variable resistor
NEM, 2, CP-3536-ND # 3.5mm jack
NEM, 1, RNF364K-ND # Heat shrink tube
NEM, 1, RNF012K-ND # Heat shrink tube
NEM, 5, A100204-ND # 8 pins DIP socket
</pre>

Parts Order

2012-04-04T14:35:30Z

Petaflot:

= Electronics Parts Order =

We usually order from [http://digikey.com DigiKey] (free shipping, fairly cheap) or [http://www.futureelectronics.com Future Electronics] ($50 shipping, very cheap).

Because DigiKey and Future carry different parts, it is not easy to do a cheap order with exactly one part, because sometimes alternative parts exist in the other store that are cheaper.
List alternative parts in the ''Article Number'' field. Let's see how that works out.



'''il me faut aussi des borniers à visser, pour du fil normal (max 2mm²) par 2 (15pc), 3 (15pc) et 12 (10pc)? je trouve pas sur digikey :-(''' [[User:Petaflot|Petaflot]] 15:52, 4 April 2012 (CEST)

<pre>
DL, 1, 27931-ND # CO detector will make ND happy ;-)
DL, 4, LM2596S-ADJ-ND # to fix DC converters..
DL, 10, 568-1047-5-ND # I²C 8-bit LED driver with linux userspace utilities :-)
DL, 10, Z995-ND # relay socket, 5 pos through-hole
DL, 6, Z855-ND # relay socket, 5 pos DIN
DL, 2, Z2605-ND #relay socket, 8 pos
DL, 2, Z207-ND # relay socket 8 pos DIN
DL, 2 Z1637-ND # DPDT relay, 5A
DL, 10, Z1633-ND # 24V SPDT relay, 10A
DL, 15, 751-1129-ND #LEDs
DL, 15, 751-1114-ND #LEDs
DL, 15, 751-1153-ND #LEDs
DL, 5, 568-1416-5-ND #demux, active high output
DL, 5, 296-1600-5-ND #ShiftRegisters
DL, 5, 296-9217-5-ND # dual analog mux/demux
DL, 10, ED3114-ND # 14 pin DIP socket
DL, 10, 3M5463-ND # 16 pin DIP socket
DL, 10, 3M5476-ND # 18 pin DIP socket
JB, 5, 568-1416-5-ND #demux, active high output
JB, 5, 296-1600-5-ND #ShiftRegisters
JB, 20, 751-1129-ND #LEDs
JB, 20, 751-1114-ND #LEDs
JB, 20, 751-1153-ND #LEDs
JB, 10, A32870-ND #16 pins DIP socket
JB, 1, 438-1022-ND #prototype board
JB, 1, 299/1 SV005-ND #non insulated wire
ND, to many things, I make the order of my items + the current list on wednesday April 4
NEM, 5, CP3-1000-ND # 2.1mm plug
NEM, 5 ATTINY13A-PU-ND # ATtiny13
NEM, 1, LM386N-1-ND # LM386 AMP Audio
NEM, 3, BH9V-PC-ND # Battery holder
NEM, 2, 3352T-104LF-ND # 100k variable resistor
NEM, 2, CP-3536-ND # 3.5mm jack
NEM, 1, RNF364K-ND # Heat shrink tube
NEM, 1, RNF012K-ND # Heat shrink tube
NEM, 5, A100204-ND # 8 pins DIP socket
</pre>

Parts Order

2012-04-04T13:52:47Z

Petaflot:

= Electronics Parts Order =

We usually order from [http://digikey.com DigiKey] (free shipping, fairly cheap) or [http://www.futureelectronics.com Future Electronics] ($50 shipping, very cheap).

Because DigiKey and Future carry different parts, it is not easy to do a cheap order with exactly one part, because sometimes alternative parts exist in the other store that are cheaper.
List alternative parts in the ''Article Number'' field. Let's see how that works out.



'''il me faut aussi des borniers à visser, pour du fil normal (max 2mm²) par 2 (15pc), 3 (15pc) et 12 (10pc)? je trouve pas sur digikey :-(''' [[User:Petaflot|Petaflot]] 15:52, 4 April 2012 (CEST)

<pre>
DL, 4, LM2596S-ADJ-ND # to fix DC converters..
DL, 10, 568-1047-5-ND # I²C 8-bit LED driver with linux userspace utilities :-)
DL, 10, Z995-ND # relay socket, 5 pos through-hole
DL, 6, Z855-ND # relay socket, 5 pos DIN
DL, 2, Z2605-ND #relay socket, 8 pos
DL, 2, Z207-ND # relay socket 8 pos DIN
DL, 2 Z1637-ND # DPDT relay, 5A
DL, 10, Z1633-ND # 24V SPDT relay, 10A
DL, 15, 751-1129-ND #LEDs
DL, 15, 751-1114-ND #LEDs
DL, 15, 751-1153-ND #LEDs
DL, 5, 568-1416-5-ND #demux, active high output
DL, 5, 296-1600-5-ND #ShiftRegisters
DL, 5, 296-9217-5-ND # dual analog mux/demux
DL, 10, ED3114-ND # 14 pin DIP socket
DL, 10, 3M5463-ND # 16 pin DIP socket
DL, 10, 3M5476-ND # 18 pin DIP socket
JB, 5, 568-1416-5-ND #demux, active high output
JB, 5, 296-1600-5-ND #ShiftRegisters
JB, 20, 751-1129-ND #LEDs
JB, 20, 751-1114-ND #LEDs
JB, 20, 751-1153-ND #LEDs
JB, 10, A32870-ND #16 pins DIP socket
JB, 1, 438-1022-ND #prototype board
JB, 1, 299/1 SV005-ND #non insulated wire
ND, to many things, I make the order of my items + the current list on wednesday April 4
NEM, 5, CP3-1000-ND # 2.1mm plug
NEM, 5 ATTINY13A-PU-ND # ATtiny13
NEM, 1, LM386N-1-ND # LM386 AMP Audio
NEM, 3, BH9V-PC-ND # Battery holder
NEM, 2, 3352T-104LF-ND # 100k variable resistor
NEM, 2, CP-3536-ND # 3.5mm jack
NEM, 1, RNF364K-ND # Heat shrink tube
NEM, 1, RNF012K-ND # Heat shrink tube
NEM, 5, A100204-ND # 8 pins DIP socket
</pre>

Parts Order

2012-04-04T13:41:44Z

Petaflot: /* Electronics Parts Order */

= Electronics Parts Order =

We usually order from [http://digikey.com DigiKey] (free shipping, fairly cheap) or [http://www.futureelectronics.com Future Electronics] ($50 shipping, very cheap).

Because DigiKey and Future carry different parts, it is not easy to do a cheap order with exactly one part, because sometimes alternative parts exist in the other store that are cheaper.
List alternative parts in the ''Article Number'' field. Let's see how that works out.



<pre>
DL, 4, LM2596S-ADJ-ND # to fix DC converters..
DL, 10, 568-1047-5-ND # I²C 8-bit LED driver with linux userspace utilities :-)
DL, 10, Z995-ND # relay socket, 5 pos through-hole
DL, 6, Z855-ND # relay socket, 5 pos DIN
DL, 2, Z2605-ND #relay socket, 8 pos
DL, 2, Z207-ND # relay socket 8 pos DIN
DL, 2 Z1637-ND # DPDT relay, 5A
DL, 10, Z1633-ND # 24V SPDT relay, 10A
DL, 15, 751-1129-ND #LEDs
DL, 15, 751-1114-ND #LEDs
DL, 15, 751-1153-ND #LEDs
DL, 5, 568-1416-5-ND #demux, active high output
DL, 5, 296-1600-5-ND #ShiftRegisters
DL, 5, 296-9217-5-ND # dual analog mux/demux
JB, 5, 568-1416-5-ND #demux, active high output
JB, 5, 296-1600-5-ND #ShiftRegisters
JB, 20, 751-1129-ND #LEDs
JB, 20, 751-1114-ND #LEDs
JB, 20, 751-1153-ND #LEDs
JB, 10, A32870-ND #16 pins DIP socket
JB, 1, 438-1022-ND #prototype board
JB, 1, 299/1 SV005-ND #non insulated wire
ND, to many things, I make the order of my items + the current list on wednesday April 4
NEM, 5, CP3-1000-ND # 2.1mm plug
NEM, 5 ATTINY13A-PU-ND # ATtiny13
NEM, 1, LM386N-1-ND # LM386 AMP Audio
NEM, 3, BH9V-PC-ND # Battery holder
NEM, 2, 3352T-104LF-ND # 100k variable resistor
NEM, 2, CP-3536-ND # 3.5mm jack
NEM, 1, RNF364K-ND # Heat shrink tube
NEM, 1, RNF012K-ND # Heat shrink tube
NEM, 5, A100204-ND # 8 pins DIP socket
</pre>

== Petaflot also needs... ==
can you let me know if you plan to go shopping somewhere, where it will be?
* headers
* ic sockets
* borniers

Parts Order

2012-03-19T14:05:50Z

Petaflot:

CPU Boards

2012-03-19T09:59:05Z

Petaflot:

A collection of embedded boards with various CPUs.

'''TODO''': put this information in a table, with info like average pricing, capabilities and peripherals

Please add boards you know about in the list, may it not be something you would chose for a project..

== PIC based ==
* http://dangerousprototypes.com/docs/Web_platform_hardware_design
* http://www.evidence.eu.com/content/view/114/204/
* http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en535770
* http://www.microchip.com/microstick
* http://www.sparkfun.com/products/27

== Atmel based ==
* http://www.arduino.cc/
* http://www.pjrc.com/teensy/index.html
* http://www.ethernut.de/en/hardware/ethernuts.html
* http://www.acmesystems.it/?id=BEEBOARD

== ARM based ==
* [[ARM_Board]]
* http://processors.wiki.ti.com/index.php/OMAP3_Boards
* http://www.acmesystems.it/?id=FOXG20
* http://www.acmesystems.it/?id=NETUSG20
* http://www.ethernut.de/en/hardware/ethernuts.html
* http://www.embeddedarm.com/products/arm-sbc.php
* http://www.mini-box.com/ARM-Systems
* http://www.evidence.eu.com/content/view/352/426/
* http://elinux.org/RaspberryPiBoard
* http://www.solid-run.com/products/cubox
* http://fit-pc.co.uk/index.php?p=Trimslice
* http://beagleboard.org/bone (OpenSource hardware)

== x86 based ==
* http://pcengines.ch/alix.htm
* http://www.embeddedarm.com/products/x86-sbc.php
* http://bifferos.co.uk/
* http://www.via.com.tw/en/products/embedded/boards/
* http://www.mini-box.com/Mini-ITX-systems-x86
* http://emlix.com/bsp-packages0.html?&language=en
* http://www.axiomtek.de/
* http://www.baudisch.de/-en
* http://www.review-displays.co.uk/acatalog/single-board-computers.html
* http://www.lantronix.com/device-networking/embedded-device-servers/xport-pro-linux-dev-kit.html basically serial port with an ethernet connector. not sure about architecture though..

== FPGA ==
* http://www.acmesystems.it/?id=COLIBRI
* http://fpga4u.epfl.ch/
* http://www.xilinx.com/products/silicon-devices/fpga/index.htm
* http://www.altera.com/
* http://www.latticesemi.com/products/fpga/index.cfm?source=topnav
* http://www.actel.com/products/devices.aspx
* http://www.siliconbluetech.com/products/devices.aspx
* http://erika.tuxfamily.org/fpg-eye-fpga-board-with-lattice-xp2-and-mico32.html

== External lists, providers for misc boards ==
* http://free-electrons.com/community/hardware/boards/
* http://www.olimex.com/ quite a few PIC/Duino/ARM/AVR/..boards, they give free dev boards for interesting projetcs that publish their code!

Parts Order

2012-03-19T09:05:03Z

Petaflot:

CPU Boards

2012-03-16T18:31:36Z

Petaflot: /* x86 based */ lantronix

A collection of embedded boards with various CPUs.

'''TODO''': put this information in a table, with info like average pricing, capabilities and peripherals

Please add boards you know about in the list, may it not be something you would chose for a project..

== PIC based ==
* http://dangerousprototypes.com/docs/Web_platform_hardware_design
* http://www.evidence.eu.com/content/view/114/204/
* http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en535770
* http://www.microchip.com/microstick
* http://www.sparkfun.com/products/27

== Atmel based ==
* http://www.arduino.cc/
* http://www.pjrc.com/teensy/index.html
* http://www.ethernut.de/en/hardware/ethernuts.html
* http://www.acmesystems.it/?id=BEEBOARD

== ARM based ==
* [[ARM_Board]]
* http://processors.wiki.ti.com/index.php/OMAP3_Boards
* http://www.acmesystems.it/?id=FOXG20
* http://www.acmesystems.it/?id=NETUSG20
* http://www.ethernut.de/en/hardware/ethernuts.html
* http://www.embeddedarm.com/products/arm-sbc.php
* http://www.mini-box.com/ARM-Systems
* http://www.evidence.eu.com/content/view/352/426/
* http://elinux.org/RaspberryPiBoard
* http://www.solid-run.com/products/cubox
* http://fit-pc.co.uk/index.php?p=Trimslice
* http://beagleboard.org/bone (OpenSource hardware)

== x86 based ==
* http://pcengines.ch/alix.htm
* http://www.embeddedarm.com/products/x86-sbc.php
* http://bifferos.co.uk/
* http://www.via.com.tw/en/products/embedded/boards/
* http://www.mini-box.com/Mini-ITX-systems-x86
* http://emlix.com/bsp-packages0.html?&language=en
* http://www.axiomtek.de/
* http://www.baudisch.de/-en
* http://www.review-displays.co.uk/acatalog/single-board-computers.html
* http://www.lantronix.com/device-networking/embedded-device-servers/xport-pro-linux-dev-kit.html basically serial port with an ethernet connector. not sure about architecture though..

== FPGA ==
* http://www.acmesystems.it/?id=COLIBRI
* http://fpga4u.epfl.ch/
* http://www.xilinx.com/products/silicon-devices/fpga/index.htm
* http://www.altera.com/
* http://www.latticesemi.com/products/fpga/index.cfm?source=topnav
* http://www.actel.com/products/devices.aspx
* http://www.siliconbluetech.com/products/devices.aspx
* http://erika.tuxfamily.org/fpg-eye-fpga-board-with-lattice-xp2-and-mico32.html

== External lists.. ==
* http://free-electrons.com/community/hardware/boards/

Ffh

2012-03-12T20:05:48Z

Petaflot: /* Components */

[[Category:Ongoing_Projects]]
== Food For Hacker ==

== Description ==
Providing an easy and reliable source of dry food at the hackerspace.
== Goal ==
* have something cheap to eat at 4 o'clock in Lausanne for long hacking night.
* No washing up
* Also provide some fruits or vegetable at the place.

== Obstacle ==
* Price

== Components ==
* Some dry noodle would be nice, we would need a keetle for this. There is a lot of different kind of noodle cup.
* It would be nice to have heating plates as well, we have one but it's fred's

Shopping list :
* kettle - i have a stainless steel kettle I should not be using in any near future [[user:petaflot]]
* dry Noodle
* Ginger ale (little bottle)
* Mineral (africola ?)

== Schedule ==
* No precise buying date for the moment

== Participant ==
* [[User:gcmalloc]]
* [[User:undert]]

Parts Order

2012-02-10T13:02:53Z

Petaflot:

=Commande Digikey du XX.XX.2011 =

Status: open

Délais: XX.XX.2011

Commandé par: ????



<pre>

100,587-1254-1-ND,simon
100,587-1255-1-ND,simon
50,587-1256-1-ND,simon or 399-5504-1-ND if not available
5,LM334M-ND,simon
5,LT3080ET#PBF-ND,simon
5,HS380-ND,simon
5,BER220-ND,simon
5,BER168-ND,simon
10,497-1597-1-ND,simon
25,MCP6L02T-E/SNCT-ND,simon
5,SC310BSKCT-ND,simon
20,497-2228-1-ND,simon
10,497-8193-1-ND,simon
5,J151-ND,simon
5,J152-ND,simon
10,AP7313-33SAG-7DICT-ND,simon
5,DS18S20+-ND,Fred
10, 497-2356-5-ND, DL
10, 296-1411-5-ND, DL
10, 296-6504-5-ND, DL
10, 296-1403-5-ND, DL
10, 497-1579-5-ND, DL
10, TLP627-4F-ND, DL
</pre>
mais aussi: (je trouve pas dans le catalogue, qqn connaît les références? [[User:Petaflot]]
* borners divers
* headers
* socles IC
* 4m lab sockets
* station soudage réglable en temp.

Parts Order

2012-02-07T08:56:13Z

Petaflot:

=Commande Digikey du XX.XX.2011 =

Status: open

Délais: XX.XX.2011

Commandé par: ????



<pre>

100,587-1254-1-ND,simon
100,587-1255-1-ND,simon
50,587-1256-1-ND,simon or 399-5504-1-ND if not available
5,LM334M-ND,simon
5,LT3080ET#PBF-ND,simon
5,HS380-ND,simon
5,BER220-ND,simon
5,BER168-ND,simon
10,497-1597-1-ND,simon
25,MCP6L02T-E/SNCT-ND,simon
5,SC310BSKCT-ND,simon
20,497-2228-1-ND,simon
10,497-8193-1-ND,simon
5,J151-ND,simon
5,J152-ND,simon
10,AP7313-33SAG-7DICT-ND,simon
5,DS18S20+-ND,Fred
10, 497-2356-5-ND, DL
10, 296-1411-5-ND, DL
10, 296-6504-5-ND, DL
</pre>
mais aussi (à chercher dans le catalogue..)
* borners divers
* headers
* socles IC
* 4m lab sockets
* station soudage réglable en temp.
* ampli-op
* opto-coupleur 4x ou plus

XMPPHWFS

2012-02-01T20:03:18Z

Petaflot: fixed locmon link

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.

== Description ==
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon/ locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
* in case you ''really'' want to notify your friends through twitter, facebook or whatever else, create a bot and make it subscribe to particular events

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.

:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?

=== Device description ===
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
==== About the HAL ====
* name
* description
* location (GPS coordinates and/or description)
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os

==== About devices on each HAL ====
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* warn/alarm thresholds for event notification
* icon? maybe not necessary. one can be chosen from the I/O name or type.

==== Sample session ====
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info with the Pub/Sub mechanism. other bots can subscribe to events, and then decide what to do.

we'll get something like: (suggestions welcome!)
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Obstacle ==
* lack of expertise and motivation to implement a client in a µC
* weak programming skills

== Components ==
=== Software ===
Some things can can be handy:
* [http://thp.io/2007/python-jabberbot/ JabberBot] in python

=== Hardware ===
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

=== Software extensions ===
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

== Schedule ==
=== as soon as possible ===
* design a smart way to handle events (scripting/rules interface)
* implement test HAL client/bot with Pub/Sub
* implement event_master with Pub/Sub
* implement ctrl_bot

=== when the above is done... ===
* implement web interface on ctrl_bot
* implement fs_bot
* implement HAL bot on µC ([[SuperCaptor]]!!)

== Participant ==
* [[User:Petaflot]]

XMPPHWFS

2012-02-01T20:01:24Z

Petaflot: added project template and minor corrections

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.

== Description ==
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
* in case you ''really'' want to notify your friends through twitter, facebook or whatever else, create a bot and make it subscribe to particular events

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.

:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?

=== Device description ===
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
==== About the HAL ====
* name
* description
* location (GPS coordinates and/or description)
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os

==== About devices on each HAL ====
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* warn/alarm thresholds for event notification
* icon? maybe not necessary. one can be chosen from the I/O name or type.

==== Sample session ====
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info with the Pub/Sub mechanism. other bots can subscribe to events, and then decide what to do.

we'll get something like: (suggestions welcome!)
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Obstacle ==
* lack of expertise and motivation to implement a client in a µC
* weak programming skills

== Components ==
=== Software ===
Some things can can be handy:
* [http://thp.io/2007/python-jabberbot/ JabberBot] in python

=== Hardware ===
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

=== Software extensions ===
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

== Schedule ==
=== as soon as possible ===
* design a smart way to handle events (scripting/rules interface)
* implement test HAL client/bot with Pub/Sub
* implement event_master with Pub/Sub
* implement ctrl_bot

=== when the above is done... ===
* implement web interface on ctrl_bot
* implement fs_bot
* implement HAL bot on µC ([[SuperCaptor]]!!)

== Participant ==
* [[User:Petaflot]]

EAN Stalker

2012-02-01T19:43:55Z

Petaflot: Created page with "Category:Ongoing Projects == Description == make a small web app that returns info about a product. info should be a string of text, as well as a flag (''good/avoid_if_possi..."

[[Category:Ongoing Projects]]

== Description ==
make a small web app that returns info about a product. info should be a string of text, as well as a flag (''good/avoid_if_possible/avoid_at_all_costs'' or ''green/orange/red'')

* people with allergies would greatly benefit from this project
* people looking to buy hardware (eg: linux-compatible) could also find it neat
* other uses?

I am aware that other things exist that do more or less the same thing, only they do not allow you to use a custom database/repository (freedom of data!!)

=== Displayed/Saved Data ===
* EAN code
* product description
* company (can be found within GS1 database)
* link/URL
* components (part included in hardware OR ingredients of food)

==== Components ====
* ID
* name
* full description
* flag
* link/URL

== Goal ==
* the user scans the EAN barcode, info is returned either as XML (for use with iPhone/android app) or as HTML (for browser)
* the app should be able to search different "repositories" and assemble the output
* user should be able to edit a product if is not in DB or if data is incomplete/incorrect
* show company ownership from GS1 database, as well as the "company tree" (who really owns the firm selling that product)

== Obstacle ==
* no knowledge in iPhone app development
* no knowledge in Android app development
* lack of motivation to dig into GS1 API (I have it will post it soon) and information about company ownership

== Components ==
* no hardware needed

== Schedule ==
== Participant ==
* [[User:Petaflot]] for base functionality

User:Petaflot

2012-01-25T17:16:52Z

Petaflot: added id_rsa.pub

http://david.lutolf.net/

ssh-dss AAAAB3NzaC1kc3MAAACBANLMBJxVEVzlbkGs3dN0hsg4zOHoQ6b6i/ds8fbTWxPkBGrCAbkdG9bSv1dtyTJz1adF1khg3JwSPDsG5xNZnW5XKxyfxSx+TNXB/mTCAbi2ydivmGAugUhdBF+1ETDlppI+XQPVonjIxACL460+PUR4Zip4BsoPl6ycyJyZEYWHAAAAFQDNoFPjYPHsU4SucqjoKCB2YrgqRQAAAIAtDAz6g044G40Hoe74WARrjhUGDtJ1BJ4+lXh9lrIlnLzeXn4ZmuF0yOKngUeonunRB5EHgS548m0wt/4mSWRcy933Oiom5rHnOFZWtDVOgf2Z8Etr8aRvyOm/VSmzjuLCMW9Qz+j2ukpzKx5oCFMdQw8Fsz8pLLarUOknCOGS/QAAAIEAu4tt+kGTGIAuBJsh7BIMPm1CFQEtaAiNtpzPNaF4OGef732fuKfdLLLbyu3SEXw4j7Ofj3vNc3bHBqk9+KMaHUXhaqYDpdfka2oA2upd9pCBbJT2G21Atd4Kj/IOCx/932Uz4ObC/8biZIaFGnui+e9Ivk0G6Nlc4y+a/2/3ksk= dave@pg21.org

== What was your motivation to join participae on the hackerspace creation ? ==
* get the best for hacking cool stuff
* meeting some capable geeks for collaboration on random projects
* seeing what cool ideas the others have

== What can you teach ? ==
* I guess time is more to learning than teaching. it's always time to share ideas and thoughts though
* theory of microcontrolers and computers, electrotechnics, basic circuits (current limiters, power sources, amplifiers, op amps.. basically what I learned during apprenticeship)

== What do you want to learn ?==
* I first need to consolidate what I'm supposed to know. that is: microcontrolers (all of them, not just PIC)
* PCB design
* 3D modelling and prototyping
* how the universe works. there _must_ be simpler rules to everything

XMPPHWFS

2012-01-17T20:37:06Z

Petaflot: /* Software */

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
* in case you ''really'' want to notify your friends through twitter, facebook or whatever else, create a bot and make it subscribe to particular events

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.

:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
=== About the HAL ===
* name
* description
* location (GPS coordinates and/or description)
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os

=== About devices on each HAL ===
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* warn/alarm thresholds for event notification
* icon? maybe not necessary. one can be chosen from the I/O name or type.

=== Sample session ===
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info to ''event-master'' who will then decide what to do. In this case, the syntax does not much, so we get something like:
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Software ==
Some things can can be handy:
* [http://thp.io/2007/python-jabberbot/ JabberBot] in python

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-12T08:37:57Z

Petaflot: social networking is still possible

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
* in case you ''really'' want to notify your friends through twitter, facebook or whatever else, create a bot and make it subscribe to particular events

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.

:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
=== About the HAL ===
* name
* description
* location (GPS coordinates and/or description)
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os

=== About devices on each HAL ===
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* warn/alarm thresholds for event notification
* icon? maybe not necessary. one can be chosen from the I/O name or type.

=== Sample session ===
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info to ''event-master'' who will then decide what to do. In this case, the syntax does not much, so we get something like:
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-12T08:09:39Z

Petaflot:

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.

:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
=== About the HAL ===
* name
* description
* location (GPS coordinates and/or description)
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os

=== About devices on each HAL ===
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* warn/alarm thresholds for event notification
* icon? maybe not necessary. one can be chosen from the I/O name or type.

=== Sample session ===
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info to ''event-master'' who will then decide what to do. In this case, the syntax does not much, so we get something like:
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-12T07:11:37Z

Petaflot: modification after corecore's PUBSUB suggestion

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change a bit. ''locmon2'' seems like a good candidate to me.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

* Debugging new hardware is simply done through communication with a human client.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this.
* GUI can also be implemented as a bot (ctrl_bot?). Simple and clean. Use a of cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd. Any interface of this type should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info to ''event-master'' who will then decide what to do. In this case, the syntax does not much, so we get something like:
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-12T01:16:35Z

Petaflot: /* Sample session */ sending commands does not require XML... updated after playing with jabberbot-python

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available on a fuse filesystem through xml messaging protocol'''

and imagine doing stuff like

garage_temp = myHome/garage/temperature
garage_heat = myHome/heating/pump1

if (( $garage_temp < 2 ))
then
echo 1 > $garage_heat
fi

the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
;From HAL:
<pre>
rfid_reader: last RFID tag read
door_lock: status of door lock
lock_delay: how long should the door stay open
temperature: tell me how cold it is outside
</pre>

;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.
<pre>
describe
</pre>
;From HAL: I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro'
type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'>
<value>open</value>
<value selected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>

;To HAL:
<pre>temperature</pre>
;From HAL:
<pre><device name='temperature' value=23.5 /></pre>

;To HAL:
<pre>door_lock unlocked</pre>
;From HAL:
<pre><device name='door_lock' value='unlocked' /></pre>
;To HAL:
<pre>door_lock foobar</pre>
;From HAL: format needs to be thought a little better here..
<pre><device name='door_lock' value='open' />error: new value out of range</device></pre>

Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead)

=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info to ''event-master'' who will then decide what to do. In this case, the syntax does not much, so we get something like:
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-11T21:55:01Z

Petaflot: added image for architecture

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available on a fuse filesystem through xml messaging protocol'''

and imagine doing stuff like

garage_temp = myHome/garage/temperature
garage_heat = myHome/heating/pump1

if (( $garage_temp < 2 ))
then
echo 1 > $garage_heat
fi

the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.

[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:
Here, it should be a good thing to have flags such as ''update_all_values'', ''used_cached_values''
<pre>
<describe />
</pre>
;From HAL:
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro' type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'
value='closed'>
<value>open</value>
<value>closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>
;To HAL:
<pre>
<set device='door_lock' value='open' />
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='door_lock' value='open' />
</devices>
</hal>
</pre>
;To HAL:
<pre>
<get device='temperature' />
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='temperature' value=23.5 />
</devices>
</hal>
</pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

File:Xmpphwfs arch.svg

2012-01-11T21:51:30Z

Petaflot: architecture of XMPPHWFS

architecture of [[XMPPHWFS]]

XMPPHWFS

2012-01-11T21:03:26Z

Petaflot: /* Sample session */ removed useless crap

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available on a fuse filesystem through xml messaging protocol'''

and imagine doing stuff like

garage_temp = myHome/garage/temperature
garage_heat = myHome/heating/pump1

if (( $garage_temp < 2 ))
then
echo 1 > $garage_heat
fi

the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:
Here, it should be a good thing to have flags such as ''update_all_values'', ''used_cached_values''
<pre>
<describe />
</pre>
;From HAL:
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro' type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'
value='closed'>
<value>open</value>
<value>closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>
;To HAL:
<pre>
<set device='door_lock' value='open' />
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='door_lock' value='open' />
</devices>
</hal>
</pre>
;To HAL:
<pre>
<get device='temperature' />
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='temperature' value=23.5 />
</devices>
</hal>
</pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-11T20:42:32Z

Petaflot: added categorization

[[Category:Ongoing_Projects]]

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available on a fuse filesystem through xml messaging protocol'''

and imagine doing stuff like

garage_temp = myHome/garage/temperature
garage_heat = myHome/heating/pump1

if (( $garage_temp < 2 ))
then
echo 1 > $garage_heat
fi

the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:
Here, it should be a good thing to have flags such as ''update_all_values'', ''used_cached_values''
<pre>
<command>
<describe />
</command>
</pre>
;From HAL:
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro' type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'
value='closed'>
<value>open</value>
<value>closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>
;To HAL:
<pre>
<command>
<set device='door_lock' value='open' />
<get device='temperature' />
</command>
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='door_lock' value='open' />
<device name='temperature' value=23.5 />
</devices>
</hal>
</pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-11T20:42:00Z

Petaflot: /* Sample session */

Under the barbarian name of XMPPHWFS stands the following idea:

'''hardware IOs made available on a fuse filesystem through xml messaging protocol'''

and imagine doing stuff like

garage_temp = myHome/garage/temperature
garage_heat = myHome/heating/pump1

if (( $garage_temp < 2 ))
then
echo 1 > $garage_heat
fi

the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
* The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
* GUI can also be implementd as a bot. Simple and clean.
* Debugging new hardware is simply done through communication with a human client.

XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.

it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.

== Device description ==
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
* variable name
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)
* I/O type (door, temperature, humidity...)
* location (GPS coordinates and/or description)
* text/blob, possibly containing icon
* min/max trigger values

=== Sample session ===
;To HAL:
Here, it should be a good thing to have flags such as ''update_all_values'', ''used_cached_values''
<pre>
<command>
<describe />
</command>
</pre>
;From HAL:
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<description>This device is a sample that does many things and actually nothing</description>
<location lat='47°00N' long='8°00E' elevation=495>Main door of building on route de Genève</location>
<devices>
<device
name='rfid_reader'
attrs='ro' type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
<device
name='door_lock'
attrs='rw'
type='enum'
value='closed'>
<value>open</value>
<value>closed</value>
<value>locked</value>
<value>unlocked</value>
</device>
<device
name='lock_delay'
attrs='rw'
type='int'
last_update_timestamp=1326310915
value=4
unit='s' />
<device
name='temperature'
attrs='ro'
type='float'
last_update_timestamp=1326312490
value=23.5
unit='°C'
alarm_high=28.0
warn_low=12.0/>
</devices>
</hal>
</pre>
;To HAL:
<pre>
<command>
<set device='door_lock' value='open' />
<get device='temperature' />
</command>
</pre>
;From HAL:
<pre>
<hal name='HalName'>
<devices>
<device name='door_lock' value='open' />
<device name='temperature' value=23.5 />
</devices>
</hal>
</pre>

== Hardware ==
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]

== Software extensions ==
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD

XMPPHWFS

2012-01-11T08:24:14Z

Petaflot: /* Device description */

XMPPHWFS

2012-01-11T08:12:25Z

Petaflot:

Talk:Movies

2012-01-07T08:20:34Z

Petaflot: Created page with "* maybe make a torrent with all this stuff? * there was a nice list @28C3"

* maybe make a torrent with all this stuff?
* there was a nice list @[[28C3]]

User:Petaflot

2012-01-07T08:18:45Z

Petaflot:

http://david.lutolf.net/

== What was your motivation to join participae on the hackerspace creation ? ==
* get the best for hacking cool stuff
* meeting some capable geeks for collaboration on random projects
* seeing what cool ideas the others have

== What can you teach ? ==
* I guess time is more to learning than teaching. it's always time to share ideas and thoughts though
* theory of microcontrolers and computers, electrotechnics, basic circuits (current limiters, power sources, amplifiers, op amps.. basically what I learned during apprenticeship)

== What do you want to learn ?==
* I first need to consolidate what I'm supposed to know. that is: microcontrolers (all of them, not just PIC)
* PCB design
* 3D modelling and prototyping
* how the universe works. there _must_ be simpler rules to everything

User:Petaflot

2012-01-07T08:18:13Z

Petaflot: Created page with "http://david.lutolf.net/ == What was your motivation to join participae on the hackerspace creation ? == * get the best for hacking cool stuff * meeting some capable geeks for c..."

http://david.lutolf.net/

== What was your motivation to join participae on the hackerspace creation ? ==
* get the best for hacking cool stuff
* meeting some capable geeks for collaboration on random projects
* seeing what cool ideas the others have

== What can you teach ? ==
* I guess time is more to learning than teaching. it's always time to share
ideas and thoughts though
* theory of microcontrolers and computers, electrotechnics, basic circuits (current limiters, power sources, amplifiers, op amps.. basically what I learned during apprenticeship)

== What do you want to learn ?==
* I first need to consolidate what I'm supposed to know. that is: microcontrolers (all of them, not just PIC)
* PCB design
* 3D modelling and prototyping
* how the universe works. there _must_ be simpler rules to everything

XMPPHWFS

2012-01-01T22:41:51Z

Petaflot: