https://wiki.munichmakerlab.de/api.php?action=feedcontributions&user=Jorgen&feedformat=atomThe Munich Maker Lab's Wiki - User contributions [en]2024-03-28T11:26:06ZUser contributionsMediaWiki 1.39.5https://wiki.munichmakerlab.de/index.php?title=Archive:Foam_cutter&diff=2809Archive:Foam cutter2017-08-29T04:59:09Z<p>Jorgen: add project template</p>
<hr />
<div>{{project<br />
|name = Foam Cutter<br />
|status = experimental<br />
|image = <br />
|description = t.b.d.<br />
|author = [[User:Demotape|Tobi]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
Discription and article content (t.b.d.)<br />
<br />
== Youtupe ==<br />
https://youtu.be/MVM_DZ3CdO0<br />
<br />
<br />
<br/><br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Scope_(R%26S_RTE)&diff=2774Archive:Scope (R&S RTE)2017-08-17T10:06:11Z<p>Jorgen: </p>
<hr />
<div><br />
{{AttentionBox<br />
| title=Borrowed Device<br />
| msg=Please use it with caution and only if you are familiar with scopes!<br />
}}<br />
<br />
We got a 2 Channel Scope ([1]) as permanent loan from Rohde & Schwarz.<br />
<br />
= Responsible User =<br />
[[User:Jorgen|Jorgen]] is working at Rohde & Schwarz and is responsible for the scope. <br />
<br />
If you have questions you can also ask [[User:Tiefpunkt|Severin]]<br />
<br />
= Using Rules =<br />
As you know, the device is just borrowed, it is really important that no one is allowed to modify the device in any way. <br />
<br />
Please just use it as it is. If there is a new firmware, Jorgen will do the update an Alignment.<br />
<br />
== You are familiar with scopes ==<br />
* use it on the workspace and do not move it out from its place<br />
* if you have good scenarios for measurements, please share your knowledge and add them to Instruction section.<br />
<br />
== You are new with scope ==<br />
* Please do not use the Scope by your own without any instructions<br />
* ask Jorgen ot Severin or someone who is already working with the scope<br />
<br />
= Features =<br />
The scope has a lot of SW options activated for us. We can use f.e. logic analysis and FFT sweeps from inside the scope. This section will be filled from time to time with the most important measurements and step by step description of how to use it.<br />
<br />
== Logic Analyzer ==<br />
t.b.d.<br />
<br />
== Cursor ==<br />
t.b.d.<br />
<br />
== Trigger ==<br />
t.b.d.<br />
<br />
== FFT? ==<br />
t.b.d.<br />
<br />
How to use example (see Instruction...t.b.d.)<br />
<br />
= Instruction =<br />
Maybe it is good make a kind of workshop or teaching for some members.<br />
<br />
Or we can fill in here some typical scenarios, to help other do their measurements. <br />
<br />
<br />
= Feedback & Issues =<br />
R&S is also really happy for every feedback we can give them to improve their Scopes:<br />
* create wish-list<br />
* write down all measurements which are not intuitive<br />
* write down bugs, ...<br />
<br />
==> This could be a good feedback for R&S which helps us to extend the borrow-deal.<br />
<br />
<br />
= Sources =<br />
* [1]: https://www.rohde-schwarz.com/us/product/rte-productstartpage_63493-54848.html<br />
<br />
[[Category:Inventory]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Sha2017&diff=2736Archive:Sha20172017-07-14T09:14:57Z<p>Jorgen: /* MuMaLab Village */ Jorgen is out :/ - have fun guys</p>
<hr />
<div>MuMaLab goes Sha2017<br />
<br />
== Quick facts ==<br />
* Location: Scoutinglandgoed in Zeewolde, 55km east of Amsterdam.<br />
* When: 4 - 8 August 2017<br />
* More Infos on the official website: [https://wiki.sha2017.org]<br />
<br />
Join our Flowdock channel #sha2017 if you have questions and to keep updated on the organization.<br />
<br />
== Who will go ==<br />
Here is a list of members who will go:<br />
<br />
=== MuMaLab Village ===<br />
(we might join the "königlich bayrisches Amstvillage")<br />
{| class=wikitable<br />
! Name !! Date of arrival !! Date of departure !! Notes<br />
|-<br />
| Matthias || Evening of August 3nd || Early on August 8th || +3kids & car<br />
|-<br />
| Cecile || August 4th, midday || undecided || by train<br />
|-<br />
| Nico || Evening of August 2nd || Early on August 9th || <br />
|-<br />
| Severin || ?? || ?? || + Fire truck<br />
|-<br />
| Peter || ?? || ?? || + Lisa, Raphael and Van<br />
|-<br />
| Andreas || ?? || ?? || +1<br />
|-<br />
| Adrian || ?? || ?? || And I need to get there somehow…<br />
|-<br />
| Paul || ?? || ?? || Same<br />
|}<br />
<br />
=== Other Village ===<br />
* ...<br />
<br />
== Not sure... ==<br />
Maybe I'll join, haven't decided yet<br />
* ...<br />
<br />
== Whats needed ==<br />
Fill in what you think we need or what you'll bring that others can benefit from<br />
* Tent<br />
* Tables<br />
* Stools<br />
* Switch<br />
* Power-Extensions (Nicolai)<br />
* Power-Distribution (Nicolai)<br />
* Blinkenlights!<br />
* Fridge or something to cool drinks/food?<br />
<br />
== Projects ==<br />
Fill in projects that you will bring and let others know if they can participate<br />
<br />
=== Local 42V DC power grid ===<br />
Feel free to join or just prepare your gadgets for 42V +/- 15% and be a consumer.<br />
More infos here: https://www.altpwr.net/<br />
* Nicolai<br />
** Ordered a single 16A connection to the grid<br />
** We need 25m of wire with 4mm2 to 16mm2 to connect to the grid<br />
** Got four of these: http://www.pollin.de/shop/dt/MjgzODQ2OTk-/Stromversorgung/Spannungswandler/DC_DC_Wandler/DC_DC_Wandler_LUCENT_915A.html<br />
* Severin<br />
** Thinking about buying a set of DC-DC Converters to 12V and 5V<br />
*** https://www.aliexpress.com/item/Waterproof-DC-DC-Step-Down-Converter-Reducer-48V-to-12V-20A-Buck-Module-Car-Power-Converter/32301052147.html<br />
*** https://www.aliexpress.com/item/48VDC-to-12VDC-10-AMP-60W-Golf-Cart-Voltage-Reducer-DC-DC-Step-Down-Converter/32227475625.html<br />
*** https://www.aliexpress.com/store/product/DC-48V-to-DC-5V-10A-Power-Converters-48-60V-to-5V-50W-DC-DC-Converter/1725318_32297965997.html<br />
** Any Idea on connectors?<br />
* Matthias<br />
** There are some recommendations: https://altpwr.net/dc-dc-test-results/ this seems to be good https://www.aliexpress.com/wholesale?catId=0&initiative_id=&SearchText=converter+48v+19v+190w</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Sha2017&diff=2675Archive:Sha20172017-06-19T10:09:37Z<p>Jorgen: /* MuMaLab Village */</p>
<hr />
<div>MuMaLab goes Sha2017<br />
<br />
== Quick facts ==<br />
* Location: Scoutinglandgoed in Zeewolde, 55km east of Amsterdam.<br />
* When: 4 - 8 August 2017<br />
* More Infos on the official website: [https://wiki.sha2017.org]<br />
<br />
Join our Flowdock channel #sha2017 if you have questions and to keep updated on the organization.<br />
<br />
== Who will go ==<br />
Here is a list of members who will go:<br />
<br />
=== MuMaLab Village ===<br />
(we might join the "königlich bayrisches Amstvillage")<br />
{| class=wikitable<br />
! Name !! Date of arrival !! Date of departure !! Notes<br />
|-<br />
| Matthias || ?? || ?? || +3kids & car<br />
|-<br />
| [[User:Jorgen|Jorgen]] || ?? || ?? || maybe no time - do anyone need a ticket?<br />
|-<br />
| Cecile || ?? || ?? || <br />
|-<br />
| Nico || Evening of August 2nd || Early on August 9th || <br />
|-<br />
| Severin || ?? || ?? || + Fire truck<br />
|-<br />
| Peter || ?? || ?? || + Lisa, Raphael and Van<br />
|-<br />
| Andreas || ?? || ?? || +1<br />
|}<br />
<br />
=== Other Village ===<br />
* ...<br />
<br />
== Not sure... ==<br />
Maybe I'll join, haven't decided yet<br />
* ...<br />
<br />
== Whats needed ==<br />
Fill in what you think we need or what you'll bring that others can benefit from<br />
* Tent<br />
* Tables<br />
* Stools<br />
* Switch<br />
* Power-Extensions (Nicolai)<br />
* Power-Distribution (Nicolai)<br />
* Blinkenlights!<br />
* Fridge or something to cool drinks/food?<br />
<br />
== Projects ==<br />
Fill in projects that you will bring and let others know if they can participate<br />
<br />
=== Local 42V DC power grid ===<br />
Feel free to join or just prepare your gadgets for 42V +/- 15% and be a consumer.<br />
More infos here: https://www.altpwr.net/<br />
* Nicolai<br />
** Ordered a single 16A connection to the grid<br />
** We need 25m of wire with 4mm2 to 16mm2 to connect to the grid<br />
** Got four of these: http://www.pollin.de/shop/dt/MjgzODQ2OTk-/Stromversorgung/Spannungswandler/DC_DC_Wandler/DC_DC_Wandler_LUCENT_915A.html<br />
* Severin<br />
** Thinking about buying a set of DC-DC Converters to 12V and 5V<br />
*** https://www.aliexpress.com/item/Waterproof-DC-DC-Step-Down-Converter-Reducer-48V-to-12V-20A-Buck-Module-Car-Power-Converter/32301052147.html<br />
*** https://www.aliexpress.com/item/48VDC-to-12VDC-10-AMP-60W-Golf-Cart-Voltage-Reducer-DC-DC-Step-Down-Converter/32227475625.html<br />
*** https://www.aliexpress.com/store/product/DC-48V-to-DC-5V-10A-Power-Converters-48-60V-to-5V-50W-DC-DC-Converter/1725318_32297965997.html<br />
** Any Idea on connectors?<br />
* Matthias<br />
** There are some recommendations: https://altpwr.net/dc-dc-test-results/ this seems to be good https://www.aliexpress.com/wholesale?catId=0&initiative_id=&SearchText=converter+48v+19v+190w</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Plenum&diff=2446Plenum2017-04-28T14:15:11Z<p>Jorgen: /* Stuff even further from the past */ add link to preview of updated rollup design</p>
<hr />
<div>The Plenum is a soon-to-be regular meeting of all people involved with the space to talk about things, and decide stuff.<br />
<br />
If you have stuff to add, go right ahead! Please sign your points with your name (by adding a "<nowiki>--~~~~</nowiki>" after your text).<br />
<br />
'''Next Plenum: ''' tbd<br />
<br />
<br />
== Topics for the next Plenum ==<br />
=== What are you currently working on? ===<br />
Tell everyone about your current projects.<br />
<br />
=== Thank you ===<br />
Let's say thank you to those who did some awesome stuff for the space since the last plenum<br />
<br />
=== Stuff from the past ===<br />
What was discussed at the last Plenum? What's the current status on those things? [[20170420 Plenum]]<br />
<br />
=== Anything you don't feel comfortable with in the space? What would you like to change or to be changed? ===<br />
Is there anything that's bothering you?<br />
<br />
<!-- NOTE IF YOU ARE ADDING A NEW POINT: Please make a separate topic, and don't add it under the "Anything you don't feel comfortable with in the space?". It's more for ad-hoc things that come up during the plenum --><br />
<br />
=== Stuff on a mission ===<br />
Sometimes, stuff from the space gets taken somewhere else. From now on, please make sure that stuff is maintained in [[Stuff on a mission]] --[[User:Tiefpunkt|Tiefpunkt]] ([[User talk:Tiefpunkt|talk]]) 22:56, 27 April 2017 (CEST)<br />
<br />
=== Stuff even further from the past ===<br />
There were a few things in the past plenums that got lost. Let's bring them back up. --[[User:Tiefpunkt|Tiefpunkt]] ([[User talk:Tiefpunkt|talk]]) 22:56, 27 April 2017 (CEST)<br />
<br />
* 23. - 25.06. Hack and Make vom FabLab Nürnberg ([[20170319_Plenum]])<br />
** Should we take part?<br />
* PM Sensors ([[20170309 Plenum]])<br />
** Still haven't bought them<br />
* Newsletter ([[20170302 Plenum]])<br />
** We still need more people to collect content<br />
* Sponsorship ([[20170119 Plenum]])<br />
** Any progress?<br />
* Buy a handheld label printer ([[20161211 Plenum]])<br />
** Any progress?<br />
* New roll up banner ([[20161009 Plenum]])<br />
** Any progress?<br />
** update the [https://github.com/munichmakerlab/design-stuff/blob/master/RollUp/MuMaLabAufsteller_preview.jpg design] to fit the spec --[[User:Jorgen|Jorgen]] ([[User talk:Jorgen|talk]]) 16:15, 28 April 2017 (CEST)<br />
* Mr Beam ([[20161009 Plenum]])<br />
** Any progress?<br />
* Better project documentation ([[20160612 Plenum]])<br />
** Any progress?<br />
[[Category:Plenum]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Make_Munich/2017&diff=2439Archive:Make Munich/20172017-04-24T04:40:23Z<p>Jorgen: /* Booth */ tourette WordClock and giant LED panel can not be fixed/finished until MakeMunich</p>
<hr />
<div>* 6.-7.5.2017<br />
* http://make-munich.de/<br />
* CFP: http://make-munich.de/mitmachen/callformakers/<br />
<br />
== Booth ==<br />
What should we display?<br />
<br />
* Open Source Furniture<br />
** Severin's models<br />
** Peter's chair<br />
* Peters Laser-Longboard<br />
* Stefan's Arcade-Machine<br />
* Tesla 3000<br />
* Jorgen & Jörg will bring some lights to catch the flies<br />
* Theos Laser Skateboard<br />
* Pauls wifi model train<br />
<br />
== Workshops ==<br />
Should we do workshops?<br />
<br />
* Severin Robot Building<br />
<br />
Ideas:<br />
* Synthesizers<br />
* Small but simple robots<br />
* Hebecon building? (will there be a hebecon?) ML: Yes! Please participate!!!<br />
<br />
== Bar ==<br />
We are providing the Bar again for the Make Munich 2017 and we will need some people to help us out with that:<br />
<br />
* To help us out at the Bar please register as a "Helfer" at: https://form.jotform.com/62742023185956 (select that you will be working at the Bar)<br />
* And for us to plan when you are available and for how long, head over here: http://doodle.com/poll/kdqdxqnu26rycuxq</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Make_Munich/2017&diff=2335Archive:Make Munich/20172017-03-12T16:10:45Z<p>Jorgen: /* Booth */ add fancy lights</p>
<hr />
<div>* 6.-7.5.2017<br />
* http://make-munich.de/<br />
* CFP: http://make-munich.de/mitmachen/callformakers/<br />
<br />
== Booth ==<br />
What should we display?<br />
<br />
* Open Source Furniture<br />
** Severin's models<br />
** Peter's chair<br />
* Peters Laser-Longboard<br />
* Stefan's Arcade-Machine<br />
* Tesla 3000<br />
* Jorgen and Jörg will bring some lights to catch the flies<br />
** 200x50cm LED Panel<br />
** some fancy WordClocks<br />
** maybe Jorgens 15x15 tourette WordClock<br />
<br />
== Workshops ==<br />
Should we do workshops?<br />
<br />
* Severin Robot Building<br />
<br />
Ideas:<br />
* Synthesizers<br />
* Small but simple robots<br />
* Hebecon building? (will there be a hebecon?) ML: Yes! Please participate!!!<br />
<br />
== Bar ==<br />
We are providing the Bar again for the Make Munich 2017 and we will need some people to help us out with that:<br />
* JanS<br />
* Jörg<br />
* Jorgen</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Make_Munich/2017&diff=2334Archive:Make Munich/20172017-03-12T16:06:16Z<p>Jorgen: /* Bar */</p>
<hr />
<div>* 6.-7.5.2017<br />
* http://make-munich.de/<br />
* CFP: http://make-munich.de/mitmachen/callformakers/<br />
<br />
== Booth ==<br />
What should we display?<br />
<br />
* Open Source Furniture<br />
** Severin's models<br />
** Peter's chair<br />
* Peters Laser-Longboard<br />
* Stefan's Arcade-Machine<br />
* Tesla 3000<br />
<br />
== Workshops ==<br />
Should we do workshops?<br />
<br />
* Severin Robot Building<br />
<br />
Ideas:<br />
* Synthesizers<br />
* Small but simple robots<br />
* Hebecon building? (will there be a hebecon?) ML: Yes! Please participate!!!<br />
<br />
== Bar ==<br />
We are providing the Bar again for the Make Munich 2017 and we will need some people to help us out with that:<br />
* JanS<br />
* Jörg<br />
* Jorgen</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Scope_(R%26S_RTE)&diff=2227Archive:Scope (R&S RTE)2017-02-02T05:17:41Z<p>Jorgen: /* Features */ add some additional info about features...</p>
<hr />
<div>{{AttentionBox<br />
| title=Where is the scope meanwhile the move?<br />
| msg=Jorgen got it back home and will bring it back after the move. <br/>If you need it for measurement, please contact Jorgen!<br />
}}<br />
<br />
<br /><br />
<br />
{{AttentionBox<br />
| title=Borrowed Device<br />
| msg=Please use it with caution and only if you are familiar with scopes!<br />
}}<br />
<br />
We got a 2 Channel Scope ([1]) as permanent loan from Rohde & Schwarz.<br />
<br />
= Responsible User =<br />
[[User:Jorgen|Jorgen]] is working at Rohde & Schwarz and is responsible for the scope. <br />
<br />
If you have questions you can also ask [[User:Tiefpunkt|Severin]]<br />
<br />
= Using Rules =<br />
As you know, the device is just borrowed, it is really important that no one is allowed to modify the device in any way. <br />
<br />
Please just use it as it is. If there is a new firmware, Jorgen will do the update an Alignment.<br />
<br />
== You are familiar with scopes ==<br />
* use it on the workspace and do not move it out from its place<br />
* if you have good scenarios for measurements, please share your knowledge and add them to Instruction section.<br />
<br />
== You are new with scope ==<br />
* Please do not use the Scope by your own without any instructions<br />
* ask Jorgen ot Severin or someone who is already working with the scope<br />
<br />
= Features =<br />
The scope has a lot of SW options activated for us. We can use f.e. logic analysis and FFT sweeps from inside the scope. This section will be filled from time to time with the most important measurements and step by step description of how to use it.<br />
<br />
== Logic Analyzer ==<br />
t.b.d.<br />
<br />
== Cursor ==<br />
t.b.d.<br />
<br />
== Trigger ==<br />
t.b.d.<br />
<br />
== FFT? ==<br />
t.b.d.<br />
<br />
How to use example (see Instruction...t.b.d.)<br />
<br />
= Instruction =<br />
Maybe it is good make a kind of workshop or teaching for some members.<br />
<br />
Or we can fill in here some typical scenarios, to help other do their measurements. <br />
<br />
<br />
= Feedback & Issues =<br />
R&S is also really happy for every feedback we can give them to improve their Scopes:<br />
* create wish-list<br />
* write down all measurements which are not intuitive<br />
* write down bugs, ...<br />
<br />
==> This could be a good feedback for R&S which helps us to extend the borrow-deal.<br />
<br />
<br />
= Sources =<br />
* [1]: https://www.rohde-schwarz.com/us/product/rte-productstartpage_63493-54848.html<br />
<br />
[[Category:Inventory]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Scope_(R%26S_RTE)&diff=2225Archive:Scope (R&S RTE)2017-01-30T18:01:21Z<p>Jorgen: </p>
<hr />
<div>{{AttentionBox<br />
| title=Where is the scope meanwhile the move?<br />
| msg=Jorgen got it back home and will bring it back after the move. <br/>If you need it for measurement, please contact Jorgen!<br />
}}<br />
<br />
<br /><br />
<br />
{{AttentionBox<br />
| title=Borrowed Device<br />
| msg=Please use it with caution and only if you are familiar with scopes!<br />
}}<br />
<br />
We got a 2 Channel Scope ([1]) as permanent loan from Rohde & Schwarz.<br />
<br />
= Responsible User =<br />
[[User:Jorgen|Jorgen]] is working at Rohde & Schwarz and is responsible for the scope. <br />
<br />
If you have questions you can also ask [[User:Tiefpunkt|Severin]]<br />
<br />
= Using Rules =<br />
As you know, the device is just borrowed, it is really important that no one is allowed to modify the device in any way. <br />
<br />
Please just use it as it is. If there is a new firmware, Jorgen will do the update an Alignment.<br />
<br />
== You are familiar with scopes ==<br />
* use it on the workspace and do not move it out from its place<br />
* if you have good scenarios for measurements, please share your knowledge and add them to Instruction section.<br />
<br />
== You are new with scope ==<br />
* Please do not use the Scope by your own without any instructions<br />
* ask Jorgen ot Severin or someone who is already working with the scope<br />
<br />
= Features =<br />
* t.b.d.<br />
== Feature 1 (t.b.d.) ==<br />
t.b.d.<br />
<br />
How to use example (see Instruction...t.b.d.)<br />
<br />
= Instruction =<br />
Maybe it is good make a kind of workshop or teaching for some members.<br />
<br />
Or we can fill in here some typical scenarios, to help other do their measurements. <br />
<br />
<br />
= Feedback & Issues =<br />
R&S is also really happy for every feedback we can give them to improve their Scopes:<br />
* create wish-list<br />
* write down all measurements which are not intuitive<br />
* write down bugs, ...<br />
<br />
==> This could be a good feedback for R&S which helps us to extend the borrow-deal.<br />
<br />
<br />
= Sources =<br />
* [1]: https://www.rohde-schwarz.com/us/product/rte-productstartpage_63493-54848.html<br />
<br />
[[Category:Inventory]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Scope_(R%26S_RTE)&diff=2196Archive:Scope (R&S RTE)2017-01-20T11:52:17Z<p>Jorgen: initial page</p>
<hr />
<div>{{AttentionBox<br />
| title=Borrowed Device<br />
| msg= Please use it with caution and only if you are familiar with scopes!<br />
}}<br />
<br />
We got a 2 Channel Scope ([1]) as permanent loan from Rohde & Schwarz.<br />
<br />
= Responsible User =<br />
[[User:Jorgen|Jorgen]] is working at Rohde & Schwarz and is responsible for the scope. <br />
<br />
If you have questions you can also ask [[User:Tiefpunkt|Severin]]<br />
<br />
= Using Rules =<br />
As you know, the device is just borrowed, it is really important that no one is allowed to modify the device in any way. <br />
<br />
Please just use it as it is. If there is a new firmware, Jorgen will do the update an Alignment.<br />
<br />
== You are familiar with scopes ==<br />
* use it on the workspace and do not move it out from its place<br />
* if you have good scenarios for measurements, please share your knowledge and add them to Instruction section.<br />
<br />
== You are new with scope ==<br />
* Please do not use the Scope by your own without any instructions<br />
* ask Jorgen ot Severin or someone who is already working with the scope<br />
<br />
= Features =<br />
* t.b.d.<br />
== Feature 1 (t.b.d.) ==<br />
t.b.d.<br />
<br />
How to use example (see Instruction...t.b.d.)<br />
<br />
= Instruction =<br />
Maybe it is good make a kind of workshop or teaching for some members.<br />
<br />
Or we can fill in here some typical scenarios, to help other do their measurements. <br />
<br />
<br />
= Feedback & Issues =<br />
R&S is also really happy for every feedback we can give them to improve their Scopes:<br />
* create wish-list<br />
* write down all measurements which are not intuitive<br />
* write down bugs, ...<br />
<br />
==> This could be a good feedback for R&S which helps us to extend the borrow-deal.<br />
<br />
<br />
= Sources =<br />
* [1]: https://www.rohde-schwarz.com/us/product/rte-productstartpage_63493-54848.html<br />
<br />
[[Category:Inventory]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Sha2017&diff=2194Archive:Sha20172017-01-20T04:44:28Z<p>Jorgen: /* Whats needed */</p>
<hr />
<div><br />
= MuMaLab goes Sha2017 =<br />
<br />
== Quick facts ==<br />
* Location: Scoutinglandgoed in Zeewolde, 55km east of Amsterdam.<br />
* When: 4 - 8 August 2017<br />
* More Infos on the official website: [https://wiki.sha2017.org]<br />
<br />
Join our Flowdock channel #sha2017 if you have questions and to keep updated on the organization.<br />
<br />
== Who will go ==<br />
Here is a list of members who will go:<br />
<br />
=== MuMaLab Village ===<br />
(we might join the "königlich bayrisches Amstvillage")<br />
* Matthias (+3kids&car)<br />
* [[User:Jorgen|Jorgen]] (+1kid)<br />
* Cecile<br />
* Nicolai (at least part time)<br />
* Severin (+ Fire Truck)<br />
<br />
=== Other Village ===<br />
* ...<br />
<br />
== Not sure... ==<br />
Maybe I'll join, haven't decided yet<br />
* ...<br />
<br />
== Whats needed ==<br />
Fill in what you think we need or what you'll bring that others can benefit from<br />
* Tent<br />
* Tables<br />
* Stools<br />
* Switch<br />
* Power-Extensions (Nicolai)<br />
* Power-Distribution (Nicolai)<br />
* Blinkenlights!<br />
* Fridge or something to cool drinks/food?<br />
<br />
== Projects ==<br />
Fill in projects that you will bring and let others know if they can participate<br />
<br />
=== Local 42V DC power grid (https://www.altpwr.net/) ===<br />
* Nicolai</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Sha2017&diff=2176Archive:Sha20172017-01-17T16:01:36Z<p>Jorgen: format and add</p>
<hr />
<div><br />
= MuMaLab goes Sha2017 =<br />
<br />
== Quick facts ==<br />
* Location: Scoutinglandgoed in Zeewolde, 55km east of Amsterdam.<br />
* When: 4 - 8 August 2017<br />
* More Infos on the official website: [https://wiki.sha2017.org]<br />
<br />
Join our Flowdock channel #sha2017 if you have questions and to keep updated on the organization.<br />
<br />
== Who will go ==<br />
Here is a list of members who will go:<br />
<br />
=== MuMaLab Village ===<br />
(we might join the "königlich bayrisches Amstvillage")<br />
* Matthias (+3kids&car)<br />
* [[User:Jorgen|Jorgen]] (+1kid)<br />
* Cecile<br />
<br />
=== Other Village ===<br />
* ...<br />
<br />
== Not sure... ==<br />
Maybe I'll join, haven't decided yet<br />
* ...</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Exodus&diff=2042Archive:Exodus2016-12-04T16:32:59Z<p>Jorgen: /* possible locations */ typo</p>
<hr />
<div>{{project<br />
|name = Exodus<br />
|status = experimental<br />
|image = Exodus.jpg<br />
|description = we need new rooms and fast! <br />
|author = <br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
<br />
We have to leave the Siemenswerke by February so let's for a bigger, better, and more awesome space!!!<br />
<br />
== requirements ==<br />
* >100m² only for us or >140m² with the HuS<br />
* ~ 12€/m²<br />
* accessible for every member 24/7<br />
* Easily reachable via public transportation<br />
<br />
== possible locations ==<br />
<br />
=== Pasing ===<br />
<br />
Due to the Pasing Arcaden, a lot of shops had to leave the area. It's a bit far of, but there are lots of S-Bahn, Buses and a Tram going there, so it's about as easy to reach than the Siemenswerke.<br />
<br />
==== Properties ====<br />
* [https://www.immobilienscout24.de/expose/90141446 Multifunktionale Gewerbefläche bei W+W Hardware + Software GmbH]<br />
* [https://www.immobilienscout24.de/expose/91407960 alte Papierfabrik]<br />
<br />
=== Kunstpark Ost ===<br />
<br />
Back to the roots! The Werkbox³ is still there, and Werk 3 has opened.<br />
<br />
==== Properties ====<br />
* [http://www.werk3-muenchen.de Werk3]<br />
<br />
=== Westend ===<br />
<br />
<br />
<br />
Cool part of the city, some office space there. Not sure if it's not to expensive by now<br />
==== Properties ====<br />
* [http://www.mgh-muc.de/startseite/ Muenchner Gewerbehoefe, im Westend-Gewerbehof ist das FabLab.]<br />
<br />
=== Misc ===<br />
everywhere else<br />
==== Properties ====<br />
* [http://www.immonet.de/angebot/27472176?drop=lp&exproot=halle-lager-produktion Riesenräume in Untergiesing!]<br />
<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=MuMaBus&diff=2021MuMaBus2016-11-30T05:37:48Z<p>Jorgen: /* Topics */</p>
<hr />
<div>{{project<br />
|name = MuMaBus<br />
|status = experimental<br />
|image = <br />
|description = Bus to connect different devices in the lab and in the outside world <br />
|author = [[User:Tiefpunkt|tiefpunkt]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
The '''MuMaBus''' is a framework to connect different devices in the lab to each other and with outside services. This is currently done using [https://en.wikipedia.org/wiki/MQ_Telemetry_Transport MQTT].<br />
<br />
== Bus details ==<br />
* MQTT Broker: <code>mqtt.munichmakerlab.de</code><br />
** Note: Old nodes in the bus still use mqtt.tiefpunkt.com. Both brokers are bridged, so messages sent to one broker will be received by devices connected to the other as well. But new devices should always use mqtt.munichmakerlab.de<br />
* Port: 1883 (unencrypted), 8883 (SSL, using a CACert certificate)<br />
* Anonymous read access to <code>mumalab/#</code><br />
* For write access, contact [[User:Siedi|Matthias]] or [[User:Tiefpunkt|Severin]]<br />
<br />
=== Topics ===<br />
{| class="wikitable sortable"<br />
! Topic !! Description !! Possible values !! Devices<br />
|-<br />
| mumalab/DMX/1/controller || MAC and IP of DMX controller, comma separated || ||<br />
|-<br />
| mumalab/DMX/1/set || interface to set DMX channels || Accepts list of DMX id:state, comma separated. State is int between 0-255 (0 is off), or 1000 (toggle between on and off) ||<br />
|-<br />
| mumalab/DMX/1/state || list of current state of DMX ids with state, comma separeted || e.g.: "0:0,1:0,2:255,3:0,4:0,5:0,6:0,7:0,8:0,9:0,10:0,11:0" ||<br />
|-<br />
| mumalab/mccafe/1/buttonpress || Button presses on the fastfood remotes || e.g. "B2" || [[Fastfood Remotes]]<br />
|-<br />
| mumalab/mpd/command || Control the MPD via MQTT ||play, pause, next, previous, toggle, volume up, volume down || [[SpaceMusic]]<br />
|-<br />
| mumalab/room/status || Status of the lab || 0 for closed, 1 for open, ? for unknown || [[StartYourEngines]]<br />
|-<br />
| mumalab/room/door/status || Status of the door of the main room || 0 for closed, 1 for open, ? for unknown || <br />
|-<br />
| mumalab/otherroom/door || Status of the door of the other room || 0 for closed, 1 for open, ? for unknown || <br />
|-<br />
| mumalab/room/sensors/# || Sensors across the space || plain numeric values || [[SensorNode]]<br />
|-<br />
| mumalab/fridge/# || Lights and Sensors of the drinks fridge || tbd || [[Fridge]]<br />
|-<br />
| mumalab/room/lights/# || Light control system || tbd || [[LightsOut]]<br />
|-<br />
| mumalab/room/lights/hanging_lights/state || Hanging lights above the worktables || 0, 1 || [[LightsOut]]<br />
|-<br />
| mumalab/room/lights/whiteboard/state || Light tube around the whiteboard || 0, 1 || [[LightsOut]]<br />
|-<br />
| mumalab/room/lights/chandelier/state || Chandelier incl. RGB LED || 0, 1 || [[LightsOut]]<br />
|-<br />
| mumalab/room/lights/ceiling/command || RGB ceiling lights || off, red, green, blue, white || <br />
|-<br />
| mumalab/room/display || VFD Display in the space || Text || [[Cash Register Display]]<br />
|-<br />
| mumalab/room/ledpanel/#|| LED Panel from Jorgen || || [[LEDPanel]]<br />
|-<br />
| mumalab/audio/x32/ || Behringer x32 mixing desk (Mischpult) || || [[Behringer x32]]<br />
|-<br />
| mumalab/room/rcsockets || RF power socket control || "a,11111,00101,0" ||<br />
|}<br />
<br />
== DMX Devices ==<br />
{| class="wikitable"<br />
! Channel !! Device !! Details<br />
|-<br />
| 1-12 || DMX Switchpack || 1: Ceiling Lamps HuS<br />
<br />
2: Projector Wall<br />
<br />
3: Center<br />
<br />
4: MML<br />
|-<br />
| 13-18 || Laser || 13: Pattern<br />
<br />
14: Laser 1<br />
<br />
15: Laser 2<br />
<br />
16: Laser 3<br />
<br />
…<br />
|-<br />
| 20-55 || Ceiling LEDs || 20-22: r, g, b (Auf Seite des Regals)<br />
23-25: r, g, b<br />
<br />
…<br />
|-<br />
|}<br />
<br />
== RF power sockets ==<br />
Switched via MQTT connected basestation. Send the following to <code>mumalab/room/rcsockets</code>:<br />
<pre><br />
type,house_code,device_code,action<br />
</pre><br />
<br />
with the options<br />
* <code>type</code> - Type of RF sockets used, according to https://github.com/sui77/rc-switch/wiki/HowTo_OperateLowCostOutlets (which is missing type D). Only implemented types are "a" and "d" right now.<br />
* <code>house_code</code> and <code>device_code</code> - Whatever is set on the socket as address<br />
* <code>action</code> - 1 for switching on, 0 for switching off<br />
<br />
=== Currently placed sockets ===<br />
{| class="wikitable sortable"<br />
! Identifier !! Description !! Switched on/off with the space status<br />
|-<br />
| a,11111,00001 || Nebenraum door status || no<br />
|-<br />
| a,11111,00010 || BobbyCar and light tube above common room || yes<br />
|-<br />
| a,11111,00011 || Wall of Monitors (only screens, no orange pis). Also switches LED strip behind the screens || yes<br />
|-<br />
| d,a,1 || Alarm light || no<br />
|-<br />
| d,a,2 || Electronics corner || yes<br />
|}<br />
<br />
== Devices & Projects using the MuMaBus ==<br />
* [[StartYourEngines]]<br />
* [[SensorNode]]<br />
* [[LightsOut]]<br />
* [[Cash Register Display]]<br />
* [[Fastfood Remotes]]<br />
* [[SpaceMusic]]<br />
<br />
[[Category:Project]]<br />
[[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Fridge&diff=2020Fridge2016-11-30T05:36:56Z<p>Jorgen: initial version (@Peter please add your parts too)</p>
<hr />
<div>{{project<br />
|name=Fridge<br />
|status=experimental<br />
|author=[[User:Jorgen|Jorgen]], [[User:Tarwin|Peter]]<br />
|description=Lights and Sensors of the drinks fridge<br />
|download=https://github.com/munichmakerlab/refrigerator-lights/<br />
}}<br />
We pimped the drinks refrigerator a while agoe with lights and also with sensors to detect open door and temperature.<br />
<br />
== Lights ==<br />
You can switch the light effect pattern by MQTT - as well brightness, play Tetris etc...<br />
<br />
=== MQTT ===<br />
{| class=wikitable<br />
! Topic<br />
! Payload<br />
|-<br />
| mumalab/fridge/lights/config || reboot<br />
|-<br />
| mumalab/fridge/lights/mode || normal, alert, tetris<br />
|-<br />
| mumalab/fridge/lights/brightness || 0 to 255, up, down<br />
|-<br />
| mumalab/fridge/lights/background || black, plasma, snake, life, fire, lava, cloud, blackwhite, blackgreen<br />
|-<br />
| mumalab/fridge/lights/tetris || reset<br />
|-<br />
| mumalab/fridge/lights/tetris/move || left, right, down, rotate<br />
|}<br />
<br />
=== Node-Red Flowdock mapping ===<br />
<br />
{| class=wikitable<br />
! Action<br />
! Chat-Message<br />
|-<br />
| mode (normal / alert / tetris) || tbd. e.g. "fridge mode normal"<br />
|-<br />
| brightness (0-255 / up / down)) || tbd. e.g. "fridge brightness 100"<br />
|-<br />
| background effect (black / plasma / snake / life / fire / lava / cloud / blackwhite / blackgreen) || tbd. e.g. "fridge effect plasma"<br />
|-<br />
| tetris reset || tbd. e.g. "fridge tetris reset"<br />
|-<br />
| tetris move (left / right / up / down) || tbd. e.g. "fridge tetris move left"<br />
|}<br />
<br />
<br />
== Door ==<br />
We can detect fridge door open or close.<br />
<br />
=== MQTT ===<br />
{| class=wikitable<br />
! Topic<br />
! Payload<br />
|-<br />
| tbd. || tbd.<br />
|}<br />
<br />
=== Node-Red Flowdock mapping ===<br />
<br />
{| class=wikitable<br />
! Action<br />
! Chat-Message<br />
|-<br />
| tbd. || tbd. <br />
|}<br />
<br />
== Temperature ==<br />
Read out the temperature inside the drinks fridge and send it on MQTT message bus.<br />
<br />
=== MQTT ===<br />
{| class=wikitable<br />
! Topic<br />
! Payload<br />
|-<br />
| tbd. || tbd.<br />
|}<br />
<br />
=== Node-Red Flowdock mapping ===<br />
<br />
{| class=wikitable<br />
! Action<br />
! Chat-Message<br />
|-<br />
| tbd. || tbd. <br />
|}<br />
<br />
<br />
[[Category:Project]][[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=LaserCutter&diff=1905LaserCutter2016-10-10T06:09:21Z<p>Jorgen: /* ToDo */</p>
<hr />
<div>{{project<br />
|name = LaserCutter<br />
|status = experimental<br />
|image = <br />
|description = A Laser to cut stuff<br />
|author = <br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = [https://cloud.munichmakerlab.de/owncloud/public.php?service=files&t=bf26c735cd6cce536a7a2ca13ff20fd9 OwnCloud Share]<br />
}}<br />
<br />
We bought a laser! This page should be used for documenting stuff. <br />
<br />
<br />
'''Before starting, please read the [http://www.repairfaq.org/sam/safety.htm#safgui Safety Guidelines]'''<br />
<br />
Here is THE Manual for using the Laser Cutter: <br />
[[Using the Laser Cutter]]<br />
<br />
== Features ==<br />
* Big build area (Table Size: 1240 x 1000 mm / max Cutting Size: 1140 x 800 mm)<br />
* Red light mode for dry run (could need a second laser source ) - In Progress<br />
* 80W CO2 (see [1]), wavelength ≈ 10 microns<br />
* AWC608 Controller (see [3])<br />
<br />
== Components / Parts ==<br />
* Anywells AWC608 Laser Engraving Cutting Controller<br />
* Reci 80W CO2 Laser Tube<br />
* HY-T80 Laser PSU (http://www.jnhyec.com/en/productxx.asp?signid=90&proid=124}<br />
* Step Up Converter LM2596S (maximum input voltage 35V)<br />
<br />
== Handover == <br />
Videos: <br />
https://www.flickr.com/gp/peterfroehlich/37Y0h0<br />
<br />
Documentation: <br />
https://www.dropbox.com/sh/enh2fepkbfpnuyg/AAB81zYn4_yINY1aRJK2Tknsa?dl=0<br />
<br />
Pictures:<br />
https://plus.google.com/photos/102115038260468952916/albums/6138055661157233265?authkey=CMCZhOKk-_q35QE<br />
<br />
Wiring diagram:<br />
http://www.lightobject.info/download/DSP/LaserMachineWiringDiagram2.jpg<br />
<br />
LaserCAD:<br />
http://www.lightobject.info/viewtopic.php?f=55&t=2484<br />
<br />
== Knowledge == <br />
<br />
Laser saur manual (our cutter is NOT a laser saur, but there are some similarities:<br />
http://www.lasersaur.com/manual/<br />
<br />
Awesome source of knowledge about diy laser cutters:<br />
http://www.buildlog.net/<br />
<br />
Open Protect and water flow pins on controller / laser psu: <br />
http://www.lightobject.info/viewtopic.php?f=8&t=2015<br />
<br />
Lasersaur Mailing list: <br />
https://groups.google.com/forum/#!forum/lasersaur<br />
<br />
Introduction to CO2 lasers (read the safety part!) <br />
http://www.repairfaq.org/sam/laserco2.htm<br />
<br />
Controller pins:<br />
* OUT1: Output "Low" when XY start to move. OK to use this output to control air-pump On or Off as "Air-pump" take time to pump air out and slow<br />
* OUT2: Output "Low" when laser is firing: <br />
** Note that there is no output when XY is moving. It is ideal to use it to control an air-valve when use "Air compressor" as air-assist. Faster action<br />
** Use the same output to trigger a timer/counter for counting laser usage.<br />
* IN1: Door open protect (pulled to GND is closed) <br />
* Other I/O are "NA" and reserved for future expansion<br />
* Warning: TTL is 24V! Still, OUT1/2 are not powerful enough to drive a classical relais.<br />
<br />
== Calibration ==<br />
Safety warning: For calibration it is necessary to deactivate the sensors of the hatch. Therefore, wearing safety glasses is absolutely mandatory. Do not calibrate the laser with persons without safety glasses in the space.<br />
<br />
Calibration works well using sticky notes attached to the mirror mounts. Laser output is to be set to 20%. The laser is then fired manually (1-3 seconds) until a burn pattern becomes visible on the sticky note. There were always two burn marks when we were calibrating (Why?). The first calibration was done starting with the mirror next to the laser tube, then working the way toward the cutting area.<br />
<br />
* The laser spot is not circular: Most probable cause is the mirror directly above the lens.<br />
<br />
== ToDo == <br />
* <strike>wire up electronics and HAL sensor</strike> <done><br />
* <strike>Review power circuitry</strike> <done><br />
* <strike>Install FlowSensor in Chiller</strike> (was already installed)<br />
* <strike>Learn serial protocol of Chiller</strike> (Adrian) There is no serial :/<br />
* <strike>Complete outer case (to avoid escaping beam)</strike><br />
* <strike>Complete inner case (to avoid escaping exhaust gases)</strike> (Ricardo)<br />
* <strike>Build exhaust venting system </strike><br />
* <strike>Install gas cylinders to prop up hood (see [4] for choosing correct cylinders)</strike> (Eymen) <done><br />
* <strike>insert optical components </strike> <br />
* <strike>calibrate optical components [6]</strike> <br />
* <strike>connecting laser tube</strike> <br />
* <strike>inside illumination (white leds)</strike> <br />
* <strike>write manual and documentation</strike> (Eymen)<br />
* <strike>Control and safety panel</strike><br />
* RFID-Access-System ([[User:Jorgen|Jorgen]]) <in progress><br />
<br />
== Safety System panel == <br />
<br />
Code on [https://github.com/munichmakerlab/LaserSafety github]<br />
<br />
The Safety System runs on an Arduino, checks for<br />
<br />
* Water flow (Right before the laser tube, arduino counting pulses)<br />
* Chiller temp (measured before and after laser tube)<br />
* Exhaust system (differetial pressure; digital)<br />
* water leak under the chiller and in connection pipe on both sides (digital) (--> Heiko)<br />
<br />
* lid closed (reed contacts, directly connected to the controller --> Peter)<br />
<br />
--> Adrian, Heiko (Code review by Peter?)<br />
<br />
Maybe later:<br />
* Compressor running<br />
* power consumption (???)<br />
* ...<br />
<br />
== Sensors ==<br />
=== Waterleak ===<br />
[[File:Wassersensor.png]]<br />
<br />
[https://wiki.munichmakerlab.de/w/images/c/c2/Waterleak_Sensor_Schematic.pdf Schematic]<br />
<br />
== Consumables == <br />
<br />
Our laser tube: <br />
* Reci W3 80W Long life CO2<br />
<br />
Mirrors: <br />
* use copper-backed or molybdenum-backed mirrors. Do not use silicone backed mirrors. <br />
<br />
== Finance == <br />
When we have this thing running, we maybe need to think how we can get the costs back in. A 100W laser tube costs around 1200€ and has a lifetime of 6000-10000h. <br />
<br />
As discussed on the [[20150315_Plenum]], we will start with the following structure: <br />
* 2€ per 10min for members, 3€ for HuS, 4€ for non-members<br />
<br />
== Logging ==<br />
We installed a data logger to keep track of the usage hours. The logger tracks the time the air assist is on, which is just about the runtime the laser controller displays for a job. We want to use this to track the working hours of the laser tube, but if you want to check how long your laser cutting jobs took, feel free to checkt that here as well:<br />
<br />
* [http://10.10.20.64/cgi-bin/get_laser.pl All jobs] (new ones at the top)<br />
* [http://10.10.20.64/laser/ Daily reports]<br />
<br />
== Inspiration == <br />
Some connectors: <br />
- https://www.flickr.com/photos/satiredun/15868308421/sizes/o/<br />
'PCB' out of steel:<br />
- https://www.youtube.com/watch?v=OtZQoIheYcc<br />
<br />
== Additional Parts ==<br />
* Gas spring, Price 24€, Manufacturer Shockex, Part number 1181202100, Amazon [5], Force: 320 N, Outer diameter 1: 18 mm, outer diameter 2: 8 mm, Stroke length: 187 mm, Lenght: 468 mm<br />
<br />
== Sources ==<br />
* [1]: http://support.epiloglaser.com/article/8205/42827/<br />
* [2]: http://www.lasersaur.com/<br />
* [3]: http://www.lightobject.com/AWC608-Commercial-DSP-CO2-Laser-Engraving-Cutter-Controller-P321.aspx<br />
* [4]: http://www.gasfedershop.de/gasfeder_berechnung/<br />
* [5]: http://www.amazon.de/gp/product/B008MPR8W8<br />
* [6]: https://www.youtube.com/watch?v=Wpsi3tKJGMo<br />
[[Category:Project]] [[Category:Inventory]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Network&diff=1904Network2016-10-10T06:04:13Z<p>Jorgen: /* Allocated IP Addresses */ remove Jorgen LED Panel (broken, nobody to fix it)</p>
<hr />
<div>== WiFi ==<br />
* SSID: "munichmakerlab" or "munichmakerlab-5g"<br />
* Security: WPA2 Personal. Preshared Key is written on the whiteboard.<br />
* Mode: 802.11gn. No 802.11b. If you really really need to connect a 11Mbit/s only device, please talk to [[User:Tiefpunkt|tiefpunkt]]<br />
=== Hardware ===<br />
2 LANCOM L-320agn Wireless Access Points [http://www.lancom-systems.de/produkte/wireless-lan/indoor-wlan-access-points/lancom-l-320agn-wireless/lancom-l-320agn-wireless/], both manually configured (no WiFi controller)<br />
* mumawireless01<br />
** SSID "munichmakerlab"<br />
** 2.4 Ghz<br />
** Channel 1<br />
* mumawireless02<br />
** SSID "munichmakerlab" and "munichmakerlab-5g"<br />
** 5Ghz<br />
** Channel 108<br />
<br />
== Network Segment ==<br />
* Subnetmask: 255.255.0.0<br />
* Gateway: 10.10.0.1<br />
* DNS-Server: 10.10.0.10<br />
* DHCP-Server: 10.10.0.1<br />
<br />
=== Allocated IP Addresses ===<br />
{| class="wikitable" width="100%"<br />
! IP Address !! Name !! Description <br />
|-<br />
| 10.10.0.1 || Router || Router<br />
|-<br />
| 10.10.0.10 || ns1 || DNS server<br />
|-<br />
| 10.10.10.20-250 || || DHCP Range<br />
|-<br />
| 10.10.20.2 || FritzBox || VoIP Gateway (FritzBox 5050)<br />
|-<br />
| 10.10.20.10 || NyanPrint || [[Printers|Color Laser Printer]]<br />
|-<br />
| 10.10.20.25 || OctoPrint || [[PrinterBot|OctoPrint]]<br />
|-<br />
| 10.10.20.31 || tokyo.local || [[LEDPanel|LED-Panel eth0]]<br />
|-<br />
| 10.10.20.32 || tokyo.local || [[LEDPanel|LED-Panel wlan0]]<br />
|-<br />
| 10.10.20.35 || - || [[Behringer x32| x32 Mixer]]<br />
|-<br />
| 10.10.20.40 || heimdal || [[Doorlock|Door Lock RPi]]<br />
|-<br />
| 10.10.20.50 || PiPunkt || [[SpaceMusic|Space Status RPi]]<br />
|-<br />
| 10.10.20.61 || hawking || [[Fileserver]]<br />
|-<br />
| 10.10.20.62 || vmhost01 || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.63 || localhorst || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.64 || broker || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.65 || vmhost02 || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.66 || coreos10 || [[Docker]] Host<br />
|-<br />
| 10.10.20.67 || ILOvmhost03 || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.68 || vmhost03 || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.81 || LaserCutPC || [[LaserCutter]]<br />
|-<br />
| 10.10.20.82 || Terminal Server || ...<br />
|-<br />
| 10.10.20.90 || vpn-access || OpenVPN Gateway<br />
|-<br />
| 10.10.20.91 || backup || Backup operator<br />
|-<br />
| 10.10.20.150 || ewindow || [[Virtual Machines]]<br />
|}<br />
<br />
==== Not moved to new subnets yet ====<br />
{| class="wikitable" width="100%"<br />
| 192.168.0.240 || wifi || WiFi Connection X350 3D Printer<br />
|}<br />
<br />
==== Getting a fixed IP address ==== <br />
If you need a fixed IP address, choose one that's not taken yet, and enter it in the table above. Done. There's currently no dedicated DNS, we'll tackle that eventually.<br />
<br />
=== IPv6 ===<br />
<del>We got native IPv6 \o/</del> IPv6 is broken, unfortunately. There is IPv6 on the Freifunk WiFi, if you really need it.<br />
<br />
== DNS ==<br />
DNS is provided by a docker bind image (https://github.com/sameersbn/docker-bind).<br />
<br />
* Internal zone is "intern.munichmakerlab.de", not all hosts are in there yet<br />
* Server is maintained via Webmin, check http://www.damagehead.com/blog/2015/04/28/deploying-a-dns-server-using-docker/ for details<br />
* Server is not configured in DHCP yet, requires some testing first<br />
<br />
=== Hostnames ===<br />
When setting up a new machine for the space, the machine should be named after a famous scientist or mathematician whose birthday is today or near today. Use the following list to avoid already used hostnames:<br />
==== Used hostnames ====<br />
{| class="wikitable" width="100%"<br />
! Hostname !! Device Type !! Location <br />
|-<br />
| Doppler || PC || Workplace 2<br />
|-<br />
| Darwin || PC || Workplace 1<br />
|-<br />
| Heisenberg || PC || Spacemonitor near the entrance<br />
|}<br />
<br />
== Uplink ==<br />
We are connected to the internet via a Telekom V-DSL connection.<br />
<br />
== VPN ==<br />
You can connect to the lab remotely, via OpenVPN. If you need access, contact [[User:JanS|JanS]].<br />
<br />
[[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=20161009_Plenum&diff=190220161009 Plenum2016-10-10T05:28:59Z<p>Jorgen: /* Buying more stuff? */ design and order also some new sticker?</p>
<hr />
<div>Anwesend: Thomas E., Adrian, Heiko, Jan S., Paul, Sebastian, Musa, Eymen, Karim, Jan, Wolfgang, Thomas, Peter, Severin, Alex K.<br />
<br />
== What are you currently working on? ==<br />
Tell everyone about your current projects.<br />
<br />
* Thomas: Fräse, 3D-Drucker<br />
* Adrian: Mischpult in MQTT<br />
* Heiko: Wetterstation, Regenmessgeräte<br />
* Jan S.: Heizungssteuerung, parametrische Sortierboxen<br />
* Paul: Telegram-Bots, Mehr Audio im Space<br />
* Sebastian: Smart Home mit MQTT<br />
* Musa: Wiki-House-Modell mit Lasercutter nachbauen<br />
* Eymen: Autonome Sensoren auf ESP-Basis<br />
* Karim: Aquarium; Experimente mit Farben und ihrer Mischung, die sich unterschiedlich Verhalten je nach Polarisierung des Lösungsmittels.<br />
* Jan: Rennsimulator, Spacemonitor an MQTT und 3d-Drucker anbinden; Kugelbahn, Flaschenlampe<br />
* Wolfgang: Elektromotor; Lagersystem<br />
* Thomas: Roboter auf ESP umstellen<br />
* Peter: Hydroponisches Rad, IoV (Internet of Vacuums), Soundlaser, Mini Moving Heads<br />
* Severin: Feinstaubsensoren, Mini Moving Heads, IT Infrastructur in den Space umziehen<br />
* Alex: Open Hardware mit flexiblem PCB<br />
* Jorgen: WordClocks, RFID-Access for the Lasercutter<br />
<br />
== Thank you ==<br />
Let's say thank you to those who did some awesome stuff for the space since the last plenum<br />
<br />
* Matthias: IT stuff<br />
* ThomasE: Fräse, Drehmaschine, Getränke<br />
* Severin: Streetlife Festival anleiern, neuer DMX Controller<br />
* Peter: Steuershit<br />
* Christian: Für Williams Buch über AVR<br />
* Heiko: Regal für Sotierboxen<br />
* Jan: Für Hackathons <br />
* Jorgen: Tshirt designs! <br />
* Thomas: Netzteile! <br />
* Rene: Equipment<br />
* Liviu: Kompressor<br />
* Adrian: Kühlschrank saubermachen<br />
<br />
== Stuff from the past ==<br />
What was discussed at the last Plenum? What's the current status on those things?<br />
<br />
* IR Camera - No progress -> Eyman besorgt Samsung S3<br />
* Immer noch kein Mr. Beam<br />
* Neuer Staubsauger: Vorhanden<br />
* Multifactory passiert<br />
** zu wenig Beteiligung vom Space<br />
** eWindow-Software ist noch nicht fertig<br />
* Streetlife war cool<br />
* Getränkekasse entwickelt sich wieder ins Plus<br />
** Küche bekommt bald ne Rückwand aus der Getränkekasse<br />
* Lightning talks - noch nix passiert<br />
* Kompressor ist vorhanden, wird bald zusammengebaut<br />
* noch keine Monitor-Matrix<br />
[[20160814 Plenum]]<br />
<br />
== Anything you don't feel comfortable with in the space? What would you like to change or to be changed? ==<br />
Is there anything that's bothering you?<br />
<br />
* Allocation of Banners to events around the MunichMakerLab. During the Leopold/Streetlife Festival the banners were missing for the booth. A lot of people had difficulties finding the booth because of the understated decoration. The communication about the banner was also distressing. Eax.<br />
** weiteres Banner anschaffen. JA.<br />
<br />
* Vive konnte nicht für längere Zeit aufgebaut werden.<br />
** Problem: gemeinsamer Tisch war nicht frei<br />
** Zu viel Platzbedarf<br />
** Zeug wurde nicht komplett weggeräumt<br />
** --> Angekündigte Vive-Tage? Mehr koordination über Kalender<br />
<br />
== Road Trip! ==<br />
A couple of us are planning a trip to Calafou Europe's first and only eco tech village. Who wants to join? http://calafou.org/en/content/open-doors-journey-autumn-2016 -- [[User:Ragnaroek23|Ragnaroek23]] ([[User talk:Ragnaroek23|talk]]) 13:18, 9 October 2016 (CEST<br />
<br />
* Simon und Karim fahren eine Woche dahin, Ende des Monats. Wer mit will, soll Bescheid sagen<br />
* Flow im Flowdock<br />
<br />
== Non-members alone in the space ==<br />
What do we do when you're the last member to leave the space, but there are still other people present? --[[User:Tiefpunkt|Tiefpunkt]] ([[User talk:Tiefpunkt|talk]]) 23:51, 7 September 2016 (CEST)<br />
<br />
* Bisherige Handhabe: Das letzte Mitglied schickt beim Verlassen die Nicht-Mitglieder raus.<br />
* Nicht-Mitglieder als letzter weiterhin rausschicken? - Durch Abstimmung beschlossen. (n = N-1)<br />
<br />
== Handling of member access keys ==<br />
: Can we trust our members to not give away their keys to untrustworthy people? <br />
: --[[User:Tarwin|Tarwin]] ([[User talk:Tarwin|talk]]) 17:12, 30 August 2016 (CEST)<br />
<br />
* Schlüssel dürfen nicht weitergegeben werden, Ausnahmen können kommuniziert werden<br />
<br />
== Theft, openness and hospitality ==<br />
: The recent theft has shaken a lot of our members. Do we have to rethink our openness? Are the two even linked? <br />
: What can we do to not let this seep into our attitude towards our guests?<br />
: -- [[User:Ragnaroek23|Ragnaroek23]] ([[User talk:Ragnaroek23|talk]]) 00:29, 3 September 2016 (CEST)<br />
<br />
* Diebstahl passiert. Deal with it.<br />
<br />
== How do we handle unclear rules? ==<br />
: Proposition 1) Members make their own responsible decisions until the rule can be specified in the next plenum.<br />
: Proposition 2) Have the Vorstand decide for everyone until the next Plenum.<br />
: -- [[User:Ragnaroek23|Ragnaroek23]] ([[User talk:Ragnaroek23|talk]]) 00:29, 3 September 2016 (CEST)<br />
<br />
* Miteinander reden. Wenn keine Klarheit, auf Plenum verschieben. Wenn schnelle Entscheidung notwendig, entscheidet der Vorstand<br />
<br />
== Commercial use of the laser cutter ==<br />
: Do we need some kind of special handling of commercial use of the laser cutter? <br />
: Do we even want that? Maybe other rates? Or no difference at all? Where is the boundary of fair use? <br />
: --[[User:Tarwin|Tarwin]] ([[User talk:Tarwin|talk]]) 17:12, 30 August 2016 (CEST)<br />
<br />
* Kommerzielle Nutzung: Nichtkommerzielle Nutzung hat immer Vorrang<br />
* 5€/10min oder mehr<br />
* Spenden erwünscht<br />
* Überproportionale Nutzung des Spaces kommunizieren!<br />
<br />
<br />
== Tech literacy workshops for refugees with engineers without borders ==<br />
: My flatmate is an engineer without borders and asked me if we (Mumaland) could cooperate. They are planing to do a couple of tech workshops for refugees, and are looking for a space to host them. <br />
: I think its a great opportunity to extend some of our tried and tested openness to a new group of people, and to make interesting contacts to other nerds.<br />
: [[User:Ragnaroek23|Ragnaroek23]] ([[User talk:Ragnaroek23|talk]]) 00:08, 1 October 2016 (CEST)<br />
<br />
* 10-12 Teilnehmer<br />
* ein Wochenende<br />
* frühzeitig Ankündigen<br />
<br />
== Buying more stuff? ==<br />
* I'd like to play around with LoRaWAN, should we buy a LoRa Gateway for the space? Costs are about 300€. --[[User:Tiefpunkt|Tiefpunkt]] ([[User talk:Tiefpunkt|talk]]) 23:51, 7 September 2016 (CEST) - OK<br />
* Mr. Beam kaufen - Angebot einholen (JanS)<br />
* Motorschloss für Traforaum (-> eBay Schnäppchen?)<br />
* zweiter Rollup Banner (Jorgen) - ''Ok - will also design and order some new sticker... [[User:Jorgen|Jorgen]] ([[User talk:Jorgen|talk]]) 07:28, 10 October 2016 (CEST)''<br />
* Lötzinn (Peter)<br />
<br />
== Sonstiges ==<br />
* Essen im Kühlschrank labeln - Adrian macht ein Schild auf den Kühlschrank<br />
* Getränke-Kühlschrank _NUR_ für Space-Getränke, alles andere in den Küchen-Kühlschrank<br />
* Mehr Kommunikation!<br />
<br />
== Weltherrschaft ==<br />
Staubsauger ist da, Weltherrschaftsplanung wird im Geheimen fortgesetzt.<br />
<br />
17:57 - Ende</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1785Archive:WiFiJoystick2016-06-30T05:37:39Z<p>Jorgen: add github link</p>
<hr />
<div>[[File:WiFiJoystick_joystick.jpg|left|thumb|one of the big and heavy joysticks]]<br />
{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
<br style="clear:both;" /><br />
= source code =<br />
[https://github.com/munichmakerlab/WiFiJoystick github]<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
[[File:WiFiJoystick_pins_color.jpg|right|thumb|pins/contacts (see table for color codes)]]<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br style="clear:both;" /><br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| '''reboot'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| '''190'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| '''200'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| '''press'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| '''press'''<br />
|}<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1784Archive:WiFiJoystick2016-06-30T04:24:12Z<p>Jorgen: add picture of joystick</p>
<hr />
<div>[[File:WiFiJoystick_joystick.jpg|left|thumb|one of the big and heavy joysticks]]<br />
{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
[[File:WiFiJoystick_pins_color.jpg|right|thumb|pins/contacts (see table for color codes)]]<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br style="clear:both;" /><br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| '''reboot'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| '''190'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| '''200'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| '''press'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| '''press'''<br />
|}<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_joystick.jpg&diff=1783File:WiFiJoystick joystick.jpg2016-06-30T04:20:59Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1782Archive:WiFiJoystick2016-06-29T11:39:08Z<p>Jorgen: /* mqtt topics (receive) */</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| '''reboot'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| '''190'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| '''200'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| '''200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| '''150,100,200'''<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| '''press'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| '''press'''<br />
|}<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1781Archive:WiFiJoystick2016-06-29T11:31:19Z<p>Jorgen: /* mqtt messages (sending) */</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| '''press'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| '''press'''<br />
|}<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1780Archive:WiFiJoystick2016-06-29T11:31:08Z<p>Jorgen: /* mqtt messages (sending) */</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| '''press'''<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| '''press'''<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| '''press'''<br />
|}<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1779Archive:WiFiJoystick2016-06-29T11:30:30Z<p>Jorgen: /* mqtt topics (receive) */</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| press<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| press<br />
|}<br />
<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''solid,255,0,0''' <br/>(solid red)</p><p>'''once,0,255,255,5000''' <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>'''fade,255,0,0,2000,0,255,0''' <br/>(fade from red to green in 2s)</p><p>'''flash,0,0,255,500''' <br/>(flash from blue to black every 500ms)</p><p>'''flash,255,0,0,1000,255,255,0''' <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1778Archive:WiFiJoystick2016-06-29T11:29:40Z<p>Jorgen: /* mqtt topics (receive) */ extend examples</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| press<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| press<br />
|}<br />
<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>solid,255,0,0 <br/>(solid red)</p><p>once,0,255,255,5000 <br/>(pink for 5s)</p><br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| solid/once/flash/fade,red,green,blue(,interval,red2,green2,blue2)<br />
| <p>fade,255,0,0,2000,0,255,0 <br/>(fade from red to green in 2s)</p><p>flash,0,0,255,500 <br/>(flash from blue to black every 500ms)</p><p>flash,255,0,0,1000,255,255,0 <br/>(flash from red to yellow every 1s)</p><br />
|}<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1777Archive:WiFiJoystick2016-06-29T11:18:18Z<p>Jorgen: add IO expander section</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| press<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| press<br />
|}<br />
<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| (solid|once|flash|fade),red,green,blue(,interval,red2,green2,blue2)<br />
| solid,255,0,0<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| (solid|once|flash|fade),red,green,blue(,interval,red2,green2,blue2)<br />
| fade,255,0,0,2000,0,255,0<br />
|}<br />
<br />
<br />
= I2C IO expander =<br />
The ESP8266 has too less IO pins - so we will use IO expander ICs with serial interface (I²C-Bus):<br />
<br />
* [https://www.reichelt.de/index.html?ACTION=3;ARTICLE=140074;SEARCH=MCP%2023017-E/SP MCP 23017-E/SP (16-Bit I/O Expander with I²C-Bus Interface)]<br />
* [https://www.reichelt.de/PCF-8574-T/3/index.html?&ACTION=3&LA=446&ARTICLE=39885&artnr=PCF+8574+T&SEARCH=PCF+8574+T PCF 8574 T (8-Bit I/O Expander with I²C-Bus Interface)]<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1776Archive:WiFiJoystick2016-06-29T11:12:03Z<p>Jorgen: mqtt topics</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick & buttons =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/config<br />
| flags to configure<br />
| reboot<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/brightness<br />
| brightness from 0 to 255<br />
| 190<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/button1<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/button2<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/left<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/right<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/up<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/debounce/down<br />
| state1,state2,state3 (debounce delay in ms)<br />
| 150,100,200<br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/push<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/button2<br />
| press or release<br />
| press<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/button/left1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/left3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/right3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/up3<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down1<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down2<br />
| press or release<br />
| press<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/button/down3<br />
| press or release<br />
| press<br />
|}<br />
<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/color/led1<br />
| (solid|once|flash|fade),red,green,blue(,interval,red2,green2,blue2)<br />
| solid,255,0,0<br />
|- <br />
| WiFiJoystick/<CHIP-ID>/color/led2<br />
| (solid|once|flash|fade),red,green,blue(,interval,red2,green2,blue2)<br />
| fade,255,0,0,2000,0,255,0<br />
|}<br />
<br />
<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1775Archive:WiFiJoystick2016-06-29T10:49:51Z<p>Jorgen: add images and short description</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
This page shows a short description of how to create a WiFi enabled Gamepad / Joystick. The WiFiJoysticks can be used to play games on LED-Panels on events like makerfaires.<br />
<br />
[[File:WiFiJoystick_pins_color.jpg|left|thumb|pins/contacts (see table for color codes)]]<br />
<br style="clear:both;" /><br />
<br />
= joystick =<br />
<br />
== pin mapping ==<br />
{| class="wikitable"<br />
! function<br />
! state 1<br />
! state 2<br />
! state 3<br />
|-<br />
| Push Button<br />
| [[File:WiFiJoystick_pushbutton.png|50px]]<br />
|<br />
|<br />
|-<br />
| left<br />
| [[File:WiFiJoystick_left1.png|50px]]<br />
| [[File:WiFiJoystick_left2.png|100px]]<br />
| [[File:WiFiJoystick_left3.png|150px]]<br />
|-<br />
| right<br />
| [[File:WiFiJoystick_right1.png|50px]]<br />
| [[File:WiFiJoystick_right2.png|100px]]<br />
| [[File:WiFiJoystick_right3.png|150px]]<br />
|-<br />
| up<br />
| [[File:WiFiJoystick_up1.png|50px]]<br />
| [[File:WiFiJoystick_up2.png|100px]]<br />
| [[File:WiFiJoystick_up3.png|150px]]<br />
|-<br />
| down<br />
| [[File:WiFiJoystick_down1.png|50px]]<br />
| [[File:WiFiJoystick_down2.png|100px]]<br />
| [[File:WiFiJoystick_down3.png|150px]]<br />
|}<br />
<br />
== mqtt topics (receive) ==<br />
<br />
{| class="wikitable"<br />
! topic<br />
! payload<br />
! example<br />
|-<br />
| WiFiJoystick/<CHIP-ID>/debounce/push<br />
| debounce delay in ms<br />
| 200<br />
|- <br />
| <br />
| <br />
| <br />
|}<br />
<br />
== mqtt messages (sending) ==<br />
<br />
= push buttons =<br />
<br />
== mqtt topics (receive) ==<br />
<br />
== mqtt messages (sending) ==<br />
<br />
= status LEDs =<br />
<br />
== mqtt topics (receive) ==<br />
<br />
<br />
<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_down3.png&diff=1774File:WiFiJoystick down3.png2016-06-29T10:42:53Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_down2.png&diff=1773File:WiFiJoystick down2.png2016-06-29T10:42:37Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_down1.png&diff=1772File:WiFiJoystick down1.png2016-06-29T10:42:23Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_up3.png&diff=1771File:WiFiJoystick up3.png2016-06-29T10:42:04Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_up2.png&diff=1770File:WiFiJoystick up2.png2016-06-29T10:41:51Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_up1.png&diff=1769File:WiFiJoystick up1.png2016-06-29T10:41:38Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_right3.png&diff=1768File:WiFiJoystick right3.png2016-06-29T10:41:19Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_right2.png&diff=1767File:WiFiJoystick right2.png2016-06-29T10:41:05Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_right1.png&diff=1766File:WiFiJoystick right1.png2016-06-29T10:40:52Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_left3.png&diff=1765File:WiFiJoystick left3.png2016-06-29T10:39:22Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_left2.png&diff=1764File:WiFiJoystick left2.png2016-06-29T10:39:06Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_left1.png&diff=1763File:WiFiJoystick left1.png2016-06-29T10:38:36Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_pushbutton.png&diff=1762File:WiFiJoystick pushbutton.png2016-06-29T10:37:04Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=File:WiFiJoystick_pins_color.jpg&diff=1761File:WiFiJoystick pins color.jpg2016-06-29T10:08:39Z<p>Jorgen: </p>
<hr />
<div></div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=%22Man_m%C3%BCsste_mal%22&diff=1760"Man müsste mal"2016-06-28T11:36:15Z<p>Jorgen: /* Fix the MQTT to DMX converter */</p>
<hr />
<div>This sentence is uttered very often when it comes to upgrades in the space, so why not gather all the ideas here?<br />
<br />
== Tea stuff==<br />
It would be nice to have a couple of teas, pots and strainers for those of us who don't care for coffee and still like hot beverages<br />
<br />
== Fix the MQTT to DMX converter ==<br />
It freezes if you send too many queries too quickly.<br />
<br />
[[User:Jorgen|Jorgen]] ([[User talk:Jorgen|talk]]) 13:36, 28 June 2016 (CEST): Maybe use the same technique as I in other projects with MQTT: ring buffer for incoming messages.<br />
(non blocking). And inside the loop() method pop one message by the other and process them to DMX...<br />
<br />
== Laser safety system ==<br />
It still crashes sometimes, especially when using high power on the laser.<br />
<br />
The wiring to the arduino needs to be shielded better (at the ends), maybe add a low pass filter and add proper connectors.<br />
<br />
== Storage robot ==<br />
<br />
We want to use the cellar for storage, but fetching the boxes is tedious. We need a storage bot to get the boxes for us.<br />
<br />
== Music ==<br />
<br />
Link the shared folder to the music system, so that we can dump our music there for all to hear.<br />
<br />
== Volume control via Flowdock ==<br />
<br />
<br />
[[Category:Project]][[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:WiFiJoystick&diff=1759Archive:WiFiJoystick2016-06-28T11:29:32Z<p>Jorgen: initial page (t.b.d.)</p>
<hr />
<div>{{project<br />
|name = WiFiJoystick<br />
|status = experimental<br />
|image = <br />
|description = WiFi connected Joystick and Gamepad<br />
|author = [[User:jorgen|Jorgen]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
t.b.d.<br />
<br />
== t.b.d. ==<br />
<br />
<br />
== t.b.d. ==<br />
<br />
{| class="wikitable"<br />
! t.b.d.<br />
! t.b.d.<br />
|-<br />
| t.b.d.<br />
| t.b.d.<br />
|}<br />
<br />
<br />
[[Category:Project]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:Raketenwerfer&diff=1758Archive:Raketenwerfer2016-06-27T11:41:37Z<p>Jorgen: add wiki table (hint: please use english description...)</p>
<hr />
<div>{{project<br />
|name = USB Rocket Launcher<br />
|status = beta<br />
|image = <br />
|description = USB Rocket Launcher<br />
|author = [[User:Elias|Elias]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
<br />
[[Category:Project]]<br />
<br />
=Usb Raketenwerfer=<br />
<br />
Bei diesem Projekt geht es um die korrekte Ansteuerung eines USB-Raketenwerfers. Die Steuerungsplatine ist ausgebrannt, kann aber gut umfunktioniert werden. Geplant ist die Ansteuerung mithilfe eines Wemos D1<br />
<br />
{| class="wikitable"<br />
! color 1<br />
! color 2<br />
! function<br />
|-<br />
| orange<br />
| red<br />
| shoot motor<br />
|- <br />
| orange<br />
| white<br />
| shoot sensor<br />
|- <br />
| blue<br />
| white<br />
| sensor "up"<br />
|- <br />
| brown<br />
| white<br />
| sensor "down"<br />
|- <br />
| brown<br />
| red<br />
| motor up/down<br />
|}</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Network&diff=1623Network2016-02-15T05:50:29Z<p>Jorgen: /* Allocated IP Addresses */</p>
<hr />
<div>== WiFi ==<br />
* SSID: "munichmakerlab" or "munichmakerlab-5g"<br />
* Security: WPA2 Personal. Preshared Key is written on the whiteboard.<br />
* Mode: 802.11gn. No 802.11b. If you really really need to connect a 11Mbit/s only device, please talk to [[User:Tiefpunkt|tiefpunkt]]<br />
=== Hardware ===<br />
2 LANCOM L-320agn Wireless Access Points [http://www.lancom-systems.de/produkte/wireless-lan/indoor-wlan-access-points/lancom-l-320agn-wireless/lancom-l-320agn-wireless/], both manually configured (no WiFi controller)<br />
* mumawireless01<br />
** SSID "munichmakerlab"<br />
** 2.4 Ghz<br />
** Channel 1<br />
* mumawireless02<br />
** SSID "munichmakerlab" and "munichmakerlab-5g"<br />
** 5Ghz<br />
** Channel 108<br />
<br />
== Network Segment ==<br />
* Subnetmask: 255.255.0.0<br />
* Gateway: 10.10.0.1<br />
* DNS-Server: 10.10.0.1<br />
* DHCP-Server: 10.10.0.1<br />
<br />
=== Allocated IP Addresses ===<br />
{| class="wikitable" width="100%"<br />
! IP Address !! Name !! Description <br />
|-<br />
| 10.10.0.1 || Router || Router<br />
|-<br />
| 10.10.10.20-250 || || DHCP Range<br />
|-<br />
| 10.10.20.2 || FritzBox || VoIP Gateway (FritzBox 5050)<br />
|-<br />
| 10.10.20.10 || NyanPrint || [[Printers|Color Laser Printer]]<br />
|-<br />
| 10.10.20.25 || OctoPrint || [[PrinterBot|OctoPrint]]<br />
|-<br />
| 10.10.20.40 || heimdal || [[Doorlock|Door Lock RPi]]<br />
|-<br />
| 10.10.20.50 || PiPunkt || [[SpaceMusic|Space Status RPi]]<br />
|-<br />
| 10.10.20.61 || hawking || [[Fileserver]]<br />
|-<br />
| 10.10.20.62 || vmhost01 || [[Virtual Machines]]<br />
|-<br />
| 10.10.20.81 || LaserCutPC || [[LaserCutter]]<br />
|}<br />
<br />
==== Not moved to new subnets yet ====<br />
{| class="wikitable" width="100%"<br />
| 192.168.0.31 || tokyo.local || [[LEDPanel|LED-Panel eth0]]<br />
|-<br />
| 192.168.0.32 || tokyo.local || [[LEDPanel|LED-Panel wlan0]]<br />
|-<br />
| 192.168.0.240 || wifi || WiFi Connection X350 3D Printer<br />
|}<br />
<br />
==== Getting a fixed IP address ==== <br />
If you need a fixed IP address, choose one that's not taken yet, and enter it in the table above. Done. There's currently no dedicated DNS, we'll tackle that eventually.<br />
<br />
=== IPv6 ===<br />
<del>We got native IPv6 \o/</del> IPv6 is broken, unfortunately. There is IPv6 on the Freifunk WiFi, if you really need it.<br />
<br />
== Hostnames ==<br />
When setting up a new machine for the space, the machine should be named after a famous scientist or mathematician whose birthday is today or near today. Use the following list to avoid already used hostnames:<br />
=== Used hostnames ===<br />
{| class="wikitable" width="100%"<br />
! Hostname !! Device Type !! Location <br />
|-<br />
| Doppler || PC || Workplace 2<br />
|-<br />
| Darwin || PC || Workplace 1<br />
|-<br />
| Heisenberg || PC || Spacemonitor near the entrance<br />
|}<br />
<br />
== Uplink ==<br />
We are connected to the internet via a Telekom V-DSL connection.<br />
<br />
<br />
<br />
[[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=SpaceMusic&diff=1622SpaceMusic2016-02-15T05:46:27Z<p>Jorgen: change IP to new network ip range</p>
<hr />
<div>{{project<br />
|name = SpaceMusic<br />
|status = beta<br />
|image = <br />
|description = MPD Service to play music at the space<br />
|author = [[User:Jan|Jan]]<br />
|username = <br />
|version = <br />
|update = <br />
|platform = <br />
|license = <br />
|download = <br />
}}<br />
<br />
== What is it? ==<br />
We have this awesome sound system at the space. It is attached to a raspberry pi running an instance of mpd (music player daemon). Please DO NOT change ANYTHING on the mixing desk, the amplifiers or unplug any cables. You may die.<br />
<br />
== Settings ==<br />
* IP: 10.10.20.50<br />
* Port: 6600<br />
* Password: ''none''<br />
<br />
== How to use ==<br />
You can control mpd using a media player client software. We recommend gmpc for Mausschubsers and ncmpc for the nerds.<br />
<br />
<code>ncmpc -h 10.10.20.50</code><br />
<br />
== MQTT Control ==<br />
The MPD can also be controlled via MQTT. Therefore, we have a service running that translates MQTT messages into MPD commands. It's currently running on the [[PrinterBot]] machine (192.168.0.25), and the code that's used can be found at https://github.com/munichmakerlab/mqtt2mpd<br />
<br />
Topics<br />
* <code>mumalab/mpd/command</code>: understands the following commands: play, pause, next, previous, toggle, volume up, volume down<br />
<br />
[[Category:Infrastructure]]</div>Jorgenhttps://wiki.munichmakerlab.de/index.php?title=Archive:PrinterBot&diff=1621Archive:PrinterBot2016-02-15T05:44:35Z<p>Jorgen: change IP to new network ip range</p>
<hr />
<div><noinclude><br />
{{project<br />
|name = PrinterBot<br />
|status = Beta<br />
|image = <br />
|description = 3d Printers multiple octoprint machine<br />
|author = Ricardo Gomes<br />
|username = organom<br />
}}<div style="margin-right:300px;"><br />
<br />
Lab pc to run multiple instances of OctoPrint and connect to the 3d printers.<br />
<br />
== Hardware ==<br />
<br />
VoomPC-2 Enclosure [http://www.mini-box.com/VoomPC-Enclosure-2?sc=8&category=1544]<br />
Point of view nvidia ion mini-itx board - QuadCore Atom 1.6Ghz (from the free to use shelf)<br />
2 x HP 2Gb ddr2 800 ECC<br />
M1-ATX [http://www.mini-itx.com/store/information/m1-atx-manual.pdf]<br />
19V 3.4A laptop charger (from the free to use shelf)<br />
8gb SanDisk usb pen as main disk -- only class 4 device :(<br />
<br />
<br />
Board detail:<br />
<br />
[[File:PrinterBot-0.jpg|500px]]<br />
<br />
<br />
Installing debian:<br />
<br />
[[File:PrinterBot-1.jpg|250px]]<br />
<br />
user: mumalab<br />
ip: 10.10.20.25<br />
<br />
<br />
'''Installing Octopi:'''<br />
<br />
sudo apt-get install python-pip python-dev git<br />
sudo apt-get install python-setuptools<br />
git clone https://github.com/foosel/OctoPrint.git<br />
cd OctoPrint<br />
sudo python setup.py install<br />
sudo usermod -a -G tty,dialout mumalab<br />
<br />
Test Run: <br />
mkdir ~/.octoprint<br />
~/Octoprint/run<br />
<br />
Open http://10.10.20.25:5000 to check if it works<br />
<br />
'''Creating n-home folders for the octoprint instances:'''<br />
numInstances=9<br />
for ((i = 1; i<=$numInstances; i++)); do cp -rf .octoprint .octoprint$i; done<br />
rm -rf .octoprint<br />
<br />
'''Creating script to boot the instances:'''<br />
<br />
Edit /home/mumalab/octoprintInstances.sh<br />
<br />
#!/bin/sh<br />
OCTOPRINT_HOME=/home/mumalab/OctoPrint<br />
numInstances=4<br />
die () {<br />
echo >&2 "$@"<br />
exit 1<br />
}<br />
[ "$#" -eq 1 ] || die "Action start, stop or restart needs to be provided as argument."<br />
for i in $(seq 1 $numInstances);<br />
do<br />
echo "Octoprint$i - $1"<br />
$OCTOPRINT_HOME/run --daemon $1 --port 500$i --pid /tmp/octoprint$i --basedir ~/.octoprint$i<br />
done<br />
<br />
'''Creating startup script:'''<br />
<br />
Edit /etc/init.d/octoprintInstances<br />
<br />
#! /bin/sh <br />
### BEGIN INIT INFO<br />
# Provides: octoprintInstances<br />
# Required-Start: $remote_fs $syslog<br />
# Required-Stop: $remote_fs $syslog<br />
# Default-Start: 2 3 4 5<br />
# Default-Stop: <br />
# Short-Description: Octoprint multiple instances script<br />
### END INIT INFO<br />
case "$1" in<br />
start)<br />
echo "Starting instances:"<br />
su mumalab -c '/home/mumalab/octoprintInstances.sh start'<br />
;;<br />
restart|reload|force-reload)<br />
echo "Restarting instances:"<br />
su mumalab -c '/home/mumalab/octoprintInstances.sh restart'<br />
;;<br />
stop)<br />
echo "Stopping instances:"<br />
su mumalab -c '/home/mumalab/octoprintInstances.sh stop'<br />
;;<br />
*)<br />
echo "Usage: $0 start|stop" >&2<br />
exit 1<br />
;;<br />
esac<br />
exit 0<br />
<br />
Adding to the startup<br />
cd /etc/rc2.d/<br />
ln -s /etc/init.d/octoprintInstances S01octoprintInstances<br />
<br />
<br />
'''Creating customized dev entries for the printers:'''<br />
<br />
Foreach device connected do a <br />
dmesg | tail<br />
and check the port the device connected to and if the idVendor and idProduct can be seen right away.<br />
<br />
For the serial attribute, use: <br />
udevadm info -a -n /dev/ttyUSB0 | grep '{serial}'<br />
<br />
Next edit the /etc/udev/rules.d/10-local.rules and add something like the following.<br />
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="AE01DRVY", SYMLINK+="SolidDoodle"<br />
SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0483", ATTRS{serial}=="12345", SYMLINK+="Neo"<br />
SUBSYSTEM=="tty", ATTRS{idVendor}=="2341", ATTRS{idProduct}=="0042", ATTRS{serial}=="55434343633351710270", SYMLINK+="Ultimaker1"<br />
<br />
Reboot so that the devices are available.<br />
<br />
'''Instances customization:'''<br />
<br />
Add the following to the /home/mumalab/.octoprint1/config.yaml <br />
serial:<br />
port: /dev/Ultimaker1<br />
autoconnect: true<br />
additionalPorts:<br />
- /dev/Ultimaker1<br />
baudrate: 250000<br />
appearance:<br />
name: Ultimaker1<br />
color: orange<br />
system:<br />
actions:<br />
- name: Restart instance<br />
command: /home/mumalab/OctoPrint/run --daemon restart --port 5001 --pid /tmp/octoprint1 --basedir ~/.octoprint1<br />
action: restartInstance<br />
confirm: You are about to restart the instance.<br />
<br />
Add the following to the /home/mumalab/.octoprint2/config.yaml <br />
serial:<br />
port: /dev/Neo<br />
autoconnect: true <br />
additionalPorts:<br />
- /dev/Neo<br />
baudrate: 250000<br />
appearance:<br />
name: Neo<br />
color: blue<br />
system:<br />
actions:<br />
- name: Restart instance<br />
command: /home/mumalab/OctoPrint/run --daemon restart --port 5002 --pid /tmp/octoprint2 --basedir ~/.octoprint2<br />
action: restartInstance<br />
confirm: You are about to restart the instance.<br />
<br />
Add the following to the /home/mumalab/.octoprint3/config.yaml <br />
serial:<br />
port: /dev/SolidDoodle<br />
autoconnect: true<br />
additionalPorts:<br />
- /dev/SolidDoodle<br />
baudrate: 250000<br />
appearance:<br />
name: SolidDoodle<br />
color: white<br />
system:<br />
actions:<br />
- action: restartInstance<br />
command: /home/mumalab/OctoPrint/run --daemon restart --port 5003 --pid /tmp/octoprint3 --basedir ~/.octoprint3<br />
confirm: You are about to restart the instance.<br />
name: Restart instance<br />
<br />
== Issues ==<br />
One of the capacitor from m1-atx was damaged and was causing weird issues on bootup of the system <br />
--> Capacitor replaced and the system went back to normal.<br />
<br />
The initial installed cpu fan was too big leaving almost no space from the case ceiling, what was causing the cooling not to work properly <br />
--> Replaced with a smaller fan.<br />
<br />
Ethernet card is not recognized and seems not to be working at all.<br />
<br />
Some errors regarding not shielded usb ports (causes the system to sometimes hang when connecting usb devices)<br />
<br />
.<br />
[[Category:Project]]</div>Jorgen