Open Source Ecology - User contributions [en]

YouTube

2020-04-03T12:45:41Z

MarkDilley: move RightTOC and minor formatting, moving content away from syntax, mostly-ish

{{RightTOC}}
= Basics =
* A website with almost a monopoly on free video streaming
* OSE YouTube channel is [https://YouTube.com/user/OpenSourceEcology OpenSourceEcology]
* Mainly used by OSE for a PR channel, and a development channel (for meeting backups/for those who missed it etc, as well as build/event updates)
* Can also be used for Livestreaming, and things like user polls, and low level text based social media
* The comments section isn't well organised, but can be used (especially with low subscirber amounts) to answer questions people have

= In-Wiki Use =
== Adding Annotations and Links ==

[https://support.google.com/youtube/answer/6035690?rd=1 Google Support]

== Embedding Youtube in the Wiki ==

<nowiki>

<html>
<iframe width="560" height="315" src="
https://www.youtube.com/embed/NWRtvaJ8iHo
" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
</iframe>
</html>

</nowiki>

= Targeting a specific audience =
This section discusses some ways that may help to target a specific audience on YouTube. For general information about target audiences, see [[Target Audience for STEAM Camps]].

For example, an audience that is aligned with OSE is the audience for the YouTube channel:

* [https://www.youtube.com/watch?v=kNp0HETeq6M&list=PLLXfVEsLI-qRC_MAQZcVxpjtF7I1-H6Gw How To Make Everything]

== Algorhythm Exploits ==
* Essentially uses reverse engineering of the youtube algorhythm to maximise either exposure, monitization/ad revenue, or both
* Can be used semi-maliciously (Kids youtube, and spam bots...) BUT OSE will use it for exposure, and monitor itself to not go "too far"
** Also once a [[OSE Tipping Point | Tipping Point]] is reached the exposure becomes "self sustaining" , and this method becomes less relevant
* This also changes everytime the algorhythm is changed
* This is often covered by various people explaining their frustration with it, or by business/pr focused channels discussing the issue

=== Current Methods ===
* As of ~2020
* A naive way to bring OSE under the attention of this audience is to create a description of an OSE YouTube video that aligns with the audience of How To Make Everything (HTME). Then if you add links in the description to these channels, people that view the OSE video may receive recommendations of HTME videos. Hopefully, YouTube's recommendation algorithm picks that up and reverses the relation and starts recommending the OSE video to HTME audience.

'''However, this may not be very effective. Instead, the following links are probably much better in providing insight in how to target a specific audience:'''

* https://de.slideshare.net/AlexanderRus/how-to-rank-videos-on-youtube-and-in-google-search
* https://backlinko.com/how-to-rank-youtube-videos

== Networking ==
* This involves much more work, and a certain degree of luck
* Email/contact popular youtube channels in related feilds
** Ask if they could do a review (such as 3D Printing Channels and OSE's 3D Printer)
** Collaborate on Development (Any relevant devices, and any relevant projects)
** Get a shoutout
** Get them to join as a SME/Developer

= See Also =
* [[Marketing]]
* [[OSE's Social Media Accounts]]
* [[OSE Tipping Points]]

= Useful Links =
*

[[Category:Social Media]]

Open Source Leadership Summit Presentation

2019-01-23T17:25:16Z

MarkDilley: add RightTOC

= Presented in March 2018 =
{{RightTOC}}
= Video =
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/kQA4iqKBoyQ" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe></html>
=Slides=
<html><iframe src="https://docs.google.com/presentation/d/e/2PACX-1vT6aJsM0rXHUfrN0bykBlyb50WCWOBTiScj17mO-MfJxZXem-FXYU75B32wrJ9y_Ppe691d2HktMrqE/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

presentation - https://docs.google.com/presentation/d/1Vl-vwD4RTDxLcxXcLSZGo1SGcKQIWkhx74xRaujNDxM/edit#slide=id.g342608a30b_0_33

OS Leadership Summit Talk.

Translating Linux Success to Open Hardware

This presentation explores the challenges of scaling an open hardware business. The presenter's team builds open source industrial machines and houses - and they are pushing the limits towards non-proprietary development across the ~$70 trillion economy of the non-software, physical goods. Marcin will share his experience with the Global Village Construction Set experiment - an initiative to open source critical infrastructure machines for building modern civilization. As Linux has changed the world of software development to non-proprietary - what are the key ingredients and lessons learned for translating this model to physical goods - to shifting the proprietary and patented norm to open source? Marcin discusses Open Source Ecology's program aimed at this transition, and how OSE is approaching financial feedback loops in volunteer-based, non-proprietary hardware development.

Intended audience is anyone who is exploring open source business models in general. It is also for anyone who is interested in how open source business models apply beyond software to physical hardware - and what common models exist between both fields. The presentation should be especially interesting to ethical entrepreneurs committed to open source development that creates one's own competition. How does one still thrive in such a distributive enterprise, when the business model actively trains its own competition? Anyone considering open hardware entrepreneurship is likely to gain encouragement from an innovative model that is working for us. We are exploring business issues of operations, recruiting, marketing for an open organization, so this should shed light on common challenges for any open source startup.

Benefit to Ecosystem: Our work is a good example of an open source startup business model, but in hardware - so cross fertilization of ideas is likely. I think providing the hardware angle will help people frame open source business opportunities from a different light. We are engrossed in scalable, modular project architecture, so that we can learn a lot from open source software and vice versa. We are also exploring issues of licensing/franchising, recruiting, collaborative literacy, certifications of products and producers, business operations, etc - all of which appears to be common interest throughout. We are especially interested in large-scale collaboration, so I would like to glean insights from peers at the conference.

1/5/18 notes - re-position as the Bible for students. Aligning contributors is key. Parallel to Linux - free OS, here free Society OS. Align Dev Method to Recruiting (copy) to Fundamental approach (Pattern Language Primitives)

=OSE Bootstrap Funding Milestones=
See [[OSE Bootstrap Funding Milestones]].

*[[Presentation Legal Disclaimer]]

=Links=
*OSLS 18 website + schedule - [https://events.linuxfoundation.org/events/open-source-leadership-summit-2018/program/schedule/]
]

3D Printer Design Evolution

2016-07-28T21:35:37Z

MarkDilley: add RightTOC and move content away from list formatting

{{RightTOC}}
= Scalable Design =
[[Image:3dpscalable.jpg|400px]]

=Design Concept - The Belgian Waffle=

<html><iframe width="420" height="315" src="https://www.youtube.com/embed/mszmCJreQvw" frameborder="0" allowfullscreen></iframe></html>

= Working Doc =
Presentation link - https://docs.google.com/presentation/d/1hmLEnQIzeOh2ui_n9pmmJSzund5lKsBtjB2aOSfN4lw/edit#slide=id.p

<html><iframe src="https://docs.google.com/presentation/d/1hmLEnQIzeOh2ui_n9pmmJSzund5lKsBtjB2aOSfN4lw/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

= Links =
* [[D3D Development]]
* [[Michel Log]]

Template:OrigLang

2016-06-30T14:42:49Z

MarkDilley:

<div class="lang"><center><ul>
<li class="lang_main">[[{{NAMESPACE}}:{{PAGENAME}}|EN]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ar|<span title="العربية">AR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bg|<span title="български">BG</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bn|<span title="বাংলা">BN</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/cs|<span title="čeština">CS</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/de|<span title="Deutsch">DE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/el|<span title="Ελληνικά">EL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/eo|<span title="Esperanto">EO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/es|<span title="Español">ES</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/fr|<span title="Français">FR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/he|<span title="עברית">HE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hi|<span title="हिन्दी">HI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|<span title="Magyar">HU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hr|<span title="Hrvatski">HR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/it|<span title="Italiano">IT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ja|<span title="日本語">JA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/lt|<span title="lietuvių kalba">LT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/nl|<span title="Nederlands">NL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/no|<span title="Norsk">NO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pa|<span title="ਪੰਜਾਬੀ">PA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pl|<span title="Polski">PL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pt|<span title="Português">PT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ro|<span title="Română">RO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ru|<span title="русский">RU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/sv|<span title="Svenska">SV</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/th|<span title="ไทย">TH</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/tr|<span title="Türkçe">TR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/uk|<span title="українська">UK</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/vi|<span title="Tiếng Việt">VI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/zh-hans|<span title="中文 (Zhōngwén), 汉语, 漢語">ZH-HANS</span>]]</li>
<li class="lang_title">Article Title: {{PAGENAME}}</li>
</ul></center></div><includeonly>{{DISPLAYTITLE:{{{1|}}}|{{PAGENAME}}}}[[Category:EN]]</includeonly><noinclude>
== Usage ==
<nowiki>{{OrigLang}}</nowiki><br>

You may display a title to your page, that is different to the page name by <nowiki>OrigLang{{OrigLang|Title}}</nowiki>. On the translated pages, you have to '''change it to use the second Template [[Template:Lang]]'''.

== Documentation ==
This template should be added to all original english articles in the main namespace, at least to all that are or are supposed to be translated.

It shows the list of all languages an article should be translated to and also sets the correct, localised display title of the article.

=== Adding new Languages ===
Additional languages can easily be added here. You just need to add one line:

* put a new language link into the div container (please make sure they are alphabetically ordered):
:<nowiki><li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|HU]]</li></nowiki>

The subpages will automatically be used by different MediaWiki extensions which detect language settings in browsers or user preferences. The user will then automatically be redirected into the appropriate subpage.

=== Appearance ===
The CSS code for the div container of the class "lang" can be adopted in [[MediaWiki:Common.css]].
[[Category: Translation]]
</noinclude>

Template:OrigLang

2016-06-30T14:42:12Z

MarkDilley:

<div class="lang"><center><ul>
<li class="lang_main">[[{{NAMESPACE}}:{{PAGENAME}}|EN]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ar|<span title="العربية">AR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bg|<span title="български">BG</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bn|<span title="বাংলা">BN</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/cs|<span title="čeština">CS</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/de|<span title="Deutsch">DE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/el|<span title="Ελληνικά">EL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/eo|<span title="Esperanto">EO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/es|<span title="Español">ES</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/fr|<span title="Français">FR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/he|<span title="עברית">HE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hi|<span title="हिन्दी">HI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|<span title="Magyar">HU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hr|<span title="Hrvatski">HR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/it|<span title="Italiano">IT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ja|<span title="日本語">JA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/lt|<span title="lietuvių kalba">LT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/nl|<span title="Nederlands">NL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/no|<span title="Norsk">NO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pa|<span title="ਪੰਜਾਬੀ">PA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pl|<span title="Polski">PL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pt|<span title="Português">PT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ro|<span title="Română">RO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ru|<span title="русский">RU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/sv|<span title="Svenska">SV</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/th|<span title="ไทย">TH</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/tr|<span title="Türkçe">TR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/uk|<span title="українська">UK</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/vi|<span title="Tiếng Việt">VI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/zh-hans|<span title="中文 (Zhōngwén), 汉语, 漢語">ZH-HANS</span>]]</li>
<li class="lang_title">Article Title: {{PAGENAME}}</li>
</ul></div><includeonly>{{DISPLAYTITLE:{{{1|}}}|{{PAGENAME}}}}[[Category:EN]]</center></includeonly><noinclude>
== Usage ==
<nowiki>{{OrigLang}}</nowiki><br>

You may display a title to your page, that is different to the page name by <nowiki>OrigLang{{OrigLang|Title}}</nowiki>. On the translated pages, you have to '''change it to use the second Template [[Template:Lang]]'''.

== Documentation ==
This template should be added to all original english articles in the main namespace, at least to all that are or are supposed to be translated.

It shows the list of all languages an article should be translated to and also sets the correct, localised display title of the article.

=== Adding new Languages ===
Additional languages can easily be added here. You just need to add one line:

* put a new language link into the div container (please make sure they are alphabetically ordered):
:<nowiki><li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|HU]]</li></nowiki>

The subpages will automatically be used by different MediaWiki extensions which detect language settings in browsers or user preferences. The user will then automatically be redirected into the appropriate subpage.

=== Appearance ===
The CSS code for the div container of the class "lang" can be adopted in [[MediaWiki:Common.css]].
[[Category: Translation]]
</noinclude>

Template:OrigLang

2016-06-30T14:41:29Z

MarkDilley: centering, that work for folks?

<center><div class="lang"><ul>
<li class="lang_main">[[{{NAMESPACE}}:{{PAGENAME}}|EN]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ar|<span title="العربية">AR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bg|<span title="български">BG</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/bn|<span title="বাংলা">BN</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/cs|<span title="čeština">CS</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/de|<span title="Deutsch">DE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/el|<span title="Ελληνικά">EL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/eo|<span title="Esperanto">EO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/es|<span title="Español">ES</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/fr|<span title="Français">FR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/he|<span title="עברית">HE</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hi|<span title="हिन्दी">HI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|<span title="Magyar">HU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/hr|<span title="Hrvatski">HR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/it|<span title="Italiano">IT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ja|<span title="日本語">JA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/lt|<span title="lietuvių kalba">LT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/nl|<span title="Nederlands">NL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/no|<span title="Norsk">NO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pa|<span title="ਪੰਜਾਬੀ">PA</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pl|<span title="Polski">PL</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/pt|<span title="Português">PT</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ro|<span title="Română">RO</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/ru|<span title="русский">RU</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/sv|<span title="Svenska">SV</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/th|<span title="ไทย">TH</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/tr|<span title="Türkçe">TR</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/uk|<span title="українська">UK</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/vi|<span title="Tiếng Việt">VI</span>]]</li>
<li>[[{{NAMESPACE}}:{{PAGENAME}}/zh-hans|<span title="中文 (Zhōngwén), 汉语, 漢語">ZH-HANS</span>]]</li>
<li class="lang_title">Article Title: {{PAGENAME}}</li>
</ul></div><includeonly>{{DISPLAYTITLE:{{{1|}}}|{{PAGENAME}}}}[[Category:EN]]</includeonly><noinclude></center>
== Usage ==
<nowiki>{{OrigLang}}</nowiki><br>

You may display a title to your page, that is different to the page name by <nowiki>OrigLang{{OrigLang|Title}}</nowiki>. On the translated pages, you have to '''change it to use the second Template [[Template:Lang]]'''.

== Documentation ==
This template should be added to all original english articles in the main namespace, at least to all that are or are supposed to be translated.

It shows the list of all languages an article should be translated to and also sets the correct, localised display title of the article.

=== Adding new Languages ===
Additional languages can easily be added here. You just need to add one line:

* put a new language link into the div container (please make sure they are alphabetically ordered):
:<nowiki><li>[[{{NAMESPACE}}:{{PAGENAME}}/hu|HU]]</li></nowiki>

The subpages will automatically be used by different MediaWiki extensions which detect language settings in browsers or user preferences. The user will then automatically be redirected into the appropriate subpage.

=== Appearance ===
The CSS code for the div container of the class "lang" can be adopted in [[MediaWiki:Common.css]].
[[Category: Translation]]
</noinclude>

Template:InternalWikiCommunicationsTalkPage

2016-03-10T23:25:36Z

MarkDilley:

<div class="plainlinks" style="font-family: arial; border: 1px #06f; background: #eef; padding: 0.5em; margin: 0.5em 0.5em 1em; text-align: center; ">Leave me a public [http://opensourceecology.org/w/index.php?title=User_talk:{{PAGENAMEE}}&action=edit&section=new wiki message] here at the [[Open Source Ecology]] Wiki or send me an [http://opensourceecology.org/w/index.php?title=Special:EmailUser/{{PAGENAMEE}} internal email]. Check out [http://opensourceecology.org/wiki/Special:Contributions/{{PAGENAMEE}} my contributions] or go to my [http://opensourceecology.org/wiki/{{PAGENAMEE}} personal page]</div>{{RightTOC}}<noinclude>[[Category:Templates]]</noinclude>

User talk:MarkDilley

2016-03-10T23:25:02Z

MarkDilley: : It has been a while since I did that detailed of template work. Will mull it over and see what I can come up with, or jump in if someone else starts it. Best, ~~~

{{InternalWikiCommunicationsTalkPage}}

Mark, can you help on the [[Infobox Template]]?

MJ

: It has been a while since I did that detailed of template work. Will mull it over and see what I can come up with, or jump in if someone else starts it. Best, [[MarkDilley]]

Facebook Stats

2016-03-08T05:09:04Z

MarkDilley: Category:Social Media

<html><iframe width=100% height='500' frameborder='0' src='https://docs.google.com/spreadsheet/pub?key=0ArpE5Y9PpJCXdExXUjFtVndiODRqb3l1QlUxY3o2X3c&output=html&widget=true'></iframe></html>

[https://docs.google.com/a/opensourceecology.org/spreadsheet/ccc?key=0ArpE5Y9PpJCXdExXUjFtVndiODRqb3l1QlUxY3o2X3c#gid=0 edit]

<html><img src="https://docs.google.com/a/opensourceecology.org/spreadsheet/oimg?key=0ArpE5Y9PpJCXdExXUjFtVndiODRqb3l1QlUxY3o2X3c&oid=1&zx=8d5tgttxbbrh" />
</html>

[[Category:Social Media]]

Facebook Publishing Policy

2016-03-08T05:08:43Z

MarkDilley: Category:Social Media

Invited authors can maintain several posts to FB and Blog:

* GVCS Community Update - scanning existing open source projects that OSE can build upon as it pursues its development goals in parallel. For example, what are the bioplastic extruder, Windmill, CNC Torch Table, 3D Printer, Scanner, Universal Seeder, Tractor, MicroCar, Industrial Robot - and other projects that we can build upon? A prioritized list should be created as part of our Collaboration Architecture.
* Character Stand and Promise needs to be applied and translated into specific action points in FB Policy for FB Posting Guidelines.

[[Category:Social Media]]

Facebook Fraud

2016-03-08T05:08:25Z

MarkDilley: Category:Social Media

https://YouTube.com/watch?v=oVfHeWTKjag

TEDx - https://YouTube.com/watch?v=AcX3IW00nuk

[[Category:Social Media]]

Facebook Boost

2016-03-08T05:07:59Z

MarkDilley: add RightTOC

{{RightTOC}}
=Ad for [[CEB Press Workshop]] of June 17=
*Go to https://www.facebook.com/ads/create
*Select Clicks to Website:
[[Image:ad1.jpg|600px]]
*URL used was the website page - http://opensourceecology.org/cebpress-workshop-2/
*Then select area - all states around Wisconsin, the location: missouri, illinois, minnesota, indiana, Michigan, Iowa
*Select areas of interest:
[[Image:ad2.png|600px]]
*Selected categories that added up to about 1M potential audience. Removed one that made it 4M - as a specified number of ads would be diluted to a non-specific audience.
*Spending $200 on 9 days of ads right up to the workshop date.
*Results? Expecting a few signups for net ROI of at least 100% (one signup at least makes it worth it). If this signup occurs tomorrow, there is a good chance that this was result of ad. Optimistic case: one signup per day for the next 9 days.

=MicroHouse=
1 day, $200 boost on a Sunday, March 30 - got 70,000 hits on the post, 0 signups. https://www.facebook.com/OpenSourceEcology/posts/10202332897220961?stream_ref=10

=3D Printer Workshop=

Also... interesting results from a small Facebook BOOST. We targeted San Diego area and picked all the little demographics... getting very good "click throughs" to the actual signup page... 98 in a day and a half... with one confirmed and two more who I spoke with on the phone who say they will sign up. - Investment is maximum of $20/day but so far it has charged less than that for some reason.

I'll keep you updated on that... but it seems encouraging so far.

=Summer of Extreme Design Build=
*Jean-Baptiste - visual for Summer School. No more than 20% text for visual
*Do a webpage -
*Then go to Facebook. Under person, not organization.
:*Go to Ad Manager - upper left
:*Click on Create Ad
:*Select clicks to website - fill in all info. 600x315 best image size. Select Sign Up is the call to action.
:*Audience: Location, etc.
:*More Demographics - Schools , interests

=Hints from Pawel of [[Cohabitat]]=
Thanks. Tell me your strategy for the social media?

it's really simple.
#Crowd-source it via trello: https://trello.com/b/VH1A46tu/fanpage
#Post no more than 2-3 times a day,
#Post viral things, not only about your work
#Do online webinar once a month
#Delate content that has activity less than 30 likes
#Do it every day.

==Emily Response==

RE:
it's really simple.

1. Crowd-source it via trello: https://trello.com/b/VH1A46tu/fanpage
You could get your true fans to post items to Trello and then curate those for posting rather than have them made collaborators on facebook. That way you control the subject matter. Perhaps the people that are contacting you and generating dialogue would be people you could personally invite. You would direct message them as Marcin.

BTW - Trello is a collaboration project management tool which I think would be great for you and your teams to use for everything. Better tool than wiki's and spreadsheets. It can become a screen capture for wiki logs.

2. Post no more than 2-3 times a day
You are already doing this.

3. Post viral things, not only about your work
Yes... share viral don't just push your own stuff. AND like other entities. Watch them in the stream. Share their work and @their name as a mention in the post so they know you are talking about them- they will get a message in their inbox.

4. Do online webinar once a month
Regarding webinars - as a way of building? For a while, College tours and workshops will serve you better. Face-to-Face brings the academic pros on board - are you getting buy in for class credit at the institutions?

5. Delate content that has activity less than 30 likes
This is interesting - news to me.

6. Do it every day.
Absolutely - you've been rigorous with consistency

7. Additionally... do the sign up ads that we discussed. It will drive participation and likes to.
facebook. Organic exposure has diminished big time as facebook moves to a monotize.

8. when you aren't pitching for workshops/summer interns - keep a like us ad going for $10 a day... building exposure in your open source/maker interests category.

best,
em

[[Category:Social Media]]

Facebook Boost

2016-03-08T05:07:36Z

MarkDilley: Category:Social Media

=Ad for [[CEB Press Workshop]] of June 17=
*Go to https://www.facebook.com/ads/create
*Select Clicks to Website:
[[Image:ad1.jpg|600px]]
*URL used was the website page - http://opensourceecology.org/cebpress-workshop-2/
*Then select area - all states around Wisconsin, the location: missouri, illinois, minnesota, indiana, Michigan, Iowa
*Select areas of interest:
[[Image:ad2.png|600px]]
*Selected categories that added up to about 1M potential audience. Removed one that made it 4M - as a specified number of ads would be diluted to a non-specific audience.
*Spending $200 on 9 days of ads right up to the workshop date.
*Results? Expecting a few signups for net ROI of at least 100% (one signup at least makes it worth it). If this signup occurs tomorrow, there is a good chance that this was result of ad. Optimistic case: one signup per day for the next 9 days.

=MicroHouse=
1 day, $200 boost on a Sunday, March 30 - got 70,000 hits on the post, 0 signups. https://www.facebook.com/OpenSourceEcology/posts/10202332897220961?stream_ref=10

=3D Printer Workshop=

Also... interesting results from a small Facebook BOOST. We targeted San Diego area and picked all the little demographics... getting very good "click throughs" to the actual signup page... 98 in a day and a half... with one confirmed and two more who I spoke with on the phone who say they will sign up. - Investment is maximum of $20/day but so far it has charged less than that for some reason.

I'll keep you updated on that... but it seems encouraging so far.

=Summer of Extreme Design Build=
*Jean-Baptiste - visual for Summer School. No more than 20% text for visual
*Do a webpage -
*Then go to Facebook. Under person, not organization.
:*Go to Ad Manager - upper left
:*Click on Create Ad
:*Select clicks to website - fill in all info. 600x315 best image size. Select Sign Up is the call to action.
:*Audience: Location, etc.
:*More Demographics - Schools , interests

=Hints from Pawel of [[Cohabitat]]=
Thanks. Tell me your strategy for the social media?

it's really simple.
#Crowd-source it via trello: https://trello.com/b/VH1A46tu/fanpage
#Post no more than 2-3 times a day,
#Post viral things, not only about your work
#Do online webinar once a month
#Delate content that has activity less than 30 likes
#Do it every day.

==Emily Response==

RE:
it's really simple.

1. Crowd-source it via trello: https://trello.com/b/VH1A46tu/fanpage
You could get your true fans to post items to Trello and then curate those for posting rather than have them made collaborators on facebook. That way you control the subject matter. Perhaps the people that are contacting you and generating dialogue would be people you could personally invite. You would direct message them as Marcin.

BTW - Trello is a collaboration project management tool which I think would be great for you and your teams to use for everything. Better tool than wiki's and spreadsheets. It can become a screen capture for wiki logs.

2. Post no more than 2-3 times a day
You are already doing this.

3. Post viral things, not only about your work
Yes... share viral don't just push your own stuff. AND like other entities. Watch them in the stream. Share their work and @their name as a mention in the post so they know you are talking about them- they will get a message in their inbox.

4. Do online webinar once a month
Regarding webinars - as a way of building? For a while, College tours and workshops will serve you better. Face-to-Face brings the academic pros on board - are you getting buy in for class credit at the institutions?

5. Delate content that has activity less than 30 likes
This is interesting - news to me.

6. Do it every day.
Absolutely - you've been rigorous with consistency

7. Additionally... do the sign up ads that we discussed. It will drive participation and likes to.
facebook. Organic exposure has diminished big time as facebook moves to a monotize.

8. when you aren't pitching for workshops/summer interns - keep a like us ad going for $10 a day... building exposure in your open source/maker interests category.

best,
em

[[Category:Social Media]]

Facebook

2016-03-08T05:06:35Z

MarkDilley:

The OSE Facebook page is http://Facebook.com/OpenSourceEcology . All core team contributors are encouraged to post on the OSE Facebook page.

Twitter Embed

2016-03-08T05:05:53Z

MarkDilley: end /html ?

Intstructions for embedding a Twitter Hashtag feed in a blog: from [http://phronesisseo.blogspot.com/2011/05/embedding-twitter-hashtag-in-blog.html]
[[Category:Social Media]]

<html><script src="http://widgets.twimg.com/j/2/widget.js"></script>
<script>
new TWTR.Widget({
version: 2,
type: 'search',
search: '@OSECology',
rpp: 30,
interval: 5000,
title: 'Latest Tweets from #OSE_Dev',
subject: 'Updated Live',
width: 300,
height: 300,
theme: {
shell: {
background: '#8ec1da',
color: '#ffffff'
},
tweets: {
background: '#ffffff',
color: '#000000',
links: '#1985b5'
}
},
features: {
scrollbar: true,
loop: false,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: true,
behavior: 'all'
}
}).render().start();
</script>
</html>

=Another at #OSE_Dev=

<html><script src="http://widgets.twimg.com/j/2/widget.js"></script>
<script>
new TWTR.Widget({
version: 2,
type: 'search',
search: '#OSE_Dev',
rpp: 30,
interval: 000,
title: 'Latest Tweets',
subject: 'Updated Live',
width: 200,
height: 300,
theme: {
shell: {
background: '#8ec1da',
color: '#ffffff'
},
tweets: {
background: '#ffffff',
color: '#000000',
links: '#1985b5'
}
},
features: {
scrollbar: true,
loop: true,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: true,
behavior: 'default'
}
}).render().start();
</script></html>

Twitter Embed

2016-03-08T05:05:24Z

MarkDilley: Category:Social Media

Intstructions for embedding a Twitter Hashtag feed in a blog: from [http://phronesisseo.blogspot.com/2011/05/embedding-twitter-hashtag-in-blog.html]

<html><script src="http://widgets.twimg.com/j/2/widget.js"></script>
<script>
new TWTR.Widget({
version: 2,
type: 'search',
search: '@OSECology',
rpp: 30,
interval: 5000,
title: 'Latest Tweets from #OSE_Dev',
subject: 'Updated Live',
width: 300,
height: 300,
theme: {
shell: {
background: '#8ec1da',
color: '#ffffff'
},
tweets: {
background: '#ffffff',
color: '#000000',
links: '#1985b5'
}
},
features: {
scrollbar: true,
loop: false,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: true,
behavior: 'all'
}
}).render().start();
</script>
</html>

=Another at #OSE_Dev=

<html><script src="http://widgets.twimg.com/j/2/widget.js"></script>
<script>
new TWTR.Widget({
version: 2,
type: 'search',
search: '#OSE_Dev',
rpp: 30,
interval: 000,
title: 'Latest Tweets',
subject: 'Updated Live',
width: 200,
height: 300,
theme: {
shell: {
background: '#8ec1da',
color: '#ffffff'
},
tweets: {
background: '#ffffff',
color: '#000000',
links: '#1985b5'
}
},
features: {
scrollbar: true,
loop: true,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: true,
behavior: 'default'
}
}).render().start();
</script><html>

[[Category:Social Media]]

Twitter

2016-03-08T05:04:26Z

MarkDilley: Category:Social Media

[[Category:Social Media]]

YouTube

2016-03-08T05:04:11Z

MarkDilley: Category:Social Media

OSE YouTube channel is OpenSourceEcology: https://YouTube.com/user/OpenSourceEcology

== Adding Annotations and Links ==

[https://support.google.com/youtube/answer/6035690?rd=1 Google Support]

[[Category:Social Media]]

Category:Social Media

2016-03-08T05:03:54Z

MarkDilley: Created page with "."

Category talk:Team Culturing

2016-03-08T04:30:21Z

MarkDilley: : Venko, can you provide some leadership on OpenStreetMaps & MediaWiki? Best, ~~~

It would be nice, and in-line with OSE Specs, to use Open Street Map instead of Google Maps. --[[User:Venko|Venko]] 20:04, 7 February 2012 (CET)
: Venko, can you provide some leadership on [[OpenStreetMaps]] & [[MediaWiki]]? Best, [[MarkDilley]]

MarkDilley

2016-03-08T04:28:14Z

MarkDilley:

{{InternalWikiCommunication|MarkDilley}}

A WikiWalker of many years. I am thrilled with the work that this wiki is representing and all my edits are available to [[Revert]].

I founded what is now known as WikiIndex.

[[Image:MarkDilley.png|thumb| MarkDilley]]

==Team Culturing Information==

* Mark DIlley
* Detroit, Michigan, United States
* http://MarkDilley.info
* ''Picture''
* ''Introductory Video''
* ''Resume/CV''

==='''WHY''' are you motivated to support/develop this work?===
* ''Do you endorse open source culture?''

* ''Why are you interested in collaborating with us?''
:* Collaborating via [[Wiki]] is extremely interesting to me.

* ''How do you think that the GVCS can address pressing world issues?''

* ''What should happen so that you become more involved with the project?''

* ''What is missing in the project?''

* ''What are your suggestions for improvement of the project?''

==='''WHAT''' are your skills?===

* '''List all of your skills in these areas: Communications - Organizational - Computer Support - Finances - Design - Natural Building - Electronics - Automation - Metallurgy - Engineering - Fabrication - Agriculture - Energy - Architecture - Video/Graphics/Art - PR/Marketing - Education - Construction - Industry - CNC - Chemistry - Product Design - Other'''

* ''How have you already contributed to the project?''

===HOW can you help?===

* ''How are you interested in contributing to the work of GVCS development?''

* ''Can you volunteer to work with us, and if so, how many hours per week?''

* ''Are you interested in working with us for pay? If so, what services can you offer, and what is your hourly or per-project rate?''

* ''Are you interested in a [[Dedicated Project Visit]]?

* ''Are you interested in purchasing equipment from us to help bootstrap development?''

* ''Are you interested in bidding for consulting/design/prototyping work?''

* ''Are you a [[True Fans|True Fan]]? If not, why not?''

* ''Would you like to see yourself working with us on a full-time basis?''

* ''Are you interested in being part of the world's first, open source, resilient community? The GVCS is the preparatory step for the OSE Village Experiment – a 2 year, immersion experiment (2013-2014) for testing whether a real, thriving, modern-day prototype community of 200 people can be built on 200 acres using local resources and open access to information? We are looking for approximately 200 people to fill a diverse array of roles, according to the Social Contract that is being developed. This may be the boldest social experiment on earth - a pioneering community whose goal is to extend the index of possibilities regarding harmonious existence of humans, ecology, and technology.''

[[Category: Team Culturing]]

D3D Development

2016-03-08T04:24:29Z

MarkDilley: moving to the front of the Category page

{{RightTOC}}
See also [[Tobben Log]]

== Development spreadsheet ==
<html><iframe src="https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/pubhtml?widget=true&headers=false" width=650 height=600></iframe></html>

[https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1 edit]

== Overview within the OSE Context ==
This is OSE's first experiment in creating a [[Distributive Enterprise]]. As the first step, Torbjorn Ludvigsen is working with OSE to deliver four 3D Printer build workshops as a self-sustaining revenue model - within the context of his Master's Thesis. Further steps are included at [[Roadmap#3D_Printer_Roadmap]]. To do this, we are building upon [[RepRap]], and optimizing the build to allow for a low cost printer that can be built and run in a single day by novices, using OSE's [[Extreme Manufacturing]] techniques. Initial phases involve taking a kit 3D printer, and optimizing to reduce an average person's build AND shakedown time from 40 hours to 8 hours. The point is to cultivate a team of collaborative development on an enterprise where the economic reward structure is a highly replicable enterprise. The enterprise intends to use social production for building: 3D printers; products made with 3D printers such as cordless drills and polycarbonate greenhouse glazing panels; ancillary toolheads (laser engraving/cutting, milling, ceramic 3D printing, metal printing, etc); and ancillary equipment for plastics recycling (grinder, filament extruder, etc). The goal is to change culture by providing a rapid learning infrastructure for people interested in self-employment and right livelihood - by lowering barriers to such a transition. We are offering the support to non-makers in a transition to understanding the power to Build Yourself, and to Build Your World.

The key features of this project involve Extreme Collaboration by inviting open source and prorprietary stakeholders to contribute open content to the project. Since the scope is rapid, [[Open Source Product Development]], our goal is to realize the proposition from the seminal paper, ''[[Achitecture of Partcipation]]'': '''systems with more modular architectures, more divisible task structures, and/or more option value in the modules would attract more voluntary effort.'''

== Most Recent Team Meeting ==
Jan 23, 2016:

<html><iframe width="420" height="315" src="https://www.youtube.com/embed/G3HP7jOxob8" frameborder="0" allowfullscreen></iframe></html>

== Critical Path ==
<html><img src="https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/pub?w=12001&h=700"></html>

[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit edit]

== Team Charter ==
<html><iframe src="https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

== Introduction ==

[[Image:d3d.jpg"|500px]] [[Image:D3D_Printer_render_4_jan.png|700px]]

This project aims to be a proof of concept instance of a [[Distributive Enterprise]] focusing on 3D printers. It's similar to the [[RepRap]] project, but instead of focusing on creating and spreading machines (3D printers) this project focuses on people, the RepRappers. The idea is to achieve exponential increase in the number of RepRappers by simultaneously teaching RepRap and how to teach RepRap.

== Chain reaction metaphor ==

The D3D stands for Distributive enterprise 3D printer. The "fusion" part is there because this project will try to bootstrap a kind of economical chain reaction:

: <big><font face="bookman">Instructor + Hardware + Plans + Participants<sub>x</sub> → X (3D printer + New Potential Instructor)</font></big>

This project will try to initiate a process where new instructors are formed who themselves obtain plans, hardware and participants to continue the process.

=== The → (workshop) ===
The "reaction" in this metaphor is a workshop. It will be designed into the smallest detail to facilitate reaction propagation. The design will be iteratively updated.

We (Tobben and Marcin) currently (6 Dec 2015) believe a one-day workshop has the best chance of propagating. This is because:
* Potential participants' time is limited. This will be squashed into peoples schedules
* Potential instructors needs economical incentives. Shorter workshops is more probable to generate a decent pay per hour

=== The Instructor ===
The first instructors will be OSE members. The <big><font face="bookman">Hardware</font></big>, <big><font face="bookman">Plans</font></big> and workshop will be designed to increase probability of a <big><font face="bookman">Participant → Instructor</font></big> transition.

=== The Plans ===
Complete instructions and ready-made plans on how to host a workshop will be made as accessible as possible.

==== Making them good ====
Relevant data such as (build time, preparation time, etc) will be collected during every workshop. This data will be analyzed by the D3D project to facilitate plan design iterations.

Initial workshop plan will be guessed from various experience and beliefs.

==== Making them accessible ====
Features believed to increase accessibility include:
* Usage of rich media (video, sound, color, ...)
* Good language
* Good translations
* Wide publication
* All in one place (MOOC?)

Increasing accessibility easy. Doing it efficiently requires some consideration/experience.

=== The Participants ===
Potentially anyone. Make as few assumptions about participants as possible. Motivating people to become participants is a major part of the project.

=== The Hardware ===
The success of the RepRap project and the resulting increased availability of the RepRap hardware and information is the main reason why 3D printers are chosen as the first proof of concept [[Distributive Enterprise]].

==== Making it good ====
Making the hardware as
* Generally useful
* Durable
* Easily repaired
* High quality
... as possible is a major part of the project.

This part of the project can build heavily on the results of the [[RepRap]] project- and community as well as other communities and available research on DIY 3D printers.

==== Making it accessible ====
Having a well engineered 3D printer will not lead to a workshop propagation unless the machine is
* Cheap
* Easy to use
* Easy to build
* Well documented
* Stylish

== Business norms and science norms ==
D3D Fusion, as a DE, will eagerly train new competitors within its own production sector. Since there's no difference between "competitor" and "external collaborator" within OSHW enterprise, maybe we should call them something else? e-collegues?

On the market for selling prints, it will compete for customers as usual. During designing, coding and researching, it will benefit from other DEs' expertise, they will be collaborators.

This combination of roles is customary within the scientific community which relies on the following norms:
# Researchers are part time teachers
# Publish or perish (risk losing your reputation and/or job)
# Research must be replicable to gain trust

D3D Fusion applies similar norms to a RepRap business.
# Founder are part time teacher (makes an income through hosting workshops where he teaches his craft)
# All R&D progress published to the Internet
# The enterprise is replicable

There are currently no norms driving D3D Fusion into decision 1 but decision 2 follows norms within the Open Source Hardware community. Norm 3 is an extension of design norms within the RepRap community.

==== Part time teaching ====
Many companies teach their craft and succeed in competitive markets at the same time. Ideo is an example within design business that sells both designs and courses on designing[https://www.ideo.com/][http://www.ideou.com/][https://www.ideo.org/], Lulzbot teaches by writing how-to guides[https://www.lulzbot.com/learn][https://ohai.lulzbot.com/], E3D teaches results of their R&D in public presentations[https://www.youtube.com/watch?v=mk30MPLoYf4]. The Ideo, Lulzbot and E3d enterprises prove that teaching your craft and selling your products simultaneously is economically sound (or at least doable).

Bootstrapping a market for DE workshops would give DE workers a special opportunities to work as part time teachers. This bootstrapping requires designing and testing a template, publishing it and supporting it with data.

==== Publish or Perish ====
The possibility to publish everything is already being used by current OSHW enterprises, such as Lulzbot[http://download.lulzbot.com/] and E3d[http://wiki.e3d-online.com/wiki/E3D-v6_Documentation#Engineering_Drawings].

==== Replicability ====
This is where D3D Fusion will be the most different from current OSHW enterprises...

== List of similar projects ==
* [http://Seed-Factory.org Seed Factory]
* [http://Appropedia.org/Evaluation_of_RepRap_3D_Printer_Workshops_in_K-12_STEM MOST lab workshops]
* [https://ifixit.com/ Ifixit]

== Naming and Links ==
This is the front page of the overarching [[D3D Fusion]] Project. It has an over arching [[D3D Fusion Project Plan]].
There exist a sub-project called [[D3D Thesis]], with its own [[D3D Thesis Project Plan]].
As a part of the [[D3D Thesis]] Project, the 3D printer design called [[D3D Printer]] and the design methodology called [[D3D Design Methodology]] are being developed.
The development of the [[D3D Printer]] follows the [[D3D Design Methodology]], and is being logged at [[D3D Printer Design Process]].
Description of the current [[D3D Printer Design]] is a dedicated developer-perspective wiki page.

=== List of Links ===
* [[D3D Distributive Enterprise]]
* [[Prusa i3 Build]]
* Follow progress of overall OSE 3D Printer Development at [[3D Printer Log]].
* [[D3D Fusion Project Plan]]
* [[D3D Thesis]]
* [[D3D Thesis Project Plan]]
* [[D3D Printer]]
* [https://github.com/tobbelobb/D3D_Printer D3D Printer Git Repo]
* [[D3D Design Methodology]]
* [[D3D Printer Design Process]]
* [[D3D Printer Design]]
* [[D3D Workshop Kit]]
* [[Prusa i3 Development]]
* [[3D Printer Distributive Enterprise Log]]
* [[D3D Workshop Roadmap]]
* [[D3D Workshop Slogans]]

[[Category: D3D| *]]

D3D Workshop Slogans

2016-03-08T04:23:33Z

MarkDilley: Category: D3D

Here are some slogan suggestions for promoting the D3D Workshops. They're based on thinking of the D3D project as developing a culture and lifestyle similar to "farming" around the D3D Printer machine. They're all inspired by the RepRap slogan "Make one for a friend".

= Suggestions =
*"Become a farmer of robots"
*"Build a champion"
*"Start your robot farm"
*"Symbiosis with robots"
*"Live in symbiosis, pass on the wisdom"
*"Be a native in the robot-age"
*"Make your machine work for you"
*"Make wealth from parts"

=Links=
See [[3D Printer Event Branding]]

[[Category: D3D]]

D3D Workshop Roadmap

2016-03-08T04:23:16Z

MarkDilley: Category: D3D

This document tries to point out when to develop what features of the D3D Workshop Plan. Only changes and new features from version to version are pointed out. Note that this is only a sketch and it will be changed/updated in the future.

=Workshop v0=
* 1-day
* X participant spots, Y scolarship/assistant spots, Z instructors
* Participants paired up throughout the day
* Every participant start with complete set of parts for one printer
* Specific timing cutoffs per build step
* Table placement plan, including table presenting working printer
* Build steps X, Y and Z: special production line tables (see PBR)
* Printer: Prusa i3 with auto-bed-level
* Printer price in parts: $500
* Instructions are mash-up of other Prusa i3 sources

=Workshop v1=
* D3D printer with same auto-bed-level as before
* Printer has XY-fixed build platform and modular tool head attachment
* Instructions tailored for workshop, produced by OSE
* Use of special production line tables adjusted for D3D Printer

=Workshop v2=
* Instructions and printer adjusted for wireless controll
* OSE Label documented for printer
* Capability of Ninjaflex printing documented
* Capability of conductive filament printing documented

=Workshop v3=
* Longevity of linear actuators (lead screws) tested and documented
* Test rigs (quality control) for special production line tables X and Y
* Heat bed + clear enclosure extension designed (not explicitly included in workshop, but linked to in documentation)

[[Category: D3D]]

3D Printer Distributive Enterprise Log

2016-03-08T04:23:05Z

MarkDilley: Category: D3D

=Wed Jan 20, 2015=
Purchased a Prusa i3 kit from [[Folger Technologies]], the aluminum extrusion version. Goal is to evaluate build, and see what it takes to do a one day build - and determine more specific value proposition as far as how to present the workshop. Considering auto bed level addition - reviews say that calibration is a big issue, and in our case, can be a show-stopper for a one day build. 2 people per team can make it happen more easily if we design for parallel process - definitely doable. I have seen reports of 7-24 hours for the complete build until good printing.

[[Category:Logs]]
[[Category: D3D]]

Prusa i3 Development

2016-03-08T04:22:54Z

MarkDilley: Category: D3D

=Original Prusa i3 Build Manual=
*http://prusa3d.dozuki.com/c/Prusa_i3_kit

*Prusa P3Steel Build Manual:
http://www.kitprinter3d.com/en/blog/p3steel-assembly-tutorial-c10
*Info on P3Steel: http://reprap.org/wiki/P3Steel

Note that many derivatives may vary from the original.

=[[Folgertech Kit]]=
Kit sells for under $300. This source [http://www.rcgroups.com/forums/showthread.php?t=2344393] says auto bed leveling is done readily.

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/UTQGLjIkLkM" frameborder="0" allowfullscreen></iframe></html>

*Review - [https://www.youtube.com/watch?v=bVyRrsc8X50] - calibration is a definite issue.
*Auto level by metal-to-metal contact - [https://www.youtube.com/watch?v=rS_nvMX6wzM]
==Build Time==
*12 hour build time - [https://www.youtube.com/watch?v=mdzsJycdSAo]

=Process=
*[http://forums.reprap.org/read.php?1,612676 Forum message] - what's the Best Workshop Kit for a 3D printer workshop? 1 day build workshop, as high quality as possible.
:*Prusa i3 from Folgertech encouraged.
*SD card or wireless - what additional cost is there?
*We identify the kit

=FreeCAD Files=
*Prusa Hephestos is available - [[File:prusahephestos.fcstd]]
*See search - [https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8&client=ubuntu#q=prusa%20i3%20in%20freecad]

=Selection=
<html><iframe src="https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>
=Original Work=
*Version used in Prusa workshops - see Readme for source - [https://github.com/josefprusa/Prusa3]. Her is the source for the workshop model. [https://github.com/josefprusa/Prusa3-vanilla].

=Links=
*Prusa i3 Buyer's Guide from RepRap - [http://reprap.org/wiki/Prusa_i3_Buyers_Guide]
*Classifieds - Missouri - [http://www.3dprinterclassifieds.com/3d-printers/prusa-i3-full-kit/]

=Sourcing with Shipping=
*Under $350 for full kit, shipping is 3-5 days - [http://www.replikeo.com/en/quick-order]. Uses [[J Head Nozzle]]. Ships "i3 rework" design: [http://reprap.org/wiki/Prusa_i3_Rework_Introduction]
**Review of Replikeo [http://projectsfromtech.blogspot.se/2015/01/replikeo-prusa-i3-rework-build-part-1.html]
**Replikeo BOM - [http://wiki.replikeo.com/index.php?title=Replikeo_Prusa_i3_BOM]

=Sourcing Issues=
*According to [http://reprap.org/wiki/Jhead] - cheap chinese J Head counterfeits do not work - so make sure the hot end works
*J Head exists from the original manufacturer - $56 - but shipping is a flat rate. Takes 48 hours to ship, but shipping method is unspecified. Need to contact seller to see if they can provide fast shipping.

=Communication=
*Josef (Prusa),

We will be doing a Prusa i3 workshop March 19.

1. Can you share some of your expertise in running workshops - do you have your process documented anywhere?

2. Which source of the Prusa i3 do you recommend as the best version to use for a workshop?

3. Are you in a position to/ interested in coming to the USA to run a workshop with OSE?

Marcin

= Research before asking on RepRap forum =
== RepRap Forum Threads ==
[http://forums.reprap.org/read.php?1,534791 Thread where thetazzbot has same one-day workshop and similar workshop plan spreading ideas as D3D]. Suggested kits: Reprappro Fisher ([https://github.com/reprappro/Fisher repo with GPL licence], [https://reprappro.com/documentation/fisher-1/ build instructions]), [http://folgertech.com/collections/3d-printer-full-kits/products/folger-tech-reprap-2020-prusa-i3-full-aluminum-3d-printer-kit folgertech 2020 prusa i3]. Note on Fisher: I (Tobben) has built one of these myself. It's not what D3D wants.

[http://forums.reprap.org/read.php?151,338570 Thread where beginner decides which Prusa i3 kit to order]. Community ends up recommending [http://www.makerfarm.com/index.php/prusa-8-i3v-kit-v-slot-extrusion.html Makerfarm's kit].

[http://forums.reprap.org/read.php?4,291461,294025 Thread where printmate3d.com founders present their workshop-friendly Prusa i3 design]. Sadly, it has a non-commercial licence. Their design can be found [http://printmate3d.com/downloads/ here].

== Other Workshops ==
[https://www.matterhackers.com/news/matterhackers-introduces-3d-printing-classes Matterhackers workshops jan 2016]

[http://botbuilder.net/ botbuilder.net] does Prusa i3 workshops, lists suppliers and uses libre licences. Fantastic! Instructor John Abella would be interesting contact for D3D.

[https://matricula.fundaciocim.org/en/catalog/workshops-reprapbcn BCN3D hosts 1-day intensive RepRap workshops]. Doesn't include build though (they have 3-day workshops for that). The printer they use ([https://www.bcn3dtechnologies.com/en/catalog/bcn3d BCN3D+]) is expensive (740€ per kit), but is libre (MIT-licence), CAD files are step. Found [https://github.com/BCN3D/CAD here]. Build manuals [https://github.com/BCN3D/Manuals here].

== Reprappro ==
Tobben's previous preferred kit-supplier, reprappro.com, closed its sales on Jan 15 2016. They left a list of alternative suppliers on their home page including:
*[http://reprap.org/wiki/RepRap_Buyers'_Guide The RepRap.org Website]
*[http://www.emakershop.com/Seller=7244 eMaker]
*[http://gb.trapletshop.com/fisher-delta-3d-printer Trapletshop (Fisher kit)]
*[http://www.replikeo.com/en/ Replikeo]
*[https://www.think3dprint3d.com/ Think3DPrint3D]
*[http://uk.rs-online.com/web/ RS Components]
*[http://www.mouser.se/ Mouser (Europe)]
*[http://uk.farnell.com/ Farnell]
*[http://www.toby.co.uk/ Toby]

== Forum thread ==
The forum thread where we ask RepRap community which kit to use: http://forums.reprap.org/read.php?1,612676

[[Category: D3D]]

D3D Workshop Kit

2016-03-08T04:22:34Z

MarkDilley: Category: D3D

After a D3D Workshop, a participant is hopefully on the way to get knowledgeable and self confident enough to become a D3D Entrepreneur and host his/her own workshops.
The [[D3D Workshop Kit]] is a set of files (eg [[D3D Printer]] design files, documentation, workshop plans, ...) and hardware.
It is intended to contain all the information and hardware a D3D Entrepreneur needs on order to get started with hosting workshops.

The [[D3D Workshop Kit]] will initially contain the [[D3D Printer Design]] and (through four iterations optimized) workshop plans created as part of the [[D3D Thesis Project]].

[[Category: D3D]]

D3D Printer Design

2016-03-08T04:22:22Z

MarkDilley: Category: D3D

= Tech Tree of Choices =
<html><iframe src="https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>
[https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p edit]

= Higher Level Goals =
#Fits [[Extreme Manufacturing]] model. This means optimizing for a parallel build process.
#Distribution of the machine through distributive enterprise propagation
#Design being built upon, resulting in design remixes/derivatives
#Distribution of derivatives through distributive enterprise propagation
#[[Distributed Market Domination]] via derivatives

= Requirements =
== Methodology ==
The following requirements lists have been compiled using parts of [https://en.wikipedia.org/wiki/Axiomatic_design Axiomatic Design Methodology]. The main point we've borrowed can be summarized like this:
We strive towards creating lower triangular matrix mappings (preferably diagonal matrices) between the four domains:

<big><font face="bookman">Customer needs ↔ Functional requirements ↔ Design parameters ↔ Process variables</font></big>

The formulation "striving towards diagonal matrix mappings" may be formulated more verbosely as
Try to organize a list (vector) of customer needs such that they are mutually independent.
Try to make each functional requirement address exactly one customer need.
Try to organize a list of functional requirements such that they are mutually independent.
Try to make each design parameter affect the fulfillment of exactly one functional requirement.
Etc...

There's a special emphasis on the mutual independence of functional requirements within the axiomatic design methodology. The principle is regarded so useful and important that it is dubbed <i>Design axiom 1</i>.

=== The matrix mapping formal language ===
...

See [http://ocw.mit.edu/courses/mechanical-engineering/2-800-tribology-fall-2004/lecture-notes/ch10_axiomatic.pdf MIT course notes] for more on axiomatic design.

== Desired Attributes ==
#Easy to use (consumer grade)
#Technical coherence within OSE product ecology
#Produce-able with other open source tools (see [[Productive Recursion]])
#Easy to build
#Cheap
#Reliable and maintenance free
#Easy to document
#Easy to teach
#Fast/effective printing
#Fills group of related production needs
#Scalable
#Easily extend-able
#Ethical and philosophical coherence with FSF and related Open Source Hardware communities
#Has documented criteria for performance and quality of printing

== Functional Requirements ==
Each FR maps to one or more desired attributes. Marked within parenthesis.

#Build-able during 1 day workshop, including a pleasant learning and social experience, even for inexperienced builders (4, 8)
#[[OSE Label]] documented (2, 14)
#Automatic bed leveling mechanism (1, 6, 8, 9)
#[http://www.oshwa.org/2015/09/19/open-source-hardware-certification-version-1/ OSHWA certification] compliant (2, 13)
#$500 in parts for single print head version (5)
#Wirelessly controllable (1, 9)
#Capable of storing and independently running wirelessly uploaded gcode (9)
#[[Ninjaflex]] print capable (10)
#Single print head version easily extend-able to accommodate quadruple parallel printing (9, 12)
#Capable of 1000 hours of maintenance free printing between any required fix (6, 14)
#Independent parts must be used in such a way that the complete design is easily scalable up to sizes that support meter scale 3D printers (2, 11)
#Addable clear enclosure (10, 12)
#Modular tool head attachment (2, 12)
#Functions as an effective [http://reprap.org/wiki/Repstrap Repstrap] (13)
#XY-fixed build platform (6, 11)
#Heated build platform that can be retrofitted readily without compromising bed leveling mechanism. (10, 12)
#Capable of bumping (strong and tall) prints off of build platform without human assistance (6, 9)
#Works with open source filament from open source filament extruder (2, 3, 13)
#Functional Logic and design rationale is fully documented (1, 4, 7, 8, 12)
#Capable of printing currently mass produced conductive filaments (10)
#Modular linear actuators (2, 4, 7, 8, 10, 12)

== Design Parameters ==
These are found in the design file [https://github.com/tobbelobb/D3D_Printer/blob/master/Design_numbers.scad Design_numbers.scad].

Some parameters that this project does not control (like exact size of Nema17 motor) are captured in [https://github.com/tobbelobb/D3D_Printer/blob/master/Measured_numbers.scad Measured_numbers.scad].

At the time of writing this (31 Dec 2015), no complete mapping between functional requirements and design parameters is yet finished.

= Future Work =
#[https://libreplanet.org/wiki?title=Group:Hardware/Certification_criteria&redirect=no Respects Your Freedom certified]
#Works with irregular dimension filament
#Coherence with other machines to achieve [[Productive Recursion]] of a complete workshop tool chain
#Capable of sensing different abort situations
##Detached print
##Failing material feed
##Improper temperature of print
##Failing positioning system (skipped stepper motor steps or similar)
#Capable of automatically pausing abort situations 1 and 2 and presenting manual mitigation instructions and resume options
#Capable of automatically mitigating abort situations 3 and 4
#Addable syringe head for conductive ink printing

= Link Matrix =
{|border="1"
| Source code: || [https://github.com/tobbelobb/D3D_Printer Github repo] ||
|-
| Licences: || Repo: GPLv3, All wiki information: CC-BY || Follows [https://www.gnu.org/licenses/license-list.html#Designs FSF's recommendations]
|-
| Part of: || [[D3D Fusion]] ||
|}

= Design Brainstorm =

== Making it modular ==

Much like Alexander Stepanenko has done for CNCs here:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/wkk4zv96Dvo" frameborder="0" allowfullscreen></iframe></html>

This would allow extending to a multi purpose machine at a later stage. Examples of existing multi purpose machines are Diyouware[http://www.diyouware.com/] and Fabtotum Fabricator[http://fabtotum.com/about].

== CoreXZ ==

This means driving the X/Z directions by rotating two motors in same/opposite directions. The idea has been tested with good results[http://forums.reprap.org/read.php?2,377858].

The big win with this configuration is saving one motor (compare to current common designs that uses 2 motors for Z axis) and much easier build (thread and bearings replace threaded rod with nut).

== CoreXYZ ==

There's nothing hindering us from also driving a Y axis with lines, like shown here:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/ceBZMyg3n3M" frameborder="0" allowfullscreen></iframe></html>

Again, saving in a Y-axis belt and motor makes it an easier build. Using v-groove bearings and dynema line for driving all axes also takes down the unique part count really low.

= Inspiration =
*Prusa i3 Steel
*Ultimaker
*DIY CNC machines - specify more here...
*Linear actuators built as stand alone modules
*[[Modular Desktop CNC]]

= Everything below here is being rewritten and filled into the D3D Tech Tree of Choices slide show =
== Weight calculation for steel sheet frame ==
Mass fills a function in itself because higher inertia counteracts vibrations. A mapping from design parameters to resulting eigenfrequencies would be useful to better explain this.
{|class="wikitable"
| Side lengths/m
| style="text-align:right;" | ~0.3
|-
| Sheet thickness/m
| style="text-align:right;" | ~0.003
|-
| Cut away fraction
| style="text-align:right;" | 0.44
|-
| Resulting steel volume/m^3
| style="text-align:right;" | 0.0006048
|-
| Density of steel/(kg/m^3)
| style="text-align:right;" | ~8000
|-
| Resulting total weight of frame/kg
| style="text-align:right;" | ~ 4.9
|}

== Motor placement ==
Z motor is placed near top of printer so that we can scale
in Z-direction by giving frame "legs" and mount a longer
Z-axis actuator without imposing a new motor position for Z motor.

== Linear motion ==
A 3-axis Cartesian 3D printer needs to control linear movement very precisely.
To keep firmware simple and computational load low, open loop arrangements (no sensor feedback regarding motion) are preferred for simple printers.
This could for example be achieved by putting electromagnets on a row and placing a ferromagnet above it.
Sequentially activating the electromagnets would make the ferromagnet move along a straight line in a controlled way.

Pros of this solution:
- Easy to understand
- Open loop control, no feedback or feedback processing needed
Cons:
- Needs many electromagnets and wires (doesn't scale)
- Off the shelf driver soulutions not available
- A range of possible speed/force-ratios are built into the machine
- Steps are discrete, so precision is limited

All small 3d printer designs overcomes the cons by having the electromagnets arranged in a circle,
and the ferromagnets attached to a shaft right in the middle of it.
This gives the advantages
- Scaling problem solved. Can do infinitely many rotations with fix number of magnets.
... but adds the disadvantage
- Outputs rotational motion that needs to be converted into linear motion

Converting the rotation into a linear motion could be done in a number of ways:
#Rotating a pulley that drive a belt/wire
#Rotating a threaded shaft
#Rotating a gear that "walks" a toothed strip
See Polhems mechanical alphabet for suggestions...

== Pulley and Belt or Wire ==
The usual way to drive the axes of a 3d printer is by belts (GT2) or by some kind of non-flexible line/wire.
The pros of belts/wires:
- Cheap
- Well known/widely used
- Easy to source
- You can change gear ratio by changing pulley, keeping the belt itself
Cons of belts/wires:
- Must be cut to length
- Must be fastened somehow
- Must be tightened somehow
- Needs retightening after some time
- Needs guides and bearings to run smooth and stay in place

== Threaded shafts ==
A common way to build a linear actuator is to use a threaded shaft and a nut/bearing for translating rotational motion into linear motion. The choice of threaded shaft type is a compromise between price and performance.

=== Construction type ===
Cheap common studs designed to be used in tension, keeping things in place. They're not designed to be very straight or to be very wear resistant. When supported by additional smooth rods or extrusions, they're good enough for light and slow linear actuators. Most RepRap designs use them in their Z axis actuator.

=== Leadscrew ===
Designed to translate turning motion into linear motion. About twice the price of construction type studs.

Available already mounted as stepper motor shafts: [http://www.ebay.com/itm/NEMA-17-Linear-Stepper-Motor-Lead-Screw-300mm-T8-Z-axis-RepRap-3D-Printer-CNC-/262200758350?hash=item3d0c62104e:g:vZ4AAOSwNSxVXvBc][http://www.ebay.com/itm/NEMA-17-Lead-Screw-260mm-Stepper-Motor-M8-Z-axis-For-3D-Printer-CNC-RepRap-/221441570637?hash=item338ef2374d:g:LFMAAMXQh8NTdeb-]

=== Ball Screw ===
A helical raceway for specialized ball bearings. Less friction than leadscrew. About twice the price of leadscrew.

=== Roller Screw ===
High precision screw type that use planetary type bearings. Performance is usually very good, but price is an order of magnitude higher than that of ball screws[https://en.wikipedia.org/wiki/Roller_screw].

=== D3D Printer Design Choice ===
The D3D Printer will have a Cartesian coordinate system driven by four linear actuators. For modularity and ease of build we want the linear actuators for the different axes to be as similar to each other as possible without sacrificing print speed or accuracy.

The leadscrew type of threaded shafts will be tested first.
Since they are sold as mounted stepper motor shafts, they can potentially eliminate the need for a coupling between motor and shafts. Couplings are usual sources for misalignments, so getting away from them is a big relief.

The pros of ready-mounted threaded shafts:
*Easy and fail safe mounting
*High and predictable precision over time
*No maintenance
*Needs less guide/support parts than belts
The cons of ready-mounted threaded shafts:
*Harder to source
*More expensive
*Fixed pitch

==== Price examples ====

==== Pitch/torque Examples ====
*3 tpi, 8 mm. 10 RPS = 600 RPM. Typical curve. - [http://www.kitprinter3d.com/en/linear-motion/87-husillos-8mm-x-300mm.html]
*RepRap Lisa Simpson - [https://www.youtube.com/watch?v=N7XVxtgHHhY]
*Using these motors - [http://www.ebay.com/itm/FREE-SHIPPING-3PCS-Nema17-CNC-Stepper-Motor-40mm-58-Oz-in-1-3A-for-3D-Printe-/252218407269?hash=item3ab9637965:g:84kAAOSwU9xUSPVp] - torque curves are - []
*About stepper motor curves - [http://www.orientalmotor.com/technology/articles/article-speed-torque-curves-for-step-motors.html]

== Linear guides ==
Use linear bearings with flanges for easier mounting: [http://www.ebay.com/itm/10pcs-LMK10UU-10mm-Square-Flange-Type-Linear-Bearing-Ball-Bushing-10x19x29mm-/120894257709?hash=item1c25dbfa2d:g:tvMAAOxyZzlTegsC]

== Positioning in 3D space ==
== Feeding plastic ==
=== Pellets ===

=== Filament ===
''' Direct extrusion '''
Used by most early RepRaps. Drawback is that Extruder motor is heavy (do we don't want to move it along with hot end). Some effort has been put into combining direct extrusion with fixed E-motor and a sliding hobbed bolt[http://garyhodgson.com/reprap/2012/01/experimental-off-carriage-extruder-motor/]. There's also the Flexible Drive Shaft Extruder[http://mutley3d.com/Flex3Drive/] which has been reported to work well.

''' Bowden extrusion '''
This is the most common way to extrude filament. Extruder motor is fixed and filament is pushed from extruder motor to hot end through a PTFE tube. Introduces more delay and tension complications than either of the direct extrusion solutions.

[[Category: D3D]]

D3D Printer Design Process

2016-03-08T04:22:01Z

MarkDilley: RightTOC

This document lists D3D Printer Design decisions and reasoning behind them in chronological order.
The intention is to make the process as debuggable as possible and facilitate later creation of formal documents such as Design Decision Tree and Conceptual Design diagrams.
It follows the [[D3D_Design_Methodology]].

{{RightTOC}}
=Calculations=
==Scalability of Threaded Rod Drive==

= Sources Driving Design Desicions in Priority Order =
#[[D3D_Fusion_printer_design#Higher_Level_Goals]]
#[[D3D_Fusion_printer_design#Desired_Attributes]]
#[[D3D_Fusion_printer_design#Functional_Requirements]]
#[http://reprap.org/wiki/RepRap_Interface_Standard RepRap Interface Standard]
#''The shape of the input determines the shape of the design and tests.''<ref name="htdp" />

= Process =

== Concept Creation ==
'''NOTE:''' We started out this process with concept creation. This deviates from the [[D3D Design Methodology]], but we document it here nontheless.

[[D3D_Printer_Design#Functional_Requirement]] nr 1 is that the printer should be buildable in one day, and a parallelizable build is highly desired.
A random Youtube search around modularity in CNC machines led to discovering the concept of modular linear actuators, as shown by Alexander Stepanenko in a [https://www.youtube.com/watch?v=wkk4zv96Dvo video]. These kind of actuators are sometimes called "linear stages" and are sold as ready-built units[http://www.amazon.com/Konmison-Linear-Actuator-CNC-Machine/dp/B016LRNV1U/ref=pd_sbs_328_10?ie=UTF8&dpID=41t83kKWDIL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1G2FWG037R3NCGMYVKW0][http://www.amazon.com/gp/product/B016MC2RDM/ref=s9_hps_bw_g328_i3].
The concept would allow
#... building linear actuators and other parts at the same time
#... defining a ubiquitous standard (screw position) interface

Normally, we would reason here around advantages that the concept of modular linear actuators could provide, but OSE found its potential exciting enough to put it directly into [[D3D_Printer_Design#Functional_Requirements]].

Instead of diving into stepwise definition of interface and linear actuator, we decided to grab the following low-hanging fruit:
*'''Standard Screw Interface''': Nema17
*'''Linear Actuator''': Stepper Motor + lead screw

=== Why Not... ===
{|
|-
| '''... ball screw?'''
| Price. See [http://www.thomsonlinear.com/downloads/articles/Why_Lead_Screws_Best_Fit_Linear_Motion_Applications_taen.pdf]
|-
| ''' ... threaded rod?'''
| Speed and straightness. See [http://www.protoparadigm.com/news-updates/accuracy-vs-precision-and-threaded-rod-vs-leadscrews-in-3d-printers/]
|-
| ''' ... threadless ball screw?'''
| Kind of hard to put together and risks slipping. See [https://www.thingiverse.com/thing:298212]
|-
|}

=== Verification Steps Taken for Lead Screw + Stepper Motor Concept ===

==== CAD viability ====
[[Image:Linear_module_render1.png|300px]][[Image:D3D_Printer_render_4_jan.png|700px]]

Looks sane...

==== Practical viability of lead screws for 3D printing loads and speeds ====
{|
|-
!Link
!Comment
|-
|https://www.youtube.com/watch?v=gk9lhcTGSH4
|Printing at 75mm/s (fast) with aggressive leadscrew. Lots of rattling from linear bearings. Sub-optimal construction with lead screw not between smooth rods may be cause. 2014.
|-
|https://www.youtube.com/watch?v=reVNrtsDfxQ
|Slow first layer, normal RepRap speed after that. Uses cheap 8/8 mm lead screws. Every time acceleration changes direction, you hear a "bump". Two flanged nuts with a spring between them would fix this. 2015.
|-
|https://www.youtube.com/watch?v=wWZqLwwwx_k
|Printer is called Fina. Leadscrews are 6-start. 18 mm travel/rev. 12 mm diameter
|-
|https://www.youtube.com/watch?v=ULVLZpHSlzc
|Trinitylabs' printer, Aluminatus. They went out of business in May 2014.
|-
|https://www.youtube.com/watch?v=4bMUlu4GF2k
|Trinitylabs again, with Aluminatus printing faster
|-
|http://www.igus.no/wpck/12976/Manus15_3D_printer_3
|In this link, Igus shows off some of their products in a all-leadscrew 3D printer
|-
|http://www.igus.eu/wpck/10783/3Dprinting
|Here Igus shows off more 3D printer applications (under "Application examples")
|}

[http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping's Jon] in mail: "I have been using my Aluminatus heavily for the 2 years or so that I've had it, and it continues to perform very well. I like the linear bearings and lead screws a lot."

==== Theoretical force viability ====
Newtons second law:
F = ma

Total linear actuator weight is approximated like
{|
! Parameter
! Estimated value
! Unit
! Source
|-
| '''Motor: '''
| align="right" | 0.4
| align="left" | kg
| [http://www.osmtec.com/nema_17_step_motor_17_hs.htm stepper motor shop]
|-
| '''Lead screw/Smooth rod: '''
| align="right" | 0.12
| align="left" | kg
| density=8000 kg/m^3, radius=4 mm and length=300 mm
|-
| ''' Linear Bearing '''
| align="right" | 0.015
| align="left" | kg
| [http://www.robotdigg.com/product/13/LM8UU-Linear-Bearing linear bearing shop]
|-
| ''' Hot End '''
| align="right" | 0.05
| align="left" | kg
| [http://www.filastruder.com/products/e3d-heatsink-v6 hot end shop]
|-
| '''X-Carriage (extruder + hot end): '''
| align="right" | 0.67
| align="left" | kg
| Hotend + Motor + Four linear bearings + 0.05 kg of plastic + 20 percent
|-
| '''Linear Actuator Module: '''
| align="right" | 0.81
| align="left" | kg
| Motor + two smooth rods + lead screw + 0.05 kg of plastic
|-
| '''Y-Carriage (X-Carriage + linear actuator module): '''
| align="right" | 1.48
| align="left" | kg
| Linear Actuator Module + X-Carriage
|-
|}

The linear actuator will have to meet following circa-requirements to be realistic:
{|
|-
! Parameter
! Value
! Unit
! Source
|-
| '''Weight load:'''
| align="right" | 0.74
| align="left" | kg
| Y-Carriage weight/2
|-
| '''Max Speed:'''
| align="right" | 0.070
| align="left" | m/s
| [[Stepper Motor]] generally don't want to run faster than 300 rev/min. Lead screws that are more aggressive than 14-15 mm per revolution are hard to source.
|-
| '''Max acceleration: '''
| align="right" | 5
| align="left" | m/s^2
| Requirements/choice
|-
| '''Worst expected Lead screw efficiency:'''
| align="right" | 60
| align="left" | %
| [http://www.cncroutersource.com/lead-screw-efficiency.html CNC router source], [https://youtu.be/HJaNyNrGT0E?t=5m19s Youtube video] showing lead screw is back drivable. Implies > 50 % efficiency[http://www.thomsonlinear.com/downloads/articles/Why_Lead_Screws_Best_Fit_Linear_Motion_Applications_taen.pdf].
|}

Torque from rotational inertia is not included in the table because inertia of the threaded rod is tiny (order of 10^-7 kg m^2).
Newton's second law gives maximum force needed:
F = (0.74 * 5)/0.6 = 6.16 N

The lever length of is ~3.5 mm, so torque on stepper motor is 0.022 Nm = 2.2 Ncm.

Let's do some more pessimistic assumptions: lead screw efficiency at 20 %, skewed weight distribution of Y-axis gives double max weight: 1.3 kg. Accelerations of 9 m/s^2. This gives a force of 58.5 N and a torque of 20.5 Ncm, which is still within stepper motor limits at max speed (70 mm/s) for three of the four tested Nema17 stepper motor models tested [http://reprap.org/wiki/Stepper_torque here].

We conclude that a linear actuator based on a lead screw and a Nema17 stepper motor seems realizable.

==== Suggested Tests For Further Validation ====
*A custom gcode generating random movements like shown in [https://youtu.be/6ZVBXBSCAfA?t=2m16s this video].
*Stepping through [http://www.orientalmotor.com/technology/articles/motor-sizing-calculations.html Oriantal Motors' Sizing Calculations].
*Verify stepper motor performance like is done here: http://www.romanblack.com/stepper.htm

==== Leadscrew sourcing viability ====

Some lead screws are already mounted on stepper motors[http://www.ebay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT][http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT]. This improves ease of build. Most of them are 8mm diameter with 8mm travel per revoultion. This would lead to challenges as it forces stepper motors into > 300 rev/min-land.

Good 8mm diameter 15mm travel lead screws can be sourced at http://www.mooreinternational.co.uk/category-31.html. Look for Speedy - Standard, 8/15.

Sources kindly shared by RepRap forums user albatroopa:
{|
!Item
!Part Number
!Source
!Price
!
|-
|3/8-8 4:1 leadscrew (3ft)
|99030A303
|Mcmaster
|$28.53
|-
|3/8-8 4:1 nut (Bronze)
|1343K111
|Mcmaster
|$32.41
|-
|3/8 bearings (flanged)
|6384K344
|Mcmaster
|$6.49
|-
|}

==== Smooth Rod Sourcing ====
*[http://www.ebay.com/itm/OD-5-6-10-12mm-Cylinder-Liner-Rail-Linear-Optical-Axis-Chrome-Shaft-Resistance-/231750293720?var=530954107634&hash=item35f564d8d8:m:moSyRqi54EIs89R0LbqJQIA ebay source that ships to Sweden but not Norway]

==== Problem with Forces Along Lead Screw ====
Some suggest cheap [http://www.cnczone.com/forums/mechanical-calculations-engineering-design/16261-lead-screw-bearings-cheap-ok.html deep groove bearings are ok]. Other say [https://www.reddit.com/r/AskEngineers/comments/3cb0jv/best_configuration_of_radialthrust_bearings_on/ angular contact bearings are what we want].

=== Possibilities of Unknown Importance ===
Could we send bed probe signal through Z-leadscrew? Would avoid a wire and improve scalability.

== Stepwise Definition of 3D Printer ==

=== 3D Printer Signature ===
'''Input''': Power, Build material, Supporting surface(s), Instructions
'''Output''': Physical object

=== 3D Printer Purpose Statement ===
A 3D printer is a machine that synthesizes build material into 3D objects according to a series of pre-determined instructions.

=== 3D Printer Examples ===
We will assume that a mains voltage will power the 3D printer, with the constant shape:
[[Image:3_phase_AC_waveform.svg|250px]][[Image:Cable_Cross_Section.svg|300px]]

For the build material, we will assume filaments behaving roughly as thermoplastics with the constant shape:
...

=References=
{{#tag:ref|FELLEISEN, Matthias. [http://www.ccs.neu.edu/home/matthias/HtDP2e/ How to Design Programs]: an introduction to programming and computing. MIT Press, 2001.|name="htdp"}}

[[Category: D3D]]

D3D Printer Design Process

2016-03-08T04:21:19Z

MarkDilley: Category: D3D

This document lists D3D Printer Design decisions and reasoning behind them in chronological order.
The intention is to make the process as debuggable as possible and facilitate later creation of formal documents such as Design Decision Tree and Conceptual Design diagrams.
It follows the [[D3D_Design_Methodology]].

=Calculations=
==Scalability of Threaded Rod Drive==

= Sources Driving Design Desicions in Priority Order =
#[[D3D_Fusion_printer_design#Higher_Level_Goals]]
#[[D3D_Fusion_printer_design#Desired_Attributes]]
#[[D3D_Fusion_printer_design#Functional_Requirements]]
#[http://reprap.org/wiki/RepRap_Interface_Standard RepRap Interface Standard]
#''The shape of the input determines the shape of the design and tests.''<ref name="htdp" />

= Process =

== Concept Creation ==
'''NOTE:''' We started out this process with concept creation. This deviates from the [[D3D Design Methodology]], but we document it here nontheless.

[[D3D_Printer_Design#Functional_Requirement]] nr 1 is that the printer should be buildable in one day, and a parallelizable build is highly desired.
A random Youtube search around modularity in CNC machines led to discovering the concept of modular linear actuators, as shown by Alexander Stepanenko in a [https://www.youtube.com/watch?v=wkk4zv96Dvo video]. These kind of actuators are sometimes called "linear stages" and are sold as ready-built units[http://www.amazon.com/Konmison-Linear-Actuator-CNC-Machine/dp/B016LRNV1U/ref=pd_sbs_328_10?ie=UTF8&dpID=41t83kKWDIL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1G2FWG037R3NCGMYVKW0][http://www.amazon.com/gp/product/B016MC2RDM/ref=s9_hps_bw_g328_i3].
The concept would allow
#... building linear actuators and other parts at the same time
#... defining a ubiquitous standard (screw position) interface

Normally, we would reason here around advantages that the concept of modular linear actuators could provide, but OSE found its potential exciting enough to put it directly into [[D3D_Printer_Design#Functional_Requirements]].

Instead of diving into stepwise definition of interface and linear actuator, we decided to grab the following low-hanging fruit:
*'''Standard Screw Interface''': Nema17
*'''Linear Actuator''': Stepper Motor + lead screw

=== Why Not... ===
{|
|-
| '''... ball screw?'''
| Price. See [http://www.thomsonlinear.com/downloads/articles/Why_Lead_Screws_Best_Fit_Linear_Motion_Applications_taen.pdf]
|-
| ''' ... threaded rod?'''
| Speed and straightness. See [http://www.protoparadigm.com/news-updates/accuracy-vs-precision-and-threaded-rod-vs-leadscrews-in-3d-printers/]
|-
| ''' ... threadless ball screw?'''
| Kind of hard to put together and risks slipping. See [https://www.thingiverse.com/thing:298212]
|-
|}

=== Verification Steps Taken for Lead Screw + Stepper Motor Concept ===

==== CAD viability ====
[[Image:Linear_module_render1.png|300px]][[Image:D3D_Printer_render_4_jan.png|700px]]

Looks sane...

==== Practical viability of lead screws for 3D printing loads and speeds ====
{|
|-
!Link
!Comment
|-
|https://www.youtube.com/watch?v=gk9lhcTGSH4
|Printing at 75mm/s (fast) with aggressive leadscrew. Lots of rattling from linear bearings. Sub-optimal construction with lead screw not between smooth rods may be cause. 2014.
|-
|https://www.youtube.com/watch?v=reVNrtsDfxQ
|Slow first layer, normal RepRap speed after that. Uses cheap 8/8 mm lead screws. Every time acceleration changes direction, you hear a "bump". Two flanged nuts with a spring between them would fix this. 2015.
|-
|https://www.youtube.com/watch?v=wWZqLwwwx_k
|Printer is called Fina. Leadscrews are 6-start. 18 mm travel/rev. 12 mm diameter
|-
|https://www.youtube.com/watch?v=ULVLZpHSlzc
|Trinitylabs' printer, Aluminatus. They went out of business in May 2014.
|-
|https://www.youtube.com/watch?v=4bMUlu4GF2k
|Trinitylabs again, with Aluminatus printing faster
|-
|http://www.igus.no/wpck/12976/Manus15_3D_printer_3
|In this link, Igus shows off some of their products in a all-leadscrew 3D printer
|-
|http://www.igus.eu/wpck/10783/3Dprinting
|Here Igus shows off more 3D printer applications (under "Application examples")
|}

[http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping's Jon] in mail: "I have been using my Aluminatus heavily for the 2 years or so that I've had it, and it continues to perform very well. I like the linear bearings and lead screws a lot."

==== Theoretical force viability ====
Newtons second law:
F = ma

Total linear actuator weight is approximated like
{|
! Parameter
! Estimated value
! Unit
! Source
|-
| '''Motor: '''
| align="right" | 0.4
| align="left" | kg
| [http://www.osmtec.com/nema_17_step_motor_17_hs.htm stepper motor shop]
|-
| '''Lead screw/Smooth rod: '''
| align="right" | 0.12
| align="left" | kg
| density=8000 kg/m^3, radius=4 mm and length=300 mm
|-
| ''' Linear Bearing '''
| align="right" | 0.015
| align="left" | kg
| [http://www.robotdigg.com/product/13/LM8UU-Linear-Bearing linear bearing shop]
|-
| ''' Hot End '''
| align="right" | 0.05
| align="left" | kg
| [http://www.filastruder.com/products/e3d-heatsink-v6 hot end shop]
|-
| '''X-Carriage (extruder + hot end): '''
| align="right" | 0.67
| align="left" | kg
| Hotend + Motor + Four linear bearings + 0.05 kg of plastic + 20 percent
|-
| '''Linear Actuator Module: '''
| align="right" | 0.81
| align="left" | kg
| Motor + two smooth rods + lead screw + 0.05 kg of plastic
|-
| '''Y-Carriage (X-Carriage + linear actuator module): '''
| align="right" | 1.48
| align="left" | kg
| Linear Actuator Module + X-Carriage
|-
|}

The linear actuator will have to meet following circa-requirements to be realistic:
{|
|-
! Parameter
! Value
! Unit
! Source
|-
| '''Weight load:'''
| align="right" | 0.74
| align="left" | kg
| Y-Carriage weight/2
|-
| '''Max Speed:'''
| align="right" | 0.070
| align="left" | m/s
| [[Stepper Motor]] generally don't want to run faster than 300 rev/min. Lead screws that are more aggressive than 14-15 mm per revolution are hard to source.
|-
| '''Max acceleration: '''
| align="right" | 5
| align="left" | m/s^2
| Requirements/choice
|-
| '''Worst expected Lead screw efficiency:'''
| align="right" | 60
| align="left" | %
| [http://www.cncroutersource.com/lead-screw-efficiency.html CNC router source], [https://youtu.be/HJaNyNrGT0E?t=5m19s Youtube video] showing lead screw is back drivable. Implies > 50 % efficiency[http://www.thomsonlinear.com/downloads/articles/Why_Lead_Screws_Best_Fit_Linear_Motion_Applications_taen.pdf].
|}

Torque from rotational inertia is not included in the table because inertia of the threaded rod is tiny (order of 10^-7 kg m^2).
Newton's second law gives maximum force needed:
F = (0.74 * 5)/0.6 = 6.16 N

The lever length of is ~3.5 mm, so torque on stepper motor is 0.022 Nm = 2.2 Ncm.

Let's do some more pessimistic assumptions: lead screw efficiency at 20 %, skewed weight distribution of Y-axis gives double max weight: 1.3 kg. Accelerations of 9 m/s^2. This gives a force of 58.5 N and a torque of 20.5 Ncm, which is still within stepper motor limits at max speed (70 mm/s) for three of the four tested Nema17 stepper motor models tested [http://reprap.org/wiki/Stepper_torque here].

We conclude that a linear actuator based on a lead screw and a Nema17 stepper motor seems realizable.

==== Suggested Tests For Further Validation ====
*A custom gcode generating random movements like shown in [https://youtu.be/6ZVBXBSCAfA?t=2m16s this video].
*Stepping through [http://www.orientalmotor.com/technology/articles/motor-sizing-calculations.html Oriantal Motors' Sizing Calculations].
*Verify stepper motor performance like is done here: http://www.romanblack.com/stepper.htm

==== Leadscrew sourcing viability ====

Some lead screws are already mounted on stepper motors[http://www.ebay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT][http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT]. This improves ease of build. Most of them are 8mm diameter with 8mm travel per revoultion. This would lead to challenges as it forces stepper motors into > 300 rev/min-land.

Good 8mm diameter 15mm travel lead screws can be sourced at http://www.mooreinternational.co.uk/category-31.html. Look for Speedy - Standard, 8/15.

Sources kindly shared by RepRap forums user albatroopa:
{|
!Item
!Part Number
!Source
!Price
!
|-
|3/8-8 4:1 leadscrew (3ft)
|99030A303
|Mcmaster
|$28.53
|-
|3/8-8 4:1 nut (Bronze)
|1343K111
|Mcmaster
|$32.41
|-
|3/8 bearings (flanged)
|6384K344
|Mcmaster
|$6.49
|-
|}

==== Smooth Rod Sourcing ====
*[http://www.ebay.com/itm/OD-5-6-10-12mm-Cylinder-Liner-Rail-Linear-Optical-Axis-Chrome-Shaft-Resistance-/231750293720?var=530954107634&hash=item35f564d8d8:m:moSyRqi54EIs89R0LbqJQIA ebay source that ships to Sweden but not Norway]

==== Problem with Forces Along Lead Screw ====
Some suggest cheap [http://www.cnczone.com/forums/mechanical-calculations-engineering-design/16261-lead-screw-bearings-cheap-ok.html deep groove bearings are ok]. Other say [https://www.reddit.com/r/AskEngineers/comments/3cb0jv/best_configuration_of_radialthrust_bearings_on/ angular contact bearings are what we want].

=== Possibilities of Unknown Importance ===
Could we send bed probe signal through Z-leadscrew? Would avoid a wire and improve scalability.

== Stepwise Definition of 3D Printer ==

=== 3D Printer Signature ===
'''Input''': Power, Build material, Supporting surface(s), Instructions
'''Output''': Physical object

=== 3D Printer Purpose Statement ===
A 3D printer is a machine that synthesizes build material into 3D objects according to a series of pre-determined instructions.

=== 3D Printer Examples ===
We will assume that a mains voltage will power the 3D printer, with the constant shape:
[[Image:3_phase_AC_waveform.svg|250px]][[Image:Cable_Cross_Section.svg|300px]]

For the build material, we will assume filaments behaving roughly as thermoplastics with the constant shape:
...

=References=
{{#tag:ref|FELLEISEN, Matthias. [http://www.ccs.neu.edu/home/matthias/HtDP2e/ How to Design Programs]: an introduction to programming and computing. MIT Press, 2001.|name="htdp"}}

[[Category: D3D]]

D3D Printer

2016-03-08T04:21:03Z

MarkDilley: Category: D3D

D3D Printer is the 3D printer developed within the D3D Fusion project, optimized for supporting a [[Distributive Enterprise]] through workshop propagation (see [[D3D_Fusion#Chain_reaction_metaphor]].
This page is for a user-perspective point of view on the printer.
For a developer description of the 3D printer design itself (not its usage), see [[D3D Printer Design]].
For a description of the development process, see [[D3D Printer Design Process]].

[[Category: D3D]]

D3D Design Methodology

2016-03-08T04:20:45Z

MarkDilley: Category: D3D

= What this is =
In this document Tobben is scratching his own methodology itch. For methodologies more tightly knit to OSE see [[GVCS_Methodology]], [[Development_Methodology]]. For OSE templates and more on OSE development, see [[Development_Spreadsheet_Template]], [[Development]].

Also note that this document does not cover how to handle teams and similar aspects. It focuses on one designer with one design problem. It is an interpretation and extension of the programming golden standard methodology developed by the [https://en.wikipedia.org/wiki/ProgramByDesign ProgramByDesign] initiative. The gist of this document is in the [[#Stepwise_Definition]] section.

==Overview==
The design process within the designers mind is inherently hard to capture within rigorous formalism without killing it.
It should treated like a wild animal with an enormous home range within the designers thoughts, making unspoken and implicit design decisions and in general behaving in arbitrary ways.
Despite this, there are some things that the designer can do (besides hosting the process in his/her head):
* Observe it
* Describe it
* Measure its outputs (exploring consequences, validation)
* Moderately change its environment (goals, requirements, inspiration, knowledge)
* Help it if it gets stuck

This methodology is intended to help designers do those things in a systematically in order to get the most out of mechanical design processes.

=== Search and Reinforcement Learning Analogy ===
All creative processes can be seen as searches in spaces of thinkable finished and unfinished results
(See for example [https://youtu.be/fThhbt23SGM?t=14m8s Mike Bostock presentation] for more on search analogy).
We'll view design processes as searches trying to arrive at the highest quality finished design with the least amount of effort.

The design process' guide during the search is a continuously updated estimate of what design quality it is heading towards.
Probability for a successful search is determined by both how accurate the estimates are and how the process makes use of them.
Within [https://en.wikipedia.org/wiki/Reinforcement_learning Reinforcement Learning], acting to improve estimate accuracy is called ''exploration'' and acting as if current estimation is good enough is called ''exploitation''. Excluding one of them leads to random design decisions.

In mechanical design, a case of exploration would for example be to build something that you know will fail in order to learn from watching ''how'' it fails.

== The Designer and the Process ==
Design decisions are made continuously and are made based on ideas that arrive at seemingly random times.
We therefore separate ''The Design Process'' and ''The Designer''.
The Process is a source of randomness continuously making an unknown number of small and big decisions.
The designers' work and responsibility is to:
*Identify decisions and ideas
*Describe decisions and ideas
*Work out consequences and validate decisions and ideas
*Try to guide and help the process from a distance
*Help the process loose if it gets stuck

This way of externalizing seemingly unpredictable aspects of creative work has roots in ancient Greek and Roman tradition (see from min 6 of [http://www.ted.com/talks/elizabeth_gilbert_on_genius#t-406473]).

== Before Starting a Design Process ==
The designer should know how the quality of the machine will be measured.
The estimate of what quality we're heading towards is the designer's compass in the vast space of thinkable designs and the design process gets confused without it.

Functional requirements and goals are good, a firm understanding of intended usage is better, direct feedback from actual usage is best.

== Movements in Design Space ==
The design process traverses a vast decision tree while exploring the thinkable design space.
That is, the design process steps through design space by making decisions.

The choice of concepts and design elements determines what kind of movements the process can take within design space.

For example the concepts "left half of machine" and "right half of machine" lets the process take a giant single step to complete machine.
(Exploring "machines with two halves" might be a worthwhile exploration, but might not lead to good design quality in itself...)

The designer should help the design process is by making it aware of the current designs surroundings.
For example, available design space gets limited by choices of
#Which ''inputs'' it is designing to handle
#Which ''primitive design elements'' it includes in the design
#What ''language, concepts and higher order design elements'' it forms and uses

The designer should describe such decisions.
The designer also has to care about questions like "do we need validation?" and "is it buildable?".

= The Designers' Job =
The following is practical advice for helping the design processes and getting the most out of it in a systematic way.

== Keep A Log ==
All thoughts, identified decisions, reasoning around them, lessons learned and similar should be logged in chronological order to help debugging the process.
Note what steps are exploration and what are exploitation.

== The Designer Routine ==
The following practical routine is intended to cover all the aspects of the designers' job.
It should help the designer keep a systematic approach both in
*Keeping documentation creation up to speed when the process moves quickly
*Helping a derailed process get back on its feet

Our designer routine will use three sub-routines:
{|
|-
|| '''Stepwise Definition''': || Heavily inspired by DE's six steps<ref name="htdp" />. Used to describe how we've understood the design (sub)problem at hand.
|-
|| '''Input Definition''': || Used to shrink design space by narrowing the range of accepted inputs.
|-
|| '''Concept Creation''': || Designing things that might be useful for whatever reason. Makes new paths through design space accessible.
|}

These sub-routines recursively call each other, so the designers' systematic logging work will branch out according to how the process explores branches of the decision tree.

A design process is preferably started out by entering Stepwise Definition at the highest possible level of abstraction.
If the process has already done progress in other directions, the designer should calm it down and describe what has already been done in terms of
the sub-routine that is found to be most suitable.
What direction to guide the process next is described in the sub-routine.

If sub-routines may be applied to modules and sub-modules recursively.
That is, when a promising sub-design is found, we may allow the process to explore necessary sub-design and its sub-sub-designs.

When the search has to be rewinded, it is preferred to re-enter the decision tree and calling designer sub-routine in a best-first manner.
That is, consider the log of several previously run sub-routines before resuming the design process, and take note of what branch is being continued on/explored.

=== Helping a Derailed or Halting Process ===
Try jumping out of Stepwise Definition and into Concept Creation whenever
*Language gets too formal to think clearly
*Design progress is so slow that we loose track

Designing unused concepts that can potentially be better defined and built upon later is fine.

Try jumping out of Concept Creation and run under-defined concepts through Stepwise Definition whenever
*Concepts become too random/har to think and reason about
*The design starts to fail tests

Making tests more specific and reviewing previous validations carefully can also be of help.

==Stepwise Definition==
{|
|-
|align=right| 1.|| '''Problem Analysis''': || Give the thing we're going to design a name and describe the types of input and output (a "signature" or "contract").
|-
|align=right| 2.|| '''Purpose Statement''': || Reformulate eventual problem statements into a couple of sentences explaining the purpose of the thing we're designing.
|-
|align=right| 3.|| '''Examples''': || Illustrate the purpose statement by listing some example usages of the soon-to-be designed thing. Serve as criteria of success and are used as tests later.
|-
|align=right| 4.|| '''Sketches''': || Some basic shape and logic of the design is already given at this stage. Write it down.
|-
|align=right| 5.|| '''Being creative''': || Put together parts in ways that will solve the problem. If there's need for further specification of input go to Input Decision. Identify new sub-modules and list them for later stepwise definition.
|-
|align=right| 6.|| '''Testing''': || The creation of a test suite from examples ensuring small inputs work as expected.
|}

==Input Decision==
*List available choices (that we can think of and express, and in reasonable detail)
*If list seems unfinished: Go into Concept Creation
*Explicitly reason around what's known, what's unknown and general pros and cons related to all the different choices
*Write down the decision to explore
*Write down how this limits the design space
*Unless design step is purely exploratory: Validate that limitations doesn't violate requirements in any obvious way.

==Concept Creation==
{|
|-
|align=right| 1.|| Dive into the space of potentially useful (for whatever reason) concepts.
|-
|align=right| 2.|| Do basic validation that the concept should be completely definable/manufacturable. Actually defining/manufacturing it is recommended.
|-
|align=right| 3.|| If concept shows a lot of promise, line up all things that can be considered a sub-module and define them with the Stepwise Definition procedure.
|-
|align=right| 4.|| Review previous design process and re-enter it from where you estimate the best overall probability to arrive at a good design. The re-entrance is what makes the algorithm best-first.
|}

=References=
{{#tag:ref|FELLEISEN, Matthias. [http://www.ccs.neu.edu/home/matthias/HtDP2e/ How to Design Programs]: an introduction to programming and computing. MIT Press, 2001.|name="htdp"}}

[[Category: D3D]]

D3D Thesis Project Plan

2016-03-08T04:20:27Z

MarkDilley: Category: D3D

=Critical Path=
<html><img src="https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/pub?w=1001&h=600"></html>

[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit edit]

=Team Charter=
<html><iframe src="https://docs.google.com/presentation/d/1aTBMiVpDHi6Hs8zXcRK3kwEk1oqxQMbY_faYgtOnGkY/embed?start=false&loop=false&delayms=60000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

[https://docs.google.com/presentation/d/1aTBMiVpDHi6Hs8zXcRK3kwEk1oqxQMbY_faYgtOnGkY/edit?usp=sharing edit]

=Background=
While production machinery have gotten more efficient, work hours have increased and wage growth has slowed down for the average Western worker during the past 30 years.
Ownership and control over means of production gravitates towards fewer people who don't consume their fortunes fast enough to maintain economic growth of the nations.(Piketty)

While increasingly centralized production has been the norm since the Industrial revolution, one notable university project started in 2007 has now achieved the opposite.(Bowyer et al)
The RepRap project created a machine capable of reproducing its own parts, and released all technical details on line with user instructions.(Sells)
New versions of the design started appearing in all corners of the world.
Research in all related areas accumulated in the online community wiki and in its forums, which established a meritocracy similar to that of FLOSS projects.
In addition to being able to self-reproduce, the RepRap machine, a FFF 3D printer, was capable of producing valuable goods.(Pierce)
It was shown that a 3D printer would be a worthwhile economical investment for the average household.(Wittbrodt, et.al)
It was also shown that the open source model was a viable model for development of physical objects.(de Bruijn)
Those who had joined the RepRap community early formed successful enterprises around their new won technical skills.
By ca 2013, it was widely believed that means and knowledge of 3D printer would have to centralize again in order to penetrate the household market. (refer to Stratasys/Makerbot aquirement)

But looking at 3D printer design statistics in 2016, it is clear that 7.8 - 20 % of the worlds 3D printer population are still RepRaps. (3Dhubs, Smarttech Publishing report, Ultimachine sales numbers)
More so, the majority (better with exact percentage here) of RepRaps are based on designs named after one single RepRap community member, Josef Prusa.
There are more Prusa-designed 3D printers in the world than the combined number of printers produced centrally by the two largest brands. (Build under with data!)
He learned FFF 3D printing entirely within the community and started the effort that became the first design to be realistically buildable during a weekend workshop.
Members of the community called it Prusa Mendel or just "the Prusa printer".
Josef Prusa himself travelled across Europe, giving workshops and meeting RepRap community members in person.
This formed the printer designs Prusa i2 and Prusa i3 to be workshop-friendly with several known modifications and a large base of workshop-educated users that are still active today.
Many former workshop participants base enterprises on remixed designs, but few base their enterprise on workshops.(ref)

This makes the RepRap Prusa the first open source hardware (OSHW) designs to channel (some significant share) of a billion dollar market(ref) towards the spread out, small scale makers, scientists, hackers and dealers costituting of the OSHW community all over the world.
Many papers have been written on how RepRap distributes production power and economical opportunity.
Build something from them here and list what parts of the RepRap project they mention as distributing production power and economical opportunity.
*Self-reproduction?
*Internet?
*Expired patents?
*Open source licences?
*Hacker culture?
*Others?

The Prusa workshops had the limitation that they continued only as long as Prusa travelled.
Others have tried to make workshops based on Prusa designs economically sustainable without the travelling, and failed.(refer to Berlin fablab, Barcelona fablab)

=Purpose=
This project aims to design a 3D printer workshop with self-reproducing properties.
Focus will be on shaping workshop plan trying to identify and include the right tools and incentives for reproduction.
The workshop plan is the inheritance material in this story, and we will modify and evaluate it through four workshop/evaluation iterations.
On each iteration, data will be collected and analyzed to improve our understanding of how to facilitate workshop self-reproduction.

Similarly to how the RepRap project focused solely on making its 3D printer design capable of self-reproduction, this project focuses only on the self-reproduction of the workshop.
Any technical features and explicit functional requirements should be seen as consequences of the self-reproduction goal that might change as our understanding of workshop self-reproduction changes.

=Goal=
First 1 day 3D printer workshops where machines for every participant are built, before April 2016.
Identify 3 major workshop replicability metrics, backed with data, before May 2016.
Describe 3 major metrics’ usage and interpretation, backed with data, before June 2016.
4 successful D3D workshops arranged, with increasing relative measured replicability, before July 2016.
Publication of Master’s thesis before August 2016.
Achieve workshop replication before September 2016.

If we do extraordinary well we hope to see a period of self-sustaining workshop reproduction and gradual improvement through evolutionary/free market selection mechanisms.
This would then serve as a proof-of-concept for an enterprise model that relies on actively training new market competitors and thereby sharing all research results.
This enterprise model, called a Distributive Enterprise, is the goal of this projects' parent project, D3D Fusion.

= Deliverables =
*Hosting four 1-day workshops
*A 3D printer design tailored for 1-day workshops
*Coherent documentation of everything involving the workshop, called the "Workshop Plan"
*A Master's thesis underpinning the Workshop Plan with data and theory

= Scope and Limitations =
We improve the workshop plan with the intent of making it self-reproduce.
The delivered 3D printer design's other specifications will not be superior to those of other 3D printer designs on the market.
We will focus on achieving the first self-reproduction and work on the part of the Workshop Plan we find most efficient at the time.

As soon as that is achieved, we will stop development and rely on the plan "improving itself" through evolution/free market- like selection mechanisms.
Market plans, recruitment plans, tax-plans and other parts of a normal enterprise are not included in the Workshop Plan.
We will not develop serial- or mass production of 3D printer parts within this project.

=SWOT Analysis=
The project is dead if we don't get:
#Hardware
#Participants
#Data

... in that order. Securing these three must be prioritized before anything else.

==Strengths and Opportunities==
#Marcin's experience with workshops
#Torbjørn's experience with RepRap
#Long project (6 months)
#Aligning interests with
##Other OSHW enterprises (Lulzbot, Prusa3D, E3D, Ifixit, etc)
##Other Researchers (MOST lab, etc)
##Existing active communities (RepRap, Arduino, Instructables, Fablabs/Makerspaces, etc)
#Marcin and Torbjørn both plan to make use of deliverables
#Philosophical, ethical and legal background already worked out and well known
#Income from workshops gives opportunity of economical sustainability

==Weaknesses and Threats==
#Scope creep, loss of focus
#Visa application processing time
#Delivery times for hardware orders
#Difficulties with recruiting participants
#Too high work load
#Printer design has unexpected technical difficulties
#Torbjørn bankruptcy
#OSE bankruptcy
#Conflict between OSE needs and university requirements
#Torbjørn gets distracted by side projects

==SWOT Matching==
{|
|-
!Strength/Opportunity
!Weakness/Threat
!Comment
|-
| 1, 2
| 1
| Focusing on what we already know avoids dead ends and wasted time
|-
| 3
| 3
| Good planning and early orders can prevent having to wait too much for hardware deliveries
|-
| 4
| 3
| Asking the community where to buy and using known suppliers increases chance of getting stuff in time
|-
| 1, 4
| 4
| Reaching out will be invaluable to find enthusiastic participants
|-
| come
| back
| to this
|}

= Related Projects within OSE =
The super-project, [[D3D Fusion]] focuses on people and [[Distributive Enterprise]].
This thesis project focuses on the workshop, including the [[D3D Printer]].

= Backlog of Tasks =
Use Scrumy:

<html><iframe src="https://scrumy.com/d3d" width=900 height=500></iframe></html>

*Evaluate RAMBO fitness for purpose (can it handle enough current). Otherwise use RAMPS with drv8825.
*Set correct V_ref and steps per mm (drivers/firmware)

*CAD l_module, including interfaces
*Order parts for l_module prototyping
*Design tests for l_module prototype
*Build l_module prototype
*Test l_module prototype, possibly iterate design
*Estimate costs for l_module design in $ and prep-time
*Record build time l_module (when built by non-developer)

*CAD frame, including corner brackets
*Order parts for frame prototype
*Design tests for frame prototype
*Build frame prototype
*Test frame, possibly iterate design
*Estimate costs for frame design in $ and prep-time
*Record build time frame (when built by non-developer)

*CAD the tool mount part, including bed probe
*Order parts for tool-mount prototype
*Design tests for tool-mount prototype
*Build tool-mount prototype
*Test tool-mount, (test reliability of bed probe)
*Estimate costs for tool-mount design in $ and prep-time
*Record build time tool-mount (when built by non-developer)

*Order hot end for extruder prototype

*CAD the tool extruder
*Order parts for extruder prototype
*Design tests for extruder prototype
*Build extruder prototype
*Test extruder, possibly iterate design
*Estimate costs for extruder design in $ and prep-time
*Record build time extruder (when built by non-developer)

*Milestone: Build times for l_module, frame, tool mount and extruder recorded
*Milestone: All modules have module-tests created
*Milestone: All modules pass module-tests
*Milestone: First complete D3D Printer prototype built

*Order Prusa Steel kits
*All instructors test out documentation and kit by building kit themselves

*Define "workshop reprodicability"
*Define what data to collect during WS and how

*Define which workstations should exist in WS (before WS1)
*For each workstation plan what hardware is needed
*Design testing procedures for each workstation
*Write instructions for each individual workstation
*Print out two sets of documentation for every workstation
*Plan and draw WS local layout and flows (workstations' relative placement and parts/participants-flow between them)
*Put chairs and tables in place in WS local
*Build complete example-printer and all example-modules for WS workstations (before WS1)
*Place example-modules, tools, instructions, test-rigs, nuts and bolts on workstations (before WS1)
*Create WS1 time schedule
*Simulate complete workshop (time: between USA arrival and first workshop)

*Compile data-collection routine, build-steps, schedule, workshop local layout and hardware flows and welcome letter into one document: "WS1 Plans". This will evolve into project main delivery
*Milestone: First version of Workshop Plans released
*Send out WS1 Plans to participants

*Host WS1 according to WS1 Plans
*Depending on type of data-collection: ask participants to fill out form.
*Milestone: First WS completed

*Collect instructor experiences through WS retrospective/evaluation meeting
*From WS1 data determine bottlenecks for reproducability (cover at least build-process, participant satisfaction and instructor satisfaction).
*Compile "WS1 Experiences and Key Metrics", thesis quality, presented on wiki (Were Prusa Steel design suitable for paralell WS production?)

*Do design improvements for D3D Printer for workshop (prepare design for WS2 action)
*Order for WS2:
**steel
**PLA filament
**stepper motors (and lead screws + coupler if not already lead screw shaft on motor)
**electronics
**endstops
**BuildTak or similar
**linear bearings
**smooth rods
**hot ends (with thermistor, resistor, maybe PTFE tubing)
**hobbed bolts
**nuts and screws
**power supplies
**Force Sensistive Resistors
*Compile BOM for WS2 with sources and prices
*Print parts for WS2
*Cut steel parts for WS2

*Adjust WS local layout to match D3D Printer build (instead of Prusa Steel)
*Compile "WS2 Plans"
*Send out WS2 Plans to participants

*Host WS2 according to WS2 Plans

*Depending on type of data-collection: ask participants to fill out form.
*Collect instructor experiences through WS retrospective/evaluation meeting.
*From WS2 data determine bottlenecks for reproducability (cover at least build-process, participant satisfaction and instructor satisfaction).
*Compile "WS2 Experiences and Key Metrics", thesis quality, presented on wiki

*Improve WS Plans
*Decide whether to use Prusa Steel or D3D Printer for remaining 2 workshops.

*Prepare WS3
*Host WS3
*Compile "WS3 Experiences and Key Metrics", thesis quality, presented on wiki

*Improve WS Plans

*Prepare WS4
*Host WS4
*Torbjørn returns to Sweden
*Compile "WS4 Experiences and Key Metrics", thesis quality, presented on wiki
*Milestone: Four workshops hosted

*Finish thesis
*Present

= Needed Resources =
*Prototype hardware
**Motors
**Frame parts
**Hot end
**Lead screws, nuts and lubrication, different kinds and materials
**CAD files
**Electronics (including different kind of motor drivers)
**Stopwatch
*Prototyping lab in Sweden (or Norway)
*Prototyping lab in the USA
*Visa & airplane ticket
*Workshop helpers (instructors)
*Participants
*Parts for D3D Printers
*Quetionare/questions for participants after WS (expert say: "Use semi-structured interview form. Questions on paper, record answers and transcribe is ideal. From Wikipedia: '... allowing new ideas to be brought up during the interview as a result of what the interviewee says'")
*16-20 WS tables
*Tools for all WS tables
*Prusa Steel kits
*Complete workshop plans (including instructions)

= Map of Deliverables =
[https://www.mindmup.com/#m:a1e6297c80b1b801333fdf43e038109e55 Mindmap via mindmup.com]

= Map of Resources in Swedish =
[https://www.mindmup.com/#m:a1892183d0b1a501333fdf43e038109e55 Mindmap via mindmup.com]

= TODO this page =
*Copy relevant stuff from https://www.overleaf.com/read/vmpdtnzsgdgg over here...

[[Category: D3D]]

Category:D3D

2016-03-08T04:20:14Z

MarkDilley: .

D3D Thesis

2016-03-08T04:19:26Z

MarkDilley: Category: D3D

{{RightTOC}}
See also [[Tobben Log]]

=Introduction=
This is the thesis sketching and working document. References, quotes, data are placed at the top of this page, and baked into thesis sketch at bottom of page as time allows.

=Critical Path=
<html><img src="https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/pub?w=1001&h=600"></html>

[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit edit]

=Team Charter=
<html><iframe src="https://docs.google.com/presentation/d/1aTBMiVpDHi6Hs8zXcRK3kwEk1oqxQMbY_faYgtOnGkY/embed?start=false&loop=false&delayms=60000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

[https://docs.google.com/presentation/d/1aTBMiVpDHi6Hs8zXcRK3kwEk1oqxQMbY_faYgtOnGkY/edit?usp=sharing edit]

== Tobben's Available Work Hours, D3D Thesis Project ==

*Ca 50 work hours: Feasibility study. Is the task suitable? Write project description. Present tentative project plan for the university examiner.
*Assure that contact between supervisor (Marcin) and examiner is established.
*Ca 650 work hours: Engineering work and report writing.
*Ca 50 work hours: Form opposition.
*Other administrative work such as self-evaluation report and handling communication: ca 50 work hours.
*Total 800 work hours

= Earlier Work =
==Printer Designs==
'''Troublemaker 1:'''

*Proprietary formats for some of the files, AutoCAD (dwg) - [http://www.thingiverse.com/thing:263814]
*NC license - license incompatibility issues. Need to resolve if we use any of these files.

'''Troublemaker 2:'''

*Blog Post 1 - [http://irnas.eu/other%20projects/2015/08/28/troublemaker-v2/]. Design spec is to be full open source hardware.
*Blog Post 2 - [http://irnas.eu/other%20projects/2015/12/07/new-generation-Troublemaker-3D/]
*License not stated at repo- [https://github.com/IRNAS/Troublemaker2]

'''Lulzbot'''

Lulzbot has an open source bed leveler. http://lulzbot.com

'''Contraptor'''

http://www.contraptor.org/

Do-it-yourself reusable construction set for hands-on learning, prototyping cartesian robots. (CC-BY-SA)

==Workshops and Printer Designs Developed for Workshops==

'''Prusa Mendel'''

It was the first printer to be realistically build-able during a weekend workshop[https://ia600801.us.archive.org/17/items/3D-printing-podcast-prusa-mendel/02-3DPS-josefPrusa-reprap.ogg] (this was 2009-2010). It's printed parts took 10 h to print, compared to the 20 h of its main contester at the time of release, the Sells Mendel[https://ia600801.us.archive.org/17/items/3D-printing-podcast-prusa-mendel/02-3DPS-josefPrusa-reprap.ogg]. Many Reprappers wanted to print printers for their friends at this time, so it received a lot of initial interest for its short print time[http://forums.reprap.org/read.php?1,70314,70447]. It established a reputation as easily customizable.

Josef Prusa was active in the community[http://blog.reprap.org/2011/11/prusa-iteration-2.html], listened to feedback and the git repo was updated almost every week. Mean days between commits on master branch: 5.5[https://github.com/prusajr/PrusaMendel]. He would travel the world giving workshops, and managed to pay airplane tickets by pre-selling the printed parts to workshop participants.

Estimated number of Prusa or remixed Prusa printers by January 15 2014 worldwide, based on retailers' summed estimates[https://archive.org/details/3D-printing-podcast-prusa-mendel]: ~70000 to 80000 (300 of these printed by Prusa himself)

He currently sells printers assembled and kit printers[http://prusa3d.com/] through an OSHW enterprise. Most customers by January 2014 was companies[https://ia600801.us.archive.org/17/items/3D-printing-podcast-prusa-mendel/02-3DPS-josefPrusa-reprap.ogg].

'''MOST lab workshops'''

The MOST lab has a concept that's very similar to D3D Fusion. They have
*Their own kit and kit supplier
*Detailed online documentation describing both how to [http://www.appropedia.org/Athena_Build_Overview build] the printer and how to [http://www.appropedia.org/Delta_Build_Workshop host a workshop]
*Gathered [http://www.appropedia.org/Evaluation_of_RepRap_3D_Printer_Workshops_in_K-12_STEM data] from workshops
*Free software source code and design files
*A separate Train-the-trainer program

==Distributive Ideas and Documentation==
'''Seed Factory'''
Dani Eder had a similar initiative in 2013, called [http://www.seed-factory.org/ Seed Factory]. He wrote a [https://en.wikibooks.org/wiki/Seed_Factories Wikibook] where he introduces several useful concepts and shares lots of engineering knowledge.

==Funding Mechanisms for Open Source Work==
The following mechanisms are places online with companies behind them that facilitates/organizes standard bank- or Bitcoin transactions.
Some of them give users Internet tools and space for presenting themselves and/or their projects.
In general, creating them doesn't seem too hard, and the competition seems rough since there exist more than 40[http://kickstarteralternatives.com/] crowdfunding pages in the Internet.
Only a very small selection is presented below.

The presented mechanisms don't teach how to do work, they only give technical help with how to ask for money.

===Pre-selling/Crowdfunding project-wise===
'''[https://kickstarter.com Kickstarter]'''
lets any (approved) project start a public fundraising campaign online (crowdfunding). All-or-nothing funding model. USA-centric. Manual approval of campaigns based on "creativeness" criteria. Products need not be open source.

'''[https://www.indiegogo.com/ Indiegogo]'''
offers less strict approval criteria than Kickstarter. No all-or-nothing model (sometime makes contributions be more like donations that pre-sales).

'''[https://www.bountysource.com/ Bountysource] Fundraisers'''
is similar to Indiegogo but focuses solely on developers of free software and OSHW. Bountysource actively helps in connecting with potential sponsors.

===Monthly Donations Person-wise===
'''[https://flattr.com/about Flattr]'''
offers a convenient way to donate small amounts on a monthly basis. After registration and filling the Flatter account, setting up monthly donations to another user takes only one click.

===Donations Feature-wise===
'''[https://www.bountysource.com/ Bountysource] Founties'''
lets vackers initiate and/or (crowd)fund bounties. Developers hunt these bounties by solving the specified issues or feature requests. Backers judge if solutions are good enough.

'''[https://freedomsponsors.org/ Freedomsponsors]'''
is very similar to Bountysource bounties.

===Monthly Donations Team/Project-wise===
'''[https://salt.bountysource.com/ Bountysource Salt]'''
Turns donations into monthly salaries for developers of free software and OSHW. To recieve the money, developers promise to spend some number of hours working on the specific project.
'''[https://snowdrift.coop Snowdrift]''' is exploring the idea of network effects (organizes donations so that more backers results in more backing per backer). For free open and libre projects only.

== Self-replication or Self-reproduction ==
"Replication seeks to copy an entire system without error, while reproduction
includes a developmental process that allows for variations."<ref name="Adams_and_Lipson" />

= Difficulties =
#Making actual potential workshop instructors in a short time. I (Tobben) have never seen a newbie that became a good instructor in < 1 year. Confirmed by MOST lab having separate (and very detailed) train-the-trainer program.

= Counting RepRaps =
The RepRap Project did their own RepRap count in 2010, which they described in their report ''RepRap - the replicating rapid prototyper'':
<blockquote>
Owing to the free distribution of the machine it is difficult
to make a worldwide estimate of the number of RepRaps
and RepStraps there are, but the sale of electronic kits for the
machine (which are also produced commercially) sets a lower
limit of 3000 machines. However, some people construct
their own electronic kits rather than buying from market.
About 4500 machines would seem to be a conservative
estimate of the total population at the time of writing this
paper (i.e., in 2010).
</blockquote>

Josef Prusa used similar methods to estimate that there were ~70k - 80k Prusa machines (including derivatives) in 2014.[https://ia600801.us.archive.org/17/items/3D-printing-podcast-prusa-mendel/02-3DPS-josefPrusa-reprap.ogg]

== 3D Hub's numbers ==
Source of these numbers is [https://www.3dhubs.com/Trends 3dhubs Trends page] retrieved Jan 5 2016.

The reported percentage of Prusa designs is 10.

The reported percentage of RepRap-manufactured 3D printers is 15.5. That's about twice as high as what other sources report(should ref here).
This could be explained by RepRap owners being more proud or their printers (they've built them themselves), or by the sharing-minded culture within the RepRap community.

We should expect the Prusa count to be as skewed/biased as the RepRap count, which leads us to assume a Prusa percentage of ca 5.

= Workshop Reproducibility =
In this thesis, the term "self-reproducing" will be used to describe a property associated to a set of workshop plans.
When a workshop student (former participant of physical workshop or not) organizes a workshop event based on copied (and maybe modified) workshop plans, then the plans have self-reproduced.

We will call it "direct self-reproduction" when a former participant of a physical workshop organizes a workshop based on the set of workshop plans.
If the organizer of the workshop using the plans have never attended such a workshop herself, then the WS plans have spread through "indirect self-reproduction".

The WS plans will contain tools and incentives for potential WS organizers.
The better the tools and the stronger the incentives, the more WSs will be based on the WS plans.
Our metrics should therefore capture the quality of the tools and the strength of the incentives.

Quality of the tools may be measured along for example the axes:
#Do they enable fast completion of task? How fast, compared to what?
#Do they require additional tools to work, or are they complete/independent?
#How much maintenance does it need to keep working over time?

The strength of incentives can be measured along:
#Net $-income per invested work hour?
#Predictability of $-income?
#Possibility of making friends?
#Fair cred and respect within community?
#Possibility for gaining valuable knowledge?
#Possibility for gaining provable knowledge (certificates or similar)?
#Sense of ethics and meaning?
#Sense of fun?

= Thesis =
== Line of Reasoning ==
A line of reasoning I might be able to build my Master's on. After each number comes a sentence that builds the line of reasoning (the rest is just fill-in which will be improved later).

0. Intro: Thomas Piketty has presented firm evidence that profit from ownership is rising faster than profit from labour, resulting in greater economical inequality in Europe and North America. His proposed solution of heavier taxation of the rich has influenced the old and polarized discussion about taxation only slightly. Big companies influence lawmaking and they have the skills to take advantage of any hole in tax legislation worldwide. The new global market has made them fewer and more powerful. A global authority and tax legislation would be needed to control them, but something like that is not on the horizon yet.

1. Economical inequality is bad, but it is not the unequal distribution of money that leads to fundamental social problems, it is unequal distribution of power, so rather than only redistributing money, we could fight inequality by also redistributing ownership of the means of production. This could mean distributing control and ownership of the stock market or it could mean making the production machines themselves distributable, and give smaller groups controll over smaller production machines.

This thesis develops a socially and economically sustainable business model that distributes itself and generally useful machines as part of its core strategy.

2. The GNU project and the Free Software Foundation (FSF) have developed computer programs and licencing schemes that lets anyone take control over their computing machines, making them potential production machines for their owners. Software, and information in general, is a very scalable approach to distributing power since it is so easily copied and transmitted. Their success in empowering the owners of computers running their software is shown clairly by the academical and programmer communities' strong preference for operating systems based on the GNU one, and the wide usage of FSF's licences.

3. However, GNU's and FSF's organizations have relied on donations and have been criticised for not being economically sustainable and not developing economically sustainable business models for the users they seek to empower. The free software community argues that proprietary software is unethical, but has so far avoided the responsibility of being everyones business advisor in order to make them behave ethically.

4. The RepRap Project, initiated by Adrian Bowyer has designed and distributed generally useful production machines by giving the hardware itself the possibility of reproducing a large fraction of it's own parts. The RepRap machines in addition can produce a wide rande of useful goods, and Adrian describes the RepRap/Human relation as a symbiosis comparable to that of Flowers/Bees. A fundamental difference between the Human/RepRap symbiosis and the Flowers/Bees would be that humans are not born to RepRap like bees are born to collect nectar. Humans needs to get motivaton and skills added after we're born to initiate the symbiotic relation.

RepRap workshops are events where RepRappers share and develop their skills. At a ceirtain type of workshops, often called build workshops or assembly workshops, skill transmission happens while participants builds their own machines from parts produced or sourced by other RepRappers.

5. We've observed RepRap assembly workshops for some time, the most successful ones being those of Josef Prusa and friends resulting in > 200.000 Prusa machines built to this date. The first Prusa RepRap design was a simplification of previous designs, shortening its assembly workshops to fit in a weekend. This was an important threshold making assembly workshop attendance possible for people with full time jobs.

6. The Prusa machines have spread, but the number of RepRap assembly workshops has declined. The common way to explain this is purely economical. Assembled RepRaps have gotten so cheap that people can afford skipping the assembly process. This explanation ignores the skills viewpoint and the possibility of social motivation. It also ignores the important time consumption threshold of one weekend.

7. Another way to explain declining assembly workshops is that RepRap machines have self-replicating properties but the workshops themselves does not. A workshop participant will typically not go into hosting workshops him/herself because
* High quality teaching material source files are not available
* RepRap teaching requires a different of skills than RepRap assembly
* There's no social community dedicated to sharing reprap worskhop knowledge. The RepRap forums typically focus on machine design.
* Participants' willingness to invest time and money into traditional assembly workshops is declining.
* Arranging workshops takes more than one weekend, so the host can not have a full time job. Hosts must make the workshops their job or arrange the workshop over weekends.

We can quantify the length of a self-replication cycle for a machine or an event by recording time needed for complete self-replication and the number and complexity of human actions needed for self-replication. Both minimum and average times are interesting to record. With recording number and complexity of actions we mean counting clicks, counting screws, unique part count... This will not be absolute metrics, but still useful for comparison.

We can quantify possibility of self-replication by assessing the requirements on the environment, counting the external inputs (vitamins).

We can quantify motivation of self-replication by and by comparing motivational factors, such as honey, money, 3D printed parts or social creds, with required investments.

8. We can combine the above three quantities into an analysis of machine or event viral replicability. A short self-replication cycle along with widely available external inputs and strong motivational factors makes more viral replicable machines and events.

9. To shorten self-replication cycle and lower the number of external inputs to the workshop, we should provide participants with Live USB sticks containing a libre (free as in Free Software Foundation) operating system along with all the information, programs and instructions needed to complete a workshop, host a workshop and contribute to the RepRap Workshop community.
This Live USB operating systems will itself be of high viral replicability since it can copy itself onto a USB stick with < 20 clicks of a mouse, and within 10 minutes of time.

== Title ==
== Abstract ==
== Introduction ==
== Background ==
While production machinery have gotten more efficient, work hours have increased and wage growth has slowed down for the average Western worker during the past 30 years.
Ownership and control over means of production gravitates towards fewer people who don't consume their fortunes fast enough to maintain economic growth of the nations.(Piketty)

While increasingly centralized production has been the norm since the Industrial revolution, one notable university project started in 2007 has now achieved the opposite.(Bowyer et al)
The RepRap project created a machine capable of reproducing its own parts, and released all technical details on line with user instructions.(Sells)
New versions of the design started appearing in all corners of the world.
Research in all related areas accumulated in the online community wiki and in its forums, which established a meritocracy similar to that of FLOSS projects.
In addition to being able to self-reproduce, the RepRap machine, a FFF 3D printer, was capable of producing valuable goods.(Pierce)
It was shown that a 3D printer would be a worthwhile economical investment for the average household.(Wittbrodt, et.al)
It was also shown that the open source model was a viable model for development of physical objects.(de Bruijn)
Those who had joined the RepRap community early formed successful enterprises around their new won technical skills.
By ca 2013, it was widely believed that means and knowledge of 3D printer would have to centralize again in order to penetrate the household market. (refer to Stratasys/Makerbot aquirement)

But looking at 3D printer design statistics in 2016, it is clear that 7.8 - 20 % of the worlds 3D printer population are still RepRaps. (3Dhubs, Smarttech Publishing report, Ultimachine sales numbers)
More so, the majority (better with exact percentage here) of RepRaps are based on designs named after one single RepRap community member, Josef Prusa.
There are more Prusa-designed 3D printers in the world than the combined number of printers produced centrally by the two largest brands. (Build under with data!)
He learned FFF 3D printing entirely within the community and started the effort that became the first design to be realistically buildable during a weekend workshop.
Members of the community called it Prusa Mendel or just "the Prusa printer".
Josef Prusa himself travelled across Europe, giving workshops and meeting RepRap community members in person.
This formed the printer designs Prusa i2 and Prusa i3 to be workshop-friendly with several known modifications and a large base of workshop-educated users that are still active today.
Many former workshop participants base enterprises on remixed designs, but few base their enterprise on workshops.(ref)

This makes the RepRap Prusa the first open source hardware (OSHW) designs to channel (some significant share) of a billion dollar market(ref) towards the spread out, small scale makers, scientists, hackers and dealers costituting of the OSHW community all over the world.
Many papers have been written on how RepRap distributes production power and economical opportunity.
Build something from them here and list what parts of the RepRap project they mention as distributing production power and economical opportunity.
*Self-reproduction?
*Internet?
*Expired patents?
*Open source licences?
*Hacker culture?
*Others?

The Prusa workshops had the limitation that they continued only as long as Prusa travelled.
Others have tried to make workshops based on Prusa designs economically sustainable without the travelling, and failed.(refer to Berlin fablab, Barcelona fablab)

=== Societal Impact of Digital Technology ===
“Digital technologies change
rapidly, but organizations and
skills aren’t keeping pace.
As a result, millions of people
are being left behind. Their
incomes and jobs are being
destroyed, leaving them
worse off … than before the
digital revolution...”<ref name="brynjolfsson2012race"/>

== Theory ==
== Method ==
=== Software tools ===
== Result ==
== Discussion ==
== Conclusions ==
== References ==
<references>
{{#tag:ref|BRYNJOLFSSON, Erik; MCAFEE, Andrew. [http://raceagainstthemachine.com/ Race against the machine: How the digital revolution is accelerating innovation, driving productivity, and irreversibly transforming employment and the economy]. Brynjolfsson and McAfee, 2012.|name="brynjolfsson2012race"}}

{{#tag:ref|ADAMS, Bryant; LIPSON, Hod. A universal framework for analysis of self-replication phenomena. Entropy, 2009, 11.2: 295-325.|name="Adams_and_Lipson"}}

</references>

== Appendix ==

[[Category: D3D]]

D3D Fusion Project Plan

2016-03-08T04:18:58Z

MarkDilley: Category: D3D

D3D Fusion is a long-term project with long-term goals, phases and so on.

= High Level Goals =
Being the first [[Distributive Enterprise]]

= Goals =
*Recruitment/enterprise propagation through MOOC as well as workshops
*Building a community of rich collaboration between D3D enterprises
*Ensuring software compatibility within the community by releasing and maintaining a OSE distro
*Dedicated and well documented FreeCAD workbench for improving on 3D printer design

=Phase 1: Bootstrap=
D3D Fusion will be bootstrapped by the sub-project [[D3D Thesis]].

[[Category: D3D]]

3D Printer Log

2016-03-08T04:18:49Z

MarkDilley: Category: D3D

=Sat Jan 23, 2016=
Added 'latest team meeting' video to [[D3D Development]]. Jonathan joins team. Planning Factor e Farm build data collection next week, and with those results, we will go forward with improvements prototyping with Jonathan Kocurek, Torbjorn Ludvigsen, and possibly Joshua Langevin and Will Bombardier.

=December 23, 2016=
Started [[D3D Development]] - "The world's first one day, economically sustainable 3D printer build workshop for a 3D Printer that works."

[[Category: D3D]]
[[Category:Logs]]

Folgertech Kit

2016-03-08T04:18:34Z

MarkDilley:

=Build Instructions According to Module-Based Design=

=Source of Kit=

*See [http://folgertech.com/products/folger-tech-reprap-2020-prusa-i3-full-aluminum-3d-printer-kit]

=Build Instructionss from Folgertech=
These contain details, but procedures are inefficient and not in the same order as should happen in a swarm [[XM]] build. These are modified for the OSE case, though individual details are still relevant.
*Folgertech's Google Drive - [https://drive.google.com/a/opensourceecology.org/folderview?id=0B9b1NbuMK524fldIWWVCa0xfSXAtZmttcDhrbjBMeFNWcENBdVUzWnhtWDZ2YWdHVXpoUXM&usp=drive_web]

=Build Results=
<html><iframe src="https://docs.google.com/presentation/d/1duikQl9HMfHuUVAIQv4cDy1sGWZLujFzLxMRIGej5AY/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>
=Build Pictures=
[[Image:folgertechbuild.jpg|700px]]

See [https://drive.google.com/drive/u/0/folders/0B7pE5Y9PpJCXZDFNeW5PZkx6YkU Folgertech Prusa i3 OSE Google Drive]].

=Build Review=
*See copious data points in the spreadsheet at [[Data Collection]]

=Improvements=
The main improvement that we will make is adding automatic bed leveling.
See [[Research_On_Inductive_Proximity_Sensors]].

#'''Note: correction needs to be made based on the top 2 posts here - on end stop plug in location and change in firmware. [http://forums.reprap.org/read.php?406,512329,569248#msg-569248]. This Github note [https://github.com/therippa/Marlin] appears to say the same thing. Further, the first link also states that the firmware is outdated - outside of hte xmax issue mentioned.
#Upgrade firmware, including auto bed level with inductive sensor - [http://www.tested.com/tech/3d-printing/561787-testing-folger-tech-2020-i3-3d-printer/]
#Anti-backlash nut case and belt tensioner - [http://www.thingiverse.com/thing:694575]
#Improvements on Thingiverse - auto level, cable chain, endstop improvements, etc. - [http://www.thingiverse.com/QuadBert/collections/folger-tech-2020-prusa-i3/]
#X endstop replacement - [http://www.thingiverse.com/thing:1225266]

==Candidates For Improvement Resolution==
#Customized firmware found [https://github.com/cyberkni/Marlin-Folger2020i3 here].
#Libre sensor and fan brackets for Folgertech Prusa found [https://www.thingiverse.com/thing:671600 here]. Our copy of the same files: [[File:Induction_Sensor_Fan_Bracket_for_Folgertech_Prusa.zip]]. Also see [https://www.thingiverse.com/thing:1201050 elkayem's solution on thingiverse]. Print in heat resistant material (not PLA).

=Other Instructionals=

*Reddit thread on building FPi3 - [https://www.reddit.com/r/Reprap/comments/42vpku/i_recently_ordered_a_folgertech_prusa_i3_2020_and/]
*Github Community Folgertech Prusa i3 documentation - [https://github.com/cyberkni/FolgertechManuals/blob/master/2020i3/README.md]. No alignment procedure mentioned.
*Extensive list on Folgertech Prusa i3 2020 resources - [https://github.com/vonnieda/FolgerTech-Prusa-i3/wiki/RepRap-Forum-Thread-Resources]
*Build videos - [https://www.youtube.com/playlist?list=PLeMdlmlLkOdeoIw7B0-8DTWRjz8Nn1hnL]
*Wikia page - [http://folgertech.wikia.com/wiki/Main_Page]
*The Folgertech Drive source itself is updated - [https://drive.google.com/folderview?id=0B9b1NbuMK524M1JFM0IyNm4xOHc&usp=drive_web]

=Software/Firmware=
*'''Firmware''' - Marlin, uploaded via Arduino IDE interface. Firmware is used to only communicate with software, to interpret g-code as related to the geometry of the 3D Printer - for example delta vs. right angle configuration.
*'''Software''' - on host computer - Repetier. Calls upon Slic3r for slicing strategy. Appears to control various 3D Printer parameters.
:*What settings are adjusted in the firmware, and what settings are adjusted in the software?
*Note that firmware may have to be updated based on the specifics of the 3D printer. So for example, we may not be able to use the same Marlin as [[Prusa i3 Marlin]] - so we download one version already set for ours - [[Folgertech 2020 Prusa i3 Marlin]]. ('''it turned out that most of the motors were reversed in this firmware compared to original build from the Folgertech instructional, and the x endstop had to be changed from its position of MIN to MAX as in the Improvements section above.)
*Marlin is one option for firmware. Others are Repetier Firmware, RepRap Firmware, Teacup, Franklin.

==Reprap Wiki Page on Gcode==
It's the best, but it sucks regarding modularity concepts. - http://reprap.org/wiki/Gcode

=Software, Calibration, Testing=
==Live Linux==
In order to eliminate any software issues, OSE is preparing a Live Linux on a USB stick so the printer can be run from a USB stick, regardless of computer platform. Our software has all the required programs and settings for running the 3D printer.

Get the software download at '''[[D3D Live ISO]]'''.

==Initial Tests==
After downloading the [[Folgertech 2020 Prusa i3 Marlin]], installed Repetier on an Ubuntu operating system. Dragged it to the sidebar (Unity launch bar) after installing via commandline, so clicking on the Repetier icon opened up Repetier.

Repetier kept crashing (apparently due to bad baud rate setting) se we switched to Cura, Lulzbot edition, which did not crash but allowed no settings to be changed. So we went to Pronterface as the most robust solution, which did not crash and allowed the baud rate to be changed. By this testing, Pronterface is thus our default choice, based on best initial performance.

So back to Pronterface. After installing on the Desktop, and going into its directory and running it by typing in Terminal: ./pronterface.py (can't run .py by double clicking it on the used Ubuntu system) (see to the right).

[[Image:pronterface2.jpg|thumb|Raw Pronterface 3D printing interface after running, prior to connecting a 3D printer.]]

*To connect to Pronterface, baud rate should be 115200 (matching the baud rate specified in Marlin's Configuration.h file), and then you can hit Connect to connect to 3D printer.
*Tested axes by moving them manually in Pronterface. Went back to Marlin to reverse the axes, until all motion worked and homing was proper. Uploaded [[OSE Folgertech Prusa i3 Marlin]] - this works with a build following the instructions and wiring ''exactly as'' the [[Folgertech Build Guide]].
*Pronterface has a Gcode command line that allows you to provide commands. For example, it has a special code for cold extrusion - ie, bypassing thermal requirement for testing the extruder. See [[G Codes in Marlin]].
*To test extruder, I stuck in a thread and hit the extrude button cold. Is sucked the thread out, so I reversed its direction in Marlin firmware, configuration.h file (using Arduino IDE)- by changing line 320 to ''#define INVERT_E0_DIR true.''
*Note that machine will not let you travel away from endstops unless the machine is homed. So home the x, y, and z axes in Pronterface. Then you can travel freely by hitting the travel buttons in Pronterface.
*Download [[10 mm Calibration Cube]] - and sliced it within Repertier Host - [[Image:slicedcube.jpg|thumb|First test print g code generation using Repertier Host.]]
*Pressed print on Pronterface and it worked on the first try. see images. [[Image:10mmcube1.jpg|thumb|First 1 cm calibration cube on Folgertech Prusa i3.]]. [[Image:10mmcube2.jpg|thumb|Dimensions are good to +/- 200 microns on base and +500 microns on top where filament lifts off.]]
*Glory. [[Image:10mmcube3.jpg|thumb|3D Printing is mature techology. Parts can be sourced at low cost and readily, and 3D printer build yields satisfactory results on the first try.]]

=Links=
*[[XM Prusa i3 Procedure]]
*[[Tobbens_Folgertech_Kit_Unboxing_Log]]

[[Category: D3D]]

D3D Distributive Enterprise

2016-03-08T04:18:18Z

MarkDilley: Category: D3D

Press Release: we are kicking off our first distributive enterprise workshop on March 19, 2016.

=OSE License=

The license of all of our content, software, and designs is open source copyleft as a general rule and Open Source for Ever. We are [[OSHWA Compliant]], and use [[CC-BY-SA]], [[GPL]], and [[GFDL]].

=Brand Licensing=
OSE has a trademark on Open Source Ecology. OSE has a strict set of standards, embodied primarily in the [[OSE Specifications]] but also found in other foundational documents - which delineate the standards and values of OSE.

You are welcome to use our Distributive Enterprises for commercial purposes, but '''individuals and/or organizations are not allowed to operate under or use the OSE brand without prior written permission from OSE'''. The OSE brand can be authorized only by permission from the executive team and the OSE Board of Directors. Inquiries should be addressed to info at opensourceecology dot org.

Specifically, usage of the OSE logo to brand products or enterrises is forbidden to third parties.

We generally encourage individuals and companies to run enterprises under their own brand, which means that the individual does not have to comply with requirements that come with OSE, and any liability is assumed by the individual and not OSE.

See also [[Chapters]] for chapter requirements.

=OSE Certification=

OSE sees its own future evolution as the maintainer of a design repository and as a standards-setting organization. As viral replication will be reached in the future, it is OSE's duty to create an environment where maximum transparency is established for the quality and standards-adherence of open source products. The framework of an open source economy makes such standards necessary for transparency.

OSE is considering a certification system that will be used to document certain qualities of products and enterprises that comply with the values of OSE. [[OSE Certified]] is a label which OSE is developing, which is intended to be a transparent label. This label will define the elements of [[OSE Specifications]] that a product or enterprise contains, akin to the 'ingredients label' on food items.

An administrative cost is associated with any type of certification. An administrative fee for recordkeeping and verification will be associated with the OSE Certification, so any enterprises seeking such certification for branding and franchising purposes need to keep this in mind.

OSE is also considering other ways towards compliance transparency, such as crowd-sourcing and artificial intelligence for documenting the level of compliance.

[[Category: D3D]]

D3D Development

2016-03-08T04:16:59Z

MarkDilley: /* Development spreadsheet */ big enough for bottom nav bar

D3D Development

2016-03-08T04:16:26Z

MarkDilley: formatting

{{RightTOC}}
See also [[Tobben Log]]

== Development spreadsheet ==
<html><iframe src="https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/pubhtml?widget=true&headers=false" width=600 height=600></iframe></html>

[https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1 edit]

== Overview within the OSE Context ==
This is OSE's first experiment in creating a [[Distributive Enterprise]]. As the first step, Torbjorn Ludvigsen is working with OSE to deliver four 3D Printer build workshops as a self-sustaining revenue model - within the context of his Master's Thesis. Further steps are included at [[Roadmap#3D_Printer_Roadmap]]. To do this, we are building upon [[RepRap]], and optimizing the build to allow for a low cost printer that can be built and run in a single day by novices, using OSE's [[Extreme Manufacturing]] techniques. Initial phases involve taking a kit 3D printer, and optimizing to reduce an average person's build AND shakedown time from 40 hours to 8 hours. The point is to cultivate a team of collaborative development on an enterprise where the economic reward structure is a highly replicable enterprise. The enterprise intends to use social production for building: 3D printers; products made with 3D printers such as cordless drills and polycarbonate greenhouse glazing panels; ancillary toolheads (laser engraving/cutting, milling, ceramic 3D printing, metal printing, etc); and ancillary equipment for plastics recycling (grinder, filament extruder, etc). The goal is to change culture by providing a rapid learning infrastructure for people interested in self-employment and right livelihood - by lowering barriers to such a transition. We are offering the support to non-makers in a transition to understanding the power to Build Yourself, and to Build Your World.

The key features of this project involve Extreme Collaboration by inviting open source and prorprietary stakeholders to contribute open content to the project. Since the scope is rapid, [[Open Source Product Development]], our goal is to realize the proposition from the seminal paper, ''[[Achitecture of Partcipation]]'': '''systems with more modular architectures, more divisible task structures, and/or more option value in the modules would attract more voluntary effort.'''

== Most Recent Team Meeting ==
Jan 23, 2016:

<html><iframe width="420" height="315" src="https://www.youtube.com/embed/G3HP7jOxob8" frameborder="0" allowfullscreen></iframe></html>

== Critical Path ==
<html><img src="https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/pub?w=12001&h=700"></html>

[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit edit]

== Team Charter ==
<html><iframe src="https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

== Introduction ==

[[Image:d3d.jpg"|500px]] [[Image:D3D_Printer_render_4_jan.png|700px]]

This project aims to be a proof of concept instance of a [[Distributive Enterprise]] focusing on 3D printers. It's similar to the [[RepRap]] project, but instead of focusing on creating and spreading machines (3D printers) this project focuses on people, the RepRappers. The idea is to achieve exponential increase in the number of RepRappers by simultaneously teaching RepRap and how to teach RepRap.

== Chain reaction metaphor ==

The D3D stands for Distributive enterprise 3D printer. The "fusion" part is there because this project will try to bootstrap a kind of economical chain reaction:

: <big><font face="bookman">Instructor + Hardware + Plans + Participants<sub>x</sub> → X (3D printer + New Potential Instructor)</font></big>

This project will try to initiate a process where new instructors are formed who themselves obtain plans, hardware and participants to continue the process.

=== The → (workshop) ===
The "reaction" in this metaphor is a workshop. It will be designed into the smallest detail to facilitate reaction propagation. The design will be iteratively updated.

We (Tobben and Marcin) currently (6 Dec 2015) believe a one-day workshop has the best chance of propagating. This is because:
* Potential participants' time is limited. This will be squashed into peoples schedules
* Potential instructors needs economical incentives. Shorter workshops is more probable to generate a decent pay per hour

=== The Instructor ===
The first instructors will be OSE members. The <big><font face="bookman">Hardware</font></big>, <big><font face="bookman">Plans</font></big> and workshop will be designed to increase probability of a <big><font face="bookman">Participant → Instructor</font></big> transition.

=== The Plans ===
Complete instructions and ready-made plans on how to host a workshop will be made as accessible as possible.

==== Making them good ====
Relevant data such as (build time, preparation time, etc) will be collected during every workshop. This data will be analyzed by the D3D project to facilitate plan design iterations.

Initial workshop plan will be guessed from various experience and beliefs.

==== Making them accessible ====
Features believed to increase accessibility include:
* Usage of rich media (video, sound, color, ...)
* Good language
* Good translations
* Wide publication
* All in one place (MOOC?)

Increasing accessibility easy. Doing it efficiently requires some consideration/experience.

=== The Participants ===
Potentially anyone. Make as few assumptions about participants as possible. Motivating people to become participants is a major part of the project.

=== The Hardware ===
The success of the RepRap project and the resulting increased availability of the RepRap hardware and information is the main reason why 3D printers are chosen as the first proof of concept [[Distributive Enterprise]].

==== Making it good ====
Making the hardware as
* Generally useful
* Durable
* Easily repaired
* High quality
... as possible is a major part of the project.

This part of the project can build heavily on the results of the [[RepRap]] project- and community as well as other communities and available research on DIY 3D printers.

==== Making it accessible ====
Having a well engineered 3D printer will not lead to a workshop propagation unless the machine is
* Cheap
* Easy to use
* Easy to build
* Well documented
* Stylish

== Business norms and science norms ==
D3D Fusion, as a DE, will eagerly train new competitors within its own production sector. Since there's no difference between "competitor" and "external collaborator" within OSHW enterprise, maybe we should call them something else? e-collegues?

On the market for selling prints, it will compete for customers as usual. During designing, coding and researching, it will benefit from other DEs' expertise, they will be collaborators.

This combination of roles is customary within the scientific community which relies on the following norms:
# Researchers are part time teachers
# Publish or perish (risk losing your reputation and/or job)
# Research must be replicable to gain trust

D3D Fusion applies similar norms to a RepRap business.
# Founder are part time teacher (makes an income through hosting workshops where he teaches his craft)
# All R&D progress published to the Internet
# The enterprise is replicable

There are currently no norms driving D3D Fusion into decision 1 but decision 2 follows norms within the Open Source Hardware community. Norm 3 is an extension of design norms within the RepRap community.

==== Part time teaching ====
Many companies teach their craft and succeed in competitive markets at the same time. Ideo is an example within design business that sells both designs and courses on designing[https://www.ideo.com/][http://www.ideou.com/][https://www.ideo.org/], Lulzbot teaches by writing how-to guides[https://www.lulzbot.com/learn][https://ohai.lulzbot.com/], E3D teaches results of their R&D in public presentations[https://www.youtube.com/watch?v=mk30MPLoYf4]. The Ideo, Lulzbot and E3d enterprises prove that teaching your craft and selling your products simultaneously is economically sound (or at least doable).

Bootstrapping a market for DE workshops would give DE workers a special opportunities to work as part time teachers. This bootstrapping requires designing and testing a template, publishing it and supporting it with data.

==== Publish or Perish ====
The possibility to publish everything is already being used by current OSHW enterprises, such as Lulzbot[http://download.lulzbot.com/] and E3d[http://wiki.e3d-online.com/wiki/E3D-v6_Documentation#Engineering_Drawings].

==== Replicability ====
This is where D3D Fusion will be the most different from current OSHW enterprises...

== List of similar projects ==
* [http://Seed-Factory.org Seed Factory]
* [http://Appropedia.org/Evaluation_of_RepRap_3D_Printer_Workshops_in_K-12_STEM MOST lab workshops]
* [https://ifixit.com/ Ifixit]

== Naming and Links ==
This is the front page of the overarching [[D3D Fusion]] Project. It has an over arching [[D3D Fusion Project Plan]].
There exist a sub-project called [[D3D Thesis]], with its own [[D3D Thesis Project Plan]].
As a part of the [[D3D Thesis]] Project, the 3D printer design called [[D3D Printer]] and the design methodology called [[D3D Design Methodology]] are being developed.
The development of the [[D3D Printer]] follows the [[D3D Design Methodology]], and is being logged at [[D3D Printer Design Process]].
Description of the current [[D3D Printer Design]] is a dedicated developer-perspective wiki page.

=== List of Links ===
* [[D3D Distributive Enterprise]]
* [[Prusa i3 Build]]
* Follow progress of overall OSE 3D Printer Development at [[3D Printer Log]].
* [[D3D Fusion Project Plan]]
* [[D3D Thesis]]
* [[D3D Thesis Project Plan]]
* [[D3D Printer]]
* [https://github.com/tobbelobb/D3D_Printer D3D Printer Git Repo]
* [[D3D Design Methodology]]
* [[D3D Printer Design Process]]
* [[D3D Printer Design]]
* [[D3D Workshop Kit]]
* [[Prusa i3 Development]]
* [[3D Printer Distributive Enterprise Log]]
* [[D3D Workshop Roadmap]]
* [[D3D Workshop Slogans]]

[[Category: D3D]]

D3D Development

2016-03-08T04:10:56Z

MarkDilley: /* Development spreadsheet */

See also [[Tobben Log]]

= Development spreadsheet =
<html><iframe src="https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/pubhtml?widget=true&headers=false" width=600 height=600></iframe></html>

[https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1 edit]

=Overview within the OSE Context=
This is OSE's first experiment in creating a [[Distributive Enterprise]]. As the first step, Torbjorn Ludvigsen is working with OSE to deliver four 3D Printer build workshops as a self-sustaining revenue model - within the context of his Master's Thesis. Further steps are included at [[Roadmap#3D_Printer_Roadmap]]. To do this, we are building upon [[RepRap]], and optimizing the build to allow for a low cost printer that can be built and run in a single day by novices, using OSE's [[Extreme Manufacturing]] techniques. Initial phases involve taking a kit 3D printer, and optimizing to reduce an average person's build AND shakedown time from 40 hours to 8 hours. The point is to cultivate a team of collaborative development on an enterprise where the economic reward structure is a highly replicable enterprise. The enterprise intends to use social production for building: 3D printers; products made with 3D printers such as cordless drills and polycarbonate greenhouse glazing panels; ancillary toolheads (laser engraving/cutting, milling, ceramic 3D printing, metal printing, etc); and ancillary equipment for plastics recycling (grinder, filament extruder, etc). The goal is to change culture by providing a rapid learning infrastructure for people interested in self-employment and right livelihood - by lowering barriers to such a transition. We are offering the support to non-makers in a transition to understanding the power to Build Yourself, and to Build Your World.

The key features of this project involve Extreme Collaboration by inviting open source and prorprietary stakeholders to contribute open content to the project. Since the scope is rapid, [[Open Source Product Development]], our goal is to realize the proposition from the seminal paper, ''[[Achitecture of Partcipation]]'': '''systems with more modular architectures, more divisible task structures, and/or more option value in the modules would attract more voluntary effort.'''

=Most Recent Team Meeting=
Jan 23, 2016:

<html><iframe width="420" height="315" src="https://www.youtube.com/embed/G3HP7jOxob8" frameborder="0" allowfullscreen></iframe></html>

=Critical Path=
<html><img src="https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/pub?w=12001&h=700"></html>

[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit edit]

=Team Charter=
<html><iframe src="https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>
=Introduction=

[[Image:d3d.jpg"|500px]] [[Image:D3D_Printer_render_4_jan.png|700px]]

This project aims to be a proof of concept instance of a [[Distributive Enterprise]] focusing on 3D printers. It's similar to the [[RepRap]] project, but instead of focusing on creating and spreading machines (3D printers) this project focuses on people, the RepRappers. The idea is to achieve exponential increase in the number of RepRappers by simultaneously teaching RepRap and how to teach RepRap.

= Chain reaction metaphor =

The D3D stands for Distributive enterprise 3D printer. The "fusion" part is there because this project will try to bootstrap a kind of economical chain reaction:

:<big><font face="bookman">Instructor + Hardware + Plans + Participants<sub>x</sub> → X (3D printer + New Potential Instructor)</font></big>

This project will try to initiate a process where new instructors are formed who themselves obtain plans, hardware and participants to continue the process.

== The → (workshop) ==
The "reaction" in this metaphor is a workshop. It will be designed into the smallest detail to facilitate reaction propagation. The design will be iteratively updated.

We (Tobben and Marcin) currently (6 Dec 2015) believe a one-day workshop has the best chance of propagating. This is because:
*Potential participants' time is limited. This will be squashed into peoples schedules
*Potential instructors needs economical incentives. Shorter workshops is more probable to generate a decent pay per hour

== The Instructor ==
The first instructors will be OSE members. The <big><font face="bookman">Hardware</font></big>, <big><font face="bookman">Plans</font></big> and workshop will be designed to increase probability of a <big><font face="bookman">Participant → Instructor</font></big> transition.

== The Plans ==
Complete instructions and ready-made plans on how to host a workshop will be made as accessible as possible.

=== Making them good ===
Relevant data such as (build time, preparation time, etc) will be collected during every workshop. This data will be analyzed by the D3D project to facilitate plan design iterations.

Initial workshop plan will be guessed from various experience and beliefs.

=== Making them accessible ===
Features believed to increase accessibility include:
*Usage of rich media (video, sound, color, ...)
*Good language
*Good translations
*Wide publication
*All in one place (MOOC?)

Increasing accessibility easy. Doing it efficiently requires some consideration/experience.

== The Participants ==
Potentially anyone. Make as few assumptions about participants as possible. Motivating people to become participants is a major part of the project.

== The Hardware ==
The success of the RepRap project and the resulting increased availability of the RepRap hardware and information is the main reason why 3D printers are chosen as the first proof of concept [[Distributive Enterprise]].

=== Making it good ===
Making the hardware as
*Generally useful
*Durable
*Easily repaired
*High quality
... as possible is a major part of the project.

This part of the project can build heavily on the results of the [[RepRap]] project- and community as well as other communities and available research on DIY 3D printers.

=== Making it accessible ===
Having a well engineered 3D printer will not lead to a workshop propagation unless the machine is
*Cheap
*Easy to use
*Easy to build
*Well documented
*Stylish

= Business norms and science norms =
D3D Fusion, as a DE, will eagerly train new competitors within its own production sector. Since there's no difference between "competitor" and "external collaborator" within OSHW enterprise, maybe we should call them something else? e-collegues?

On the market for selling prints, it will compete for customers as usual. During designing, coding and researching, it will benefit from other DEs' expertise, they will be collaborators.

This combination of roles is customary within the scientific community which relies on the following norms:
#Researchers are part time teachers
#Publish or perish (risk losing your reputation and/or job)
#Research must be replicable to gain trust

D3D Fusion applies similar norms to a RepRap business.
#Founder are part time teacher (makes an income through hosting workshops where he teaches his craft)
#All R&D progress published to the Internet
#The enterprise is replicable

There are currently no norms driving D3D Fusion into decision 1 but decision 2 follows norms within the Open Source Hardware community. Norm 3 is an extension of design norms within the RepRap community.

=== Part time teaching ===
Many companies teach their craft and succeed in competitive markets at the same time. Ideo is an example within design business that sells both designs and courses on designing[https://www.ideo.com/][http://www.ideou.com/][https://www.ideo.org/], Lulzbot teaches by writing how-to guides[https://www.lulzbot.com/learn][https://ohai.lulzbot.com/], E3D teaches results of their R&D in public presentations[https://www.youtube.com/watch?v=mk30MPLoYf4]. The Ideo, Lulzbot and E3d enterprises prove that teaching your craft and selling your products simultaneously is economically sound (or at least doable).

Bootstrapping a market for DE workshops would give DE workers a special opportunities to work as part time teachers. This bootstrapping requires designing and testing a template, publishing it and supporting it with data.

=== Publish or Perish ===
The possibility to publish everything is already being used by current OSHW enterprises, such as Lulzbot[http://download.lulzbot.com/] and E3d[http://wiki.e3d-online.com/wiki/E3D-v6_Documentation#Engineering_Drawings].

=== Replicability ===
This is where D3D Fusion will be the most different from current OSHW enterprises...

= List of similar projects =
*[http://www.seed-factory.org/ Seed Factory]
*[http://www.appropedia.org/Evaluation_of_RepRap_3D_Printer_Workshops_in_K-12_STEM MOST lab workshops]
*[https://www.ifixit.com/ Ifixit]

= Naming and Links =
This is the front page of the overarching [[D3D Fusion]] Project. It has an over arching [[D3D Fusion Project Plan]].
There exist a sub-project called [[D3D Thesis]], with its own [[D3D Thesis Project Plan]].
As a part of the [[D3D Thesis]] Project, the 3D printer design called [[D3D Printer]] and the design methodology called [[D3D Design Methodology]] are being developed.
The deveolpment of the [[D3D Printer]] follows the [[D3D Design Methodology]], and is being logged at [[D3D Printer Design Process]].
Description of the current [[D3D Printer Design]] is a dedicated developer-perspective wiki page.

== List of Links ==
*[[D3D Distributive Enterprise]]
*[[Prusa i3 Build]]
*Follow progress of overall OSE 3D Printer Development at [[3D Printer Log]].
*[[D3D Fusion Project Plan]]
*[[D3D Thesis]]
*[[D3D Thesis Project Plan]]
*[[D3D Printer]]
*[https://github.com/tobbelobb/D3D_Printer D3D Printer Git Repo]
*[[D3D Design Methodology]]
*[[D3D Printer Design Process]]
*[[D3D Printer Design]]
*[[D3D Workshop Kit]]
*[[Prusa i3 Development]]
*[[3D Printer Distributive Enterprise Log]]
*[[D3D Workshop Roadmap]]
*[[D3D Workshop Slogans]]

Tobben Log

2016-03-08T04:10:04Z

MarkDilley: indented content of days. please revert if you don't like this.

{{RightTOC}}
[[Torbjorn CV]].

I'm studying RepRap workshops, events where participants build their own generally useful production machines that can produce a large fraction of their own parts.

I want to find factors that predict whether participants become workshop organizers themselves or not.

This would let us design workshops that reproduce and evolve while simultaneously distributing the machines' potential to improve people's standards of living and quality of life on a large scale.

== Mar 7, 2016 ==
: [[Tobbens Adding Inductive Proximity Sensor Log#Data]]
: [[Tobbens Adding Inductive Proximity Sensor Log#Implementation]]

== Mar 6, 2016 ==
: [[Tobbens Adding Inductive Proximity Sensor Log]]
: New model added to [[D3D Live ISO#Computer Models Verified to Boot]]

== Mar 5, 2016 ==
: [https://github.com/tobbelobb/D3D_Folgertech_Prusai3_Marlin D3D_Folgertech_Prusai3_Marlin repo]
: [[Tobbens Folgertech Kit Assembly Log]]
: Started a Python script for future automation of this pre-flight quality control, published [https://github.com/tobbelobb/RepRap_QC_scripts/blob/master/pre_flight_routine.py here]
: [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v2.iso Porteus-D3D-Workshop-x86_64-v2.iso]

== Mar 4, 2016 ==
: [http://forums.reprap.org/read.php?14,607341,634998#msg-634998 Reports on speed limit] of cheapest and most easily built drive system of single threaded rod + stepper motor. Research suggesting anti-resonant drivers could be cheaper than aggressively threaded lead screws posted in [http://forums.reprap.org/read.php?14,607341,635107#msg-635107 forum thread].
: [[Tobbens Folgertech Kit Assembly Log]]

== Mar 3, 2016 ==
: [[Tobbens Folgertech Kit Assembly Log]]

== Mar 2, 2016 ==
: [[D3D Live ISO#Computer Models Verified to Boot]]
: Some activity on [http://forums.reprap.org/read.php?14,607341,634531#msg-634531 Lead Screw forum thread].

== Feb 28, 2016 ==
: Mapped OpenSCAD dependencies properly [http://opensourceecology.org/wiki/File:Openscad2.png Dependency map]
: Re-compiled OpenSCAD, uploaded new 64-bit iso: [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v1.iso Porteus-D3D-Workshop-x86_64-v1.iso]. Updated [[D3D Live ISO#Instructions]] link.

== Feb 26, 2016 ==
: Been through [https://en.wikipedia.org/wiki/Dependency_hell Dependency hell] trying to compile CAD software to Porteus. OpenSCAD works now, FreeCAD doesn't.

== Feb 25, 2016 ==
: [[D3D Live ISO#On Creating xzm Packages]]

== Feb 24, 2016 ==
: Published 64-bit Porteus ISO. See [[D3D Live ISO#Instructions]] Still lacks configured Marlin source code.
: Tried to compile FreeCAD. [[D3D Live ISO#Compilation of FreeCAD]] Abandoned because of difficulties with compiling Coin3.
: Documented creation of 64-bit Arduino package: [[D3D Live ISO#Arduino]]

== Feb 23, 2016 ==
: Compiled gcc-5.3.0 package for 64-bit version of Porteus and documented the process: [[D3D Live ISO#Choice of Compiler Version]]
: Compiled OpenSCAD package for Porteus and documented the process: [[D3D Live ISO#CAD Software]]

== Feb 22, 2016 ==
: Got OpenSCAD 2015.03 to work on the 32-bit Live USB.
: Uploaded ~600 MiB iso file [http://vitana.se/opr3d/tbear/iso/Porteus_pronterface_slic3r_arduino_openscad_conf_i486.iso here].
: Minor changes to [[D3D Live ISO]]
: [[D3D Live ISO#Steps to boot Porteus on Macbook Air 2011]]

== Feb 21, 2016 ==
: Made repo with D3D Porteus Live USB OS [https://github.com/tobbelobb/D3D_Workshop_Configuration config files]
: Compiled GCC 5.3.0 for use in 32-bit version of Porteus: [http://vitana.se/opr3d/tbear/xzm/devel/gcc-5.3.0-i486.xzm xzm package link]

== Feb 19, 2016 ==
: [[D3D Thesis#Line of Reasoning]]
: [[D3D Thesis#Background]]
: [[3D Printer Build Plate]]
:Updated point 15 on [[Tobbens Folgertech Kit Unboxing Log]]

== Feb 18, 2016 ==
: Got iso size down from 493 MiB (517 MB) to 299 MiB (313 MB). See [[D3D Live ISO#Stripping it down]] and updated download link in [[D3D Live ISO#Instructions]]
: Completed [[Tobbens Folgertech Kit Unboxing Log]] with some images and clarifying comments

== Feb 17, 2016 ==
: [[Tobbens Folgertech Kit Unboxing Log]]

== Feb 16, 2016 ==
: Ordered four LJ12A3-4-Z/BX Inductive Proximity Sensor Switches.
: Ordered GT2 belts, pulleys and belt tensioning springs.
: Ordered signal switching 1N4148 diodes.
: [[Research On Inductive Proximity Sensors]]
: Updated [[File:Bed leveling and compensation comparison.ods]] with [https://www.youtube.com/watch?v=EcGFLwj0pnA Thomas Sanladerer's recommendation] and further comments on inductive sensing.
: Researched some brackets for induction sensor: [[Folgertech Kit#Candidates For Improvement Resolution]]

== Feb 15, 2016 ==
: New extensive Folgertech resource found: [[Folgertech Kit#Other Instructionals]].
: [[Gcode Modularity]]
: More work on [[D3D Live ISO]]. Got Slic3r working nicely, and integrated with Pronterface. Got Arduino IDE working. Latest version ISO: [http://vitana.se/opr3d/tbear/iso/Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso]
: [https://docs.google.com/presentation/d/1-kF_PPt1NU2PQZHaQFh712hjdcBuCc3dafmPdRSzNu0/edit?ts=56c23f04#slide=id.g1192b7f2d5_0_8 Prototype Planning]

== Feb 13, 2016 ==
: Further Porteus config. Now handling Pronterface better, updated iso to v1. See [[D3D Live ISO#ISO images]]

== Feb 11, 2016 ==
: [[D3D Live ISO]]
: Tested out [http://ProjectLibre.org/ Project Libre] with Andreas. [[File:D3D.pod]]

== Feb 9, 2016 ==
: Experiment with 3D printing assembly manual using only OpenSCAD renders as visuals: [http://Vitana.se/opr3d/tbear/index.html#Clerck_assembly_manual Clerck assembly manual]
: [[D3D Live ISO]]
: Helped by Andreas to create [[D3D Thesis Project Plan#Map of Deliverables]] to more easily manage myself and include others.

== Feb 5, 2016 ==
: Adjustments to [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 lead screw sourcing forum post] from yesterday.
: Ordered F6-12 thrust bearings for prototyping.

== Feb 4, 2016 ==
: Sourcing research on lead screws. Posted in [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 forum thread].
: Igus links in [[D3D Printer Design Process#Practical viability of lead screws for 3D printing loads and speeds]]
: Ordered following products for lead screw prototyping: [http://no.rs-online.com/web/p/products/8854956/], [http://no.rs-online.com/web/p/products/8854814/], [http://no.rs-online.com/web/p/products/8854830/], [http://no.rs-online.com/web/p/products/8854827/], [http://no.rs-online.com/web/p/products/8854987/]

== Feb 2, 2016 ==
: Initiated [[3D Printer Quality Control Research]]
: Initiated [[3D Printer Extruder Research]]
: Researched [[3D Printer Bed Leveling]]. See [[File:Bed leveling and compensation comparison.ods]] for full assessment matrix.

== Feb 1, 2016 ==
: Small change to [[Prusa i3 Build]].
: New research and complete rewrite of [[3D Printer Bed Leveling]].
: Small change to [[3D Printer Hot End Research]].
: Initiated [[3D Printer Print Surface Research]].

== Jan 30, 2016 ==
: [[D3D Workshop Roadmap]], [[D3D Workshop Slogans]], [https://docs.google.com/presentation/d/1duikQl9HMfHuUVAIQv4cDy1sGWZLujFzLxMRIGej5AY/edit?pref=2&pli=1#slide=id.p Folgertech 2020 Prusa i3 build working document], [https://www.facebook.com/OpenSourceEcology/photos/a.10151381815921562.574965.66469461561/10154554553731562/?type=3&theater Build Facebook post]

== Jan 29, 2016 ==
: Meeting with Jonathan and Marcin.
:* We should investigate bulk prices for key parts (like stepper motors)
:* I (Tobben) should collect some stories from the people I've given printers to. Stories of people who got empowered and made some money with their new RepRap knowledge and machines.
:* Thesis data collection nr 1 happens tomorrow when Folgertech Prusa i3 kit is assembled on the Factor e farm.

== Jan 23, 2016 ==
: [[3D Printer Bed Leveling]]
: [https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.g10745b77da_3_3 Prusa i3 selection Google document]

== Jan 20, 2016 ==
: Created [http://forums.reprap.org/read.php?1,612676 forum thread] asking for input on workshop kits.

== Jan 19, 2016 ==
: CADded LM8UU standard linear bearings into D3D Printer (see repo).
: Meeting on kit selection [https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.p Kit considerations]
: [[Prusa i3 Development]]
: [[3D Printer Kit for Workshop Research]]
: [[3D Printer Hot End Research]]

== Jan 17, 2016 ==
: [[D3D Thesis#Workshop Reproducibility]], some reserve plans created in [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project]

== Jan 13, 2016 ==
: Wrote [[D3D Thesis Project Plan]], sent to examiner.
: More insights on lead screws on the [http://forums.reprap.org/read.php?14,607341,607483 forum thread].
: Verification from [http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping] that lead screws used by Trinitylabs lasts for at least 2 years. Put in [[D3D Printer Design Process#Practical viability of lead screws for 3D printing loads and speeds]].

== Jan 12, 2016 ==
: [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project], embedded in [[D3D Thesis Project Plan]].
: Bought:
:* 3xForce Sensing Resistors (Interlink Electronics FSR 400) for prototyping
:* [https://ultimachine.com/content/rambo-13-complete-kit RAMBO v1.3 for prototyping]
: [[3D Printer Troubleshooting]]

== Jan 11, 2016 ==
: Wrote and published [[D3D Thesis#Team Charter]].
: [[D3D Enterprise Logic Model]]

== Jan 10, 2016 ==
: Some progress on the [http://forums.reprap.org/read.php?14,607341,607483 lead screw forum thread]. Emailed more skillful developers.
: Read up on possible choices for [[D3D Printer Electronics]]. Ordered smooth rods with linear bearings (sizes 8 mmm and 10 mm) for prototyping. Ordered powdered graphite for lubrication testing.

== Jan 9, 2016 ==
: Verification of lead screw: [https://YouTube.com/watch?v=gk9lhcTGSH4 working all-leadscrew 3D printer], [[Stepper Motor#Torque Tests]], [[D3D Printer Design Process#Verification Steps Taken for Lead Screw .2B Stepper Motor Concept]]
: Bought:
:* [http://eBay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 1] and
:* [http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 2] for some hands-on testing in February.
: Contacted [http://MooreInternational.co.uk Moore International] and [http://Danish3d.dk Danish 3D] for help with choice and supply of lead screws.
: Discovered [http://Contraptor.org Contraptor] that tries to use the concept of modular linear motion units, put into [[D3D Thesis#Earlier Work]].
: Read up on [[3D Printer Bed Leveling]].
: Summarized state of lead screw discussion in the RepRap community in a [http://forums.reprap.org/read.php?14,607341 forum thread asking for further insights]. Emailed various developers with lead screw designs, asking for experiences, thoughts, insights...
: [[3D Printer Filament Load Sensor]]

== Jan 8, 2016 ==
: Some work on the [[D3D Design Methodology]].
: Some usage of it logged in [[D3D Printer Design Process]].
: Meeting with Marcin, initiated [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path doc].

== Jan 7, 2016 ==
: Checked/commented on lifetimes: [[Stepper Motor#Lifetime]], [[FFF Extruder]], [[Lead Screw]]
: Structuring of 3D printer design work: [[D3D Printer Design Process]], [[D3D Design Methodology]].
: Structured wiki pages such that [[D3D Thesis]] is a sub-project of [[D3D Fusion]]. Changed [[D3D Fusion Project Plan]] to reflect this and initiated [[D3D Thesis Project Plan]].
: The thesis project aims to bootstrap the [[D3D Workshop Kit]].
: Explained structure in [[D3D Fusion#Naming and Links]]

== Jan 6, 2016 ==
: Meeting with Andreas S, [https://docs.google.com/spreadsheets/d/1-NuTg0c_uta0i3vNUZtciD3cq6j1bS4RKWCIG8AOaR0/edit#gid=0 Work Breakdown Structure], [https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/edit#slide=id.geb160911a_2_25 D3D Team Project Charter].
: Meeting with Marcin [https://docs.google.com/presentation/d/1jXC3V40cHqc2P8Oo-G2Z1G7IyytujYb4R3rIT9nZCpI/edit#slide=id.g8184a0e10_0_101 Long term Distributive Enterprise Milestones]
: Wrote something on [[D3D Fusion thesis#Funding Mechanisms for Open Source Work]]

== Jan 5, 2016 ==
: [[D3D Fusion Printer Conceptual Design]]

== Jan 4, 2016 ==
: Wrote some [https://Overleaf.com/read/vmpdtnzsgdgg Project Plan stuff on Overleaf]. 3h meeting with Marcin. Finished [https://docs.google.com/document/d/1sQKi3QuQ1yPu_08zyo1cLMhrQGytiTHL4Mfd7JMUK2M/edit?ts=568a0631 OSE NEGOTIATION INVITATION].

== Jan 3, 2016 ==
: Defined moving part of D3D Printer's linear actuator. Reorganized code and wrote README (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Jan 2, 2016 ==
: Added [[D3D Fusion printer design#Weight calculation for steel sheet frame]] and [[D3D Fusion printer design#Motor placement]] to wiki. Two minor commits in [https://github.com/tobbelobb/D3D_Printer Github repo].

== Dec 31, 2015 ==
: Re-organized [[D3D Requirements]]. Some progress on [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

== Dec 30, 2015 ==
: Meeting with Marcin. Started [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

== Dec 28, 2015 ==
: Reworked l_plate and basic frame (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Dec 27, 2015 ==
: First rough visualization of D3D Fusion Printer done (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Dec 26, 2015 ==
: Meeting with Marcin. Finished [[D3D Requirements]] together.

== Dec 25, 2015 ==
: Some progress in [https://github.com/tobbelobb/D3D_Printer Github repo].

== Dec 25, 2015 ==
: Made [https://github.com/tobbelobb/D3D_Printer Github repo] for D3D Printer OpenSCAD design.

== Dec 23, 2015 ==
: Wrote something on the D3D Printer design. [[D3D Fusion Printer Design]] Needs to be fitted into a template.

== Dec 22, 2015 ==
: Work on visa application process. Skype meeting with Marcin. Discussion points:
:# [[Torbjorn DEF Agreement]]. DEF=Distributive Enterprise Fellow, under the [[EIR]] program. Including workshop schedule and number, and your tentative arrival date, and details regarding your university.
:# Locking in design requirements - [[D3D Requirements]] - both overall and module by module
:# Defining the 'story' for the thesis. [[D3D Thesis Story]].
:# Beginning discussion on the tech tree of choices that we select to move forward - meaning specific implementation path for each module
: Found some data: [https://www.3dhubs.com/trends]
: Nice discussion on hangout, got some text produced from it: [https://docs.google.com/document/d/1Ber5iA-2V7m_3mbh54ZsuRB-viTLd-sfb9GL3jj58GQ/edit?ts=5679a219]
: Asked for data on RepRap Freenode IRC chat. Generated discussion about Prusa i3 Steel. Didn't read it all, so putting it here for future reference: [[Cut_From_Freenode_RepRap_22_Dec]]

== Dec 21, 2015 ==
: Initiated Project Plan [[D3D Fusion project plan]]. This is what Martin must approve before we can move on. Made thesis skeleton [[D3D Fusion thesis#Thesis Skeleton]] from template in course documentation. Limited progress in FreeCAD.

== Dec 19, 2015 ==
: Commented proposed D3D requirements: [[Talk:D3D Requirements]]. Added Lyman extruder to [[Open Source Filament Extruders]]. ''See [[Power Tool Construction Set]].

== Dec 16, 2015 ==
: Presented some 3d printer design ideas in [[D3D Fusion printer design]].

== Dec 15, 2015 ==
: Summarized short research about prior work of Prusa: [[D3D Fusion thesis#Earlier Work]]

== Sun Dec 13, 2015 ==
: Wrote short [[D3D Fusion#Business norms and science norms]] comparison between DE norms and science norms.

== Thu Dec 10, 2015 ==
: Initiated [[D3D Fusion thesis]] sketch. Also did a little overview on [[Large Scale Fused Pellet Fabrication]]. Got an overview of the MOST lab's work. Put in in [[D3D Fusion thesis]].

== Sun Dec 6, 2015 ==
: Initiated this work log. Initiated [[D3D Fusion]]. Initiated D3D dev spreadsheed [https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1&vpid=A1]. '''Nice. Please embed spreadsheet in wiki.'''-MJ Embedding [[D3D Fusion#Development spreadsheet| Done]]

[[Category:Logs]]

D3D Live ISO

2016-03-08T04:01:18Z

MarkDilley: move content up, TOC to the right

{{RightTOC}}
=Instructions For Creating Live USB Thumbdrive=
These instructions are compiled from the file [[File:USB_INSTALLATION.txt]], and other documentation at [http://porteus.org porteus home page].

*If you have a 32-bit computer, download 299 MiB [http://vitana.se/opr3d/tbear/iso/Porteus_D3D_i486_stripped.iso 32-bit iso without OpenSCAD] or 613 MiB [http://vitana.se/opr3d/tbear/iso/Porteus_pronterface_slic3r_arduino_openscad_conf_i486.iso 32-bit iso with OpenSCAD]. The larger version requires at least 1GB USB storage and 4GB RAM.
*If you have a 64-bit computer and 4GB RAM or more, download 480 MB [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v2.iso Porteus-D3D-Workshop-x86_64-v2.iso].
*Attach USB stick to computer
*Backup data already on USB stick

=== From Within Ubuntu-instructions ===

*Optional: Format USB stick to ext4. Most USB sticks are preformatted with FAT filesystems. This complicates writing to the USB from within Porteus.
:*Follow [https://www.youtube.com/watch?v=m9zctyRP434 this guide], except format to ext4 instead of fat32.
*Open iso with Archive Manager, extract contents to USB folder
*Run the script Porteus-installer-for-Linux.com. It resides in the directory called boot on your USB stick. Root privileges (sudo) might be required, depending on your system.
:*Navigate to USB directory
cd /media/<user>/<USB-stick-name>/boot
:*Once in USB boot directory
sudo ./Porteus-installer-for-Linux.com

=== From Within Porteus-instructions ===

*Open Porteus Installer program
:*Open the Start Menu (top left corner)
:*Choose "System"
:*Choose "Porteus Installer"

== From Within Other Systems ==

See [http://www.porteus.org/component/content/article/26-tutorials/general-info-tutorials/114-official-porteus-installation-guide.html porteus.org's official installation instructions].

=Introduction=
The D3D Thesis project aims to provide participants a Live ISO.
This is an operating system that resides on a CD, DVD or USB stick that can run on all common computers, independent of the state of their computer's hard drives, thereby bypassing installation procedures for 3D printing related programs.

The idea is that we do 2 things to make the D3D Distributive Enterprise spread far and wide, which is part of [[Viral Replication Criteria]]:

#Enable an average user with clear instructions for downloading our ISO, and installing on a USB drive in Linux, Windows, and Mac.
#Providing USB sticks at the workshop to users who have not already installed the 3D printer software. The assumption is that we will preload the firmware onto the controller board.

== Links ==
* [http://porteus.org/ Porteus home page]
* [https://en.wikipedia.org/wiki/Porteus_%28operating_system%29 Wikipedia article on Porteus]

== Tobben's Notes While Developing ISO ==

Porteus uses [http://www.porteus.org/component/content/article/9-tutorials/modules/56-what-are-porteus-modules.html modules], Slackware style.
We have ISO for
* Printrun (including Pronterface)
* Slic3r
* XFCE (graphical environment)
* Mozilla Firefox
* Arduino
* OpenSCAD

Two ISO images are maintained:
* 32-bit. Enabling usage of legacy computers. Limited by [https://en.wikipedia.org/wiki/3_GB_barrier 3 GB barrier].
* 64-bit. Will be used most frequently.

New ISO's are created within Portheus with script /mnt/sdXN/porteus/make_iso.sh.

Maybe useful:
save-changes - dump whole changes from the live session into a module

Wrote ISO to USB stick
sudo dd if=Porteus-KDE4-v3.1-x86_64.iso of=/dev/sdc

Didn't work. Re-formatted USB stick, extracted contents of ISO file and put it on USB stick.
Mounted USB-stick, copied Portheus files over there and ran the script

/media/torbjorn/Porteus/Porteus/boot/Porteus-installer-for-Linux.com

This produced a final message:
Installation finished successfully.
You may reboot your PC now and start using Porteus.
Please check the /boot/docs folder for additional information about
the installation process, Porteus requirements and booting parameters.
In case of making tweaks to the bootloader config,
please edit: /media/torbjorn/Porteus/Porteus/boot/syslinux/porteus.cfg file.

Didn't work. Made new ISO with following changes
* UEFI support
* 32-bit
* FAT32 filesystem on stick

That did work, but FAT32 prevented anything from being stored on USB stick while in Porteus.
Changed to ext4. Worked fine.

[http://www.porteus.org/component/content/article/36-modules/121-howto-understanding-module-creat+on-and-manipulation-two-case-studies.html Guide to package creation and manipulation at porteus.org]

Created xzm package that allows Pronterface to be run from source. [[File:Pront-package-incomplete.xzm]]

Made changes to /boot/syslinux/porteus.cfg to tailor a boot-mode for D3D Workshops.

= Computer Models Verified to Boot =

{|border="1" class="wikitable sortable"
|-
!Computer Model Name
!ISO version
!Comment
!Links
|-
|Acer M5-581TG
|64-bit and 32-bit
|
|
|-
|Lenovo g580
|64-bit
|Start with "Novo button" instead of usual power button and select boot menu, or press F2 on startup to enter boot menu. Disable "Secure boot", enable "legacy mode", enable "legacy first".
|[https://askubuntu.com/questions/318119/lenovo-g580-ideapad-replacing-windows-8-with-ubuntu], [https://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-windows-with-uefi Extensive answer on askubuntu.com]
|-
|Macbook Air from 2011
|64-bit
|Hold left "alt"-key while turning on the computer. Keep holding alt pressed for several seconds. A [https://i.stack.imgur.com/PzjcY.jpg boot screen] should eventually appear.
|
|-
|ASUS ET2210INTS
|64-bit and 32-bit
|Press "Esc" on power up to enter boot menu.
|
|-
|HP Pavilion zt3000
|32-bit
|Press "F10". Has only 512MB of RAM, so try smallest ISO first.
|
|-
|Lenovo Thinkpad SL510
|64-bit and 32-bit
|
|
|}

= Computer Models Refusing to Boot From USB =
None yet.

= Old ISO images =

== 64-bit ==
[http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v0.iso Porteus-D3D-Workshop-x86_64-v0.iso]

[http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v1.iso Porteus-D3D-Workshop-x86_64-v1.iso]

== 32-bit ==

[http://vitana.se/opr3d/tbear/iso/Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso].

=Communications=
Torbjorn: Configured a 32-bit (64-bit machines can also use it) Porteus Live OS
ISO today, taking up 412 MiB space, but looks quite good (KDE4), runs
very very fast, includes Pronterface source code and starts Pronterface
on boot.

I'm on a slow connection, so iso will take another hour to upload...

See if you can get it to work. We can step through it at the meeting
tomorrow.
http://opensourceecology.org/wiki/D3D_Live_ISO#ISO_images

= Mac Work =

== Steps to boot Porteus on Macbook Air 2011 ==
*Shut Down computer
*Insert USB thumb drive with Porteus 64-bit and EFI support installed (D3D ISO will be uploaded soon)
*Hold left "alt"-key while turning on the computer.
*Keep holding alt pressed for several seconds. A [https://i.stack.imgur.com/PzjcY.jpg boot screen] should eventually appear.
*The Porteus USB thumbstick will be represented by a yellow icon (sometimes with the text "windows", see [https://i.stack.imgur.com/PzjcY.jpg picture]). Choose Porteus using arrow keys and enter.
*The Macbook air should now boot Porteus

Above steps tested and shown to work by Tobben on Feb 22 2016.

== Research ==

=== Ubuntu.com article ===
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx

States:
Most Macs with Intel processors will work with either 64-bit or Mac images. If the 64-bit image doesn't work, try the Mac image.

Their DVD instructions simply consist of burning the iso onto the DVD with Disk Utility.

Recommends CD instead of USB.

Converts iso to an .img or .dmg file before using Disk Destroyer to burn the image onto the USB.

=== Makeuseof.com article ===
http://www.makeuseof.com/tag/how-to-boot-a-linux-live-usb-stick-on-your-mac/

Tested on 2011 Macbook pro.

Uses FAT32 ant master boot record partition.

Uses EFI boot.

Uses iso images that are somehow customized for mac.

=== support.apple.com article ===
https://support.apple.com/en-us/HT201663

Says we need GUID partition

=== rEFInd article ===
http://www.rodsbooks.com/refind/

Explains difference between boot manager and boot loader.

Says this about (U)EFI
Prior to mid-2011, few computers outside of Intel-based Macs used EFI; but starting in 2011, computer manufacturers began adopting UEFI in droves, so most computers bought since then use EFI.

=== Randomtutor article ===
http://randomtutor.blogspot.co.uk/2014/01/installing-ubuntu-on-retina-macbook-pro_19.html

Uses Ubuntu USB for Mac OS X article mentioned above with 64-bit Mac iso image.

Installs and uses the rEFInd boot manager:
cd ~/Downloads/refind-bin-0.7.7
./install.sh --alldrivers

NOTE: If you have Mac OS X 10.10 (Yosemite) installed, then the rEFInd installation needs to be handled differently. See [http://www.rodsbooks.com/refind/yosemite.html].

=== Porteus Forum Thread 1 ===
http://forum.porteus.org/viewtopic.php?f=81&t=4177

Says that Porteus-installer-for-Linux.com script installs a boot loader.

=== rEFInd Forum Thread 1 ===
https://sourceforge.net/p/refind/discussion/general/thread/b9c7cefa/

Suggests we should try rEFInd and Porteus with EFI boot first. Note that Roderick W. Smith is the rEFInd dev himself.

= Earlier Work =
http://rafaelalcocer.com/downloads/index.php?dirpath=./3D-printer&order=0

A Porteus user that created a lot of related i486 xzm packages. His blog: [http://rafaelalcocer.com/doku.php].

The aruino.xzm of D3D Porteus uses his packages jre-7u40-i586-1.xzm and 010-avr-package-v0.3-1-1b.xzm to back up Arduino.

= Stripping it down =
{|border="1" class="wikitable sortable"
!Time order
!Change
!Measured in
!MiB saved
|-
|0
|Replaced KDE with Xfce
|iso size
|41
|-
|1
|Removed dictionaries from Firefox
|Deployed size
|0.6
|-
|2
|Removed developer tools (make, gcc, etc)
|iso size
|72
|-
|3
|Removed changes folder
|Deployed size
|80
|-
|4
|Removed optional packages
|Deployed size
|1.7
|-
|5
|Removed unused geany scripts in avr package
|Deployed size
|0.1
|-
|6
|Removed geany plugins docs in avr package
|Deployed size
|6.4
|-
|7
|Removed man pages in avr package
|Deployed size
|5.6
|-
|8
|Removed kicad from avr package
|Deployed size
|17
|-
|9
|Removed /usr/share/doc from avr package
|Deployed size
|13
|-
|10
|Removed /usr/share/geany and geany-plugins from avr package
|Deployed size
|2.6
|-
|11
|Removed /usr/share/locale from avr package
|Deployed size
|4.4
|-
|12
|Removed geany binary from avr package
|Deployed size
|2.3
|-
|13
|Removed pcbnew and eeschema rests from kicad in avr package
|Deployed size
|4.4
|-
|14
|Removed kontrollerlab binary from avr package
|Deployed size
|1.3
|-
|15
|Removed ponyprog2000 from avr package
|Deployed size
|0.8
|-
|16
|Removed remaining kicad files from avr package
|Deployed size
|1
|-
|17
|Removed usr/lib/geany and geany-plugins from avr package
|Deployed size
|1.5
|-
|18
|Removed folder x86_64-unknown-linux-gnu from /opt/arduino/hardware/tools/avr
|Deployed size
|0.9
|-
|19
|Removed /opt/arduino/reference
|Deployed size
|25
|-
|20
|Removed /usr/doc and man from python deps package
|Deployed size
|53
|-
|21
|Removed locales from /usr/share/locale in python deps package
|Deployed size
|9
|-
|22
|Removed gtk-doc in python deps package
|Deployed size
|14
|-
|}

= On Creating xzm Packages =
Note that the packages that are created below are thrown together to work for the first workshop.
They do not follow the Slax or Porteus package standards perfectly (found [http://old.slax.org/documentation_create_modules_rules.php here (Slax)] and [http://www.porteus.org/component/content/article/9-tutorials/modules/57-compiling-a-module-from-source.html here (Porteus)]).

= Choice of Compiler Version =
Porteus v3.1 that we're building upon ships with gcc-4.3.2 by default (inside the devel-package).
D3D Porteus versions with OpenSCAD pre-installed ship with an additional gcc-5.3.0 package, because of this bug: [https://github.com/openscad/openscad/issues/514 SegFault: Linux, gcc-4.8.2 #514]

== Creating the gcc-5.3.0.xzm Package in D3D Porteus ==
These instructions are compiled from [https://gcc.gnu.org/install/index.html Installing GCC] found on gnu.org.

=== Compiling GCC From Source Within Porteus 64-bit ===

*The devel-package in Porteus v3.1 contains the prerequisities we need, make sure it is activated.
*Download the source code to a hard drive. I use my computer's installed SDD disk found on /mnt/sda. See [https://gcc.gnu.org/mirrors.html list of mirrors] for download.
*See [https://gcc.gnu.org/gcc-5/changes.html list of gcc5 changes] to know what you're installing. Note for example the new ABI for libstdc++. This could play a role in Porteus V3.1 since the package manager's binaries are probably compiled with gcc4. Be careful when using multiple compilers. For compiling libstd++ as the only statically linked library, use the -static-libstdc++ flag (see [https://gcc.gnu.org/onlinedocs/gcc/Link-Options.html#Link-Options gcc link options]).
*Create a build directory (called objdir in the gcc documentation) separate from the directory containing gcc source code (called srcdir in gcc documentation)
mkdir /path/to/objdir
cd /path/to/objdir
*Configure while still standing in objdir. These flags are just the ones I use. See the [https://gcc.gnu.org/install/configure.html documentation] for what they mean.
/path/to/srcdir configure --prefix=/usr --libdir=/usr/lib --mandir=/usr/man --infodir=/usr/info \
--enable-shared --enable-bootstrap --enable-languages=c,c++,lto,fortran --enable-threads=posix \
--enable-checking=release --with-system-zlib --with-python-dir=/lib/python2.7/site-packages \
--disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp --with-gnu-ld \
--verbose --disable-gtktest --disable-multilib
*Make the executables You could just run 'make' here (without the quotes). This command will take a while to finish.
make -j 2 BOOT_CFLAGS='-O2' bootstrap-lean
*Also, make sure that gcc gets the -fPIC flag passed when building shared libraries (such as libstc++.so), see [https://stackoverflow.com/questions/966960/what-does-fpic-mean-when-building-a-shared-library?rq=1].

=== Installing to Staging area (fake root) and Packaging ===
*Create a directory that will act as the fake root
mkdir /path/to/fakeRoot
*Make sure you're still standing in objdir and do the install
make DESTDIR=/path/to/fakeRoot install
*Create the compressed package
dir2xzm /path/to/fakeRoot gcc-5.3.0-x86_64.xzm
*Move the package to your USB thumbdrive
mv gcc-5.3.0-x86_64.xzm /mnt/sdX1/porteus/optional

= CAD Software =

== Compilation of OpenSCAD ==
*Create a basedir to compile dependencies in later
mkdir -p openscadBasedir/usr
*Set the BASEDIR variable for the setenv-unibuild.sh to use later.
BASEDIR=/path/to/openscadBasedir/usr
*Get source code. The files will be quite big, so cd to a hard drive before proceeding.
git clone https://github.com/openscad/openscad.git
cd openscad

=== Compile OpenSCAD Dependencies ===

====The Ones That the Repos Give us ====
*Note that superuser privileges might be needed to execute some of the following commands. Change to super user with 'su'. Change back with 'exit'.
*Start with git
usm -u all
usm -g git
*Save and activate git
mv /tmp/usm/git-something.xzm /mnt/sdX1/porteus/modules
activate /mnt/sdX1/porteus/modules/git-something.xzm
*Any qt-4 package usm gives you is good enough.
usm -g qt-4
*Save and activate qt-4
mv /tmp/usm/qt-4.x.x_something.xzm /mnt/sdX1/porteus/modules
activate /mnt/sdX1/porteus/modules/qt-4.x.x_something.xzm
*To get around the [https://github.com/openscad/openscad/issues/514 SegFault: Linux, gcc-4.8.2 #514], use any other C/C++-compiler than gcc4.8.2, gcc4.8.1, clang3.3 or clang3.4 when compiling from source. If you've compiled gcc-5.3.0 like explained above do
activate /mnt/sdX1/porteus/optional/gcc-5.3.0-x86_64.xzm

====The Ones That Openscad Helps Us Compile====
*Openscad has scripts helping to install other dependencies. Run scripts from the openscad folder. First set variables and such with
source ./scripts/setenv-unibuild.sh
*We need an empty file in gtk-doc to work around a quirk in ragel's build script:
mkdir -p /usr/share/gtk-doc/data
touch /usr/share/gtk-doc/data/gtk-doc.notmpl.make
*Then run the script that downloads and installs all necessary dependencies to the BASEDIR. This will download a lot of source code and do lots of compilation. It will take a while. Notice that this will create and place a lot of un-movable shared object files in BASEDIR. We won't consider this a problem since we're building a static binary later. If you want movable .so files, you will have to modify the build script.
./scripts/uni-build-dependencies.sh
*Clean up the 1.5 GB of source code
rm -r $BASEDIR/src

====The One We Need to Fix Ourselves====
*The script does not build QScintilla for us, so that needs to be built from source as well. The following procedure follows the pattern from uni-build-dependencies.sh
wget http://sourceforge.net/projects/pyqt/files/QScintilla2/QScintilla-2.9.1/QScintilla-gpl-2.9.1.tar.gz
tar -xzvf QScintilla-gpl-2.9.1.tar.gz
cd QScintilla-gpl-2.9.1/Qt4Qt5
qmake qscintilla.pro PREFIX=$BASEDIR
make
make install
cd ../..

*Package up, move to USB thumbdrive and activate temporarily. Since .so files point at BASEDIR internally, this is only valid and used during this specific compilation.
dir2xzm $BASEDIR openscad-deps-x86_64.xzm
activate openscad-deps-x86_64.xzm
*Check if dependencies are OK. This might fail to discover our qt-4 installation, in wich case you can run 'qmake -v' or 'pkg-config -modversion QtCore' to check manually.
./scripts/check-dependencies.sh

=== Compile OpenSCAD Itself ===
*Create the Makefile. Here, we send the -static flag to gcc, since OpenSCAD's dependencies will be used for OpenSCAD only (including gcc-5.3.0).
qmake openscad.pro PREFIX=/usr CONFIG+=libstatic
*Compile the binary. This takes a while.
make -j2
*Deactivate the openscad-deps package created earlier.
deactivate openscad-deps-x86_64.xzm
rm openscad-deps-x86_64.xzm
*Test the binary
./openscad
*Test that the binary was really statically compiled. This should produce no output.
lld openscad
*Move files over to an installation dir
INSTALL_DIR=/path/to/some/installdir
INSTALL_ROOT=$INSTALL_DIR make install

=== Create the OpenSCAD Package ===
*Create a desktop icon
mkdir -p $INSTALL_DIR/home/guest/Desktop
echo -e '#!/usr/bin/env xdg-open\n[Desktop Entry]\nEncoding=UTF-8\nName=OpenSCAD\nExec=openscad\nIcon=openscad\nType=Application' > $BASEDIR/home/guest/Desktop/OpenSCAD.desktop
*Fix the permissions and ownership of files
chown -R guest $INSTALL_DIR/home/guest
chgrp -R guest $INSTALL_DIR/home/guest
chmod a+x $INSTALL_DIR/home/guest/Desktop/OpenSCAD.desktop
*Create the package and move it
dir2xzm $INSTALL_DIR openscad-with-deps-x86_64.xzm
mv openscad-with-deps-x86_64.xzm /mnt/sdX1/porteus/modules
*Reboot and see it it worked. Note that the qt-4 package must be activated before calling the openscad executable binary.

== Compilation of FreeCAD ==
These instructions were compiled from [http://www.freecadweb.org/wiki/?title=CompileOnUnix FreeCAD's official instructions].

Note that using FreeCAD requires a lot of RAM.
One of Porteus' most distinct features is the ability to copy the whole OS to RAM at boot time, giving a very responsive usage experience.
However, before using the copy2ram feature, we must translate free disk space-requirements into RAM-requirements.

FreeCAD depends on the OpenCasCade library which in itself requires [http://dev.opencascade.org/doc/overview/html/index.html ~600MB], just for storage, and an additional ~512MB RAM while running.
Such high system requirements makes FreeCAD unusable with the copy2ram boot flag unless the used computer has 8 GiB or more of RAM.

=== Compile FreeCAD Dependencies ===
When building from source within a Porteus that is loaded into RAM, be sure to build in a directory with several GiB of free storage space.
Even though we compiled the dependencies Boost and Eigen3 ourselves with gcc-5.3.0 in the OpenSCAD instructions above, we'll try to use versions compiled with gcc-4.3.2 for FreeCAD.
FreeCAD, like OpenSCAD, depends on Python, git and Qt. See the OpenSCAD instructions for how to get this from Slackware's repos.

====OpenCasCade====
'''Build from source'''
git clone git://github.com/tpaviot/oce.git
cd oce
mkdir build
cd build
cmake -DOCE_INSTALL_PREFIX:PATH=/usr -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TGZ:BOOL=ON -DCPACK_BINARY_TZ:BOOL=OFF -DCPACK_SOURCE_TBZ2:BOOL=OFF -DCPACK_SOURCE_TGZ:BOOL=OFF -DCPACK_SOURCE_TZ:BOOL=OFF ..
The next step will take a long time to finish.
make -j2
make package
mv OCE-xxx.tar.gz OCE-xxx.tgz
txz2xzm OCE-xxx.xzm
Move the package to the USB thumbdrive and activate.

====Boost====
*Available as precompiled package
usm -s boost

====Coin3D====
'''Build from source'''
wget https://bitbucket.org/Coin3D/coin/downloads/Coin-3.1.3.tar.gz
tar -xzvf Coin-3.1.3.tar.gz
mkdir Coin_install
mkdir Coin_build
cd Coin_build
../Coin-3.1.3/configure --prefix=/usr CC=gcc CXX=gcc
make -j2
make DESTDIR=/path/to/Coin_install install

Tested this, and even tested the CMake branch. Both failed. The CMake version completed build, but SoQt later required a coin coin-config executable. This executable required a configuration file somewhere in /usr/share... Didn't manage to locate the coin-default.cfg file and put it in place.

====SoQt====
*This is available as a Slackbuild, but depends on Coin3D to build.
usm -g SoQt

====Xerces-C++====
*Build from source

====Eigen3====
*Available as precompiled package
usm -s Eigen3

====Shiboken====
*This is available as a Slackbuild.
usm -s shiboken

====libarea====
*Build from source

=== Compile FreeCAD Itself ===
Get the latest FreeCAD source code.
git clone https://github.com/FreeCAD/FreeCAD.git free-cad-code

= Arduino =
This should get an xzm package containing java
usm -g openjre-7u79
This doesn't create a link to the executable java from /usr/bin, so lets add that
mkdir jav
xzm2dir openjre-7u79_b14-x86_64-bundle.xzm jav
cd jav/usr/bin
ln -s /usr/lib64/java/jre/bin/java java
cd ../../..
deactivate openjre-7u79_b14-x86_64-bundle.xzm
rm openjre-7u79_b14-x86_64-bundle.xzm
dir2xzm jav openjre-7u79_b14-x86_64-bundle_with_symlink.xzm
activate openjre-7u79_b14-x86_64-bundle_with_symlink.xzm
That should give you jre with the symlink.

Arduino itself is found in slackbuilds
usm -s arduino
If there's a md5sum mismatch, try
cat /tmp/usmsbo/arduino/arduino.info
to get the download url anyways, or clone the repo with
git clone https://github.com/arduino/Arduino.git
Independent of how you got the source code, put it in /tmp/usmsbo/aruino/arduino-1.6.5 and run usm again
usm -s arduino
For some reason, Arduino and openjre need gsettings-desktop-schemas to work together
usm -g gsettings-desktop-schemas

== Getting Icon On Desktop ==
Navigate to where you put the arduino-1.6.5-x86_64-1_SBo.xzm package.
mkdir ard
xzm2dir arduino-1.6.5-x86_64-1_SBo.xzm ard
cd ard
mkdir -p home/guest/Desktop
echo -e '#!/usr/bin/env xdg-open\n'\
'[Desktop Entry]\n'\
'Type=Application\n'\
'Name=Arduino IDE\n'\
'GenericName=Integrated Development Environment\n'\
'Comment=An IDE for Arduino-compatible electronics prototyping platforms\n'\
'Exec=/opt/arduino/arduino\n'\
'Icon=/opt/arduino/lib/arduino.png\n'\
'Terminal=false\n'\
'Categories=Development;IDE;Electronics;\n'\
'MimeType=text/x-arduino\n'\
'Keywords=embedded electronics;electronics;avr;microcontroller;' > home/guest/Desktop/arduino.desktop
chown -R guest home/guest
chgrp -R guest home/guest
chmod u+x home/guest/Desktop/arduino.desktop
cd ..
deactivate arduino-1.6.5-x86_64-1_SBo.xzm
rm arduino-1.6.5-x86_64-1_SBo.xzm
dir2xzm ard arduino-1.6.5-x86_64-1_with_desktop_icon.xzm
activate arduino-1.6.5-x86_64-1_with_desktop_icon.xzm
That's it, now you should get a nice icon on your desktop when you activate the package.

Tobben Log

2016-03-08T03:59:38Z

MarkDilley: finished going to level 2 headers, don't know how I missed so many. Removed underscores for readability. as always, please revert any edits not wanted.

{{RightTOC}}
[[Torbjorn CV]].

I'm studying RepRap workshops, events where participants build their
own generally useful production machines that can produce a large
fraction of their own parts.

I want to find factors that predict whether participants become workshop
organizers themselves or not.

This would let us design workshops that reproduce and evolve while
simultaneously distributing the machines' potential to improve people's
standards of living and quality of life on a large scale.

== Mar 7, 2016 ==
[[Tobbens Adding Inductive Proximity Sensor Log#Data]]

[[Tobbens Adding Inductive Proximity Sensor Log#Implementation]]

== Mar 6, 2016 ==

[[Tobbens Adding Inductive Proximity Sensor Log]]

New model added to [[D3D Live ISO#Computer Models Verified to Boot]]

== Mar 5, 2016 ==

[https://github.com/tobbelobb/D3D_Folgertech_Prusai3_Marlin D3D_Folgertech_Prusai3_Marlin repo]

[[Tobbens Folgertech Kit Assembly Log]]

Started a Python script for future automation of this pre-flight quality control, published [https://github.com/tobbelobb/RepRap_QC_scripts/blob/master/pre_flight_routine.py here]

[http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v2.iso Porteus-D3D-Workshop-x86_64-v2.iso]

== Mar 4, 2016 ==

[http://forums.reprap.org/read.php?14,607341,634998#msg-634998 Reports on speed limit] of cheapest and most easily built drive system of single threaded rod + stepper motor. Research suggesting anti-resonant drivers could be cheaper than aggressively threaded lead screws posted in [http://forums.reprap.org/read.php?14,607341,635107#msg-635107 forum thread].

[[Tobbens Folgertech Kit Assembly Log]]

== Mar 3, 2016 ==
[[Tobbens Folgertech Kit Assembly Log]]

== Mar 2, 2016 ==

[[D3D Live ISO#Computer Models Verified to Boot]]

Some activity on [http://forums.reprap.org/read.php?14,607341,634531#msg-634531 Lead Screw forum thread].

== Feb 28, 2016 ==

Mapped OpenSCAD dependencies properly [http://opensourceecology.org/wiki/File:Openscad2.png Dependency map]

Re-compiled OpenSCAD, uploaded new 64-bit iso: [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v1.iso Porteus-D3D-Workshop-x86_64-v1.iso]. Updated [[D3D_Live_ISO#Instructions]] link.

== Feb 26, 2016 ==

Been through [https://en.wikipedia.org/wiki/Dependency_hell Dependency hell] trying to compile CAD software to Porteus. OpenSCAD works now, FreeCAD doesn't.

== Feb 25, 2016 ==
[[D3D Live ISO#On Creating xzm Packages]]

== Feb 24, 2016 ==
Published 64-bit Porteus ISO. See [[D3D Live ISO#Instructions]] Still lacks configured Marlin source code.

Tried to compile FreeCAD. [[D3D Live ISO#Compilation of FreeCAD]] Abandoned because of difficulties with compiling Coin3.

Documented creation of 64-bit Arduino package: [[D3D Live ISO#Arduino]]

== Feb 23, 2016 ==

Compiled gcc-5.3.0 package for 64-bit version of Porteus and documented the process: [[D3D Live ISO#Choice of Compiler Version]]

Compiled OpenSCAD package for Porteus and documented the process: [[D3D Live ISO#CAD Software]]

== Feb 22, 2016 ==
Got OpenSCAD 2015.03 to work on the 32-bit Live USB.

Uploaded ~600 MiB iso file [http://vitana.se/opr3d/tbear/iso/Porteus_pronterface_slic3r_arduino_openscad_conf_i486.iso here].

Minor changes to [[D3D Live ISO]]

[[D3D Live ISO#Steps to boot Porteus on Macbook Air 2011]]

== Feb 21, 2016 ==
Made repo with D3D Porteus Live USB OS [https://github.com/tobbelobb/D3D_Workshop_Configuration config files]

Compiled GCC 5.3.0 for use in 32-bit version of Porteus: [http://vitana.se/opr3d/tbear/xzm/devel/gcc-5.3.0-i486.xzm xzm package link]

== Feb 19, 2016 ==
[[D3D Thesis#Line of Reasoning]]

[[D3D Thesis#Background]]

[[3D Printer Build Plate]]

Updated point 15 on [[Tobbens Folgertech Kit Unboxing Log]]

== Feb 18, 2016 ==
Got iso size down from 493 MiB (517 MB) to 299 MiB (313 MB). See [[D3D Live ISO#Stripping it down]] and updated download link in [[D3D Live ISO#Instructions]]

Completed [[Tobbens Folgertech Kit Unboxing Log]] with some images and clarifying comments

== Feb 17, 2016 ==
[[Tobbens Folgertech Kit Unboxing Log]]

== Feb 16, 2016 ==
Ordered four LJ12A3-4-Z/BX Inductive Proximity Sensor Switches.

Ordered GT2 belts, pulleys and belt tensioning springs.

Ordered signal switching 1N4148 diodes.

[[Research On Inductive Proximity Sensors]]

Updated [[File:Bed leveling and compensation comparison.ods]] with [https://www.youtube.com/watch?v=EcGFLwj0pnA Thomas Sanladerer's recommendation] and further comments on inductive sensing.

Researched some brackets for induction sensor: [[Folgertech Kit#Candidates For Improvement Resolution]]

== Feb 15, 2016 ==
New extensive Folgertech resource found: [[Folgertech Kit#Other Instructionals]].

[[Gcode Modularity]]

More work on [[D3D Live ISO]]. Got Slic3r working nicely, and integrated with Pronterface. Got Arduino IDE working. Latest version ISO: [http://vitana.se/opr3d/tbear/iso/Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso]

[https://docs.google.com/presentation/d/1-kF_PPt1NU2PQZHaQFh712hjdcBuCc3dafmPdRSzNu0/edit?ts=56c23f04#slide=id.g1192b7f2d5_0_8 Prototype Planning]

== Feb 13, 2016 ==
Further Porteus config. Now handling Pronterface better, updated iso to v1. See [[D3D Live ISO#ISO images]]

== Feb 11, 2016 ==

[[D3D Live ISO]]

Tested out [http://ProjectLibre.org/ Project Libre] with Andreas. [[File:D3D.pod]]

== Feb 9, 2016 ==
Experiment with 3D printing assembly manual using only OpenSCAD renders as visuals: [http://Vitana.se/opr3d/tbear/index.html#Clerck_assembly_manual Clerck assembly manual]

[[D3D Live ISO]]

Helped by Andreas to create [[D3D Thesis Project Plan#Map of Deliverables]] to more easily manage myself and include others.

== Feb 5, 2016 ==
Adjustments to [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 lead screw sourcing forum post] from yesterday.

Ordered F6-12 thrust bearings for prototyping.

== Feb 4, 2016 ==
Sourcing research on lead screws. Posted in [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 forum thread].

Igus links in [[D3D Printer Design Process#Practical viability of lead screws for 3D printing loads and speeds]]

Ordered following products for lead screw prototyping: [http://no.rs-online.com/web/p/products/8854956/], [http://no.rs-online.com/web/p/products/8854814/], [http://no.rs-online.com/web/p/products/8854830/], [http://no.rs-online.com/web/p/products/8854827/], [http://no.rs-online.com/web/p/products/8854987/]

== Feb 2, 2016 ==
Initiated [[3D Printer Quality Control Research]]

Initiated [[3D Printer Extruder Research]]

Researched [[3D Printer Bed Leveling]]. See [[File:Bed leveling and compensation comparison.ods]] for full assessment matrix.

== Feb 1, 2016 ==
Small change to [[Prusa i3 Build]].

New research and complete rewrite of [[3D Printer Bed Leveling]].

Small change to [[3D Printer Hot End Research]].

Initiated [[3D Printer Print Surface Research]].

== Jan 30, 2016 ==
[[D3D Workshop Roadmap]], [[D3D Workshop Slogans]], [https://docs.google.com/presentation/d/1duikQl9HMfHuUVAIQv4cDy1sGWZLujFzLxMRIGej5AY/edit?pref=2&pli=1#slide=id.p Folgertech 2020 Prusa i3 build working document], [https://www.facebook.com/OpenSourceEcology/photos/a.10151381815921562.574965.66469461561/10154554553731562/?type=3&theater Build Facebook post]

== Jan 29, 2016 ==
Meeting with Jonathan and Marcin.
* We should investigate bulk prices for key parts (like stepper motors)
* I (Tobben) should collect some stories from the people I've given printers to. Stories of people who got empowered and made some money with their new RepRap knowledge and machines.
* Thesis data collection nr 1 happens tomorrow when Folgertech Prusa i3 kit is assembled on the Factor e farm.

== Jan 23, 2016 ==
[[3D Printer Bed Leveling]]

[https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.g10745b77da_3_3 Prusa i3 selection Google document]

== Jan 20, 2016 ==
Created [http://forums.reprap.org/read.php?1,612676 forum thread] asking for input on workshop kits.

== Jan 19, 2016 ==
CADded LM8UU standard linear bearings into D3D Printer (see repo).

Meeting on kit selection [https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.p Kit considerations]

[[Prusa i3 Development]]

[[3D Printer Kit for Workshop Research]]

[[3D Printer Hot End Research]]

== Jan 17, 2016 ==
[[D3D Thesis#Workshop Reproducibility]], some reserve plans created in [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project]

== Jan 13, 2016 ==
Wrote [[D3D Thesis Project Plan]], sent to examiner.
More insights on lead screws on the [http://forums.reprap.org/read.php?14,607341,607483 forum thread].
Verification from [http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping] that lead screws used by Trinitylabs lasts for at least 2 years. Put in [[D3D Printer Design Process#Practical viability of lead screws for 3D printing loads and speeds]].

== Jan 12, 2016 ==
[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project], embedded in [[D3D Thesis Project Plan]].

Bought:
* 3xForce Sensing Resistors (Interlink Electronics FSR 400) for prototyping
* [https://ultimachine.com/content/rambo-13-complete-kit RAMBO v1.3 for prototyping]

[[3D Printer Troubleshooting]]

== Jan 11, 2016 ==
Wrote and published [[D3D Thesis#Team Charter]].

[[D3D Enterprise Logic Model]]

== Jan 10, 2016 ==

Some progress on the [http://forums.reprap.org/read.php?14,607341,607483 lead screw forum thread]. Emailed more skillful developers.

Read up on possible choices for [[D3D Printer Electronics]]. Ordered smooth rods with linear bearings (sizes 8 mmm and 10 mm) for prototyping. Ordered powdered graphite for lubrication testing.

== Jan 9, 2016 ==
Verification of lead screw: [https://YouTube.com/watch?v=gk9lhcTGSH4 working all-leadscrew 3D printer], [[Stepper Motor#Torque Tests]], [[D3D Printer Design Process#Verification Steps Taken for Lead Screw .2B Stepper Motor Concept]]

Bought: [http://eBay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 1] and [http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 2] for some hands-on testing in February.

Contacted [http://MooreInternational.co.uk Moore International] and [http://Danish3d.dk Danish 3D] for help with choice and supply of lead screws.

Discovered [http://Contraptor.org Contraptor] that tries to use the concept of modular linear motion units, put into [[D3D Thesis#Earlier Work]].

Read up on [[3D Printer Bed Leveling]].

Summarized state of lead screw discussion in the RepRap community in a [http://forums.reprap.org/read.php?14,607341 forum thread asking for further insights]. Emailed various developers with lead screw designs, asking for experiences, thoughts, insights...

[[3D Printer Filament Load Sensor]]

== Jan 8, 2016 ==
Some work on the [[D3D Design Methodology]].
Some usage of it logged in [[D3D Printer Design Process]].
Meeting with Marcin, initiated [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path doc].

== Jan 7, 2016 ==
Checked/commented on lifetimes: [[Stepper Motor#Lifetime]], [[FFF Extruder]], [[Lead Screw]]

Structuring of 3D printer design work: [[D3D Printer Design Process]], [[D3D Design Methodology]].

Structured wiki pages such that [[D3D Thesis]] is a sub-project of [[D3D Fusion]]. Changed [[D3D Fusion Project Plan]] to reflect this and initiated [[D3D Thesis Project Plan]].
The thesis project aims to bootstrap the [[D3D Workshop Kit]].

Explained structure in [[D3D Fusion#Naming and Links]]

== Jan 6, 2016 ==
Meeting with Andreas S, [https://docs.google.com/spreadsheets/d/1-NuTg0c_uta0i3vNUZtciD3cq6j1bS4RKWCIG8AOaR0/edit#gid=0 Work Breakdown Structure], [https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/edit#slide=id.geb160911a_2_25 D3D Team Project Charter].

Meeting with Marcin [https://docs.google.com/presentation/d/1jXC3V40cHqc2P8Oo-G2Z1G7IyytujYb4R3rIT9nZCpI/edit#slide=id.g8184a0e10_0_101 Long term Distributive Enterprise Milestones]

Wrote something on [[D3D Fusion thesis#Funding Mechanisms for Open Source Work]]

== Jan 5, 2016 ==
[[D3D Fusion Printer Conceptual Design]]

== Jan 4, 2016 ==
Wrote some [https://Overleaf.com/read/vmpdtnzsgdgg Project Plan stuff on Overleaf]. 3h meeting with Marcin. Finished [https://docs.google.com/document/d/1sQKi3QuQ1yPu_08zyo1cLMhrQGytiTHL4Mfd7JMUK2M/edit?ts=568a0631 OSE NEGOTIATION INVITATION].

== Jan 3, 2016 ==
Defined moving part of D3D Printer's linear actuator. Reorganized code and wrote README (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Jan 2, 2016 ==
Added [[D3D Fusion printer design#Weight calculation for steel sheet frame]] and [[D3D Fusion printer design#Motor placement]] to wiki. Two minor commits in [https://github.com/tobbelobb/D3D_Printer Github repo].

== Dec 31, 2015 ==
Re-organized [[D3D Requirements]]. Some progress on [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

== Dec 30, 2015 ==
Meeting with Marcin. Started [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

== Dec 28, 2015 ==
Reworked l_plate and basic frame (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Dec 27, 2015 ==
First rough visualization of D3D Fusion Printer done (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

== Dec 26, 2015 ==
Meeting with Marcin. Finished [[D3D Requirements]] together.

== Dec 25, 2015 ==
Some progress in [https://github.com/tobbelobb/D3D_Printer Github repo].

== Dec 25, 2015 ==
Made [https://github.com/tobbelobb/D3D_Printer Github repo] for D3D Printer OpenSCAD design.

== Dec 23, 2015 ==
Wrote something on the D3D Printer design. [[D3D Fusion Printer Design]] Needs to be fitted into a template.

== Dec 22, 2015 ==
Work on visa application process. Skype meeting with Marcin. Discussion points:
# [[Torbjorn DEF Agreement]]. DEF=Distributive Enterprise Fellow, under the [[EIR]] program. Including workshop schedule and number, and your tentative arrival date, and details regarding your university.
# Locking in design requirements - [[D3D Requirements]] - both overall and module by module
# Defining the 'story' for the thesis. [[D3D Thesis Story]].
# Beginning discussion on the tech tree of choices that we select to move forward - meaning specific implementation path for each module

Found some data: [https://www.3dhubs.com/trends]
Nice discussion on hangout, got some text produced from it: [https://docs.google.com/document/d/1Ber5iA-2V7m_3mbh54ZsuRB-viTLd-sfb9GL3jj58GQ/edit?ts=5679a219]

Asked for data on RepRap Freenode IRC chat. Generated discussion about Prusa i3 Steel. Didn't read it all, so putting it here for future reference: [[Cut_From_Freenode_RepRap_22_Dec]]

== Dec 21, 2015 ==
Initiated Project Plan [[D3D Fusion project plan]]. This is what Martin must approve before we can move on. Made thesis skeleton [[D3D Fusion thesis#Thesis Skeleton]] from template in course documentation. Limited progress in FreeCAD.

== Dec 19, 2015 ==
Commented proposed D3D requirements: [[Talk:D3D Requirements]]. Added Lyman extruder to [[Open Source Filament Extruders]]. ''See [[Power Tool Construction Set]].

== Dec 16, 2015 ==
Presented some 3d printer design ideas in [[D3D Fusion printer design]].

== Dec 15, 2015 ==
Summarized short research about prior work of Prusa: [[D3D Fusion thesis#Earlier Work]]

== Sun Dec 13, 2015 ==
Wrote short [[D3D Fusion#Business norms and science norms]] comparison between DE norms and science norms.

== Thu Dec 10, 2015 ==
Initiated [[D3D Fusion thesis]] sketch. Also did a little overview on [[Large Scale Fused Pellet Fabrication]]. Got an overview of the MOST lab's work. Put in in [[D3D Fusion thesis]].

== Sun Dec 6, 2015 ==
Initiated this work log. Initiated [[D3D Fusion]]. Initiated D3D dev spreadsheed [https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1&vpid=A1]. '''Nice. Please embed spreadsheet in wiki.'''-MJ Embedding [[D3D Fusion#Development spreadsheet| Done]]

[[Category:Logs]]

Tobben Log

2016-03-08T03:31:11Z

MarkDilley: headers down a size, easier to read?

{{RightTOC}} [[Torbjorn CV]]. [[Category:Logs]]

I'm studying RepRap workshops, events where participants build their
own generally useful production machines that can produce a large
fraction of their own parts.

I want to find factors that predict whether participants become workshop
organizers themselves or not.

This would let us design workshops that reproduce and evolve while
simultaneously distributing the machines' potential to improve people's
standards of living and quality of life on a large scale.

== Mar 7, 2016 ==
[[Tobbens Adding Inductive Proximity Sensor Log#Data]]

[[Tobbens_Adding_Inductive_Proximity_Sensor_Log#Implementation]]

== Mar 6, 2016 ==

[[Tobbens_Adding_Inductive_Proximity_Sensor_Log]]

New model added to [[D3D_Live_ISO#Computer_Models_Verified_to_Boot]]

== Mar 5, 2016 ==

[https://github.com/tobbelobb/D3D_Folgertech_Prusai3_Marlin D3D_Folgertech_Prusai3_Marlin repo]

[[Tobbens_Folgertech_Kit_Assembly_Log]]

Started a Python script for future automation of this pre-flight quality control, published [https://github.com/tobbelobb/RepRap_QC_scripts/blob/master/pre_flight_routine.py here]

[http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v2.iso Porteus-D3D-Workshop-x86_64-v2.iso]

== Mar 4, 2016 ==

[http://forums.reprap.org/read.php?14,607341,634998#msg-634998 Reports on speed limit] of cheapest and most easily built drive system of single threaded rod + stepper motor. Research suggesting anti-resonant drivers could be cheaper than aggressively threaded lead screws posted in [http://forums.reprap.org/read.php?14,607341,635107#msg-635107 forum thread].

[[Tobbens_Folgertech_Kit_Assembly_Log]]

== Mar 3, 2016 ==
[[Tobbens_Folgertech_Kit_Assembly_Log]]

== Mar 2, 2016 ==

[[D3D_Live_ISO#Computer_Models_Verified_to_Boot]]

Some activity on [http://forums.reprap.org/read.php?14,607341,634531#msg-634531 Lead Screw forum thread].

== Feb 28, 2016 ==

Mapped OpenSCAD dependencies properly [http://opensourceecology.org/wiki/File:Openscad2.png Dependency map]

Re-compiled OpenSCAD, uploaded new 64-bit iso: [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v1.iso Porteus-D3D-Workshop-x86_64-v1.iso]. Updated [[D3D_Live_ISO#Instructions]] link.

== Feb 26, 2016 ==

Been through [https://en.wikipedia.org/wiki/Dependency_hell Dependency hell] trying to compile CAD software to Porteus. OpenSCAD works now, FreeCAD doesn't.

== Feb 25, 2016 ==
[[D3D_Live_ISO#On_Creating_xzm_Packages]]

== Feb 24, 2016 ==
Published 64-bit Porteus ISO. See [[D3D_Live_ISO#Instructions]] Still lacks configured Marlin source code.

Tried to compile FreeCAD. [[D3D_Live_ISO#Compilation_of_FreeCAD]] Abandoned because of difficulties with compiling Coin3.

Documented creation of 64-bit Arduino package: [[D3D_Live_ISO#Arduino]]

== Feb 23, 2016 ==

Compiled gcc-5.3.0 package for 64-bit version of Porteus and documented the process: [[D3D_Live_ISO#Choice_of_Compiler_Version]]

Compiled OpenSCAD package for Porteus and documented the process: [[D3D_Live_ISO#CAD_Software]]

== Feb 22, 2016 ==
Got OpenSCAD 2015.03 to work on the 32-bit Live USB.

Uploaded ~600 MiB iso file [http://vitana.se/opr3d/tbear/iso/Porteus_pronterface_slic3r_arduino_openscad_conf_i486.iso here].

Minor changes to [[D3D_Live_ISO]]

[[D3D_Live_ISO#Steps_to_boot_Porteus_on_Macbook_Air_2011]]

== Feb 21, 2016 ==
Made repo with D3D Porteus Live USB OS [https://github.com/tobbelobb/D3D_Workshop_Configuration config files]

Compiled GCC 5.3.0 for use in 32-bit version of Porteus: [http://vitana.se/opr3d/tbear/xzm/devel/gcc-5.3.0-i486.xzm xzm package link]

== Feb 19, 2016 ==
[[D3D_Thesis#Line_of_Reasoning]]

[[D3D_Thesis#Background]]

[[3D_Printer_Build_Plate]]

Updated point 15 on [[Tobbens_Folgertech_Kit_Unboxing_Log]]

== Feb 18, 2016 ==
Got iso size down from 493 MiB (517 MB) to 299 MiB (313 MB). See [[D3D_Live_ISO#Stripping_it_down]] and updated download link in [[D3D_Live_ISO#Instructions]]

Completed [[Tobbens_Folgertech_Kit_Unboxing_Log]] with some images and clarifying comments

== Feb 17, 2016 ==
[[Tobbens_Folgertech_Kit_Unboxing_Log]]

== Feb 16, 2016 ==
Ordered four LJ12A3-4-Z/BX Inductive Proximity Sensor Switches.

Ordered GT2 belts, pulleys and belt tensioning springs.

Ordered signal switching 1N4148 diodes.

[[Research_On_Inductive_Proximity_Sensors]]

Updated [[File:Bed_leveling_and_compensation_comparison.ods]] with [https://www.youtube.com/watch?v=EcGFLwj0pnA Thomas Sanladerer's recommendation] and further comments on inductive sensing.

Researched some brackets for induction sensor: [[Folgertech_Kit#Candidates_For_Improvement_Resolution]]

= Feb 15, 2016 =
New extensive Folgertech resource found: [[Folgertech_Kit#Other_Instructionals]].

[[Gcode_Modularity]]

More work on [[D3D Live ISO]]. Got Slic3r working nicely, and integrated with Pronterface. Got Arduino IDE working. Latest version ISO: [http://vitana.se/opr3d/tbear/iso/Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso]

[https://docs.google.com/presentation/d/1-kF_PPt1NU2PQZHaQFh712hjdcBuCc3dafmPdRSzNu0/edit?ts=56c23f04#slide=id.g1192b7f2d5_0_8 Prototype Planning]

= Feb 13, 2016 =
Further Porteus config. Now handling Pronterface better, updated iso to v1. See [[D3D_Live_ISO#ISO_images]]

= Feb 11, 2016 =

[[D3D Live ISO]]

Tested out [http://www.projectlibre.org/ Project Libre] with Andreas. [[File:D3D.pod]]

= Feb 9, 2016 =
Experiment with 3D printing assembly manual using only OpenSCAD renders as visuals: [http://vitana.se/opr3d/tbear/index.html#Clerck_assembly_manual Clerck assembly manual]

[[D3D Live ISO]]

Helped by Andreas to create [[D3D_Thesis_Project_Plan#Map_of_Deliverables]] to more easily manage myself and include others.

= Feb 5, 2016 =
Adjustments to [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 lead screw sourcing forum post] from yesterday.

Ordered F6-12 thrust bearings for prototyping.

= Feb 4, 2016 =
Sourcing research on lead screws. Posted in [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 forum thread].

Igus links in [[D3D_Printer_Design_Process#Practical_viability_of_lead_screws_for_3D_printing_loads_and_speeds]]

Ordered following products for lead screw prototyping: [http://no.rs-online.com/web/p/products/8854956/], [http://no.rs-online.com/web/p/products/8854814/], [http://no.rs-online.com/web/p/products/8854830/], [http://no.rs-online.com/web/p/products/8854827/], [http://no.rs-online.com/web/p/products/8854987/]

= Feb 2, 2016 =
Initiated [[3D_Printer_Quality_Control_Research]]

Initiated [[3D_Printer_Extruder_Research]]

Researched [[3D Printer Bed Leveling]]. See [[File:Bed_leveling_and_compensation_comparison.ods]] for full assessment matrix.

= Feb 1, 2016 =
Small change to [[Prusa i3 Build]].

New research and complete rewrite of [[3D_Printer_Bed_Leveling]].

Small change to [[3D_Printer_Hot_End_Research]].

Initiated [[3D_Printer_Print_Surface_Research]].

= Jan 30, 2016 =
[[D3D_Workshop_Roadmap]], [[D3D_Workshop_Slogans]], [https://docs.google.com/presentation/d/1duikQl9HMfHuUVAIQv4cDy1sGWZLujFzLxMRIGej5AY/edit?pref=2&pli=1#slide=id.p Folgertech 2020 Prusa i3 build working document], [https://www.facebook.com/OpenSourceEcology/photos/a.10151381815921562.574965.66469461561/10154554553731562/?type=3&theater Build Facebook post]

= Jan 29, 2016 =
Meeting with Jonathan and Marcin.
*We should investigate bulk prices for key parts (like stepper motors)
*I (Tobben) should collect some stories from the people I've given printers to. Stories of people who got empowered and made some money with their new RepRap knowledge and machines.
*Thesis data collection nr 1 happens tomorrow when Folgertech Prusa i3 kit is assembled on the Factor e farm.

= Jan 23, 2016 =
[[3D_Printer_Bed_Leveling]]

[https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.g10745b77da_3_3 Prusa i3 selection Google document]

= Jan 20, 2016 =
Created [http://forums.reprap.org/read.php?1,612676 forum thread] asking for input on workshop kits.

= Jan 19, 2016 =
CADded LM8UU standard linear bearings into D3D Printer (see repo).

Meeting on kit selection [https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.p Kit considerations]

[[Prusa_i3_Development]]

[[3D_Printer_Kit_for_Workshop_Research]]

[[3D_Printer_Hot_End_Research]]

= Jan 17, 2016 =
[[D3D_Thesis#Workshop_Reproducibility]], some reserve plans created in [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project]

= Jan 13, 2016 =
Wrote [[D3D Thesis Project Plan]], sent to examiner.
More insights on lead screws on the [http://forums.reprap.org/read.php?14,607341,607483 forum thread].
Verification from [http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping] that lead screws used by Trinitylabs lasts for at least 2 years. Put in [[D3D_Printer_Design_Process#Practical_viability_of_lead_screws_for_3D_printing_loads_and_speeds]].

= Jan 12, 2016 =
[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project], embedded in [[D3D Thesis Project Plan]].

Bought:
*3xForce Sensing Resistors (Interlink Electronics FSR 400) for prototyping
*[https://ultimachine.com/content/rambo-13-complete-kit RAMBO v1.3 for prototyping]

[[3D_Printer_Troubleshooting]]

= Jan 11, 2016 =
Wrote and published [[D3D_Thesis#Team_Charter]].

[[D3D_Enterprise_Logic_Model]]

= Jan 10, 2016 =

Some progress on the [http://forums.reprap.org/read.php?14,607341,607483 lead screw forum thread]. Emailed more skillful developers.

Read up on possible choices for [[D3D_Printer_Electronics]]. Ordered smooth rods with linear bearings (sizes 8 mmm and 10 mm) for prototyping. Ordered powdered graphite for lubrication testing.

= Jan 9, 2016 =
Verification of lead screw: [https://www.youtube.com/watch?v=gk9lhcTGSH4 working all-leadscrew 3D printer], [[Stepper_Motor#Torque_Tests]], [[D3D Printer Design Process#Verification_Steps_Taken_for_Lead_Screw_.2B_Stepper_Motor_Concept]]

Bought: [http://www.ebay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 1] and [http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 2] for some hands-on testing in February.

Contacted [http://www.mooreinternational.co.uk/ Moore International] and [http://danish3d.dk/ Danish 3D] for help with choice and supply of lead screws.

Discovered [http://www.contraptor.org/ Contraptor] that tries to use the concept of modular linear motion units, put into [[D3D Thesis#Earlier Work]].

Read up on [[3D Printer Bed Leveling]].

Summarized state of lead screw discussion in the RepRap community in a [http://forums.reprap.org/read.php?14,607341 forum thread asking for further insights]. Emailed various developers with lead screw designs, asking for experiences, thoughts, insights...

[[3D_Printer_Filament_Load_Sensor]]

= Jan 8, 2016 =
Some work on the [[D3D Design Methodology]].
Some usage of it logged in [[D3D Printer Design Process]].
Meeting with Marcin, initiated [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path doc].

= Jan 7, 2016 =
Checked/commented on lifetimes: [[Stepper_Motor#Lifetime]], [[FFF_Extruder]], [[Lead_Screw]]

Structuring of 3D printer design work: [[D3D Printer Design Process]], [[D3D Design Methodology]].

Structured wiki pages such that [[D3D Thesis]] is a sub-project of [[D3D Fusion]]. Changed [[D3D Fusion Project Plan]] to reflect this and initiated [[D3D Thesis Project Plan]].
The thesis project aims to bootstrap the [[D3D Workshop Kit]].

Explained structure in [[D3D_Fusion#Naming_and_Links]]

= Jan 6, 2016 =
Meeting with Andreas S, [https://docs.google.com/spreadsheets/d/1-NuTg0c_uta0i3vNUZtciD3cq6j1bS4RKWCIG8AOaR0/edit#gid=0 Work Breakdown Structure], [https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/edit#slide=id.geb160911a_2_25 D3D Team Project Charter].

Meeting with Marcin [https://docs.google.com/presentation/d/1jXC3V40cHqc2P8Oo-G2Z1G7IyytujYb4R3rIT9nZCpI/edit#slide=id.g8184a0e10_0_101 Long term Distributive Enterprise Milestones]

Wrote something on [[D3D_Fusion_thesis#Funding_Mechanisms_for_Open_Source_Work]]

= Jan 5, 2016 =
[[D3D_Fusion_Printer_Conceptual_Design]]
= Jan 4, 2016 =
Wrote some [https://www.overleaf.com/read/vmpdtnzsgdgg Project Plan stuff on Overleaf]. 3h meeting with Marcin. Finished [https://docs.google.com/document/d/1sQKi3QuQ1yPu_08zyo1cLMhrQGytiTHL4Mfd7JMUK2M/edit?ts=568a0631 OSE NEGOTIATION INVITATION].

= Jan 3, 2016 =
Defined moving part of D3D Printer's linear actuator. Reorganized code and wrote README (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Jan 2, 2016 =
Added [[D3D_Fusion_printer_design#Weight_calculation_for_steel_sheet_frame]] and [[D3D_Fusion_printer_design#Motor_placement]] to wiki. Two minor commits in [https://github.com/tobbelobb/D3D_Printer Github repo].
= Dec 31, 2015 =
Re-organized [[D3D Requirements]]. Some progress on [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

= Dec 30, 2015 =
Meeting with Marcin. Started [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

= Dec 28, 2015 =
Reworked l_plate and basic frame (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Dec 27, 2015 =
First rough visualization of D3D Fusion Printer done (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Dec 26, 2015 =
Meeting with Marcin. Finished [[D3D Requirements]] together.

= Dec 25, 2015 =
Some progress in [https://github.com/tobbelobb/D3D_Printer Github repo].

= Dec 25, 2015 =
Made [https://github.com/tobbelobb/D3D_Printer Github repo] for D3D Printer OpenSCAD design.

= Dec 23, 2015 =
Wrote something on the D3D Printer design. [[D3D_Fusion_Printer_Design]] Needs to be fitted into a template.

= Dec 22, 2015 =
Work on visa application process. Skype meeting with Marcin. Discussion points:
#[[Torbjorn DEF Agreement]]. DEF=Distributive Enterprise Fellow, under the [[EIR]] program. Including workshop schedule and number, and your tentative arrival date, and details regarding your university.
#Locking in design requirements - [[D3D Requirements]] - both overall and module by module
#Defining the 'story' for the thesis. [[D3D Thesis Story]].
#Beginning discussion on the tech tree of choices that we select to move forward - meaning specific implementation path for each module

Found some data: [https://www.3dhubs.com/trends]
Nice discussion on hangout, got some text produced from it: [https://docs.google.com/document/d/1Ber5iA-2V7m_3mbh54ZsuRB-viTLd-sfb9GL3jj58GQ/edit?ts=5679a219]

Asked for data on RepRap Freenode IRC chat. Generated discussion about Prusa i3 Steel. Didn't read it all, so putting it here for future reference: [[Cut_From_Freenode_RepRap_22_Dec]]

= Dec 21, 2015 =
Initiated Project Plan [[D3D_Fusion_project_plan]]. This is what Martin must approve before we can move on. Made thesis skeleton [[D3D_Fusion_thesis#Thesis_Skeleton]] from template in course documentation. Limited progress in FreeCAD.

= Dec 19, 2015 =
Commented proposed D3D requirements: [[Talk:D3D_Requirements]]. Added Lyman extruder to [[Open_Source_Filament_Extruders]]. ''See [[Power Tool Construction Set]].

= Dec 16, 2015 =
Presented some 3d printer design ideas in [[D3D_Fusion_printer_design]].

= Dec 15, 2015=
Summarized short research about prior work of Prusa: [[D3D_Fusion_thesis#Earlier_Work]]

=Sun Dec 13, 2015=
Wrote short [http://opensourceecology.org/wiki/D3D_Fusion#Business_norms_and_science_norms comparison] between DE norms and science norms.

=Thu Dec 10, 2015=
Initiated [[D3D_Fusion_thesis]] sketch. Also did a little overview on [[Large_Scale_Fused_Pellet_Fabrication]]. Got an overview of the MOST lab's work. Put in in [[D3D_Fusion_thesis]].

=Sun Dec 6, 2015=
Initiated this work log. Initiated [[D3D Fusion]]. Initiated D3D dev spreadsheed [https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1&vpid=A1]. '''Nice. Please embed spreadsheet in wiki.'''-MJ Embedding [[D3D_Fusion#Development_spreadsheet|Done]]

[[Category:Logs]]

Tobben Log

2016-03-08T03:29:25Z

MarkDilley: test, heading size and losing the underscore, while keeping the page anchor, which, by the way, is pretty awesome, thanks!

{{RightTOC}} [[Torbjorn CV]]. [[Category:Logs]]

I'm studying RepRap workshops, events where participants build their
own generally useful production machines that can produce a large
fraction of their own parts.

I want to find factors that predict whether participants become workshop
organizers themselves or not.

This would let us design workshops that reproduce and evolve while
simultaneously distributing the machines' potential to improve people's
standards of living and quality of life on a large scale.

== Mar 7, 2016 ==
[[Tobbens Adding Inductive Proximity Sensor Log#Data]]

[[Tobbens_Adding_Inductive_Proximity_Sensor_Log#Implementation]]

= Mar 6, 2016 =

[[Tobbens_Adding_Inductive_Proximity_Sensor_Log]]

New model added to [[D3D_Live_ISO#Computer_Models_Verified_to_Boot]]

= Mar 5, 2016 =

[https://github.com/tobbelobb/D3D_Folgertech_Prusai3_Marlin D3D_Folgertech_Prusai3_Marlin repo]

[[Tobbens_Folgertech_Kit_Assembly_Log]]

Started a Python script for future automation of this pre-flight quality control, published [https://github.com/tobbelobb/RepRap_QC_scripts/blob/master/pre_flight_routine.py here]

[http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v2.iso Porteus-D3D-Workshop-x86_64-v2.iso]

= Mar 4, 2016 =

[http://forums.reprap.org/read.php?14,607341,634998#msg-634998 Reports on speed limit] of cheapest and most easily built drive system of single threaded rod + stepper motor. Research suggesting anti-resonant drivers could be cheaper than aggressively threaded lead screws posted in [http://forums.reprap.org/read.php?14,607341,635107#msg-635107 forum thread].

[[Tobbens_Folgertech_Kit_Assembly_Log]]

= Mar 3, 2016 =
[[Tobbens_Folgertech_Kit_Assembly_Log]]

= Mar 2, 2016 =

[[D3D_Live_ISO#Computer_Models_Verified_to_Boot]]

Some activity on [http://forums.reprap.org/read.php?14,607341,634531#msg-634531 Lead Screw forum thread].

= Feb 28, 2016 =

Mapped OpenSCAD dependencies properly [http://opensourceecology.org/wiki/File:Openscad2.png Dependency map]

Re-compiled OpenSCAD, uploaded new 64-bit iso: [http://vitana.se/opr3d/tbear/iso/Porteus-D3D-Workshop-x86_64-v1.iso Porteus-D3D-Workshop-x86_64-v1.iso]. Updated [[D3D_Live_ISO#Instructions]] link.

= Feb 26, 2016 =

Been through [https://en.wikipedia.org/wiki/Dependency_hell Dependency hell] trying to compile CAD software to Porteus. OpenSCAD works now, FreeCAD doesn't.

= Feb 25, 2016 =
[[D3D_Live_ISO#On_Creating_xzm_Packages]]

= Feb 24, 2016 =
Published 64-bit Porteus ISO. See [[D3D_Live_ISO#Instructions]] Still lacks configured Marlin source code.

Tried to compile FreeCAD. [[D3D_Live_ISO#Compilation_of_FreeCAD]] Abandoned because of difficulties with compiling Coin3.

Documented creation of 64-bit Arduino package: [[D3D_Live_ISO#Arduino]]

= Feb 23, 2016 =

Compiled gcc-5.3.0 package for 64-bit version of Porteus and documented the process: [[D3D_Live_ISO#Choice_of_Compiler_Version]]

Compiled OpenSCAD package for Porteus and documented the process: [[D3D_Live_ISO#CAD_Software]]

= Feb 22, 2016 =
Got OpenSCAD 2015.03 to work on the 32-bit Live USB.

Uploaded ~600 MiB iso file [http://vitana.se/opr3d/tbear/iso/Porteus_pronterface_slic3r_arduino_openscad_conf_i486.iso here].

Minor changes to [[D3D_Live_ISO]]

[[D3D_Live_ISO#Steps_to_boot_Porteus_on_Macbook_Air_2011]]

= Feb 21, 2016 =
Made repo with D3D Porteus Live USB OS [https://github.com/tobbelobb/D3D_Workshop_Configuration config files]

Compiled GCC 5.3.0 for use in 32-bit version of Porteus: [http://vitana.se/opr3d/tbear/xzm/devel/gcc-5.3.0-i486.xzm xzm package link]

= Feb 19, 2016 =
[[D3D_Thesis#Line_of_Reasoning]]

[[D3D_Thesis#Background]]

[[3D_Printer_Build_Plate]]

Updated point 15 on [[Tobbens_Folgertech_Kit_Unboxing_Log]]

= Feb 18, 2016 =
Got iso size down from 493 MiB (517 MB) to 299 MiB (313 MB). See [[D3D_Live_ISO#Stripping_it_down]] and updated download link in [[D3D_Live_ISO#Instructions]]

Completed [[Tobbens_Folgertech_Kit_Unboxing_Log]] with some images and clarifying comments

= Feb 17, 2016 =
[[Tobbens_Folgertech_Kit_Unboxing_Log]]

= Feb 16, 2016 =
Ordered four LJ12A3-4-Z/BX Inductive Proximity Sensor Switches.

Ordered GT2 belts, pulleys and belt tensioning springs.

Ordered signal switching 1N4148 diodes.

[[Research_On_Inductive_Proximity_Sensors]]

Updated [[File:Bed_leveling_and_compensation_comparison.ods]] with [https://www.youtube.com/watch?v=EcGFLwj0pnA Thomas Sanladerer's recommendation] and further comments on inductive sensing.

Researched some brackets for induction sensor: [[Folgertech_Kit#Candidates_For_Improvement_Resolution]]

= Feb 15, 2016 =
New extensive Folgertech resource found: [[Folgertech_Kit#Other_Instructionals]].

[[Gcode_Modularity]]

More work on [[D3D Live ISO]]. Got Slic3r working nicely, and integrated with Pronterface. Got Arduino IDE working. Latest version ISO: [http://vitana.se/opr3d/tbear/iso/Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso Porteus_with_Pronterface_Slic3r_Arduino_and_D3D_Conf_v0.iso]

[https://docs.google.com/presentation/d/1-kF_PPt1NU2PQZHaQFh712hjdcBuCc3dafmPdRSzNu0/edit?ts=56c23f04#slide=id.g1192b7f2d5_0_8 Prototype Planning]

= Feb 13, 2016 =
Further Porteus config. Now handling Pronterface better, updated iso to v1. See [[D3D_Live_ISO#ISO_images]]

= Feb 11, 2016 =

[[D3D Live ISO]]

Tested out [http://www.projectlibre.org/ Project Libre] with Andreas. [[File:D3D.pod]]

= Feb 9, 2016 =
Experiment with 3D printing assembly manual using only OpenSCAD renders as visuals: [http://vitana.se/opr3d/tbear/index.html#Clerck_assembly_manual Clerck assembly manual]

[[D3D Live ISO]]

Helped by Andreas to create [[D3D_Thesis_Project_Plan#Map_of_Deliverables]] to more easily manage myself and include others.

= Feb 5, 2016 =
Adjustments to [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 lead screw sourcing forum post] from yesterday.

Ordered F6-12 thrust bearings for prototyping.

= Feb 4, 2016 =
Sourcing research on lead screws. Posted in [http://forums.reprap.org/read.php?14,607341,621359#msg-621359 forum thread].

Igus links in [[D3D_Printer_Design_Process#Practical_viability_of_lead_screws_for_3D_printing_loads_and_speeds]]

Ordered following products for lead screw prototyping: [http://no.rs-online.com/web/p/products/8854956/], [http://no.rs-online.com/web/p/products/8854814/], [http://no.rs-online.com/web/p/products/8854830/], [http://no.rs-online.com/web/p/products/8854827/], [http://no.rs-online.com/web/p/products/8854987/]

= Feb 2, 2016 =
Initiated [[3D_Printer_Quality_Control_Research]]

Initiated [[3D_Printer_Extruder_Research]]

Researched [[3D Printer Bed Leveling]]. See [[File:Bed_leveling_and_compensation_comparison.ods]] for full assessment matrix.

= Feb 1, 2016 =
Small change to [[Prusa i3 Build]].

New research and complete rewrite of [[3D_Printer_Bed_Leveling]].

Small change to [[3D_Printer_Hot_End_Research]].

Initiated [[3D_Printer_Print_Surface_Research]].

= Jan 30, 2016 =
[[D3D_Workshop_Roadmap]], [[D3D_Workshop_Slogans]], [https://docs.google.com/presentation/d/1duikQl9HMfHuUVAIQv4cDy1sGWZLujFzLxMRIGej5AY/edit?pref=2&pli=1#slide=id.p Folgertech 2020 Prusa i3 build working document], [https://www.facebook.com/OpenSourceEcology/photos/a.10151381815921562.574965.66469461561/10154554553731562/?type=3&theater Build Facebook post]

= Jan 29, 2016 =
Meeting with Jonathan and Marcin.
*We should investigate bulk prices for key parts (like stepper motors)
*I (Tobben) should collect some stories from the people I've given printers to. Stories of people who got empowered and made some money with their new RepRap knowledge and machines.
*Thesis data collection nr 1 happens tomorrow when Folgertech Prusa i3 kit is assembled on the Factor e farm.

= Jan 23, 2016 =
[[3D_Printer_Bed_Leveling]]

[https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.g10745b77da_3_3 Prusa i3 selection Google document]

= Jan 20, 2016 =
Created [http://forums.reprap.org/read.php?1,612676 forum thread] asking for input on workshop kits.

= Jan 19, 2016 =
CADded LM8UU standard linear bearings into D3D Printer (see repo).

Meeting on kit selection [https://docs.google.com/presentation/d/194yjcF-Nk5P-wWkNLZduG910FuK_HnFIApBTexUDjxo/edit#slide=id.p Kit considerations]

[[Prusa_i3_Development]]

[[3D_Printer_Kit_for_Workshop_Research]]

[[3D_Printer_Hot_End_Research]]

= Jan 17, 2016 =
[[D3D_Thesis#Workshop_Reproducibility]], some reserve plans created in [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project]

= Jan 13, 2016 =
Wrote [[D3D Thesis Project Plan]], sent to examiner.
More insights on lead screws on the [http://forums.reprap.org/read.php?14,607341,607483 forum thread].
Verification from [http://www.vermontrapidprototyping.com/3dprinters Vermont Rapid Prototyping] that lead screws used by Trinitylabs lasts for at least 2 years. Put in [[D3D_Printer_Design_Process#Practical_viability_of_lead_screws_for_3D_printing_loads_and_speeds]].

= Jan 12, 2016 =
[https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path for Thesis Project], embedded in [[D3D Thesis Project Plan]].

Bought:
*3xForce Sensing Resistors (Interlink Electronics FSR 400) for prototyping
*[https://ultimachine.com/content/rambo-13-complete-kit RAMBO v1.3 for prototyping]

[[3D_Printer_Troubleshooting]]

= Jan 11, 2016 =
Wrote and published [[D3D_Thesis#Team_Charter]].

[[D3D_Enterprise_Logic_Model]]

= Jan 10, 2016 =

Some progress on the [http://forums.reprap.org/read.php?14,607341,607483 lead screw forum thread]. Emailed more skillful developers.

Read up on possible choices for [[D3D_Printer_Electronics]]. Ordered smooth rods with linear bearings (sizes 8 mmm and 10 mm) for prototyping. Ordered powdered graphite for lubrication testing.

= Jan 9, 2016 =
Verification of lead screw: [https://www.youtube.com/watch?v=gk9lhcTGSH4 working all-leadscrew 3D printer], [[Stepper_Motor#Torque_Tests]], [[D3D Printer Design Process#Verification_Steps_Taken_for_Lead_Screw_.2B_Stepper_Motor_Concept]]

Bought: [http://www.ebay.com/itm/301833740948?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 1] and [http://www.ebay.com/itm/262200758350?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Lead screw stepper motor 2] for some hands-on testing in February.

Contacted [http://www.mooreinternational.co.uk/ Moore International] and [http://danish3d.dk/ Danish 3D] for help with choice and supply of lead screws.

Discovered [http://www.contraptor.org/ Contraptor] that tries to use the concept of modular linear motion units, put into [[D3D Thesis#Earlier Work]].

Read up on [[3D Printer Bed Leveling]].

Summarized state of lead screw discussion in the RepRap community in a [http://forums.reprap.org/read.php?14,607341 forum thread asking for further insights]. Emailed various developers with lead screw designs, asking for experiences, thoughts, insights...

[[3D_Printer_Filament_Load_Sensor]]

= Jan 8, 2016 =
Some work on the [[D3D Design Methodology]].
Some usage of it logged in [[D3D Printer Design Process]].
Meeting with Marcin, initiated [https://docs.google.com/drawings/d/1wSlnfzftSjfkOlMdXA6-QYl57jqg7d5m88IQpmr567E/edit Critical Path doc].

= Jan 7, 2016 =
Checked/commented on lifetimes: [[Stepper_Motor#Lifetime]], [[FFF_Extruder]], [[Lead_Screw]]

Structuring of 3D printer design work: [[D3D Printer Design Process]], [[D3D Design Methodology]].

Structured wiki pages such that [[D3D Thesis]] is a sub-project of [[D3D Fusion]]. Changed [[D3D Fusion Project Plan]] to reflect this and initiated [[D3D Thesis Project Plan]].
The thesis project aims to bootstrap the [[D3D Workshop Kit]].

Explained structure in [[D3D_Fusion#Naming_and_Links]]

= Jan 6, 2016 =
Meeting with Andreas S, [https://docs.google.com/spreadsheets/d/1-NuTg0c_uta0i3vNUZtciD3cq6j1bS4RKWCIG8AOaR0/edit#gid=0 Work Breakdown Structure], [https://docs.google.com/presentation/d/1CrmuvgX19dYkeBbUlYqTmXBTjc8wqiDNU7MEwVNuTsg/edit#slide=id.geb160911a_2_25 D3D Team Project Charter].

Meeting with Marcin [https://docs.google.com/presentation/d/1jXC3V40cHqc2P8Oo-G2Z1G7IyytujYb4R3rIT9nZCpI/edit#slide=id.g8184a0e10_0_101 Long term Distributive Enterprise Milestones]

Wrote something on [[D3D_Fusion_thesis#Funding_Mechanisms_for_Open_Source_Work]]

= Jan 5, 2016 =
[[D3D_Fusion_Printer_Conceptual_Design]]
= Jan 4, 2016 =
Wrote some [https://www.overleaf.com/read/vmpdtnzsgdgg Project Plan stuff on Overleaf]. 3h meeting with Marcin. Finished [https://docs.google.com/document/d/1sQKi3QuQ1yPu_08zyo1cLMhrQGytiTHL4Mfd7JMUK2M/edit?ts=568a0631 OSE NEGOTIATION INVITATION].

= Jan 3, 2016 =
Defined moving part of D3D Printer's linear actuator. Reorganized code and wrote README (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Jan 2, 2016 =
Added [[D3D_Fusion_printer_design#Weight_calculation_for_steel_sheet_frame]] and [[D3D_Fusion_printer_design#Motor_placement]] to wiki. Two minor commits in [https://github.com/tobbelobb/D3D_Printer Github repo].
= Dec 31, 2015 =
Re-organized [[D3D Requirements]]. Some progress on [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

= Dec 30, 2015 =
Meeting with Marcin. Started [https://docs.google.com/presentation/d/18lZ-c7xICEuWqdkpj-hTEY5QemeCp4e1U80k2w5bYFw/edit?pref=2&pli=1#slide=id.p Tech Tree of Choices for D3D Printer].

= Dec 28, 2015 =
Reworked l_plate and basic frame (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Dec 27, 2015 =
First rough visualization of D3D Fusion Printer done (see [https://github.com/tobbelobb/D3D_Printer Github repo]).

= Dec 26, 2015 =
Meeting with Marcin. Finished [[D3D Requirements]] together.

= Dec 25, 2015 =
Some progress in [https://github.com/tobbelobb/D3D_Printer Github repo].

= Dec 25, 2015 =
Made [https://github.com/tobbelobb/D3D_Printer Github repo] for D3D Printer OpenSCAD design.

= Dec 23, 2015 =
Wrote something on the D3D Printer design. [[D3D_Fusion_Printer_Design]] Needs to be fitted into a template.

= Dec 22, 2015 =
Work on visa application process. Skype meeting with Marcin. Discussion points:
#[[Torbjorn DEF Agreement]]. DEF=Distributive Enterprise Fellow, under the [[EIR]] program. Including workshop schedule and number, and your tentative arrival date, and details regarding your university.
#Locking in design requirements - [[D3D Requirements]] - both overall and module by module
#Defining the 'story' for the thesis. [[D3D Thesis Story]].
#Beginning discussion on the tech tree of choices that we select to move forward - meaning specific implementation path for each module

Found some data: [https://www.3dhubs.com/trends]
Nice discussion on hangout, got some text produced from it: [https://docs.google.com/document/d/1Ber5iA-2V7m_3mbh54ZsuRB-viTLd-sfb9GL3jj58GQ/edit?ts=5679a219]

Asked for data on RepRap Freenode IRC chat. Generated discussion about Prusa i3 Steel. Didn't read it all, so putting it here for future reference: [[Cut_From_Freenode_RepRap_22_Dec]]

= Dec 21, 2015 =
Initiated Project Plan [[D3D_Fusion_project_plan]]. This is what Martin must approve before we can move on. Made thesis skeleton [[D3D_Fusion_thesis#Thesis_Skeleton]] from template in course documentation. Limited progress in FreeCAD.

= Dec 19, 2015 =
Commented proposed D3D requirements: [[Talk:D3D_Requirements]]. Added Lyman extruder to [[Open_Source_Filament_Extruders]]. ''See [[Power Tool Construction Set]].

= Dec 16, 2015 =
Presented some 3d printer design ideas in [[D3D_Fusion_printer_design]].

= Dec 15, 2015=
Summarized short research about prior work of Prusa: [[D3D_Fusion_thesis#Earlier_Work]]

=Sun Dec 13, 2015=
Wrote short [http://opensourceecology.org/wiki/D3D_Fusion#Business_norms_and_science_norms comparison] between DE norms and science norms.

=Thu Dec 10, 2015=
Initiated [[D3D_Fusion_thesis]] sketch. Also did a little overview on [[Large_Scale_Fused_Pellet_Fabrication]]. Got an overview of the MOST lab's work. Put in in [[D3D_Fusion_thesis]].

=Sun Dec 6, 2015=
Initiated this work log. Initiated [[D3D Fusion]]. Initiated D3D dev spreadsheed [https://docs.google.com/spreadsheets/d/1q4Smbyc0_MUNIIFQjmBc1-yq6sgeVxerCedJtWzahdo/edit#gid=1&vpid=A1]. '''Nice. Please embed spreadsheet in wiki.'''-MJ Embedding [[D3D_Fusion#Development_spreadsheet|Done]]

[[Category:Logs]]

YouTube

2016-03-08T03:26:00Z

MarkDilley: hide URL behind sensible name. CamelCase URL for easier reading.

OSE YouTube channel is OpenSourceEcology: https://YouTube.com/user/OpenSourceEcology

== Adding Annotations and Links ==

[https://support.google.com/youtube/answer/6035690?rd=1 Google Support]

Collaborative Literacy Webinar

2016-03-08T03:23:24Z

MarkDilley: formatting, spell check, WikiLink YouTube

{{RightTOC}}
==Introduction==
; [[Collaborative Literacy]] is the shared understanding about how to work together effectively in the field of [[Open Source Product Development]]. The critical challenge is how to build on other work - or and how to [[Time-Bind]] development effort.

; This is important to OSE because OSE's mission is to develop the [[Open Source Economy]] by mass creation of livelihoods - according to our [[Roadmap]]. An open source economy is built around a paradigm of collaborative development. A characteristic feature of the open source economy is the creation of [[Distributive Enterprise]].

; The weekly Collaborative Literacy Webinar runs at 8 PM CST USA time every Monday. The format is a Google Hangout on Air, which is recorded online and posted at the corresponding date below, immediately after the webinar becomes available on YouTube. To join the webinar, see below or the [[OSE Facebook Page]] for a link to the Webinar, which will be posted on the day of the webinar.

== Monday, Mar 7, 2016 ==
* 8 PM CST USA - '''[https://plus.google.com/hangouts/_/ytl/sSPRzi9D_lUF9dmWc1fC-PzWb6dMyusLuwnH9r3ubps=?hl=en_US&authuser=1 Join Session (up to 10 people)'''] - Or '''[https://www.youtube.com/watch?v=TqVqmr37d4whttps://plus.google.com/hangouts/_/ytl/sSPRzi9D_lUF9dmWc1fC-PzWb6dMyusLuwnH9r3ubps=?hl=en_US&authuser=1 Watch Livestream]''' (unlimited number of participants).
* '''Abstract:''' Last week we covered the collaborative development of the 3D printer [[Distributive Enterprise]]. This week we will cover how design collaboration can happen in a large scale with Computer Aided Design (CAD) software. We are using the open source [[FreeCAD]] software. We will introduce the workflows for doing large scale collaborative design in FreeCAD, and apply that to our current developments - [[3D Printer Development]]. OSE's approach to wide collaboration is its [[Construction Set Approach]] - and in this - open source CAD software is critical. First - how to download and use? We can start with a [[Live Linux]] install with all settings pre-configured. We will discuss how we can then create part libraries - how to work with part libraries - and how part libraries can be used to create a Construction Set workbench in FreeCAD. The goal is that anyone who can learn basic CAD techniques - can begin to design 3D printers on their own - by using accepted library parts which have the engineering already worked out. We will explain how to do an initial large scale collaboration exercise: how to find and import parts into FreeCAD, and how to manipulate them to create designs based on accurate parts and real parts from manufacturers. We will leave the meeting with a challenge of creating an (1) OSE Live Linux FreeCAD, and (2) the part library in FreeCAD, using the [[3D Printer Bill of Materials]] as a starting point. This process can apply to any design - such that if OSE produces Design Guides and Construction Sets in FreeCAD - any individual in the world will be able to do meaningful design on any product. This can become the basis of an [[Open Source Product Development]] paradigm that displaces the current state of art - which is based on large amounts of competitive waste.

== Monday, Feb. 29, 2016 ==
'''Abstract:''' This is the second webinar of 2016, and you can hear last week's webinar about the [[Roadmap]] below. We will cover [[Viral Replicability Criteria]]. What are Viral Replicability Criteria for an enterprise? How do we motivate a developer community to develop them? Read the latest blog post on the Viral Replicability Criteria - http://bit.ly/1TJbOCY. We will apply the Viral Replicability Criteria to the 3D Printer Workshop Business Plan - http://bit.ly/1TgA3do. We will survey the main needs for succeeding in replicating a 3D Printer Workshop with participants who are interested in replicating the workshop. If you are potentially interested in running 1 day 3D printer builds from scratch - where people take the 3D printer home - we can teach you how to run a workshop, and to develop a source of livelihood. To get started, join this webinar.

'''Participants:''' MJ, Jonathan Kocurek, +..... Working doc: [https://docs.google.com/presentation/d/15kcAQryATrafgYRZheFJDqsGqK0s48_42VxNCHdV0sc/edit#slide=id.g84263c56c_9_12]

=== Video ===
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/pe85FleyInM" frameborder="0" allowfullscreen></iframe></html>

==== Comments and Questions for the Webinar ====
Feel free to ask questions for the webinar here.

<html><div id="disqus_thread"></div>
<script>
/**
* RECOMMENDED CONFIGURATION VARIABLES: EDIT AND UNCOMMENT THE SECTION BELOW TO INSERT DYNAMIC VALUES FROM YOUR PLATFORM OR CMS.
* LEARN WHY DEFINING THESE VARIABLES IS IMPORTANT: https://disqus.com/admin/universalcode/#configuration-variables
*/
/*
var disqus_config = function () {
this.page.url = PAGE_URL; // Replace PAGE_URL with your page's canonical URL variable
this.page.identifier = PAGE_IDENTIFIER; // Replace PAGE_IDENTIFIER with your page's unique identifier variable
};
*/
(function() { // DON'T EDIT BELOW THIS LINE
var d = document, s = d.createElement('script');

s.src = '//collaborativeliteracy.disqus.com/embed.js';

s.setAttribute('data-timestamp', +new Date());
(d.head || d.body).appendChild(s);
})();

</script>
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript" rel="nofollow">comments powered by Disqus.</a></noscript></html>

== Monday, Feb. 22, 2016 ==
'''Abstract:''' The first webinar of 2016 covers some of the bigger picture items regarding the approach of OSE: the OSE [[Roadmap]] for the next 20 years, and the [[3D Printer Roadmap]] in particular, since the [[3D Printer Development]] marks our first concerted effort to create a [[Distributive Enterprise]] with [[Viral Replicability Criteria]]. See the video at the '''[[3D Printer Workshop]]''', which we plan to make into our first ongoing and regular workshop offering. We are currently developing the [[Extreme Manufacturing Workshop Model]] as a way to bootstrap fund our operations. Bootstrap funding is important to us because this model of funding allows the OSE movement to scale to many locations worldwide, and allied efforts can also build on this model. After a discussion of the OSE Roadmap, we will get into the basics of [[Open Source Product Development]], and the key elements of documentation, modular breakdown, and value creation. Finally, we will cover the first [[Design Sprint]] of 2016 - an invitation to collaborating on the 3D Printer Distributive Enterprise. The key development items on the 3D Printer are the [[3D Printer Open Source Supply Chain]]; a [[D3D Live ISO]] with software and firmware for controlling the 3D printer, so that success of the 3D Printer Workshop is not derailed in any way by computer-related issues; and initial considerations on the [[3D Printed Cordless Drill]] - which is on the 3D Printer Roadmap.

Participants: MJ, Donald, James Q

<html><iframe width="280" height="165" src="https://www.youtube.com/embed/t5EWBT_Mtfw" frameborder="0" allowfullscreen></iframe></html>

== Archives ==
See [[Collaborative Literacy Playlist]] on [[YouTube]].

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/videoseries?list=PL6Jpysxw3Ty--ILAxCWI5DRFFFvH4KzXW" frameborder="0" allowfullscreen></iframe></html>

[[Category:Collaborative Literacy Webinars]]

OSE Facebook Page

2016-03-08T02:22:08Z

MarkDilley: Category: Social Media

== Page ==
: https://Facebook.com/OpenSourceEcology

== Hashtags ==

: #OpenSourceEcology: https://Facebook.com/search/top/?q=%23OpenSourceEcology

: #OSE: https://Facebook.com/search/top/?q=%23OSE

[[Category: Social Media]]