http://www.hackerspace-ffm.de/wiki/api.php?action=feedcontributions&user=Hephaisto&feedformat=atomHackerspace Ffm - Benutzerbeiträge [de]2024-03-29T08:39:20ZBenutzerbeiträgeMediaWiki 1.25.3http://www.hackerspace-ffm.de/wiki/index.php?title=Ancient_Board&diff=11500Ancient Board2023-04-30T01:42:00Z<p>Hephaisto: Add PCB photos</p>
<hr />
<div>The goal of this project is to build something that resembles the optics of a certain type of sci-fi device which controls something by putting transparent plates at specific places. Examples include the [https://stargate.fandom.com/wiki/Control_crystal#Ancients Ancient control crystals in Stargate] (which gave the project its name) and control plates in [https://en.wikipedia.org/wiki/The_Expanse_(TV_series) The Expanse].<br />
<br />
Important features are:<br />
* transparent plates<br />
* a holder with slits to insert the plates<br />
* *lots* of 135 degree angles (because sci-fi!)<br />
* illumination of the plates<br />
* inserting the plates triggers some feature (what exactly, I don't care) -> it will just publish which plate is inserted via MQTT, and you can connect whatever you want to that<br />
* proper security: Full (client+server) certificate-based TLS authentication+encryption<br />
* configurable in the number of slots, size etc.<br />
<br />
=== Design overview ===<br />
<br />
==== Construction ====<br />
<br />
The visible casing and the plates are laser-cut acrylic plates. They can be engraved as suitable.<br />
The casing is mounted onto a 3D-printed backplane, which also holds multiple switches. The switches are pressed by protrusions of the inserts (which of course have 135 degree angles!). The slits on the side have a backside made of diffuse acrylic with LEDs mounted behind them to allow illumination of the inserts.<br />
<br />
The SVGs for lasercutting are generated "by hand" in python.<br />
The 3D-printed base is generated using MuSCAD[https://pypi.org/project/muscad/] and OpenSCAD[https://openscad.org/].<br />
<br />
<gallery widths="400px" heights="300px"><br />
Datei:Ancient_board_base.png|3D printed base<br />
Datei:iter2.png|with insert and translucent side walls<br />
Datei:iter3.png|the translucent side wall is covered by a black front plate with cutouts for the inserts <br />
Datei:iter4.png|plates are clipped in horizontally and serve as the bottom of the pocket<br />
Datei:iter5.png|the pocket is closed with plates. cutouts at the bottom allow exit of cables for the switches<br />
Datei:iter6.png|the whole box is covered with a top plate<br />
Datei:iter7.png|all plates on the side are fixed by screws<br />
</gallery><br />
<br />
==== Electronics ====<br />
<br />
The system is controlled by an ESP32 running ESP-IDF and FreeRTOS.<br />
The switches are handled by I2C port expanders. The LED strips are controlled by WS2812 chips.<br />
<br />
<gallery widths="400px" heights="300px"><br />
Datei:IMG_20230416_023446_267.jpg|Bottom side with port expanders and logos<br />
Datei:IMG_20230416_023438_465.jpg|Top side with ESP32 and connectors for LEDs and Switches<br />
</gallery><br />
<br />
I'm particularly proud of this because this PCB was a "first" in multiple ways<br />
* It was my first PCB made with '''LibrePCB'''[https://librepcb.org/] (that actually works). If you want do create PCBs with an open source tool and found Eagle much more usable than KiCad, you should check it out.<br />
* It's my first 4-layer PCB. 2 Layers would probably have been sufficient if I spent more time on optimizing the design. But I wanted to try out making a 4-layer PCB anyway.<br />
* It's the first time I soldered TSSOP packages. They are a PITA if you are as motorically incompetent as I am.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:IMG_20230416_023438_465.jpg&diff=11499Datei:IMG 20230416 023438 465.jpg2023-04-30T01:36:15Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:IMG_20230416_023446_267.jpg&diff=11498Datei:IMG 20230416 023446 267.jpg2023-04-30T01:35:06Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Ancient_Board&diff=11496Ancient Board2023-04-16T03:24:42Z<p>Hephaisto: </p>
<hr />
<div>The goal of this project is to build something that resembles the optics of a certain type of sci-fi device which controls something by putting transparent plates at specific places. Examples include the [https://stargate.fandom.com/wiki/Control_crystal#Ancients Ancient control crystals in Stargate] (which gave the project its name) and control plates in [https://en.wikipedia.org/wiki/The_Expanse_(TV_series) The Expanse].<br />
<br />
Important features are:<br />
* transparent plates<br />
* a holder with slits to insert the plates<br />
* *lots* of 135 degree angles (because sci-fi!)<br />
* illumination of the plates<br />
* inserting the plates triggers some feature (what exactly, I don't care) -> it will just publish which plate is inserted via MQTT, and you can connect whatever you want to that<br />
* proper security: Full (client+server) certificate-based TLS authentication+encryption<br />
* configurable in the number of slots, size etc.<br />
<br />
=== Design overview ===<br />
<br />
==== Construction ====<br />
<br />
The visible casing and the plates are laser-cut acrylic plates. They can be engraved as suitable.<br />
The casing is mounted onto a 3D-printed backplane, which also holds multiple switches. The switches are pressed by protrusions of the inserts (which of course have 135 degree angles!). The slits on the side have a backside made of diffuse acrylic with LEDs mounted behind them to allow illumination of the inserts.<br />
<br />
The SVGs for lasercutting are generated "by hand" in python.<br />
The 3D-printed base is generated using MuSCAD[https://pypi.org/project/muscad/] and OpenSCAD[https://openscad.org/].<br />
<br />
<gallery widths="400px" heights="300px"><br />
Datei:Ancient_board_base.png|3D printed base<br />
Datei:iter2.png|with insert and translucent side walls<br />
Datei:iter3.png|the translucent side wall is covered by a black front plate with cutouts for the inserts <br />
Datei:iter4.png|plates are clipped in horizontally and serve as the bottom of the pocket<br />
Datei:iter5.png|the pocket is closed with plates. cutouts at the bottom allow exit of cables for the switches<br />
Datei:iter6.png|the whole box is covered with a top plate<br />
Datei:iter7.png|all plates on the side are fixed by screws<br />
</gallery><br />
<br />
==== Electronics ====<br />
<br />
The system is controlled by an ESP32 running ESP-IDF and FreeRTOS.<br />
The switches are handled by I2C port expanders. The LED strips are controlled by WS2812 chips.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter7.png&diff=11495Datei:Iter7.png2023-04-16T03:20:36Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter6.png&diff=11494Datei:Iter6.png2023-04-16T03:20:26Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter5.png&diff=11493Datei:Iter5.png2023-04-16T03:19:20Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter4.png&diff=11492Datei:Iter4.png2023-04-16T03:18:43Z<p>Hephaisto: plates are clipped in horizontally and serve as the bottom of the pocket</p>
<hr />
<div>plates are clipped in horizontally and serve as the bottom of the pocket</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter3.png&diff=11491Datei:Iter3.png2023-04-16T03:06:57Z<p>Hephaisto: the translucent side wall is covered by a black front plate with cutouts for the inserts</p>
<hr />
<div>the translucent side wall is covered by a black front plate with cutouts for the inserts</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Iter2.png&diff=11490Datei:Iter2.png2023-04-16T03:06:20Z<p>Hephaisto: with insert and translucent side walls</p>
<hr />
<div>with insert and translucent side walls</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:Ancient_board_base.png&diff=11489Datei:Ancient board base.png2023-04-16T03:04:54Z<p>Hephaisto: 3D printed base</p>
<hr />
<div>3D printed base</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Ancient_Board&diff=11486Ancient Board2023-02-28T02:09:54Z<p>Hephaisto: Die Seite wurde neu angelegt: „The goal of this project is to build something that resembles the optics of a certain type of sci-fi device which controls something by putting transparent pla…“</p>
<hr />
<div>The goal of this project is to build something that resembles the optics of a certain type of sci-fi device which controls something by putting transparent plates at specific places. Examples include the [https://stargate.fandom.com/wiki/Control_crystal#Ancients Ancient control crystals in Stargate] (which gave the project its name) and control plates in [https://en.wikipedia.org/wiki/The_Expanse_(TV_series) The Expanse].<br />
<br />
Important features are:<br />
* transparent plates<br />
* a holder with slits to insert the plates<br />
* *lots* of 135 degree angles (because sci-fi!)<br />
* illumination of the plates<br />
* inserting the plates triggers some feature (what exactly, I don't care) -> it will just publish which plate is inserted via MQTT, and you can connect whatever you want to that<br />
* proper security: Full (client+server) certificate-based TLS authentication+encryption<br />
* configurable in the number of slots, size etc.<br />
<br />
=== Design overview ===<br />
<br />
==== Construction ====<br />
<br />
The visible casing and the plates are laser-cut acrylic plates. They can be engraved as suitable.<br />
The casing is mounted onto a 3D-printed backplane, which also holds multiple switches. The switches are pressed by protrusions of the inserts (which of course have 135 degree angles!). The slits on the side have a backside made of diffuse acrylic with LEDs mounted behind them to allow illumination of the inserts.<br />
<br />
==== Electronics ====<br />
<br />
The system is controlled by an ESP32 running ESP-IDF and FreeRTOS.<br />
The switches are handled by I2C port expanders. The LED strips are controlled by WS2812 chips.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Reloaded:_CO%E2%82%82-Laser_2.0&diff=11140Reloaded: CO₂-Laser 2.02020-06-08T20:43:34Z<p>Hephaisto: /* 100W-CO₂-Laser Quick and Dirty HOW_TO */</p>
<hr />
<div>== '''!! ACHTUNG !!''' ==<br />
Der neue LASER ist noch nicht fertig eingerichtet. Die hier notierten Erfahrungen sind "work in progress". Es fehlt noch an allen möglichen Sicherheitseinrichtungen. Daher ist der Laser noch nicht für die Allgemeinheit freigegegeben.<br />
<br />
Max. Arbeitsfläche: 900mm x 600mm<br />
<br />
== 100W-CO₂-Laser Quick and Dirty HOW_TO ==<br />
Benötigte Software:<br />
* RD Works (ausprobiert: V8.1.21) http://www.thunderlaser.com/laser-download<br />
* evtl. Inkscape http://www.inkscape.org/de/ mit Plugin https://github.com/jnweiger/inkscape-thunderlaser - geht, ist aber '''spiegelverkehrt'''!<br />
* Spezielles Visicut mit Thundelaser-Unterstützung: https://github.com/fablabnbg/VisiCut/releases<br />
* USB-Port über Netzwerk via Virtualhere-Client ansteuern: https://www.virtualhere.com/usb_client_software<br />
<br />
== RD Works unter Linux installieren ==<br />
<br />
RD Works lässt sich unter Linux Mint mittels Wine installieren. Die Installationsdatei (.rar) auf dem Rechner speichern, entpacken und die RDWorksV8Setup8.01.21.exe mittels Rechtsklick "Öffnen mit... Wine-Windows-Programmstarter" installieren.<br />
Die Software lässt sich dann aus dem Startmenü (Wine-Ordner) öffnen.<br />
<br />
Verbindung zum Laser: Windows-Rechner lassen sich per USB anschließen, unter Linux noch keine Erfahrung damit.<br />
Unter Linux funktioniert die Verbindung per LAN. Dazu in der Software unter "Device -> Port Settings" ein neues Gerät anlegen "Add..." und "Web" auswählen und die IP-Adresse eingeben. '''Achtung: IP-Adresse noch nicht festgelegt.''' Der Laser muss anscheinend eine feste, manuell vergebene IP-Adresse bekommen. Bei den Tests wurde die IP 10.0.0.205 verwendet, diese kann aber jederzeit vom Router anderweitig vergeben werden. Eine feste Laser-IP muss noch eingerichtet werden. <br />
<br />
Die Verbindung zwischen Linux-Rechner und Lasersteuerung kam erst nach mehrmaligen Einstellungen und Ausprobieren zustande. Danach lief sie aber (zumindest einen Abend lang) stabil.<br />
<br />
<br />
== Bedienung RDWorks ==<br />
Es gibt ein paar "Handbuch"-PDFs zur Steuerung und zur Software.<br />
Die Software bietet einfache Grafik- und Text-Funktionen. Außerdem kann man Pfade vereinfachen und einen Daten-Check (offene Pfade?) durchführen.<br />
<br />
== Materialeinstellungen ==<br />
<br />
Bisher ausprobiert: Sperrholz 4 mm, Hartfaserplatte und Acrylglas 3 mm<br />
==== Referenz====<br />
<br />
==== Sperrholz 4mm====<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut ||80 %||20|| Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
<br />
<br />
==== Acrylglas 3mm====<br />
Bei durchsichtigen Materialien am besten spiegelverkehrt gravieren!<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut||40 %||20||Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
==== Hartfaserplatte 3mm====<br />
Inkscape-thunderlaser:<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Speed!!Power min!!Power max<br />
|-<br />
|Cut||10||80||100<br />
|-<br />
|Cut Shintaro||25||60||80<br />
|-<br />
|Mark||30||10||10<br />
|-<br />
|}<br />
<br />
==== Eurobox (Toom/Surplus systems, transparent) ====<br />
cut: 15, 70, 100 - besser weniger und 2x<br />
<br />
==== MDF ====<br />
<br />
==== Spiegel Acryl 3mm ====<br />
<br />
==== Wellpappe ====<br />
<br />
==== Goldkarton, beidseitg matt-gold (gibs beim Real) ====<br />
<br />
==== [https://de.wikipedia.org/wiki/Polyoxymethylen POM 4mm] ====<br />
<br />
==== Glas gravieren ====<br />
<br />
== CO₂-Laser 100W ==<br />
<br />
=== Was noch gefixt werden muss ===<br />
* Klappenschalter hat keine Rolle mehr<br />
* Klappenschalter kann von Front-Panel-Schalter überbrückt werden<br />
* Klappenschalter wirkt nicht direkt auf das Lasernetzteil<br />
* Abluftschlauch an der Seite ist evtl. ungünstig<br />
* Abluft per Nachlaufsteuerung anschliessen<br />
* Klappen entscheppern/abdichten<br />
* Sicherheitsschalter evtl. auch in Front-Tür bauen<br />
* Schläuche für Wasser und Luft verlängern (andere kaufen)<br />
<br />
Laser Steuerung<br />
[[Datei:LasetSteuerungChina.jpg|200px]]<br />
<br />
=== Was schon ein bisschen gefixt wurde===<br />
* Steps/mm Einstellungen<br />
** Dazu einfach RDWorks per USB verbinden, unter File/Vendor Settings (Passwort: RD8888) gibt es für jede Achse Steps/mm. (unter dem ... Menü können auch direkt gemessene vs. geschnittene Werte eingetragen werden und die Steps werden automatisch berechnet.<br />
* Frontschlitze optisch undurchlässig machen - 17.09.18<br />
<br />
== Reverse Engineering ==<br />
* Laser horcht auf UDP-Ports 50200 und 50207 - evtl. müssen sich diese aber im gleichen 255.255.255.0-Subnetz befinden: https://github.com/jnweiger/ruida-laser/blob/master/doc/protocol.md<br />
* Weitere infos:<br />
** https://wiki.fablab-nuernberg.de/w/Nova_35<br />
** http://www.thunderlaser.com/laser-download<br />
** https://github.com/kkaempf/ruida<br />
** https://github.com/jnweiger/ruida-laser<br />
** https://github.com/jnweiger/ruida-laser/blob/master/doc/laser-nova35-rdworks.md<br />
<br />
== Nützliches ==<br />
Link für Infos zu Lasermaterial<br />
http://atxhackerspace.org/wiki/Laser_Cutter_Materials<br />
<br />
Laser Pfad justieren:<br />
https://www.youtube.com/watch?v=W5390ajG_0k<br />
<br />
==Fotos==<br />
<gallery caption="Foto 05.09.2018"><br />
Datei:Neuer_CO2-Laser.jpg|Neuer 100W-CO2-Laser<br />
</gallery><br />
<br />
==Screens Installation==<br />
<gallery caption="Windows 10"><br />
Datei:2020-01-13 21 59 25-Bonjour.png<br />
Datei:2020-01-13 22 01 11-VirtualHereUI.png<br />
Datei:2020-01-13 22 02 20-VirtualHereUI.png<br />
Datei:2020-01-13 22 03 05-VirtualHereUI.png<br />
Datei:2020-01-13 22 16 33-RDWorksV8Uninstall.png<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Reloaded:_CO%E2%82%82-Laser_2.0&diff=11139Reloaded: CO₂-Laser 2.02020-06-08T20:42:09Z<p>Hephaisto: /* Materialeinstellungen */</p>
<hr />
<div>== '''!! ACHTUNG !!''' ==<br />
Der neue LASER ist noch nicht fertig eingerichtet. Die hier notierten Erfahrungen sind "work in progress". Es fehlt noch an allen möglichen Sicherheitseinrichtungen. Daher ist der Laser noch nicht für die Allgemeinheit freigegegeben.<br />
<br />
Max. Arbeitsfläche: 900mm x 600mm<br />
<br />
== 100W-CO₂-Laser Quick and Dirty HOW_TO ==<br />
Benötigte Software:<br />
* RD Works (ausprobiert: V8.1.21) http://www.thunderlaser.com/laser-download<br />
* evtl. Inkscape http://www.inkscape.org/de/ mit Plugin https://github.com/jnweiger/inkscape-thunderlaser<br />
* Spezielles Visicut mit Thundelaser-Unterstützung: https://github.com/fablabnbg/VisiCut/releases<br />
* USB-Port über Netzwerk via Virtualhere-Client ansteuern: https://www.virtualhere.com/usb_client_software <br />
<br />
== RD Works unter Linux installieren ==<br />
<br />
RD Works lässt sich unter Linux Mint mittels Wine installieren. Die Installationsdatei (.rar) auf dem Rechner speichern, entpacken und die RDWorksV8Setup8.01.21.exe mittels Rechtsklick "Öffnen mit... Wine-Windows-Programmstarter" installieren.<br />
Die Software lässt sich dann aus dem Startmenü (Wine-Ordner) öffnen.<br />
<br />
Verbindung zum Laser: Windows-Rechner lassen sich per USB anschließen, unter Linux noch keine Erfahrung damit.<br />
Unter Linux funktioniert die Verbindung per LAN. Dazu in der Software unter "Device -> Port Settings" ein neues Gerät anlegen "Add..." und "Web" auswählen und die IP-Adresse eingeben. '''Achtung: IP-Adresse noch nicht festgelegt.''' Der Laser muss anscheinend eine feste, manuell vergebene IP-Adresse bekommen. Bei den Tests wurde die IP 10.0.0.205 verwendet, diese kann aber jederzeit vom Router anderweitig vergeben werden. Eine feste Laser-IP muss noch eingerichtet werden. <br />
<br />
Die Verbindung zwischen Linux-Rechner und Lasersteuerung kam erst nach mehrmaligen Einstellungen und Ausprobieren zustande. Danach lief sie aber (zumindest einen Abend lang) stabil.<br />
<br />
<br />
== Bedienung RDWorks ==<br />
Es gibt ein paar "Handbuch"-PDFs zur Steuerung und zur Software.<br />
Die Software bietet einfache Grafik- und Text-Funktionen. Außerdem kann man Pfade vereinfachen und einen Daten-Check (offene Pfade?) durchführen.<br />
<br />
== Materialeinstellungen ==<br />
<br />
Bisher ausprobiert: Sperrholz 4 mm, Hartfaserplatte und Acrylglas 3 mm<br />
==== Referenz====<br />
<br />
==== Sperrholz 4mm====<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut ||80 %||20|| Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
<br />
<br />
==== Acrylglas 3mm====<br />
Bei durchsichtigen Materialien am besten spiegelverkehrt gravieren!<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut||40 %||20||Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
==== Hartfaserplatte 3mm====<br />
Inkscape-thunderlaser:<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Speed!!Power min!!Power max<br />
|-<br />
|Cut||10||80||100<br />
|-<br />
|Cut Shintaro||25||60||80<br />
|-<br />
|Mark||30||10||10<br />
|-<br />
|}<br />
<br />
==== Eurobox (Toom/Surplus systems, transparent) ====<br />
cut: 15, 70, 100 - besser weniger und 2x<br />
<br />
==== MDF ====<br />
<br />
==== Spiegel Acryl 3mm ====<br />
<br />
==== Wellpappe ====<br />
<br />
==== Goldkarton, beidseitg matt-gold (gibs beim Real) ====<br />
<br />
==== [https://de.wikipedia.org/wiki/Polyoxymethylen POM 4mm] ====<br />
<br />
==== Glas gravieren ====<br />
<br />
== CO₂-Laser 100W ==<br />
<br />
=== Was noch gefixt werden muss ===<br />
* Klappenschalter hat keine Rolle mehr<br />
* Klappenschalter kann von Front-Panel-Schalter überbrückt werden<br />
* Klappenschalter wirkt nicht direkt auf das Lasernetzteil<br />
* Abluftschlauch an der Seite ist evtl. ungünstig<br />
* Abluft per Nachlaufsteuerung anschliessen<br />
* Klappen entscheppern/abdichten<br />
* Sicherheitsschalter evtl. auch in Front-Tür bauen<br />
* Schläuche für Wasser und Luft verlängern (andere kaufen)<br />
<br />
Laser Steuerung<br />
[[Datei:LasetSteuerungChina.jpg|200px]]<br />
<br />
=== Was schon ein bisschen gefixt wurde===<br />
* Steps/mm Einstellungen<br />
** Dazu einfach RDWorks per USB verbinden, unter File/Vendor Settings (Passwort: RD8888) gibt es für jede Achse Steps/mm. (unter dem ... Menü können auch direkt gemessene vs. geschnittene Werte eingetragen werden und die Steps werden automatisch berechnet.<br />
* Frontschlitze optisch undurchlässig machen - 17.09.18<br />
<br />
== Reverse Engineering ==<br />
* Laser horcht auf UDP-Ports 50200 und 50207 - evtl. müssen sich diese aber im gleichen 255.255.255.0-Subnetz befinden: https://github.com/jnweiger/ruida-laser/blob/master/doc/protocol.md<br />
* Weitere infos:<br />
** https://wiki.fablab-nuernberg.de/w/Nova_35<br />
** http://www.thunderlaser.com/laser-download<br />
** https://github.com/kkaempf/ruida<br />
** https://github.com/jnweiger/ruida-laser<br />
** https://github.com/jnweiger/ruida-laser/blob/master/doc/laser-nova35-rdworks.md<br />
<br />
== Nützliches ==<br />
Link für Infos zu Lasermaterial<br />
http://atxhackerspace.org/wiki/Laser_Cutter_Materials<br />
<br />
Laser Pfad justieren:<br />
https://www.youtube.com/watch?v=W5390ajG_0k<br />
<br />
==Fotos==<br />
<gallery caption="Foto 05.09.2018"><br />
Datei:Neuer_CO2-Laser.jpg|Neuer 100W-CO2-Laser<br />
</gallery><br />
<br />
==Screens Installation==<br />
<gallery caption="Windows 10"><br />
Datei:2020-01-13 21 59 25-Bonjour.png<br />
Datei:2020-01-13 22 01 11-VirtualHereUI.png<br />
Datei:2020-01-13 22 02 20-VirtualHereUI.png<br />
Datei:2020-01-13 22 03 05-VirtualHereUI.png<br />
Datei:2020-01-13 22 16 33-RDWorksV8Uninstall.png<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Holz&diff=10418Holz2019-03-09T03:04:30Z<p>Hephaisto: Die Seite wurde neu angelegt: „== Sperrholz Arten == 500px Von oben nach unten: * ? * Buche * Ahorn? * Pappel?“</p>
<hr />
<div>== Sperrholz Arten ==<br />
<br />
[[Datei:SperrholzLaser.jpg|500px]]<br />
<br />
Von oben nach unten:<br />
* ?<br />
* Buche<br />
* Ahorn?<br />
* Pappel?</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:SperrholzLaser.jpg&diff=10417Datei:SperrholzLaser.jpg2019-03-09T01:37:01Z<p>Hephaisto: Sperrholzplatten für CO2-Laser</p>
<hr />
<div>Sperrholzplatten für CO2-Laser</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Reloaded:_CO%E2%82%82-Laser_2.0&diff=10416Reloaded: CO₂-Laser 2.02019-03-09T00:30:04Z<p>Hephaisto: /* Materialeinstellungen */</p>
<hr />
<div>== '''!! ACHTUNG !!''' ==<br />
Der neue LASER ist noch nicht fertig eingerichtet. Die hier notierten Erfahrungen sind "work in progress". Es fehlt noch an allen möglichen Sicherheitseinrichtungen. Daher ist der Laser noch nicht für die Allgemeinheit freigegegeben.<br />
<br />
<br />
== 100W-CO₂-Laser Quick and Dirty HOW_TO ==<br />
Benötigte Software:<br />
* RD Works (ausprobiert: V8.1.21) http://www.thunderlaser.com/laser-download<br />
* evtl. Inkscape http://www.inkscape.org/de/ mit Plugin https://github.com/jnweiger/inkscape-thunderlaser<br />
* Spezielles Visicut mit Thundelaser-Unterstützung: https://github.com/fablabnbg/VisiCut/releases<br />
<br />
== RD Works unter Linux installieren ==<br />
<br />
RD Works lässt sich unter Linux Mint mittels Wine installieren. Die Installationsdatei (.rar) auf dem Rechner speichern, entpacken und die RDWorksV8Setup8.01.21.exe mittels Rechtsklick "Öffnen mit... Wine-Windows-Programmstarter" installieren.<br />
Die Software lässt sich dann aus dem Startmenü (Wine-Ordner) öffnen.<br />
<br />
Verbindung zum Laser: Windows-Rechner lassen sich per USB anschließen, unter Linux noch keine Erfahrung damit.<br />
Unter Linux funktioniert die Verbindung per LAN. Dazu in der Software unter "Device -> Port Settings" ein neues Gerät anlegen "Add..." und "Web" auswählen und die IP-Adresse eingeben. '''Achtung: IP-Adresse noch nicht festgelegt.''' Der Laser muss anscheinend eine feste, manuell vergebene IP-Adresse bekommen. Bei den Tests wurde die IP 10.0.0.205 verwendet, diese kann aber jederzeit vom Router anderweitig vergeben werden. Eine feste Laser-IP muss noch eingerichtet werden. <br />
<br />
Die Verbindung zwischen Linux-Rechner und Lasersteuerung kam erst nach mehrmaligen Einstellungen und Ausprobieren zustande. Danach lief sie aber (zumindest einen Abend lang) stabil.<br />
<br />
<br />
== Bedienung RDWorks ==<br />
Es gibt ein paar "Handbuch"-PDFs zur Steuerung und zur Software.<br />
Die Software bietet einfache Grafik- und Text-Funktionen. Außerdem kann man Pfade vereinfachen und einen Daten-Check (offene Pfade?) durchführen.<br />
<br />
== Materialeinstellungen ==<br />
<br />
Bisher ausprobiert: Sperrholz 4 mm, Hartfaserplatte und Acrylglas 3 mm<br />
==== Referenz====<br />
<br />
==== Sperrholz 4mm====<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut ||80 %||20|| Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
<br />
<br />
==== Acrylglas 3mm====<br />
Bei durchsichtigen Materialien am besten spiegelverkehrt gravieren!<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Power!!Speed!!Bild<br />
|-<br />
|Cut||40 %||20||Auf Anhieb durch<br />
|-<br />
|}<br />
<br />
==== Hartfaserplatte 3mm====<br />
Inkscape-thunderlaser:<br />
{|class="wikitable" style="text-align: left; color: #333; padding:12px; vertical-align:top; "<br />
!Schnitt!!Speed!!Power min!!Power max<br />
|-<br />
|Cut||10||80||100<br />
|-<br />
|Mark||30||10||10<br />
|-<br />
|}<br />
<br />
<br />
==== MDF ====<br />
<br />
==== Spiegel Acryl 3mm ====<br />
<br />
==== Wellpappe ====<br />
<br />
==== Goldkarton, beidseitg matt-gold (gibs beim Real) ====<br />
<br />
==== [https://de.wikipedia.org/wiki/Polyoxymethylen POM 4mm] ====<br />
<br />
==== Glas gravieren ====<br />
<br />
== CO₂-Laser 100W ==<br />
<br />
=== Was noch gefixt werden muss ===<br />
* Klappenschalter hat keine Rolle mehr<br />
* Klappenschalter kann von Front-Panel-Schalter überbrückt werden<br />
* Klappenschalter wirkt nicht direkt auf das Lasernetzteil<br />
* Abluftschlauch an der Seite ist evtl. ungünstig<br />
* Abluft per Nachlaufsteuerung anschliessen<br />
* Klappen entscheppern/abdichten<br />
* Sicherheitsschalter evtl. auch in Front-Tür bauen<br />
* Schläuche für Wasser und Luft verlängern (andere kaufen)<br />
<br />
Laser Steuerung<br />
[[Datei:LasetSteuerungChina.jpg|200px]]<br />
<br />
=== Was schon ein bisschen gefixt wurde===<br />
* Steps/mm Einstellungen<br />
** Dazu einfach RDWorks per USB verbinden, unter File/Vendor Settings (Passwort: RD8888) gibt es für jede Achse Steps/mm. (unter dem ... Menü können auch direkt gemessene vs. geschnittene Werte eingetragen werden und die Steps werden automatisch berechnet.<br />
* Frontschlitze optisch undurchlässig machen - 17.09.18<br />
<br />
== Reverse Engineering ==<br />
* Laser horcht auf UDP-Ports 50200 und 50207 - evtl. müssen sich diese aber im gleichen 255.255.255.0-Subnetz befinden: https://github.com/jnweiger/ruida-laser/blob/master/doc/protocol.md<br />
* Weitere infos:<br />
** https://wiki.fablab-nuernberg.de/w/Nova_35<br />
** http://www.thunderlaser.com/laser-download<br />
** https://github.com/kkaempf/ruida<br />
** https://github.com/jnweiger/ruida-laser<br />
** https://github.com/jnweiger/ruida-laser/blob/master/doc/laser-nova35-rdworks.md<br />
<br />
== Nützliches ==<br />
Link für Infos zu Lasermaterial<br />
http://atxhackerspace.org/wiki/Laser_Cutter_Materials<br />
<br />
Laser Pfad justieren:<br />
https://www.youtube.com/watch?v=W5390ajG_0k<br />
<br />
==Fotos==<br />
<gallery caption="Foto 05.09.2018"><br />
Datei:Neuer_CO2-Laser.jpg|Neuer 100W-CO2-Laser<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Hackerspace_Ffm:Gemeinschaftsportal&diff=9199Hackerspace Ffm:Gemeinschaftsportal2017-04-16T18:23:50Z<p>Hephaisto: /* Besondere Werkzeuge im Hackerspace */ -> Ordnungssysteme</p>
<hr />
<div>Übersicht der aktuellen Aktivitäten und Gemeinschafts-Projekte<br />
<br />
== Laufende Aktivitäten ==<br />
* [[Termine]]<br />
* [[Projekte]]<br />
* [[Workshops]]<br />
* [[Vorträge]]<br />
* [[Einrichtung]]<br />
<br />
== Besondere Werkzeuge im Hackerspace ==<br />
Siehe [[:Kategorie:Werkzeug|Werkzeug-Seite]] - bitte die [[Ordnungssysteme]] beachten!<br />
<br />
== Hackerspace-FFM Konten ==<br />
* [https://github.com/hackffm GitHub]<br />
* [https://twitter.com/#!/hackffm @hackffm]<br />
<br />
== Vergünstigungen ==<br />
* [[Rabatte]]<br />
<br />
== Organisatorisches ==<br />
* [[Protokolle]]<br />
* [[Kooperation]]</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Ordnungssysteme&diff=9125Ordnungssysteme2017-04-16T17:54:32Z<p>Hephaisto: Die Seite wurde neu angelegt: „Entropiedestruktionssysteme == Farbkodierung für Werkzeug == right Alle transportablen Werkzeuge kr…“</p>
<hr />
<div>Entropiedestruktionssysteme<br />
<br />
== Farbkodierung für Werkzeug ==<br />
[[Image:AutoUpload 2017 04 16 19 53 01.jpg|200px|thumb|right]]<br />
<br />
Alle transportablen Werkzeuge kriegen eine aufgemalte Farbkodierung, in welchen Raum sie gehören. Bitte wieder in den entsprechenden Raum zurückbringen, oder besser gar nicht erst aus diesem entfernen.<br />
{| class="wikitable"<br />
| Farbe<br />
| Raum<br />
|-<br />
| style="background:#FFFF00; border-collapse:collapse;" | gelb<br />
| Lounge<br />
|-<br />
| style="background:#FF0000; border-collapse:collapse;" | rot<br />
| Werkstatt<br />
|-<br />
| ?<br />
| E-Labor<br />
|-<br />
|}<br />
<br />
<br />
== Tisch-Cache (E-Labor) ==<br />
[[Image:AutoUpload 2017 04 16 19 49 48.jpg|200px|thumb|right]]<br />
Wenn sich jemand über zuviel "wertvolle Bauteile" auf dem E-Labor-Tisch aufregt (was häufig passiert), kommen die Teile einfach in die erste Stage vom Tisch-Cache. Wenn die voll ist, kommt alles von der ersten Stage in die zweite Stage. Wenn die voll ist, wird der Inhalt weggeworfen.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9040BrickUsingMultipleModules2017-03-20T21:03:48Z<p>Hephaisto: /* Make Rhein-Main 2017 */</p>
<hr />
<div>BrickUsingMultipleModules (short: '''BUMM''') is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes], I was sure that this had to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round. Maybe someone will build a robot arm for that in the future.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Modules ==<br />
<br />
=== Gates module ===<br />
The gates module has 7 LEDs, 4 toggle switches and a push button (looking like a switch).<br />
Depending on the status of the LEDs, the toggle switches have to be set correctly, then the RUN button has to be pressed.<br />
There are two instances of the manual, which both evaluate to the same instructions.<br />
The one which gave the module its name has a big network of binary NAND/NOR gates which take the LEDs as inputs and give output levels that correspond to the switch states.<br />
For the less nerdy players, there is a second manual, which lists a lot of rules which reference other rules depending on the LED state.<br />
<br />
A random gate network is generated using python and visualized using PyGraphViz.<br />
Then all possible outcomes are calculated and placed in a big lookup table, which is stored on the arduino.<br />
The rules are created by reading the lookup table and pruning.<br />
Higher difficulties are achieved by creating larger networks, which depend on more LED states.<br />
<br />
=== Blink module ===<br />
The blink module has a red and a green LED, which blink in a specific pattern.<br />
Depending on this pattern, a push button below either the red or green LED has to be pressed.<br />
Correct solutions are taken from a lookup table (both on the arduino and in the manual).<br />
Higher difficulties require multiple iterations and increase the blink frequency and pattern length (and therefore lookup table size).<br />
<br />
=== Planned ===<br />
* PCB: Lots of resistors dumped onto a board. Find the correct pins to bridge using resistor color codes.<br />
* Balance: Two dots chase each other. One has randomly varying speed, the other's speed is controlled using a potentiometer. If one catches the other, it goes boom.<br />
* High stakes: Spray cold water onto the handler on explosion or failures. Alternative: One button which has to stay pressed the whole time (also makes handling harder) gets wired to a shocker.<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
Bringing a bomb mockup to a fair - what could possibly go wrong? BUMM was present on the [https://make-rhein-main.de/ Make Rhein-Main 2017]. There is also a short [https://streamable.com/bikcu clip].<br />
<br />
The BUMM was placed in a small chamber built just for this weekend. It is made of a wooden frame with black stretch foil. Of course, we also needed warning tape.<br />
Communication is done using a field telephone to the booth, where the manuals were located.<br />
As an eye catcher, we made a live video feed using extra crappy cables for an analog S-Video camera.<br />
<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera for live feed and an FF-OB/ZB field telephone to our booth<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery><br />
<br />
== Links ==<br />
* [https://github.com/hackffm/BrickUsingMultipleModules Github repository]</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9039BrickUsingMultipleModules2017-03-20T20:56:19Z<p>Hephaisto: plans</p>
<hr />
<div>BrickUsingMultipleModules (short: '''BUMM''') is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes], I was sure that this had to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round. Maybe someone will build a robot arm for that in the future.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Modules ==<br />
<br />
=== Gates module ===<br />
The gates module has 7 LEDs, 4 toggle switches and a push button (looking like a switch).<br />
Depending on the status of the LEDs, the toggle switches have to be set correctly, then the RUN button has to be pressed.<br />
There are two instances of the manual, which both evaluate to the same instructions.<br />
The one which gave the module its name has a big network of binary NAND/NOR gates which take the LEDs as inputs and give output levels that correspond to the switch states.<br />
For the less nerdy players, there is a second manual, which lists a lot of rules which reference other rules depending on the LED state.<br />
<br />
A random gate network is generated using python and visualized using PyGraphViz.<br />
Then all possible outcomes are calculated and placed in a big lookup table, which is stored on the arduino.<br />
The rules are created by reading the lookup table and pruning.<br />
Higher difficulties are achieved by creating larger networks, which depend on more LED states.<br />
<br />
=== Blink module ===<br />
The blink module has a red and a green LED, which blink in a specific pattern.<br />
Depending on this pattern, a push button below either the red or green LED has to be pressed.<br />
Correct solutions are taken from a lookup table (both on the arduino and in the manual).<br />
Higher difficulties require multiple iterations and increase the blink frequency and pattern length (and therefore lookup table size).<br />
<br />
=== Planned ===<br />
* PCB: Lots of resistors dumped onto a board. Find the correct pins to bridge using resistor color codes.<br />
* Balance: Two dots chase each other. One has randomly varying speed, the other's speed is controlled using a potentiometer. If one catches the other, it goes boom.<br />
* High stakes: Spray cold water onto the handler on explosion or failures. Alternative: One button which has to stay pressed the whole time (also makes handling harder) gets wired to a shocker.<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
Bringing a bomb mockup to a fair - what could possibly go wrong? BUMM was present on the [https://make-rhein-main.de/ Make Rhein-Main 2017]. There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera for live feed and an FF-OB/ZB field telephone to our booth<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery><br />
<br />
== Links ==<br />
* [https://github.com/hackffm/BrickUsingMultipleModules Github repository]</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9038BrickUsingMultipleModules2017-03-20T20:48:02Z<p>Hephaisto: </p>
<hr />
<div>BrickUsingMultipleModules (short: '''BUMM''') is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes], I was sure that this had to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round. Maybe someone will build a robot arm for that in the future.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Modules ==<br />
<br />
=== Gates module ===<br />
The gates module has 7 LEDs, 4 toggle switches and a push button (looking like a switch).<br />
Depending on the status of the LEDs, the toggle switches have to be set correctly, then the RUN button has to be pressed.<br />
There are two instances of the manual, which both evaluate to the same instructions.<br />
The one which gave the module its name has a big network of binary NAND/NOR gates which take the LEDs as inputs and give output levels that correspond to the switch states.<br />
For the less nerdy players, there is a second manual, which lists a lot of rules which reference other rules depending on the LED state.<br />
<br />
A random gate network is generated using python and visualized using PyGraphViz.<br />
Then all possible outcomes are calculated and placed in a big lookup table, which is stored on the arduino.<br />
The rules are created by reading the lookup table and pruning.<br />
Higher difficulties are achieved by creating larger networks, which depend on more LED states.<br />
<br />
=== Blink module ===<br />
The blink module has a red and a green LED, which blink in a specific pattern.<br />
Depending on this pattern, a push button below either the red or green LED has to be pressed.<br />
Correct solutions are taken from a lookup table (both on the arduino and in the manual).<br />
Higher difficulties require multiple iterations and increase the blink frequency and pattern length (and therefore lookup table size).<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
Bringing a bomb mockup to a fair - what could possibly go wrong? BUMM was present on the [https://make-rhein-main.de/ Make Rhein-Main 2017]. There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera for live feed and an FF-OB/ZB field telephone to our booth<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery><br />
<br />
== Links ==<br />
* [https://github.com/hackffm/BrickUsingMultipleModules Github repository]</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9037BrickUsingMultipleModules2017-03-20T20:27:55Z<p>Hephaisto: </p>
<hr />
<div>BrickUsingMultipleModules (short: '''BUMM''') is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes], I was sure that this had to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round. Maybe someone will build a robot arm for that in the future.<br />
<br />
[https://github.com/hackffm/BrickUsingMultipleModules Github repository]<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Modules ==<br />
<br />
=== Gates module ===<br />
The gates module has 7 LEDs, 4 toggle switches and a push button (looking like a switch).<br />
Depending on the status of the LEDs, the toggle switches have to be set correctly, then the RUN button has to be pressed.<br />
There are two instances of the manual, which both evaluate to the same instructions.<br />
The one which gave the module its name has a big network of binary NAND/NOR gates which take the LEDs as inputs and give output levels that correspond to the switch states.<br />
For the less nerdy players, there is a second manual, which lists a lot of rules which reference other rules depending on the LED state.<br />
<br />
A random gate network is generated using python and visualized using PyGraphViz.<br />
Then all possible outcomes are calculated and placed in a big lookup table, which is stored on the arduino.<br />
The rules are created by reading the lookup table and pruning.<br />
Higher difficulties are achieved by creating larger networks, which depend on more LED states.<br />
<br />
=== Blink module ===<br />
The blink module has a red and a green LED, which blink in a specific pattern.<br />
Depending on this pattern, a push button below either the red or green LED has to be pressed.<br />
Correct solutions are taken from a lookup table (both on the arduino and in the manual).<br />
Higher difficulties require multiple iterations and increase the blink frequency and pattern length (and therefore lookup table size).<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
Bringing a bomb mockup to a fair - what could possibly go wrong? BUMM was present on the [https://make-rhein-main.de/ Make Rhein-Main 2017]. There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera for live feed and an FF-OB/ZB field telephone to our booth<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9036BrickUsingMultipleModules2017-03-20T20:20:10Z<p>Hephaisto: </p>
<hr />
<div>BrickUsingMultipleModules (short: *BUMM*) is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes], I was sure that this had to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round. Maybe someone will build a robot arm for that in the future.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Modules ==<br />
<br />
=== Gates module ===<br />
The gates module has 7 LEDs, 4 toggle switches and a push button (looking like a switch).<br />
Depending on the status of the LEDs, the toggle switches have to be set correctly, then the RUN button has to be pressed.<br />
There are two instances of the manual, which both evaluate to the same instructions.<br />
The one which gave the module its name has a big network of binary NAND/NOR gates which take the LEDs as inputs and give output levels that correspond to the switch states.<br />
For the less nerdy players, there is a second manual, which lists a lot of rules which reference other rules depending on the LED state.<br />
<br />
A random gate network is generated using python and visualized using PyGraphViz.<br />
Then all possible outcomes are calculated and placed in a big lookup table, which is stored on the arduino.<br />
The rules are created by reading the lookup table and pruning.<br />
Higher difficulties are achieved by creating larger networks, which depend on more LED states.<br />
<br />
=== Blink module ===<br />
The blink module has a red and a green LED, which blink in a specific pattern.<br />
Depending on this pattern, a push button below either the red or green LED has to be pressed.<br />
Correct solutions are taken from a lookup table (both on the arduino and in the manual).<br />
Higher difficulties require multiple iterations and increase the blink frequency and pattern length (and therefore lookup table size).<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
Bringing a bomb mockup to a fair - what could possibly go wrong? BUMM was present on the [[Make Rhein-Main 2017]]. There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera for live feed and an FF-OB/ZB field telephone to our booth<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9033BrickUsingMultipleModules2017-03-20T19:59:59Z<p>Hephaisto: /* Pictures */</p>
<hr />
<div>BrickUsingMultipleModules (short: *BUMM*) is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes] I was sure that this has to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
=== Basic test video ===<br />
https://streamable.com/lxtuu<br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
BUMM was present on the [[Make Rhein-Main 2017]] - bringing a bomb mockup to a fair - what could possibly go wrong? There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera with live feed to our booth and an FF-OB/ZB field telephone<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=9032BrickUsingMultipleModules2017-03-20T19:38:09Z<p>Hephaisto: Switch to english, manuals, pictures from make</p>
<hr />
<div>BrickUsingMultipleModules (short: *BUMM*) is a riddle game themed around bomb defusals. After an evening of playing [http://www.keeptalkinggame.com/ Keep talking and nobody explodes] I was sure that this has to be transferred to hardware. The goal of defusing multiple modules is the same, but the hardware implementation calls for some serious changes. Cutting wires was out of the question, since nobody was found to replace them for a new round.<br />
<br />
== Pictures ==<br />
<br />
=== Front panels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und manipulation detector aka life counter (left), blink-module (right)<br />
Image:BUMM serial and gates front.jpg|Serial number display (left) und gates-module (right)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-module<br />
</gallery><br />
<br />
<br />
=== Backsides ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-module (left), serial number display (right)<br />
Image:BUMM countdown and md.jpg|Countdown und manipulation detector<br />
Image:BUMM blink module.jpg|Blink-module<br />
Image:BUMM module b backside.jpg|Gates-module before mounting<br />
</gallery><br />
<br />
<br />
=== Complete Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. Why cut the copper stripes if we only need 5 signals (GND, 5V, Tx, Rx, 12V) anyway?<br />
Image:BUMM speaker.jpg|Speaker for beeping and firmly mounted audio amplifier<br />
Image:BUMM bus ftdi.jpg|Bus backplane and usb-serial converter<br />
Image:BUMM powerpack.jpg|On the last Make Rhein-Main, we had lots of power outages. Not stopping this device!<br />
Image:BUMM gui.png|Remote control with countdown, life counter, serial number, configuration and status for each module<br />
</gallery><br />
<br />
== Background ==<br />
<br />
[[Image:BUMM block diagram.png|200px|thumb|right]]<br />
<br />
Each module has its own arduino and is connected to a parallel bus backplane ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu speaking 5V UART at 19200 baud]).<br />
Each module contains its own logic and only tells the gamemaster whether it has been defused and if any manipulations (mistakes) were detected.<br />
<br />
The gamemaster is a Raspberry Pi running a python script.<br />
Apart from the game logic and audio output, it opens a TCP socket which can be used to control the game remotely.<br />
The network protocol is based on tree structures serialized to JSON and terminated with NULL.<br />
<br />
All lookuptables and manuals are generated completely automatic from config files using python and make.<br />
<br />
All material, be it gamemaster scripts, arduino code, *.tex for manuals or svg files for lasercutting are available on [https://github.com/hackffm/BrickUsingMultipleModules github].<br />
<br />
== Manuals ==<br />
* [[Medium:BUMM manual en.pdf|Introduction]]<br />
* [[Medium:BUMM manual en b.pdf|Gates module]]<br />
* [[Medium:BUMM manual en d.pdf|Blink module]]<br />
* [[Medium:BUMMleicht.pdf|Eine Anleitung für Jünglinge (german)]]<br />
<br />
<br />
=== Make Rhein-Main 2017 ===<br />
BUMM was present on the [[Make Rhein-Main 2017]] - bringing a bomb mockup to a fair - what could possibly go wrong? There is also a short [https://streamable.com/bikcu clip].<br />
<gallery><br />
Image:BUMM MRM2017 chamber.jpg|Chamber for the BUMM<br />
Image:BUMM MRM2017.jpg|Inside the chamber there is also a video camera with live feed to our booth and an FF-OB/ZB field telephone<br />
Image:BUMM MRM notes.jpg|Lots of notes have been taken<br />
</gallery></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_MRM_notes.jpg&diff=9031Datei:BUMM MRM notes.jpg2017-03-20T19:36:32Z<p>Hephaisto: Notes taken on the Make Rhein-Main 2017</p>
<hr />
<div>Notes taken on the Make Rhein-Main 2017</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_module_b_backside.jpg&diff=9030Datei:BUMM module b backside.jpg2017-03-20T19:34:20Z<p>Hephaisto: Lots of superglue and flat cable on BUMM gates module.</p>
<hr />
<div>Lots of superglue and flat cable on BUMM gates module.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_manual_en.pdf&diff=9029Datei:BUMM manual en.pdf2017-03-20T18:52:58Z<p>Hephaisto: BUMM manual introduction</p>
<hr />
<div>BUMM manual introduction</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_manual_en_d.pdf&diff=9028Datei:BUMM manual en d.pdf2017-03-20T18:51:42Z<p>Hephaisto: BUMM manual for module d (blink).</p>
<hr />
<div>BUMM manual for module d (blink).</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_manual_en_b.pdf&diff=9027Datei:BUMM manual en b.pdf2017-03-20T18:49:00Z<p>Hephaisto: BUMM manual for module b (gates). There are two explanations which evaluate to the same instructions. Print out those you like more.</p>
<hr />
<div>BUMM manual for module b (gates). There are two explanations which evaluate to the same instructions. Print out those you like more.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_MRM2017.jpg&diff=9026Datei:BUMM MRM2017.jpg2017-03-20T18:40:41Z<p>Hephaisto: Inside the chamber</p>
<hr />
<div>Inside the chamber</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_MRM2017_chamber.jpg&diff=9025Datei:BUMM MRM2017 chamber.jpg2017-03-20T18:37:19Z<p>Hephaisto: Chamber made of wood and stretch foil built for the Make Rhein-Main 2017</p>
<hr />
<div>Chamber made of wood and stretch foil built for the Make Rhein-Main 2017</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_block_diagram.png&diff=9024Datei:BUMM block diagram.png2017-03-20T18:34:02Z<p>Hephaisto: </p>
<hr />
<div></div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=8948BrickUsingMultipleModules2017-03-06T22:57:06Z<p>Hephaisto: /* Bilder */</p>
<hr />
<div>BrickUsingMultipleModules (kurz: BUMM) ist ein Rätselspiel, das unter dem Theme "Bombenentschärfung" spielt. Angelehnt an [http://www.keeptalkinggame.com/ Keep talking and nobody explodes] geht es darum, unter Zeitdruck verschiedene Rätselmodule lösen, um eine Bombe rechtzeitig zu entschärfen.<br />
<br />
== Bilder ==<br />
<br />
=== Frontpanels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und Manipulationsdetektor (links), blink-Modul (rechts)<br />
Image:BUMM serial and gates front.jpg|Seriennummer-Anzeige (links) und gates-Modul (rechts)<br />
Image:BUMM in action countdown.jpg |Countdown<br />
Image:BUMM in action gates.jpg |gates-Modul<br />
</gallery><br />
<br />
<br />
=== Panelrückseite ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-Modul (links), Seriennummer-Anzeige (rechts)<br />
Image:BUMM countdown and md.jpg|Countdown und Manipulationsdetektor<br />
Image:BUMM blink module.jpg|Blink-Modul<br />
</gallery><br />
<br />
<br />
=== Fertiger Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. 5 Signale (GND, 5V, Tx, Rx, 12V) auf 10er-Pinheadern sorgen für bequemes Löten und Verkabeln :)<br />
Image:BUMM speaker.jpg|Lautsprecher und massiv befestigter Verstärker<br />
Image:BUMM bus ftdi.jpg|Busplatine von oben und USB<->seriell-Wandler<br />
Image:BUMM powerpack.jpg|Erfahrungsgemäß ist auf die Stromversorgung auf der Make kein Verlass...<br />
Image:BUMM gui.png|Fernsteuerung mit Countdown, MD-Status, Seriennummbern, Konfiguration und Status für jedes Modul<br />
</gallery><br />
<br />
== Technik ==<br />
Jedes Modul enthält einen Arduino (oder anderen Controller), der über einen gemeinsamen Bus (5V) via UART kommuniziert ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu Protokoll]). Dabei ist jedes Modul von der Logik her eigenständig und gibt nur an, ob es entschärft wurde und ob es eine Manipulation detektiert hat.<br />
Als Zentrale fungiert ein Raspberry Pi, auf dem ein Pythonscript mit der gesamten Gamelogik läuft. Neben der Buskommunikation stellt dieses auch einen TCP-Server bereit, über den der Brick ferngesteuert werden kann.<br />
<br />
== TODO ==<br />
Folgendes ist noch notwendig (was noch nicht geklärt ist und noch Hilfe braucht, ist fett).<br />
* WLAN (Raspi 3 coming?)<br />
<br />
=== [[Make Rhein-Main 2017]] ===<br />
Der Brick soll auf der [[Make Rhein-Main 2017]] in einer separaten Kammer untergebracht werden, aus der nur auf elektronischem Wege kommuniziert werden kann. <br />
* Kammer: Da vermutlich kein separater Raum zur Verfügung stehen wird, wäre es cool, eine kleine Kammer aufzubauen. Vermutlich wird es ein Rahmen aus Holz mit eingespannter Folie.<br />
* Zur Kommunikation zwischen den Spielern werden Feldtelefone eingesetzt werden.<br />
* Eine Videoübertragung nach außen, insbesondere für die Signalwirkung für potentielle neue Spieler.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_in_action_gates.jpg&diff=8947Datei:BUMM in action gates.jpg2017-03-06T22:55:40Z<p>Hephaisto: BUMM in action: gates module</p>
<hr />
<div>BUMM in action: gates module</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_in_action_countdown.jpg&diff=8946Datei:BUMM in action countdown.jpg2017-03-06T22:54:15Z<p>Hephaisto: BUMM in action: countdown timer</p>
<hr />
<div>BUMM in action: countdown timer</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=8945BrickUsingMultipleModules2017-03-06T22:50:29Z<p>Hephaisto: /* Bilder */</p>
<hr />
<div>BrickUsingMultipleModules (kurz: BUMM) ist ein Rätselspiel, das unter dem Theme "Bombenentschärfung" spielt. Angelehnt an [http://www.keeptalkinggame.com/ Keep talking and nobody explodes] geht es darum, unter Zeitdruck verschiedene Rätselmodule lösen, um eine Bombe rechtzeitig zu entschärfen.<br />
<br />
== Bilder ==<br />
<br />
=== Frontpanels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und Manipulationsdetektor (links), blink-Modul (rechts)<br />
Image:BUMM serial and gates front.jpg|Seriennummer-Anzeige (links) und gates-Modul (rechts)<br />
</gallery><br />
<br />
<br />
=== Panelrückseite ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-Modul (links), Seriennummer-Anzeige (rechts)<br />
Image:BUMM countdown and md.jpg|Countdown und Manipulationsdetektor<br />
Image:BUMM blink module.jpg|Blink-Modul<br />
</gallery><br />
<br />
<br />
=== Fertiger Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. 5 Signale (GND, 5V, Tx, Rx, 12V) auf 10er-Pinheadern sorgen für bequemes Löten und Verkabeln :)<br />
Image:BUMM speaker.jpg|Lautsprecher und massiv befestigter Verstärker<br />
Image:BUMM bus ftdi.jpg|Busplatine von oben und USB<->seriell-Wandler<br />
Image:BUMM powerpack.jpg|Erfahrungsgemäß ist auf die Stromversorgung auf der Make kein Verlass...<br />
Image:BUMM gui.png|Fernsteuerung mit Countdown, MD-Status, Seriennummbern, Konfiguration und Status für jedes Modul<br />
</gallery><br />
<br />
== Technik ==<br />
Jedes Modul enthält einen Arduino (oder anderen Controller), der über einen gemeinsamen Bus (5V) via UART kommuniziert ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu Protokoll]). Dabei ist jedes Modul von der Logik her eigenständig und gibt nur an, ob es entschärft wurde und ob es eine Manipulation detektiert hat.<br />
Als Zentrale fungiert ein Raspberry Pi, auf dem ein Pythonscript mit der gesamten Gamelogik läuft. Neben der Buskommunikation stellt dieses auch einen TCP-Server bereit, über den der Brick ferngesteuert werden kann.<br />
<br />
== TODO ==<br />
Folgendes ist noch notwendig (was noch nicht geklärt ist und noch Hilfe braucht, ist fett).<br />
* WLAN (Raspi 3 coming?)<br />
<br />
=== [[Make Rhein-Main 2017]] ===<br />
Der Brick soll auf der [[Make Rhein-Main 2017]] in einer separaten Kammer untergebracht werden, aus der nur auf elektronischem Wege kommuniziert werden kann. <br />
* Kammer: Da vermutlich kein separater Raum zur Verfügung stehen wird, wäre es cool, eine kleine Kammer aufzubauen. Vermutlich wird es ein Rahmen aus Holz mit eingespannter Folie.<br />
* Zur Kommunikation zwischen den Spielern werden Feldtelefone eingesetzt werden.<br />
* Eine Videoübertragung nach außen, insbesondere für die Signalwirkung für potentielle neue Spieler.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_gui.png&diff=8944Datei:BUMM gui.png2017-03-06T22:48:31Z<p>Hephaisto: BUMM control GUI</p>
<hr />
<div>BUMM control GUI</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=BrickUsingMultipleModules&diff=8943BrickUsingMultipleModules2017-03-06T22:29:52Z<p>Hephaisto: Bilder, aktueller Status</p>
<hr />
<div>BrickUsingMultipleModules (kurz: BUMM) ist ein Rätselspiel, das unter dem Theme "Bombenentschärfung" spielt. Angelehnt an [http://www.keeptalkinggame.com/ Keep talking and nobody explodes] geht es darum, unter Zeitdruck verschiedene Rätselmodule lösen, um eine Bombe rechtzeitig zu entschärfen.<br />
<br />
== Bilder ==<br />
<br />
=== Frontpanels ===<br />
<gallery><br />
Image:BUMM countdown blink front.jpg |Countdown und Manipulationsdetektor (links), blink-Modul (rechts)<br />
Image:BUMM serial and gates front.jpg|Seriennummer-Anzeige (links) und gates-Modul (rechts)<br />
</gallery><br />
<br />
<br />
=== Panelrückseite ===<br />
<gallery><br />
Image:BUMM serial and gates back.jpg|Gates-Modul (links), Seriennummer-Anzeige (rechts)<br />
Image:BUMM countdown and md.jpg|Countdown und Manipulationsdetektor<br />
Image:BUMM blink module.jpg|Blink-Modul<br />
</gallery><br />
<br />
<br />
=== Fertiger Brick ===<br />
<gallery><br />
Image:BUMM total side.jpg|<br />
Image:BUMM total back.jpg|<br />
Image:BUMM total corner.jpg|<br />
</gallery><br />
<br />
=== Details ===<br />
<gallery><br />
Image:BUMM bus backplane.jpg|Bus Backplane. 5 Signale (GND, 5V, Tx, Rx, 12V) auf 10er-Pinheadern sorgen für bequemes Löten und Verkabeln :)<br />
Image:BUMM speaker.jpg|Lautsprecher und massiv befestigter Verstärker<br />
Image:BUMM bus ftdi.jpg|Busplatine von oben und USB<->seriell-Wandler<br />
Image:BUMM powerpack.jpg|Erfahrungsgemäß ist auf die Stromversorgung auf der Make kein Verlass...<br />
</gallery><br />
<br />
== Technik ==<br />
Jedes Modul enthält einen Arduino (oder anderen Controller), der über einen gemeinsamen Bus (5V) via UART kommuniziert ([https://github.com/hackffm/BrickUsingMultipleModules/tree/master/bus_docu Protokoll]). Dabei ist jedes Modul von der Logik her eigenständig und gibt nur an, ob es entschärft wurde und ob es eine Manipulation detektiert hat.<br />
Als Zentrale fungiert ein Raspberry Pi, auf dem ein Pythonscript mit der gesamten Gamelogik läuft. Neben der Buskommunikation stellt dieses auch einen TCP-Server bereit, über den der Brick ferngesteuert werden kann.<br />
<br />
== TODO ==<br />
Folgendes ist noch notwendig (was noch nicht geklärt ist und noch Hilfe braucht, ist fett).<br />
* WLAN (Raspi 3 coming?)<br />
<br />
=== [[Make Rhein-Main 2017]] ===<br />
Der Brick soll auf der [[Make Rhein-Main 2017]] in einer separaten Kammer untergebracht werden, aus der nur auf elektronischem Wege kommuniziert werden kann. <br />
* Kammer: Da vermutlich kein separater Raum zur Verfügung stehen wird, wäre es cool, eine kleine Kammer aufzubauen. Vermutlich wird es ein Rahmen aus Holz mit eingespannter Folie.<br />
* Zur Kommunikation zwischen den Spielern werden Feldtelefone eingesetzt werden.<br />
* Eine Videoübertragung nach außen, insbesondere für die Signalwirkung für potentielle neue Spieler.</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_powerpack.jpg&diff=8942Datei:BUMM powerpack.jpg2017-03-06T22:21:07Z<p>Hephaisto: BUMM buffered power supply</p>
<hr />
<div>BUMM buffered power supply</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_bus_ftdi.jpg&diff=8941Datei:BUMM bus ftdi.jpg2017-03-06T22:20:17Z<p>Hephaisto: BUMM bus backplane and ftdi usb<->serial converter</p>
<hr />
<div>BUMM bus backplane and ftdi usb<->serial converter</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_speaker.jpg&diff=8940Datei:BUMM speaker.jpg2017-03-06T22:19:16Z<p>Hephaisto: BUMM Speaker and amplifier</p>
<hr />
<div>BUMM Speaker and amplifier</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_total_corner.jpg&diff=8939Datei:BUMM total corner.jpg2017-03-06T22:09:49Z<p>Hephaisto: BUMM</p>
<hr />
<div>BUMM</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_total_back.jpg&diff=8938Datei:BUMM total back.jpg2017-03-06T22:08:47Z<p>Hephaisto: BUMM Rückansicht</p>
<hr />
<div>BUMM Rückansicht</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_total_side.jpg&diff=8937Datei:BUMM total side.jpg2017-03-06T22:07:13Z<p>Hephaisto: Seitenansicht BUMM</p>
<hr />
<div>Seitenansicht BUMM</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_serial_and_gates_front.jpg&diff=8936Datei:BUMM serial and gates front.jpg2017-03-06T21:48:35Z<p>Hephaisto: BUMM serial number display (left) and gates module (right)</p>
<hr />
<div>BUMM serial number display (left) and gates module (right)</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_countdown_blink_front.jpg&diff=8935Datei:BUMM countdown blink front.jpg2017-03-06T21:47:33Z<p>Hephaisto: BUMM countdown and manipulation detector (left) and blink module (right).</p>
<hr />
<div>BUMM countdown and manipulation detector (left) and blink module (right).</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_bus_backplane.jpg&diff=8934Datei:BUMM bus backplane.jpg2017-03-06T21:45:10Z<p>Hephaisto: Backplane for bus. 5 signals: GND, 5V, Rx, Tx and (optional) 12V on 10 pin headers make for easy soldering :)</p>
<hr />
<div>Backplane for bus. 5 signals: GND, 5V, Rx, Tx and (optional) 12V on 10 pin headers make for easy soldering :)</div>Hephaistohttp://www.hackerspace-ffm.de/wiki/index.php?title=Datei:BUMM_serial_and_gates_back.jpg&diff=8933Datei:BUMM serial and gates back.jpg2017-03-06T21:42:19Z<p>Hephaisto: Hephaisto lud eine neue Version von Datei:BUMM serial and gates back.jpg hoch</p>
<hr />
<div>BUMM gates module (left) and serial number display (right).</div>Hephaisto