Open Source Ecology - User contributions [en]

User talk:Mjn

2014-02-21T20:56:29Z

Mjn:

Hi Mark! I will of course include you in any changes I make. I suppose my first step after telling everyone who I am is to ask where I can help. I am interested in making this information readily available in a straightforward manner but I don't want to step on any toes. Guess I'm looking for an introduction to the work online here.

--[[User:Ryan Lutz|Ryan Lutz]] 22:29, 27 June 2011 (PDT)

hi mark! would you like me to merge your two pages, [[Mark J Norton]] and [[User:Mjn]]? this way, we can reduce redundancy and avoid confusing people checking out your profile.
you can check out how mine works and tell me if that's fine with you :)
my pages are [[Pepe Bawagan]] and [[User:Syk0 saje]]

--[[User:Syk0 saje|syk0saje]] 08:54, 4 May 2011 (PDT)

I've considered it, but there is a problem. My login name is Mjn, which shows up in the logs, etc. However, that's probably not enough info to tell people who I am, so I have retained [[Mark J Norton]]. I have cross-linked the pages. What is your opinion? I suppose we could FORWARD [[User:Mjn]] to [[Mark J Norton]]. That would work for me.

I had a look at your pages. I guess it comes down to: do you want to be known by your name or by your handle (login name)?

I think I'll leave both of my pages up for now and think about how to merge them at a future date.

--[[User:Mjn]] 12:08, 4 May 2011 (EDT)

Hi Mark,
I've noticed your contributions to the Nickel-Iron battery concept. I'd like to compare notes with you, as I have only a basic understanding of its chemistry. I've got a decent design figured out, using sheet steel and nickel hydroxide (build the battery discharged, then charge it). Turns out that a 1kWh cell is quite feasible. Anyway, I hope to learn a thing or two from you and I hope we can flesh this battery out as well.
 Thanks! [[User:Colin|Colin]] 14:38, 16 May 2011 (PDT)

== CAD for a steam engine ==
Mark, I have been noticing you are putting up a whole bunch of stuff related to the steam engine. Specifically you have enough diagrams of different designs that it should be possible for me to knock together a rough model of one of them. I was wondering if you had a particular design that you think we will use that I could try to make a CAD model for.

I am looking to make a tutorial for how to use FreeCad to contribute to OSE and wanted a model to use as an example and I think this would be a good one. All the diagrams/drawings you have uploaded make it easy to put together pictures of what we want combined with pictures of what you do in FreeCad which I think will make a very nice tutorial. The model would be mostly procedural based, meaning you would be able to change things like the cylinder bore and other properties by just changing a single number and other parts of the model adjust accordingly. Although it will probably not be a final CAD model, and may not even be the design we ultimately use, it should be useful to you in your design work to have a 3D model to examine/tweak, rather than having to work all in 2D. Anyway, let me know what you think of this. -[[User:Andrew Buck|Andrew Buck]] 06:20, 25 May 2011 (PDT)

== Duplicated Images ==
I was going through the drawings you are making and categorizing them and I happened to notice you have two copies of basically the same image at [[:File:Spec-Valve.png]] and [[:File:Valve-spec.png]] (the first one is linked to from a page, the second one is not. Let me know which one you want to keep, or if you want to keep both of them and I will take care of the rest. Also, what program are you using to draw the part drawings you have been uploading? They look very nice and should make the cad model pretty easy to do. I got my tutorial finished (I ended up making an engine block as an example) and will probably start making parts for the steam engine either tonight or tommorow. Hopefully I can make and assemble the parts in CAD as fast as you are drawing them. I think this is going to be a lot of fun. I will keep my skype open (username andrewbuck40) and if you want to chat about any of this sometime, give me a ring. -[[User:Andrew Buck|Andrew Buck]] 13:33, 26 May 2011 (PDT)

== Incorrect Dimension for Valve ==

I was putting together the CAD model of the valve and I noticed a mistake in the stated dimensions for the 'valve head' (see [[Steam Engine Build/Valve]]). You list D3 as being 2.4 inches and D4 as being 0.8 with a 0.4 inch horizontal distance between them. However, using those dimensions you do not arrive at a 45 degree bevel. If you start with a 0.8 inch valve opening and then extrude it out on a 45 degree bevel for 0.4 inches, the radius increases by 0.4, meaning the diameter increases by 0.8. So D3 should be 1.6, rather than 2.4 like it is stated. I think this is the way the mistake should be resolved as the valve seat thickness of 0.4 and the 0.8 for the opening diameter sound like the figures you wanted so they are the ones I think you want unchanged. Let me know for sure if this should be how the matter is resolved and I will update the CAD model accordingly. -[[User:Andrew Buck|Andrew Buck]] 10:12, 27 May 2011 (PDT)

nice work on the build instructions. looks really good. --[[User:Dorkmo|Dorkmo]] 20:19, 5 June 2011 (PDT)

Re switching to Zn Br, I woudl not advocate switching just yet because while I am personally pretty sure, there shoudl be some hysteresis when it comes to switching the actual project focus. After I learn more I think I probably will recommend switching. There are still some issues, mainly whether the bromine resistant plastics are patented, and the vapor pressure of bromine (if it is above atmospheric that could be a real safety issue) that I need to check, and also to do the financial calculations to compare LA, NiFe and Zn Br to determine roughly how much they are really worth quantitatively. [[User:Gregortheinventor|Gregor]] 16:37, 25 June 2011 (PDT)

Yes, I may do that at some point, but I was sort of waiting until we had better wiki tools like the ones I did research on and posted about in the forum, so it won't take forever. [[User:Gregortheinventor|Gregor]] 09:01, 13 July 2011 (PDT)

== RE: Hierarchy structure ==

I do believe you're right in using a separate navigation system for the subpages of each GVCS tool, but I think the ToolTemplate should still be at the top of every page so as to give an easy way to jump between larger sections. The way I see it, from any page, one should be able to trace back all the way (i.e. breadcrumb) but with the added functionality of jumping to other sibling sections (i.e. from [[LifeTrac/Manufacturing Instructions/Assembly/Frame]] to [[LifeTrac/User's Manual]]

I'm all for each GVCS tool fabricator organizing his or her respective nav system, we just need a way for people to be able to see where they are and where they want to go at any time more easily. I think having ToolTemplate over a GVCS tool-specific navbar is the best way to cover all our bases. [[User:Ryan Lutz|Ryan Lutz]] 04:41, 26 July 2011 (CEST)

== Missing soil pulverizor for CEB press flowchart ==

Hey there. I thought I'd point out something I noticed in documentation. In this diagram we have soil that points into the CEB press, but it also looks like the soil pulverizer and tractor are dependencies for this to work. If you want to give me the file you used to generate the image I can update it for you if you think this is correct.

http://opensourceecology.org/wiki/File:4b-Constructioneco.png#filelinks

As an idea should we also generally provide the source files used to generate any images like flow charts for future modification? -[[User:Andrew_Graham]] 21:14, 21 February 2014‎

-- Sent to your GMail account [[User:Mjn|Mjn]] 15:54, Feb. 21, 2014

User talk:Mjn

2014-02-21T20:55:17Z

Mjn:

Hi Mark! I will of course include you in any changes I make. I suppose my first step after telling everyone who I am is to ask where I can help. I am interested in making this information readily available in a straightforward manner but I don't want to step on any toes. Guess I'm looking for an introduction to the work online here.

--[[User:Ryan Lutz|Ryan Lutz]] 22:29, 27 June 2011 (PDT)

hi mark! would you like me to merge your two pages, [[Mark J Norton]] and [[User:Mjn]]? this way, we can reduce redundancy and avoid confusing people checking out your profile.
you can check out how mine works and tell me if that's fine with you :)
my pages are [[Pepe Bawagan]] and [[User:Syk0 saje]]

--[[User:Syk0 saje|syk0saje]] 08:54, 4 May 2011 (PDT)

I've considered it, but there is a problem. My login name is Mjn, which shows up in the logs, etc. However, that's probably not enough info to tell people who I am, so I have retained [[Mark J Norton]]. I have cross-linked the pages. What is your opinion? I suppose we could FORWARD [[User:Mjn]] to [[Mark J Norton]]. That would work for me.

I had a look at your pages. I guess it comes down to: do you want to be known by your name or by your handle (login name)?

I think I'll leave both of my pages up for now and think about how to merge them at a future date.

--[[User:Mjn]] 12:08, 4 May 2011 (EDT)

Hi Mark,
I've noticed your contributions to the Nickel-Iron battery concept. I'd like to compare notes with you, as I have only a basic understanding of its chemistry. I've got a decent design figured out, using sheet steel and nickel hydroxide (build the battery discharged, then charge it). Turns out that a 1kWh cell is quite feasible. Anyway, I hope to learn a thing or two from you and I hope we can flesh this battery out as well.
 Thanks! [[User:Colin|Colin]] 14:38, 16 May 2011 (PDT)

Sent to your GMail account [[User:Mjn|Mjn]] 15:54, Feb. 21, 2014

== CAD for a steam engine ==
Mark, I have been noticing you are putting up a whole bunch of stuff related to the steam engine. Specifically you have enough diagrams of different designs that it should be possible for me to knock together a rough model of one of them. I was wondering if you had a particular design that you think we will use that I could try to make a CAD model for.

I am looking to make a tutorial for how to use FreeCad to contribute to OSE and wanted a model to use as an example and I think this would be a good one. All the diagrams/drawings you have uploaded make it easy to put together pictures of what we want combined with pictures of what you do in FreeCad which I think will make a very nice tutorial. The model would be mostly procedural based, meaning you would be able to change things like the cylinder bore and other properties by just changing a single number and other parts of the model adjust accordingly. Although it will probably not be a final CAD model, and may not even be the design we ultimately use, it should be useful to you in your design work to have a 3D model to examine/tweak, rather than having to work all in 2D. Anyway, let me know what you think of this. -[[User:Andrew Buck|Andrew Buck]] 06:20, 25 May 2011 (PDT)

== Duplicated Images ==
I was going through the drawings you are making and categorizing them and I happened to notice you have two copies of basically the same image at [[:File:Spec-Valve.png]] and [[:File:Valve-spec.png]] (the first one is linked to from a page, the second one is not. Let me know which one you want to keep, or if you want to keep both of them and I will take care of the rest. Also, what program are you using to draw the part drawings you have been uploading? They look very nice and should make the cad model pretty easy to do. I got my tutorial finished (I ended up making an engine block as an example) and will probably start making parts for the steam engine either tonight or tommorow. Hopefully I can make and assemble the parts in CAD as fast as you are drawing them. I think this is going to be a lot of fun. I will keep my skype open (username andrewbuck40) and if you want to chat about any of this sometime, give me a ring. -[[User:Andrew Buck|Andrew Buck]] 13:33, 26 May 2011 (PDT)

== Incorrect Dimension for Valve ==

I was putting together the CAD model of the valve and I noticed a mistake in the stated dimensions for the 'valve head' (see [[Steam Engine Build/Valve]]). You list D3 as being 2.4 inches and D4 as being 0.8 with a 0.4 inch horizontal distance between them. However, using those dimensions you do not arrive at a 45 degree bevel. If you start with a 0.8 inch valve opening and then extrude it out on a 45 degree bevel for 0.4 inches, the radius increases by 0.4, meaning the diameter increases by 0.8. So D3 should be 1.6, rather than 2.4 like it is stated. I think this is the way the mistake should be resolved as the valve seat thickness of 0.4 and the 0.8 for the opening diameter sound like the figures you wanted so they are the ones I think you want unchanged. Let me know for sure if this should be how the matter is resolved and I will update the CAD model accordingly. -[[User:Andrew Buck|Andrew Buck]] 10:12, 27 May 2011 (PDT)

nice work on the build instructions. looks really good. --[[User:Dorkmo|Dorkmo]] 20:19, 5 June 2011 (PDT)

Re switching to Zn Br, I woudl not advocate switching just yet because while I am personally pretty sure, there shoudl be some hysteresis when it comes to switching the actual project focus. After I learn more I think I probably will recommend switching. There are still some issues, mainly whether the bromine resistant plastics are patented, and the vapor pressure of bromine (if it is above atmospheric that could be a real safety issue) that I need to check, and also to do the financial calculations to compare LA, NiFe and Zn Br to determine roughly how much they are really worth quantitatively. [[User:Gregortheinventor|Gregor]] 16:37, 25 June 2011 (PDT)

Yes, I may do that at some point, but I was sort of waiting until we had better wiki tools like the ones I did research on and posted about in the forum, so it won't take forever. [[User:Gregortheinventor|Gregor]] 09:01, 13 July 2011 (PDT)

== RE: Hierarchy structure ==

I do believe you're right in using a separate navigation system for the subpages of each GVCS tool, but I think the ToolTemplate should still be at the top of every page so as to give an easy way to jump between larger sections. The way I see it, from any page, one should be able to trace back all the way (i.e. breadcrumb) but with the added functionality of jumping to other sibling sections (i.e. from [[LifeTrac/Manufacturing Instructions/Assembly/Frame]] to [[LifeTrac/User's Manual]]

I'm all for each GVCS tool fabricator organizing his or her respective nav system, we just need a way for people to be able to see where they are and where they want to go at any time more easily. I think having ToolTemplate over a GVCS tool-specific navbar is the best way to cover all our bases. [[User:Ryan Lutz|Ryan Lutz]] 04:41, 26 July 2011 (CEST)

== Missing soil pulverizor for CEB press flowchart ==

Hey there. I thought I'd point out something I noticed in documentation. In this diagram we have soil that points into the CEB press, but it also looks like the soil pulverizer and tractor are dependencies for this to work. If you want to give me the file you used to generate the image I can update it for you if you think this is correct.

http://opensourceecology.org/wiki/File:4b-Constructioneco.png#filelinks

As an idea should we also generally provide the source files used to generate any images like flow charts for future modification? -[[User:Andrew_Graham]] 21:14, 21 February 2014‎

Year-End Report Goals for 2013-2014

2014-01-23T21:45:38Z

Mjn: /* Stabilize Organization */

=Stabilize Organization=

We have grown rapidly since our emergence to the world stage in 2011. We went through significant growing pains in 2012. Our main goal for this year is to stabilize the organization. This means recruiting a solid executive team and attaining the structure that qualifies us for multi-million dollar funding in 2014. We are demonstrating how our techniques will be used in practice at Factor e Farm in the Kansas City area, and we are setting up a design branch for OSE in New York City. We aim to develop standards for OSE Chapters worldwide.

=Develop Open Source Hardware Documentation Standards=

We are pioneers of open source economic development within the open source hardware community. We intend to develop a collaborative platform where both OSE and other groups are encourage to contribute to a common pool of human knowledge. This begins with an Open Source Hardware Development Platform to collect open source know-how from key stakeholders in the open source hardware community. This allows the whole community to build on prior work, accelerating innovation, and realizing the promise of open source economic development.

=Streamline Open Source Hardware Development Process=

Along with the development of documentation standards, we will also streamline our process for designing and developing Global Village Construction Set machines. We are defining new standards of Collaborative Design and Collaborative Production. By defining specific techniques for achieving rapid, collaborative development - we aim to scale this process within our own organization. We are also developing these techniques such that others can use them and build upon them - to accelerate collaborative innovation. We are creating a generalized methodology for open, collaborative hardware development - to transition the world to the efficient economy.

=Accelerate Machine Prototyping=

We have pioneered efficient methods of collaborative production. We have developed methods of building complex machines in one day. We are developing Documentation and Development standards for open hardware. Our next milestone is to demonstrate that we can attain 4-6 machine builds per month - while attaining high quality control standards and complete documentation. If we can attain this, we will complete the entire set of 50 GVCS tools by the end of 2015.

Talk:Archived Katie Log July 2013

2013-08-04T19:16:06Z

Mjn: Created page with "Why are there so many links to locked documents, Katie? OSE was started with a policy of openness and transparency. Seems a shame to change that now. I requested some access..."

Why are there so many links to locked documents, Katie? OSE was started with a policy of openness and transparency. Seems a shame to change that now.
I requested some access to documents that were of interest to me. - @mjn

OSLoom

2013-05-29T13:33:45Z

Mjn: Added project status update.

http://www.osloom.org/

Excerpt from OSLOOM News Letter v.02: [http://osloom.us5.list-manage.com/track/click?u=cc90c6aa076b0d85f68d2b30d&id=7eb0757858&e=6894d4ac46]

Happy Summer everyone! The really good news is that despite the lack of updates enormous progress has been made all thanks to the help of Nathan Clark our new local mechanical engineer and Chris Yanc our software developer. The 64 prototype (photos to follow) actually wove for the first time at Mini Maker Faire Cleveland. Unfortunately, the design of the heddle hooks snagged with each other and ended up being a bit imprecise so it wove a good mess. We already redesigned the heddle holders and have to redesign the heddles next to make the 64 thread successfully weave a bit better. A special shout out to Steve Otlowski (one of the awesome folks we met at the faire) who gave us some wonderful ideas to try on the heddle redesign. We have to fine tune the lifting mech, but all the commands get sent via software to the Arduino and the Centipede shield.

Crash Course in Steam

2013-05-23T17:06:32Z

Mjn:

{{Category=Steam Engine}}

==Tutorial==
See Spirax Scarco Steam Engineering Tutorial. [http://www.spiraxsarco.com/resources/steam-engineering-tutorials.asp]

==Basics==
Pressure = force per area.

Work = force times distance.

Power = work per time.

These three get you the power output of a steam engine. The distance in a steam engine is the length of the stroke. The force is the pressure times cylinder area.

Work is energy.

Solar power is 1 kW per meter squared.

Study the enthalpy of water, heat of fusion of water, and enthalpy of steam. Then tell me how much energy is required to convert water to steam at a certain temperature and pressure.

Then note that the RATE is what matters. Rate is power, or energy over time.

Choose your units, and then you can tell me:

# How much steam can be generated from a given energy.
# How much time it will take to do #1 if you know the rate of energy input (power input)
# How much solar steam you should generate from a certain rate of solar power input
# How much power is obtained from the steam you generate when running through the engine.

Ie, you're now able to tell me how much power you will get from a given heat input. There's the ideal value - and the real value.

If you can do all of the above, then you know more than 99% of people who call themselves steam experts.

Spend a few hours on the above, and you will have steam literacy, and you will get excited about your ability to make theoretical calculations plus the encouraging results that these calculations enable you to make.

This concludes a crash course in steam. Let me know if this is at your level, or what else you need to know to perfect your ability to make steam calculations.

==Discussions==
* http://openfarmtech.org/forum/discussion/85/crash-course-in-steam

[[Category:Crash Course]][[Category:Steam Engine]]

Crash Course in Steam

2013-05-23T17:05:58Z

Mjn:

{{Category=Steam Engine}}

==Tutorial==
See [http://www.spiraxsarco.com/resources/steam-engineering-tutorials.asp]

==Basics==
Pressure = force per area.

Work = force times distance.

Power = work per time.

These three get you the power output of a steam engine. The distance in a steam engine is the length of the stroke. The force is the pressure times cylinder area.

Work is energy.

Solar power is 1 kW per meter squared.

Study the enthalpy of water, heat of fusion of water, and enthalpy of steam. Then tell me how much energy is required to convert water to steam at a certain temperature and pressure.

Then note that the RATE is what matters. Rate is power, or energy over time.

Choose your units, and then you can tell me:

# How much steam can be generated from a given energy.
# How much time it will take to do #1 if you know the rate of energy input (power input)
# How much solar steam you should generate from a certain rate of solar power input
# How much power is obtained from the steam you generate when running through the engine.

Ie, you're now able to tell me how much power you will get from a given heat input. There's the ideal value - and the real value.

If you can do all of the above, then you know more than 99% of people who call themselves steam experts.

Spend a few hours on the above, and you will have steam literacy, and you will get excited about your ability to make theoretical calculations plus the encouraging results that these calculations enable you to make.

This concludes a crash course in steam. Let me know if this is at your level, or what else you need to know to perfect your ability to make steam calculations.

==Discussions==
* http://openfarmtech.org/forum/discussion/85/crash-course-in-steam

[[Category:Crash Course]][[Category:Steam Engine]]

Steam engine piston rings

2013-05-10T18:23:33Z

Mjn:

{{Category=Steam Engine}}

=General=

Pistons are describe in detail at http://en.wikipedia.org/wiki/Piston. The seal against the cylinder wall is formed by one or more piston rings.

Piston rings need to be cut so that they can slide over the piston into a machined groove. Cast iron rings are brittle, so care must be taken when fitting them. Cuts come in several types:

* Step Cut - common for noncritical sealing applications
* Butt Cut - common where high leakage rates are permitted
* Hook Cut - used in transmissions (etc) where oil passage may be needed.
* Angle Cut - used in rotating seals. Restricts bypass in the joint.
* Angle Step - injection moulding.
* Step Seal - a step cut with in inner seal.
* Two Ring Set - butt cut inner and a step but outer ring. Good for high temps and high pressure seals.
* Three Ring Set - 1 butt cut inner and two butt cut outers (staggered).
* Locking Ring Set - two rings with a locking element at the joints.

[[Image:Piston-Ring-Cuts.png]]

Other features of piston rings include:

* Chamfer
* Radius
* Scraper
* Vent
* Groove
* Bronze Insert
* Taper

Cast iron rings are used because they are low-friction and resist wear. The mechanical structure of cast iron produces consistent pressure against the bore (cylinder walls).

=Manufacturing Description=

At Federal-Mogul grey iron piston rings are cast as individual rings in a noncircular shape; there are other ring manufacturers who cut the individual rings from pots or cuffs. The rings are generally machined to the required shape by means of double cam turning, a process in which the ring blank, already axially ground, is copy turned simultaneously on the inside and outside diameters. After a segment equivalent to the free gap is cut from the ring it assumes the free shape that will give it the required radial pressure distribution when fitted into the cylinder. Once inside the cylinder the ring is completely light tight on its outside diameter and exerts the predefined radial pressure against the cylinder wall.

Besides using double cam turning, ring blanks can also be shaped by machining the inside and outside diameters separately. This involves cam turning the outside diameter of the noncircular blank and machining the inside diameter with the ring in the compressed state. The gap is cut out in a step between O.D. and I.D. machining. Heat forming as a means of shaping piston rings should be mentioned to complete the range of options, but this process is seldom used.

Steel piston rings are made from a profiled wire. The rings are first coiled into a circular shape and then the gap is cut out. The necessary shape is obtained using a heat treatment process in which the rings are mounted onto an arbor appropriately designed to impart the required radial pressure distribution.

Profiling of the running faces of taper faced, Napier and slotted oil rings is carried out, depending on the ring design, on automatic O.D. lathes or profile grinding machines using special profile cutting tools before or after coating.

=ISO Standards for Piston Rings=
''From Federal Mogul''

{| border="1" cellspacing="0" cellspacing="2"
! ISO Designation
! Edition
! Title
|-
| ISO 6621-1
| 11 / 2007
| Vocabulary
|-
| ISO 6621-2
| 11 / 2003
| Inspection measuring principles
|-
| ISO 6621-3
| 09 / 2000
| Material specifications
|-
| ISO 6621-4
| 10 / 2003
| General specifications
|-
| ISO 6621-5
| 12 / 2005
| Quality requirements
|-
| ISO 6622-1
| 12 / 2003
| Rectangular rings made of cast iron
|-
| ISO 6622-1
| 10 / 2003
| Rectangular rings made of steel
|-
| ISO 6623
| 02 / 2004
| Scraper rings made of cast iron
|-
| ISO 6624-1
| 08 / 2001
| Keystone rings made of cast iron
|-
| ISO 6624-2
| 10 / 2003
| Half keystone rings made of cast iron
|-
| ISO 6624-3
| 08 / 2001
| Keystone rings made of steel
|-
| ISO 6624-4
| 10 / 2003
| Half keystone rings made of steel
|-
| ISO 6625
| 12 / 1986
| Oil control rings
|-
| ISO 6626
| 07 / 1989
| Coil spring loaded oil control rings
|-
| ISO 6626-2
| 10 / 2004
| Coil spring loaded oil control rings of narrow width made of cast iron
|-
| ISO 6626-3
| neu
| Coil spring loaded oil control rings made of steel
|-
| ISO 6627
| 09 / 2000
| Expander / segment oil control rings
|-
|}

Talk:Car/Research Development

2013-04-12T12:54:23Z

Mjn: Created page with "Interesting to note that the Open Source Car project is over a year old at this point and this page hasn't had a single change to it in all that time. - mjn"

Interesting to note that the Open Source Car project is over a year old at this point and this page hasn't had a single change to it in all that time. - mjn

User talk:KhalidH

2013-01-07T02:31:11Z

Mjn: Created page with "Thanks for the updates, Khalid. mjn"

Thanks for the updates, Khalid. [[mjn]]

Technical Blogging Standards

2012-07-25T18:50:03Z

Mjn: Corrected simple spelling mistakes.

=Technical Blogging Standards=

'''The key deliverable that brought OSE to the world stage has been regular reporting of prototyping and progress results og GVCS development. The core deliverable of OSE is such documentation.''' Every blog showing a finished build + test cycle by active project developers should include several features listed here. The [[Soil Pulverizer Prototype II Blog Post]] is referenced in the descriptions below as a representative example of all the element.

#'''Status update and context regarding its importance''': ''We have finished the second prototype of the open source soil pulverizer – an important labor-saving device for soil-handling in CEB construction. It is useful because it combines digging-pulverizing-loading the CEB press in one device...''
#'''Fabrication video''' - This video should tell a '''story''' and be interesting and aesthetically appealing by including basic editing and a soundtrack. Fabrication footage should be taken at each single change of the fabrication process, so the viewer can see all the steps - which can be used to tell a story even without using a script. A script is useful for improving quality. A tripod or camera stand should be used to capture action footage. ''Example: notice how the Pulverizer video walks the viewer dynamically through all the steps and actions in an effort to keep the viewer's attention, while covering the process from start to finish.''
#'''Product CAD''' - Show CAD, models, animations, embed 3D manipulable files (STL, Sketchup, etc) into blog post, and link to the source files. ''Example: Note the CAD of the Pulverizer in qCAD with a direct link to the file repository.''
#'''Product Specifications''' - Shows specifications and performance data, focusing on [[OSE Specifications]]. ''Example: see the table of specifications shown.''
#'''Basic discussion of economic significance''' - discuss why the performance to cost ratio is high. ''Example: Note that the author points out a $200 dedicated parts cost for the soil pulverizer, or a fraction of what one would pay for a commercial counterpart.''
#'''Field Testing Video''' - It is useful to cap off a blog post with actual usage video. See video at end of post.

For other work product - such as construction or fabrication results, or even organizational development - blog posts can be written with the corresponding 6 pieces of content that are closest to the actual item - such as a video demonstration of a web platform instead of the ''Field Testing Video.''
[[Category:Documentation]]

Talk:Open source software for permaculture

2012-04-11T17:19:31Z

Mjn: Created page with "Have you ever had any experience with developing an expert system? There are three main parts to it: # Gathering the knowledge # Representing them as "rules" # Using them via a..."

Have you ever had any experience with developing an expert system? There are three main parts to it:

# Gathering the knowledge
# Representing them as "rules"
# Using them via an inference engine

Each of these requires special skills, which are (unfortunately) not all that common. It's a branch of AI that was quite popular back in the eighties, but has fallen by the wide side in favor of other, perhaps more interesting, projects.

Sometimes this can be done using a database, but that approach is better applied to static selection of records based on query criteria. It's very difficult to express complex statements in SQL such as "what kinds of co-plants should be considered to suppress competitive weeds and harmful insects when planting red cabbages in heavy clay soil in a temperate climate modified to create a micro-climate using Wall-O-Water devices?" Trust me, it's almost impossible.

This is why expert systems were developed, but they are not so easy to create, either. While it's fairly simple to write rules like:

1. Cabbage worms will harm cabbage plants
2. Garden slugs will harm cabbage plants
3. Ducks eat cabbage worms

What's hard is to understand how rules interact with each other. As an example, consider adding the following rule:

4. Ducks prefer to eat garden slugs.

So, if my cabbages are suffering from cabbage worms, will the ducks eat them? It's not clear from the rules. Debugging expert systems can be VERY difficult. Again, special skills are called for.

- Mark Norton

Car/Open Source

2012-03-01T13:50:24Z

Mjn: Created page with "I'd like to explore some of the ideas around open source design as it applies to hardware. Let me preface these remarks by saying that they are my point of view and opinion. Th..."

I'd like to explore some of the ideas around open source design as it applies to hardware. Let me preface these remarks by saying that they are my point of view and opinion.

The intent of open source is to make access to information unencumbered by legal restrictions and to be free of cost. When I open source something that I create, I want people to be able to take the plans and build them. It is a gift for the betterment of our global community.

The problem we run into is that society (in general, there are regional differences in law) is not set up to protect such a gift. If we do not protect our gifts to the world, we leave ourselves open to having them stolen - in the sense that they will no longer be freely available to other people subsequently. The two primary mechanisms used to prevent free distribution of design information are patents and copyright.

This problem was first encountered in the software world by a man named Richard Stallman (http://en.wikipedia.org/wiki/Stallman). Stallman (or rms as he is known in the software world) wanted to create a version of Unix (an early operating system) that he could give away for free. However, many of the basic concepts of Unix were tied down by copyrights (software patents came later). What he did was to re-engineer several key software tools from the ground up - with out using any of the commercially available software. These tools were to form the basis of the GNU operating environment (GNU stands for Gnu's Not Unix).

So, while he was able to create these new software applications that were free from previous restrictions, he encountered a problem. There was nothing to prevent someone from taking his work and filing a US Copyright on it and claim it as their own. Information in the public domain is free to be used by anyone - including someone who wants to file a patent or copyright on it. In 1989, rms developed a solution to this problem that he called the GNU General Public License or GPL.

The GPL has a very clever legal trick in it - one that was carefully reviewed by lawyers before it was released. It says that any GNU application is NOT in the public domain at all. In fact, all GNU applications are fully owned by the GNU Foundation. They own the intellectual property. Having established their ownership, the GNU Foundation proceeded to offer a use license to anyone who wanted to use their property free of charge, but subject to the terms spelled out in the license.

The GPL has two main provisions. All software distributions must include the source code and a copy of the license. Any changes must be distributed under the terms of the original license (this is the so-called viral aspect of the GPL). Finally, it must be distributed in either the original or derivative form for no money. Note that this final provision prevents anyone from making money off of a GPL protected application or design. RMS really didn't like software companies making money off of other people's ideas, hence this clause.

OSE's stance on these issues is (in part) described in the Open Source Ecology Paradigm (see http://opensourceecology.org/wiki/Open_Source_Ecology_Paradigm). In this document, Marcin declares that OSE is a distributive enterprise, working towards the end of economies based on artificial scarcity by making information resources transparent and freely available to all.

In Dec. of 2011, OSE released the Civilization Starter Kit DVD v0.01 (see http://opensourceecology.org/wiki/Civilization_Starter_Kit_DVD_v0.01). This DVD and the information included on it is distributed under the OSE License for Distributive Economics (see http://opensourceecology.org/wiki/License). This is the license that Marcin has chosen for GVCS products, which will presumably apply to the OSE Car and other products as they come along. It has the following provisions:

Based on Creative Commons Universal Public Domain Dedication
Ethical adherence to the OSE Paradigm
Intent to create a Distributive Enterprise

There are several problems with this as a license from a legal perspective but I don't think that's what Marcin had in mind. Rather, it is a declaration of a moral and ethical stance regarding word done by OSE and how it will be made available to the world. The main problem with this, as I see it, is that it doesn't prevent anyone from taking an OSE design, modifying it very slightly and filing for a patent on it. If granted, the patent holder could then enjoin OSE to cease distribution of "his" design.

An alternative approach, one that I favor, is the TAPR Open Source Hardware License (see http://www.tapr.org/OHL). Under the terms of the OSH (summary):

You may modify the documentation and make products based upon it.
You may use products for any legal purpose without limitation.
You may distribute unmodified documentation, but you must include the complete package as you received it.
You may distribute products you make to third parties.
You may distribute modified documentation or products based on it.
If you create a design that you want to license under the OHL, you should (provisions follow)
Any time the OHL requires you to make documentation available to others, you must include all the materials you received.

It specifically allows commercial products to be developed and sold without affecting the terms of the license.

Now let me say a few works about what this means for the OSE Car project. These are largely recommendations at this point, since neither Marcin nor OSE requires them.

Two main points:

A. Contributors to the OSE Car project should be prepared to assert that their work is original and not derived from older works that are protected by IP laws in any way.

B. The ownership of all work (drawings, designs, correspondence, assembly instructions, etc.) should be assigned to OSE so that it may grant such licenses it decides will further it's organization needs and ethics.

If WikiSpeed or Kinetic Vehicles decides to contribute earlier design work to be considered as the basis for an OSE Car design, they must be prepared to assert that the work is completely original and free of any IP restrictions, that they own the exclusive rights to it, and that they assign those rights in perpetuity to OSE.

One final word needs to be seed about COTS parts (Commercial, Off the Shelf). This is something that occasionally comes up in the software world, particularly around the use of databases. The OSE Car projects may choose to specify commonly available parts for inclusion in the design. I would recommend that such parts be either standardized elements (such as nuts and bolts) or specified as a generic part. The assembly instructions could require an oil pump such as the "Bosch Rexroth High Pressure Pump (HP008X)". The example mentioned (Rexroth HP Pump) is a proprietary part protected by several patents, but it's use in the OSE car is optional - any oil pump that meets the OSE Car requirement could be used.

This is actually an important consideration from an OSE perspective, since it is quite possible that (one day) OSE will describe how to make an oil pump using GVCS fabrication tools.

- Mark Norton

PS. Regarding my knowledge of open source licenses - I am the License Steward for the Kuali Foundation and I have contributed to license review and audits for the Sakai Foundation. While I am not a lawyer, I have read MANY variations on open source licenses and have a good understanding of how they are applied. I would urge OSE to have it's open source license policy reviewed by legal counsel.

PPS. The above explores intellectual property rights. Indemnification and liability protection is a whole other ball of wax.

Car/Correspondence

2012-02-29T13:05:17Z

Mjn: Bulk entry of email messages.

{{Category=Car}}

On Feb. 22, 2012, Marcin Jakubowski asked Mark Norton to facilitate the discussion around starting an OSE Car project and help with negotiations.

=Feb. 22, 2012=

I am working resolving some of the social aspects of the Car project. I'd like to communicated directly with Joe Justice. Do you have an email address for him?

- Mark

----

Jack:

It has very recently come to my attention that Joe Justice of WikiSpeed has expressed interest in working with OSE to produce an open source car design. You may recall Joe's TED talk on using Agile/SCRUM techniques to prototype a low cost car.

Frankly, this complicates things considerably. Joe is a strong leader and will have his own ideas on how this project should be managed. Also, while he has expressed interest, he hasn't put anywhere near the level of effort into participating that you have.

I have put together some of my views on this issue and posted it to the OSE Forum in http://forum.opensourceecology.org/discussion/657/2012-specs-for-open-source-car. I welcome your response there. Privately, I'd like to hear your thoughts on competition vs. cooperation. I think that if you want to pursue this as a competitive design effort, you'd have a good shot a winning - based our correspondence to date, the commitments you've made in your proposal, and your efforts to date.

There is, however, some attraction to a cooperative efforts. You'd be in a position to learn from what Joe accomplished in his earlier design efforts. Naturally, the reverse is true as well. A cooperative effort will be more difficult to manage, in my opinion, but those who participate may get more out of that approach. Kinentic Vehicles/Aerospace would still be in a good position to fabricate parts and assembly kits or whole cars at the conclusion of the design effort - if that is your motivation.

I welcome your input on this.

- Mark

----

good to meet you Mark. go right ahead, let's do awesome together.

Joe Justice

----

Hi Joe,

My name is Mark Norton and I am project leader with the Open Source Ecology project. As you know, we are trying to get an OSE Car project started and I understand that you've expressed interest in participating. I talked a bit with Khuong Dinh as well. Marcin has asked me to help coordinate the project kickoff and get things organized.

There are two main tasks facing us at this time: design criteria and structuring the design effort.

In order to establish reasonable expectations of the design and prototyping effort, I have started to collect a set of proposed design criteria. You can view an early draft of these as http://opensourceecology.org/wiki/Car/Design_Criteria. While OSE has high expectations for a very efficient car in the future, I've lowered the bar a bit for the first round of prototyping. My thought is that it will be difficult enough to design and built a truly open source car without worrying about advancing the state of the art as well. Please let me know what you think of these criteria. If there some that I am missing, please let me know.

The second has to do with structuring the early design effort. We could set this up as a design challenge and look for competitive proposals. Such competitions have been successful in other venues (X-Prize, etc.), but are wasteful when you look at the combined effort to reach the prototyping stage. A collaborative effort might be preferred, but OSE hasn't had much success with that approach to date. Awarding a project to an established expert and existing team has yielded better results in the past.

There is a question of who would lead a collaborative effort. You have demonstrated success in using Agile methods to design and build a car. However, Jack McCornack of Kinentic Vehicles has also demonstrated equally good results in leading a team to building a highly efficient car (the Mother Earth News MAX). If OSE determined that Jack was better suited to leading this project, would you be willing to participate under his direction? Jack, I have the same question for you - would you contribute under Joe's leadership? If leadership is not an issue, then we can proceed with the collaborative approach. If it is, then we will likely go down the competitive path.

Ultimately, what the world needs is a high quality, low cost, easy to build open source car. I think OSE has a framework in place that will foster the development of such a car. We also have the funds needed to support prototype development (within reason and the limits of the OSE budget).

I am open to all points of view and suggestions.

- Mark Norton

=Feb. 23, 2012=

sounds excellent. I'm a fan working under anyone (Jack is a great guy) or leading a group. The design_criteria you provided are a good start- they aren't exhaustive and I like that, they avoid being prescriptive and hit the most important points. I'd like to mention WIKISPEED may already have the car that meets this description, but it needs to be tested by OSE to verify fit or not with these Design Criteria, and then needs to be published so folks can start building it and enhancing the design. Also, we need a group to integrate power cubes into an engine module for testing (likely 2 cubes, stacked vertically if I understand the dimensions correctly).

Awesome,
Joe

----

I'd like to add Tom Griffing (product owner of the power cube) to this
discussion because he will be the key component to the integration
group.

Thanks! khuong

----

Hello all - Tom Griffing here.

I had a good discussion with Khoung last night about the car, power cubes and such - all quite interesting.

With the goal of having an OSE car by the year's end in mind, I think buying a Wikispeed car would be a huge jump toward the OSE goals.

From my conversation with Khoung, the power plant is an obstacle for the Wikispeed folk and they would like to lower its cost. From an OSE perspective, we would like a power plant that would serve other OSE machines (ie: Power Cube). In its current configuration, the Power Cube provides hydraulic fluid power for various uses, but has shortcomings for use in a car. We have discussed "enhancements" to the Power Cube to overcome these shortcomings.

I don't think hydraulic fluid power is the best means for delivering power for a car - mostly for its inefficiencies.

Probably the single largest consideration for the OSE cars is power delivery:

* Direct mechanical power would provide the quickest means of getting a working car

* Electrical power would provide greater utility and modularity

The Wikispeed vehicle could also provide a jumpstart by delivering either a working car or a platform for developing an electrically driven vehicle. If funds are available, we should consider both, as most of the cost of the Wikispeed vehicle is in their engine.

I look forward to this development.

Tom Griffing

----

Hi Mark,

Pretty cool. I got the word from Nikolay yesterday...

On Thu, 23 Feb 2012 00:29:58 +0100, Nikolay Georgiev wrote
> it seems that we will have the Awesome Team of Wikispeed joining in
>
> That's great news!
> http://opensourceecology.org/wiki/Team_Wikispeed
>
> Best,
> Nikolay
...and wrote back to him...

> Woohoo! It may be that my contribution to the OS Car project will only be
> the lighting of the fire under my betters.
I'll stay active. No matter which way the project goes (presuming it goes) the
car needs specifications to meet, or it will be difficult to tell if the
project succeeded.

After I've absorbed today's mail, I'll write a "reply all" to your message and
we'll see where I best fit in. I'll have to say that Joe's and Marcin's
management styles (and promotional styles) are better matched to each other
than mine is to theirs, but that doesn't necessarily mean better balanced;
perhaps some yin-and-yang is in order. I'll do more reading (including my X
Prize competitor notes) and get back to you.

Regards, Jack

=Feb. 24, 2012=

Tom, likely the best method to get started is to form a team around assembling a WIKISPEED car in it's current version, in order to understand it deeply. And then updating modules at a time to make it even more compatible with other OSE parts. Here is a list of key steps for assembly, and tools needed, as used by our Texas team currently:

lling chassis chassis receive in mail or cut and weld on location. cut and weld on location requires bandsaw set to cut square, jig plates (can be mailed or CNC'd locally), speed square and accurate 48" tape measure with 1/16th" or smaller tick marks. If made on site, chassis must then be drilled, requires centering punch, hammer, centering 3/8ths drill bit and drill (drill press or coal drill preferred).

suspension module receive in mail or CNC on location.

Assemble

compare to photos for test. NEED TO MAKE PHOTO OR RENDER

bolt on to car recieve grade 8, 3/8" bolts, washers, and lock nuts 9/16ths wrench and socket with ratchet required

compare to photos for test. NEED TO MAKE PHOTO OR RENDER

wheels and tires receive wheels with tires and lungnuts in mail (tirerack)

jack up chassis. set up car jack put wood block on car jack to avoid scratching frame.

bolt on wheels Lug wrench required

braking chassis pedal plate receive pedal plate in mail or CNC on location.

bolt pedal plate onto chassis recieve grade 8, 3/8" bolts, washers, and lock nuts

receive brake pedal in mail (willwood)

receive brake master cylinder in mail (willwood)

receive accelerator pedal in mail.

bolt pedals and master cylinder to pre-drilled holes on pedal plate. recieve grade 8, 1/4" bolts, washers, and lock nuts

Brake lines receive brake lines in the mail, pre-flared or flare on location if flaring on location, requires bubble flare tool, metric AND SAE brake line fittings.

bend lines to match diagram NEED TO MAKE DIAGRAM

receive brake line clips in the mail

attach clips to existing holes on pedal plate and chassis according to diagram NEED TO MAKE DIAGRAM NEED TO CAD BRAKE LINE CLIP LOCATIONS. NEED TO PICK BRAKE LINE CLIP SUPPLIER AND TEST.

screw on brake line fittings line/flare wrench required, SAE and Metric

Brake Fluid buy, locally, DOT3 brake fluid. CAUTIION: Brake fluid is one of the few seriously toxic fluids we deal with. Be careful, goggles and latex gloves are suggested.

fill brake fluid resevoir

bleed brakes. Requires brake bleeder kit or modified empty water bottle or 3/16th surgical tube.

Verify brake pressure Step on brake and verify rock-hard pedal before pedal is fully depressed. Have friends heave on the car and verify car slides before wheels rotate.

steering chassis Steering rack receive steering rack in the mail.

receive steering rack mounts in the mail or make locally with CNC.

bolt steering rack mounts to pedal plate. recieve grade 8, 3/8" bolts, washers, and lock nuts

bolt steering rack to steering rack mounts recieve grade 8, 3/8" bolts, washers, and lock nuts

receive tie rod extendors in the mail or tap locally from hexagonal bar stock. if tapping locally, need metric tap, I believe M14x1.5.

receive tie rods in the mail.

thread tie rods onto tie rod extendors.

thread tie rod extendors onto steering rack.

bolt tie rods to steering knuckles.

verify can heave on front wheel by hand and one wheel does not move at all without the opposite wheel moving.

Steering column. receive steering column in the mail.

receive interior module in mail or cut and weld locally. same tools required as making a chassis. STANDARDIZE STEERING COLUMN MOUNT IN INTERIOR MODULE

set interior module in chassis, and bolt in. recieve grade 8, 3/8" bolts, washers, and lock nuts

receive steering wheel in the mail. TEST OUR OWN CNC'D STEERING WHEEL.

slide steering column onto steering rack, tighten pinch bolt. metric socket set required.

attach steering column to interior module.

Bolt steering wheel to steering rack SAE socket set required

verify steering wheel turns both wheels without wobbling.

align wheels (professional alignment or local with speed square, plumb bob, and level).

body on body top mount frame receive body top mount frame in the mail

receive button-head hex bolts in mail.

bolt body top mount frame to car

receive body by freight.

set body onto body top mount frame.

bolt body on to body top mount frame with button-hread hex bolts.

push and shake body, verify does not flex, wobble, or make noise under force that would dent a fender on a new car.

dust and polish car body.

- Joe

=Feb. 26, 2012=

Hello gents,

I've been plugging away on specs, and on integrating the PowerCube to a
lightweight automobile. I just now added my New Improved Specifications
(Mark's Car/Design_Criteria page with my own enhancements added) to my
proposal page at...

http://opensourceecology.org/wiki/Car/Kinentic_Vehicles_Proposal

...and earlier in the week I used the 'discussion' page of that proposal for
my research and conclusions re PowerCube in the OS Car (executive summary:
It's a good idea that needs developing, 'cause with the current pump and
off-the-shelf hydraulic motors, the engine-to-wheel power transmission
efficiency will be a smidge under 50%) but I'm quite bullish on the concept,
and though I don't think a PowerCube should be planned for the 2012 first
prototype, I do think the prototype should be built to accommodate PowerCube
drive with minimum modification. Success may be as close as a variable
displacement pump and a bigger engine. I'm thinking Metro motor because
they're everywhere and the bodies are rusted out, and though it would make a
PowerCube you'd need two guys to lift, it provides a healthy fuel efficient 50
horses and there may be times a more powerful PowerCube option would be useful
for the heavy equipment components of the GVCS 50...sorry, I'm drifting. Point
is, while OS Car Prototype #1 is likely to need a conventional automotive
powerplant (at least on the budget and schedule I've proposed) we should
design it to fit a PowerCube later, when the conversion is ready.

Or we could make a prototype with a PowerCube just to show it can be done,
though it'd maybe have a top speed of 50 mph and take a minute-plus to get there.

Joe mentioned...

> I'd like to mention WIKISPEED may already have the car that meets this
description

...and if so that'd sure be a time saver. Joe, if you'll send me a link to
photos or specs of it, I swear I'll keep it secret until you're ready to
reveal it. Man, you've got me curious.

I'm hoping for an answer mid-day Monday re if Mother Earth News will let me
turn the MAX design over to OSE. Hey, no 'may' about it, MAX -does- already
meet the description, but it's not fully mine to give away. However MEN's main
goal is to promote their magazine, and a little blurb on the intro to the
Final Release saying something like "the first prototype was built on behalf
of Mother Earth News, motherearthnews.com" that would probably satisfy them.
Bot please keep this to yourselves; there's one guy to go and if he says,
"Naaa" I don't want to have jumped the gun.

However there are a few things about MAX that are not ideal. If that was a
path OSE wanted to take, I'd think converting it to gasoline (yep, a Metro
engine) would be a good move. For one thing, the Kubota diesel costs over four
grand and with the Metro motor the total parts-and-materials bill drops to
around $7000. For another, not every state will go for that Kubota engine in a
newly built car.

Also, in 3+ years and 20,000+ miles of driving that thing, I've become
convinced that more creature comforts are in order. I listed them in my
proposal, but the main one is an enclosed cabin. MAX is not a suitable car for
anybody but high mileage zealots until it gets a top and side windows. Not too
hard to do, I don't think--it'd be a piece of cake for Joe and his crew--but I
do think a roof is needed to make that car acceptable to the general public.

I've concluded that the three wheeler (even a tadpole, and even a tilter) is
so poorly suited to the PowerCube that it's not worth bothering with. Four
wheels are needed for space, and because the PowerCube's width and high CG
would increase rollover risk for a trike.

As far as working under Joe goes, my problem is he has 40 folks already and I
don't see where I have skills that they don't. I'd love to if I could help,
but I don't really know what I have to bring to the table. I'm a decent
aerodynamicist if you don't need higher tech than about 1950, but if the goal
is to keep it slippery and slow (like under 300 mph), most of subsonic
aerodynamics was well understood by then. But if I could be useful, that'd be
neat. Joe is clearly a strong leader and I know I'd learn a lot from the
experience.

As far as vise-versa goes, I've been following WikiSpeed since we were both
xprizing, and the speed with which the black body was built is amazing. The
carbon fiber may be better suited to a $25,000 car than a $7000 or $8000 car,
but at $12,000 it might be just the ticket. The same techniques could be used
to make patterns for conventionally molded FRP parts, and a somewhat simpler
design could be made with mostly sheetmetal and a few compound curve bits
(fenders, nose, leading edge of the roof) to tie them together. So I don't
think Joe would be working under me as such, I think it's be more a matter of
giving him a portion of the project and turning him loose.

I've built a lot of bolt-and-bond aluminum structures (aircraft for the most
part) and it has its advantages in stiffness to weigh ratio (or I wouldn't
have used it) but for a GVCS car, I favor the usual GVCS materials and
techniques of mild steel and welding. It's rugged, it's cheap, and when GVCS
has its induction furnace and OSE welder and plasma cutter going, welded steel
is going to be the predominant fabrication process (as I think it is already).

Yawn. It's 1:20 AM in Yuma. Nighty night, all.

Regards, Jack

PS--Joe, I think the wikispeed web site has been down for a couple days, or
maybe there's some glitch on my end, but I just gave it a try and it popped
up...and now it's 1:30 Double-yawn. J
PPS--Tom, can you point me to the best bang-per-buck brand of small variable
displacement hydraulic pumps?

----

Hello;

We have had our focus on air-cooled gasoline to date, though there are some diesel
engines in use as well. The ultimate goal is to use renewable fuel sources and to this
end, the OSE steam engine is being developed.

Meanwhile, we need to get the other projects going, so we use what is available and
add flexibility for switching power plants later - thus the power cube. In it's prior
implementations, it has provided hydraulic fluid power. While this does lend some
flexibility, it also has limitations (like poor efficiency).

Lately, we have discussed splitting the Power Cube into two components: the "Engine"
component and the "Driven" component (for lack of better terms). The engine component
would have the engine, battery, fuel tank and deliver power to the driven component using
a "quick connect" shaft. The driven component would be whatever the engine drives:
Hydraulic pump, electric generator, air blower, water pump, direct kinetic drive, etc. This adds
flexibility and also the opportunity for better efficiency. Of course, efficiency is a key concern
as it is a focal point for cars.

This brings us to the question of the best power delivery for the OSE car? Here are my
thoughts on the following two options:

* Direct kinetic drive - requires clutch, transmission, shafts. Fixed configuration. Fast implementation.
* Electric generator - requires control/power electronics, cables, electric motors. Needs R&D time.

The first option is by far the easiest to implement (buy or build a WikiSpeed car), add roof
and other creature comforts. This would be fairly rigid implementation - for example: it would
be a major task to switch from an engine with a vertical shaft to one with a horizontal shaft.

In my opinion, electric power is by far more flexible but would require much more R&D
time, but could be accelerated by using available designs for electric / hybrid autos. It
would also lend the flexibility of adding a second power reserve in the form of batteries.
In fact, the best route would be a batter driven car, possibly supplemented by a fuel driven
engine. Electricity is generated much more efficiently on large-scale, then charge batteries.
Use batteries first, then the engine only after batteries are exhausted.

Run engine at most efficient RPM for power generation. When running, the engine can
provide some power to the car and some to the batteries. It will likely generate more power
than necessary for charging batteries and some type of governor may be necessary.

I think either power delivery option would work, or perhaps we should explore (if funds are available).

The project could be greatly accelerated by distributing the design & implementation tasks. Many of
these will still be necessary even if buying a WikiSpeed car:

* Frame
* Wheels
* Powertrain
* Exterior
* Interior
* Controls
* Part ordering
* Compliance / Standards

This would enable members to work in areas of their expertise.

To get this project going, should define:

* Timeline
* Funding
* Power Delivery options
* Fabrication Location(s)

- Jack

----

We need to get organized and get going.

To answer your inquiry: We have bought most of our hydraulic parts from SurplusCenter.com
but lately, I have bought some from a local store (Stuart Hose & Pipe) which has better prices.
Note: I haven't bought any variable displacement pumps, so that may not help at all.

Tom Griffing

----

On Sun, 26 Feb 2012 09:17:58 -0500, Mark J. Norton wrote

Sorry I missed your call last night, Jack. I can only plead that I
was away at a party with my wife having a good time.

- Mark

----

Hi Mark,

An excellent alternative to sitting by the phone.

I'll give you another try in about an hour.

Regards, Jack

----

Hi Tom (and guys),

> With the goal of having an OSE car by the year's end in mind, I
> think buying a Wikispeed car would be a huge jump toward the OSE goals.
I'm not up to date on the Wikispeed proposal, mostly...is this Wikispeed car
the SGT01, or another car design?

> Probably the single largest consideration for the OSE cars is power delivery
I think it's a major consideration, but since the eventual power source goal
is established and we seem to be in agreement that it's unlikely to be ready
for the first prototype, flexibility is the key -- that is, we shouldn't let
the first prototype lock the design into any specific method of power delivery.

> Direct mechanical power would provide the quickest means of getting
> a working car
That's my intent, though I didn't specify delivery because there's the hope of
a late breaking PowerCube advancement, and I'd like to keep the option of
switching to it if time allows (e.g. a suitable PowerCube in October).

Direct mechanical is sure the quickest and easiest for a car. Diesel-Electric
is well suited to trains, where the enormous weight that has to be accelerated
makes slipping the clutch impractical. Diesel trains use electrical power
delivery because it's lighter, cheaper, and more reliable than a 60 speed
transmission and a clutch the size of a satellite dish.

Jack

=Feb. 27, 2012=

Gentlemen,

Per Tom, Jack and Joe's points w.r.t using the current wikispeed car
as prototype 1 and then improving on it, I'm 100% in favor of that.
After all, that's what being modular is all about(the current asset is
the research and design that Joe and his team has already done, so
lets build around that). once we have an OSE/wikispeed team, we can
then plug and chug the most efficient and modular engine as we dev
prototype 2.

To address Tom's point of fabrication location and Mark's point of
leadership, I'm in favor of working around Joe's team and under his
leadership out in WA(integrating our concerns/requirements/designs
into their backlogs and sprinting from that). It's amazing to see how
organized and collaborative they are. This will also shape the
timeline that Tom mentioned below.

As for the finance, I think Marcin or Mark will have the answers.

khuong

----

I admit I was afraid something like this might happen. After a series of emails that suggested we might be taking a collaborative approach, you move immediately to suggest that the design be based on your previous work. I would suggest, Khuong, that this is not a collaborative approach. Have you looked at Jack's design in any kind of detail? Why would you assume that the WikiSpeed design is better?

I've looked at the photos on wikispeed.com. I don't see any links to detailed design specs. I do note that the prototype is a single person vehicle - which doesn't meet the initial OSE requirements.

Khuong - if you want this to be a competitive bid process, then we should proceed down that path. It means that Team WikiSpeed will be required to submit a formal proposal with enough detail to satisfy us (OSE) that the result will meet OSE needs and requirements. The proposal should include development cost estimates.

If you'd rather approach this in a collaborative manner, then the first thing to do (beyond organizing the team, perhaps) is to examine all existing designs and evaluate what features will best suit an OSE design. If the team - as a whole - decides that one existing design is close enough that it can be used as base, that's fine, but don't try to do it by fiat. I'd like to see documented REASONS why one design is better than another and HOW it meets OSE requirements.

Joe: Jack and the others have a lot of respect for your previous accomplishments in leading projects like this one. As near as I can tell, they are willing to accept you as the leader of the OSE Car project (subject to approval by Marcin), provided you handle it in a fair and inclusive manner. As such, it's time to step up to the plate and exert some leadership. If you want to be involved, now is a very good time to step in and help us get this organized.

- Mark Norton

----

On Mon, Feb 27, 2012 at 6:43 AM, Mark J. Norton <markjnorton@earthlink.net> wrote:

> I admit I was afraid something like this might happen. After a series of emails that suggested we might be taking a collaborative approach, you move immediately to suggest that the design be based on your previous work. I would suggest, Khuong, that this is not a collaborative approach. Have you looked at Jack's design in any kind of detail? Why would you assume that the WikiSpeed design is better?

> I've looked at the photos on wikispeed.com. I don't see any links to detailed design specs. I do note that the prototype is a single person vehicle - which doesn't meet the initial OSE requirements.

The WIKISPEED car has 4 seat and 2 seat interiors, we campaigned in the 4 seat, mainstream class in the X Prize. Where do you see a single person vehicle? It may help spending some time on www.youtube.com/WIKISPEED, www.facebook.com/WIKISPEED, or www.twitter.com/WIKISPEED, or consuming the links Marcin has posted about WIKISPEED on OSE: http://opensourceecology.org/wiki/Lessons_Learned

> Khuong - if you want this to be a competitive bid process, then we should proceed down that path. It means that Team WikiSpeed will be required to submit a formal proposal with enough detail to satisfy us (OSE) that the result will meet OSE needs and requirements. The proposal should include development cost estimates.

> If you'd rather approach this in a collaborative manner, then the first thing to do (beyond organizing the team, perhaps) is to examine all existing designs and evaluate what features will best suit an OSE design. If the team - as a whole - decides that one existing design is close enough that it can be used as base, that's fine, but don't try to do it by fiat. I'd like to see documented REASONS why one design is better than another and HOW it meets OSE requirements.

Joe: Jack and the others have a lot of respect for your previous accomplishments in leading projects like this one. As near as I can tell, they are willing to accept you as the leader of the OSE Car project (subject to approval by Marcin), provided you handle it in a fair and inclusive manner. As such, it's time to step up to the plate and exert some leadership. If you want to be involved, now is a very good time to step in and help us get this organized.

I'm looking for a member or the OSE to go through WIKISPEED CAD and publish it on OSE, and then take tasks that we collaboratively determine as gaps between the SGT01 (current WIKISPEED car) and the OSE open source car, and pair with team WIKISPEED members to execute them (bend roll bars, for example). Then, that OSE group would build an example, using only the GVCS, of the OSE car from those CADs they've published, film and photo the progress, and use that to publish a "how to" guide.

As soon as an OSE member says "hey, that's me! I'll go through the CAD, review with Joe, and publish it on OSE!" and signs a team WIKISPEED member form so they have full access, then we can get started.

Let's do awesome together,
-Joe

=Feb. 28, 2012=

With Mark's permission, I've added Matt Maier to the cc line. He's a sharp
cookie and he's been keeping me in line when I go adrift on the OS Car specs
(or even on my own proposal).

Also to quote from Matt's reply, "I think at the moment I'm the only OSE guy
who also belongs to Wikispeed, so I can help bridge between the two groups."

Mark, if you click the video on the
http://www.wikispeed.com/p/wikispeed-fuel-efficient-cars page, at 6:27 there's
a quick in-cockpit clip from a camera mounted on the passenger side of the
dash and you can see it has two seats. However, it's not particularly
noticeable in the rest of the video because the driver masks the passenger's seat.

I think there'd be comfort issues with two people aboard as it sits, and Joe,
if Wikispeed wants to keep that narrow windshield you're probably going to
have to get creative. Back in Ye Olde Days, sports racers had to have two
seats, and in Ye Oldest Olde Days, when sports racers were front engined, that
was easy because the drive shaft went between the seats. But after mid-engine
racers became the rage, the seats got bumped together, and historic photos of
victory laps show passengers who are either skinny girls or contortionists.

The trouble is, shoulders are wider than hips, and two bucket seats next to
each other look way cool at the car shows, and are very comfortable when
driving solo, and reduce frontal area and drag because the "greenhouse" (the
cockpit above the doorline) can be so narrow, but the driver's right and
passenger's left shoulders and arms attempt to occupy the same space and they
are horribly uncomfortable for two people on an extended drive.

Joe, since the Wikispeed can have a 4 seat interior, you might try moving the
passenger's seat back 8 inches or so and put the passenger's left shoulder
behind the driver's right. This staggered seating has worked for some other
exotic two-seaters, giving reasonable comfort without loosing the
lean-and-mean modern racecar look.

I may be going overboard with the comfort and practicality specs in my own
proposal (at http://opensourceecology.org/wiki/Car/Kinentic_Vehicles_Proposal
), but I've spent over 400 hours in MAX, and I've found that comfort matters,
and day-to-day practicality matters, and my specification list has had some
additions in the last two years and they comes mostly from experience.

Re a competitive bid process, I've got my bid in, and if Joe cares to he can
beat it. I'm comfortable with my quote and not interested in getting into a
reverse auction. My concept of a best OS Car first prototype hasn't changed
much since Marcin an I talked two winters ago: steel frame, mid engine, Metro
power, and forward-compatible to PowerCube. Okay, the last couple winters in
MAX have convinced me the OS Car needs a top, but that's about it.

I favor a new OS Car specific design, but about a month ago, someone on the
forum asked about MAX as an OS Car possibility (since MAX meets the original
OS Car design criteria and has shown a measure of reliability) and I replied
(to paraphrase myself) "No, that's Mother Earth New's, I'll have to start with
a clean slate," but I asked MEN-folk anyway. Well apparently Mother Earth News
doesn't have an objection to MAX carrying on under different management. All
MEN is concerned about is that MAX doesn't go to another magazine.

I have the basic parts list to convert MAX to MAXine (MAX with a Metro
automotive gasoline engine instead of the Kubota industrial diesel...but it's
your choice) and other than the cockpit enclosure specification of line 6.6
(which I added to the original requirements) MAX trounces the Design Criteria.
It gets better than 100 mpg on the highway and has a top speed (with its
current governor setting) of 91 mph, and those aren't calculated figures,
they're measured figures, they're confirmed by GPS and witnesses, and MAX will
perform to spec on demand, any day of the week.

So if designating an existing car as the OS Car is what Marcin and OSE want,
my hat is in the ring. That's probably the quickest way to get the first
prototype into the GVCS, and you've two options to choose from. One way Marcin
could choose would be for Joe and me to drive our cars to a mid-point between
Seattle and Cave Junction, verify our performance with sealed tanks, GPS and
video, and have Marcin fly out and decide in person. Portland International
Airport would be a terrific meeting place; Joe and I could meet Marcin at PDX
Arrivals and we could each take Marcin on rides.

Joe, is the Wikispeed prototype licensed and legal? Is it up to a couple
hundred mile road trip? It would be good publicity for OSE, Wikispeed, and
Kinetic Vehicles, and I'm sure Marcin would have the courtesy to give the car
not selected some "It was a difficult choice..." quotes for our web sites and
magazines.

>From Joe's response to Mark's message:

> I'm looking for a member or the OSE to go through WIKISPEED CAD and publish
> it on OSE, and then take tasks that we collaboratively determine as gaps
> between the SGT01 (current WIKISPEED car) and the OSE open source
> car, and pair with team WIKISPEED members to execute them (bend roll
> bars, for example).
Fine by me. I have a roll bar bender and I'm delighted to find there's a place
on the Awesome Wikispeed Team where I can be of service.

> Then, that OSE group would build an example,
> using only the GVCS, of the OSE car from those CADs they've
> published, film and photo the progress, and use that to publish a
> "how to" guide.
Sounds easy.

> As soon as an OSE member says "hey, that's me! I'll go through the
> CAD, review with Joe, and publish it on OSE!" and signs a team
> WIKISPEED member form so they have full access, then we can get started.
Matt, you're already a Wikispeed member, would this be down your alley?

> Let's do awesome together,
> -Joe

If this is the approach Marcin selects, I'll be happy to pitch in. How do I
become a member? The web site isn't clear, all I got was "New members are
invited and will be paired with an experienced professional." I may not be
awesome, but I can bend tubes on my own and can verify test data if I'm
paired with an experienced professional.

-Jack

----

On 2/27/2012 6:37 PM, Joe Justice wrote:
> The WIKISPEED car has 4 seat and 2 seat interiors, we campaigned in the 4 seat, mainstream class in the X Prize. Where do you see a single person vehicle? It may help spending some time on www.youtube.com/WIKISPEED, www.facebook.com/WIKISPEED, or www.twitter.com/WIKISPEED, or consuming the links Marcin has posted about WIKISPEED on OSE: http://opensourceecology.org/wiki/Lessons_Learned

Ok, I withdraw that objection, though it really wasn't clear from the pictures on your website. Seating will be an issue, I think.

>
> I'm looking for a member or the OSE to go through WIKISPEED CAD and publish it on OSE, and then take tasks that we collaboratively determine as gaps between the SGT01 (current WIKISPEED car) and the OSE open source car, and pair with team WIKISPEED members to execute them (bend roll bars, for example). Then, that OSE group would build an example, using only the GVCS, of the OSE car from those CADs they've published, film and photo the progress, and use that to publish a "how to" guide.
>
> As soon as an OSE member says "hey, that's me! I'll go through the CAD, review with Joe, and publish it on OSE!" and signs a team WIKISPEED member form so they have full access, then we can get started.
> Let's do awesome together,

If I understand this correctly, you want OSE to use the STG01 as the basis of it's open source car. Let me clear about one thing, Joe, if we take the WikiSpeed CAD, convert it to our formats, and publish it on our wiki site, it will become an OSE design.

Historically, OSE uses one of two approaches to declaring one of the GVCS-50 designed and prototyped. The first way is to point to another project and say (in effect) "This meets the needs of this GVCS-50 product and will be used." An example of this is the Mendel 3D printer. It meets all of OSE's needs for a 3D printer, so there is no need to re-design it. The second approach is to either start from scratch or adopt an existing design, flesh it out, document it and publish it. This results in an OSE designed GVCS-50 product, ie, and OSE Design.

If we take your CAD, convert it, modify it, and publish it, it will become an OSE design. Credit will be given to WikiSpeed as having contributed to the design effort, but it will not be a WikiSpeed design thereafter. I hope you understand this distinction. Lest you think this is an egotistical argument - it's not. It's about protecting the basis of open source by having a design that we have vetted both technically and legally. As such, if we do as you suggest, it will be necessary for Team WikiSpeed to sign over open source rights to the design so that it may serve as the basis of an OSE design. I should also note that OSE cannot accept any design that is protected under an active patent.

Please note that the terms of our open source license do not prevent you from manufacturing, selling, and profiting from your initial design or even the subsequent OSE design. OSE intends to encourage an after market for the GVCS, as long as it doesn't violate the licensing terms and OSE philosphy. All OSE design must be completely free and open - unencumbered by legal restrictions (specifically IP rights and patents). We believe that this approach allows every one to benefit.

Team WikiSpeed has the option of suggesting it's design to be the designated OSE Car recommendation (as in the 3D printer example I mentioned above). If this is approach you prefer, then the following should be followed:

* Provide a link to online plans and instructions for how to build your car design. Link should be public.
* Provide a link or copy of the license under which this design its to be offered. Open source is a requirement here.

The OSE Car project team will then evaluate your design against OSE requirements. It will also review your license to ensure that it is free and open to all. It helps to use one of the standard licenses, but that is not a requirement. If your design meets our needs, then OSE will consider designating it as the recommended design.

This later approach is essentially a competitive bid, since there are other designs being offered to OSE as well.

- Mark Norton

----

On 2/28/2012 1:05 AM, Kinetic Aerospace wrote:
> With Mark's permission, I've added Matt Maier to the cc line. He's a sharp
> cookie and he's been keeping me in line when I go adrift on the OS Car specs
> (or even on my own proposal).

Matt has been contributing to OSE via the forums and wiki for some time now. He is quite welcome in this conversation.

> Mark, if you click the video on the
> http://www.wikispeed.com/p/wikispeed-fuel-efficient-cars page, at 6:27 there's
> a quick in-cockpit clip from a camera mounted on the passenger side of the
> dash and you can see it has two seats. However, it's not particularly
> noticeable in the rest of the video because the driver masks the passenger's seat.

I have ceded the point to Team Wiki. It just wasn't clear to me from the photos.

> I think there'd be comfort issues with two people aboard as it sits
Your comments on seating and comfort is a good analysis of the problems involved. Thank you for capturing this issue and documenting it.

> Re a competitive bid process, I've got my bid in, and if Joe cares to he can
> beat it. I'm comfortable with my quote and not interested in getting into a
> reverse auction.
While the discussion about car requirements and possible solutions is all good, I'm largely interested in deciding how we will proceed. I think I've made OSE's position more clear in my recent message to Joe and Team WikiSpeed. That position applies to you (Jack) as well. Please have a read and see if you are comfortable with it. Questions and suggestions are welcome. This is not intended to be dictatorial, but rather an attempt to protect the philosophical basis that OSE operates on.

> I favor a new OS Car specific design, but about a month ago, someone on the
> forum asked about MAX as an OS Car possibility (since MAX meets the original
> OS Car design criteria and has shown a measure of reliability) and I replied
> (to paraphrase myself) "No, that's Mother Earth New's, I'll have to start with
> a clean slate," but I asked MEN-folk anyway. Well apparently Mother Earth News
> doesn't have an objection to MAX carrying on under different management. All
> MEN is concerned about is that MAX doesn't go to another magazine.

That's good news, Jack. Have you made it clear to Mother Earth News that the design will be offered under open source licensing terms? As long as they assert that they retain no rights to the design, then I believe you are free to open source it.

> So if designating an existing car as the OS Car is what Marcin and OSE want,
> my hat is in the ring. That's probably the quickest way to get the first
> prototype into the GVCS, and you've two options to choose from. One way Marcin
> could choose would be for Joe and me to drive our cars to a mid-point between
> Seattle and Cave Junction, verify our performance with sealed tanks, GPS and
> video, and have Marcin fly out and decide in person. Portland International
> Airport would be a terrific meeting place; Joe and I could meet Marcin at PDX
> Arrivals and we could each take Marcin on rides.

This is a good suggestion for the evaluation process.

> Joe, is the Wikispeed prototype licensed and legal? Is it up to a couple
> hundred mile road trip? It would be good publicity for OSE, Wikispeed, and
> Kinetic Vehicles, and I'm sure Marcin would have the courtesy to give the car
> not selected some "It was a difficult choice..." quotes for our web sites and
> magazines.
Also good questions that need to be addressed. Quotes can be made, though that is up to Marcin.

>
>> As soon as an OSE member says "hey, that's me! I'll go through the
>> CAD, review with Joe, and publish it on OSE!" and signs a team
>> WIKISPEED member form so they have full access, then we can get started.
> Matt, you're already a Wikispeed member, would this be down your alley?

See comments in previous message.

> If this is the approach Marcin selects, I'll be happy to pitch in. How do I
> become a member? The web site isn't clear, all I got was "New members are
> invited and will be paired with an experienced professional."

I sent you a personal email describing how to become an OSE member. Membership is rather vague at this time. It's more a matter of how to be come involved and actively contribute to OSE projects.

- Mark Norton

----

Marcin:

Unless positions change (and they might), I think that things are starting to become clear with respect to the OSE Car project. Essentially we have two teams who have expressed interest: Kintentic Vehicles led by Jack McCornack, and Team WikiSpeed led by Joe Justice. In my opinion, both teams are technically capable of designing and prototyping cars. That said, there are some pretty large differences in approach.

Jack McCornack has offered his MAX design as the basis of a design, but he's actually gone further than that. He is actively discussing how to meet OSE requirements on the forum and in the wiki. Effectively, he is already working as an OSE contributor and is willing to be flexible with regards to our needs, though there may be technical challenges presented. Jack is willing to start from scratch and design a new car. He has also expressed his willingness to be part of a team and even cede project leadership to another person.

Joe Justice has offered his SGT01 design as the basis of a design, but rather than working towards making this happen, he's asking OSE to do the work of converting the CAD drawings, build the prototype, and then do the assembly documentation. This doesn't sound like someone really interested in working closely with us. In a sense, he is "throwing the design over the wall". Even if we were willing to do that, I have concerns about the IP basis of his design. Unless he is will willing to declare it open source under a license that I can read, I have serious concerns about his motives. Joe seems to suggest that any collaboration with OSE will be done on his terms, using his techniques, and on his websites. It would be a WikiSpeed project, in other words.

In a recent message (earlier this morning), I tried to make clear that there are two approaches we might consider: evolving/building a design or designating a design. If Joe wants the latter, then he needs to be come a lot more involved in OSE. If he prefers the form, then he needs to submit drawings and a license that we can evaluate against our needs.

Given that both of these teams have firmly established technical credentials, both seem capable of submitting a design bid for review and award by OSE. Jack has expressed a willingness to collaborate and work with a team. Joe is being a bit cagey about how he will work with us. I think he wants to lead it - as Team WikiSpeed, not as the OSE Car project.

In my opinion, Joe and his team are not positioning themselves to work with OSE, but would be willing to work for OSE. Jack and his team are willing to do either. How we proceed from here is largely your call. If you ask Joe to be the OSE project leader for the car project, I think we will have problems down the line, though he is the logical person to lead the effort. Thought it goes against my own philosophy, I think a collaborative effort with the existing group of people would lead to strife, frustration, and a waste of money. That leaves us with a competitive approach.

I believe that there are two ways we can implement a competitive approach going forward:

* Assumption of existing design - perhaps modified
* Bids for a new OSE design

If the first, then we need to ask all people involved to submit an existing design for evaluation against OSE criteria. Design must be offered under free and open source license terms with no IP restrictions. If the second, then we need to formally invite design bids that include cost estimates and schedules. In both cases, we must be very clear on our requirements and expectations. I have started to describe such criteria and documented them in the wiki. Jack has helped refine the requirements, Joe hasn't.

Please on advise on how to proceed.

- Mark

----

Hey guys, thanks for including me.

lemme go ahead and get this said. I've been poking around on OSE and Wikispeed, I'm trained in systems engineering, and I'd like to make some points that I don't think have been aired out yet.

1) The first priority should be to "publish early and often." I've described a treatment of the idea in more detail, but the summary is that the RepRap is a great example of how OSE is going to maximize its value. Quite simply, the first generation RepRap sucked. It barely worked, but it did technically work. Within 3-4 years multiple generations, made possible by the participation of thousands of people, produced several models of printer that are around $500 and rival or exceed the performance of $20,000 commercial printers. The takeaway is that we only need to get GVCS machines to the prototype stage, then get people to replicate them independently.

1a) That priority can be achieved by aggressively limiting the scope of each machine. We can better multiply our efforts by getting SOMETHING out in public, and letting it evolve, than by doing everything in-house. That means dropping as many features as possible. The tractor is a good example. It barely even has a place to sit.

2) The second priority should be modularity & integration. We aren't making 50 machines. We're making a 50-part system. Other projects can do whatever they want, but OSE is doing something bigger. We won't achieve the scale we're chasing with an additive strategy (by adding up machines). We need a multiplying strategy (synergistic machines). Rather than designing from the outside-in, where we make machines to do something and then later figure out if they can be integrated, we need to design from the inside-out, where we start from a common core and make it do different somethings.

2a) That priority can be achieved by reusing anything that has already worked in a previous prototype. It is really important that we measure the performance of each machine based on the performance of the GVCS as a system, rather than as an individual machine. Again, the tractor is a good example. The 3-way square tube technique isn't going to work forever, but it works great for prototyping. We should reuse that technique as often as possible so that the first-generation GVCS shares a common modular structure. The same with the power cubes and wheel units and whatnot. There's no reason we can't prototype the car in a week by making a frame out of square tubes, tossing a couple power cubes on top, and rolling on 3-4 wheel units.

That's where my head is at. For what it's worth, I would councel against focusing on traditional car metrics. This is because I would counel focusing on a strategy of modularity and fast turn-around. It's the same concept Wikispeed used to iterate their car so quickly, only applied to the entire GVCS rather than one machine. The car doesn't need 100mpg. I would say 20mpg is good enough. It doesn't need to seat 4 people. 2 people is good enough. It doesn't need a smooth ride. Staying upright in a turn is good enough. Etc. I think we should assume that this car is going to suck, and that's okay. Our goal shouldn't be to design an awesome car; it should be to design an adequate people-mover using the GVCS modular pieces. Putting out a vehicle design that costs $5000 means we can get people to replicate it and start the evolution. $15,000 means we need to include an mp3 player and a warranty.

This approach is a departure from the discussions I've seen here, on the forum and on the wiki. I bring it up because I think it's a more accurate implementation of OSE's core values and more likely to get the GVCS done by the end of the year. Something like a car is BEGGING to become a time and money black-hole. If we let it, the thing will take years and never really work. We need to approach the car as a sub-component of the GVCS and remember that the performance of the GVCS is more important than the performance of the car.

To put it in more emotional terms...we shouldn't be proud of the car. If the first published prototype of the car is good enough for us to be proud of it, then we gave it too much time and money. Pride will come later, when the GVCS is in its first complete generation, and much later, when it has evolved into something spectacular.

-Matt

----

The car absolutely should be road legal. In fact, I think one discussion we should have is about what sort of tricks we can pull to get a super-cheap car on the road.

I just think the design process should start with the existing components of the GVCS.

-Matt

----

In response to...

> While the discussion about car requirements and possible solutions
> is all good, I'm largely interested in deciding how we will proceed.
> I think I've made OSE's position more clear in my recent message to
> Joe and Team WikiSpeed. That position applies to you (Jack) as
> well. Please have a read and see if you are comfortable with it.
I presume, Mark, you're referring to...

> Let me clear about one thing, Joe, if we take the WikiSpeed CAD, convert it
> to our formats, and publish it on our wiki site, it will become an OSE
> design. [and so forth*]
...and I'm completely comfortable with OSE as the owner and OSE publishing the
information under its open source license.

> This is not intended to be
> dictatorial, but rather an attempt to protect the philosophical
> basis that OSE operates on.
No, that's not dictatorial at all, if you folks have the
how-to-do-open-source-licensing part of the program figured out, then you're
the ones who should handle that.

My own open source license isn't equal to modern os licenses, but in my
defense I've been os'ing my designs for over 35 years. I didn't have other os
licenses to copy (I don't think the term had been invented yet) and the legal
system taught me some harsh lessons that left me paranoid (or as my dad used
to say, "Even paranoids have real problems."

Also my main interest has been supporting homebuilders, and they've all been
happy with my open source policies, which...here, I'll quote myself from the
intro on my...
http://kineticvehicles.com/DwgFrontSuspension.htm
...Locost front suspension part drawing page:

Darn near every component Kinetic manufactures, using production tooling, CNC,
and the economies of scale, can be made individually, with common tools and
elbow grease. For those with more time than money, or who enjoy "scratch
building" for any number of reasons, we're providing drawings so you can
fabricate the fiddly bits yourself.
The license itself is part of the jpg that is the drawing, to make it harder
to remove (the rights include right to copy the drawing, provided the license
text is included).

"Free license for one time personal use, for anyone building a Locost or
similar vehicle for education or recreation" and so on.

The "education and recreation" part comes from FAA regs re homebuilt
aircraft, which goes back to my recreational aircraft design.

But then it goes on to prohibit commercial use, a lesson learned the hard way,
starting with a manufacturer that copied my Pterodactyl Fledge design in every
respect but the color of anodizing (their aluminum parts were "proprietary
blue", I kid you not) and my company and I were never mentioned until the day
one of their customers got hurt, and suddenly, they remembered I was the
designer and I was embroiled in a product liability (defect of design) lawsuit.

A couple of years later, a process server brought me an envelope from Melvin
Belli's office, suing me for another injury, on the basis that my design was
an attractive nuisance. The injured client said he was inspired to build an
ultralight aircraft after seeing mine on a National Geographic cover, and then
found out how easy it was to get information from me and my company, so he
built one. The Belli theory was that I had failed in "...your legal obligation
to vigorously enforce your copyright" and my failure to make my design hard to
copy was equivalent to having a swimming pool with no fence around it.

So I'm willing to update my os licenses, or let OSE provide them, but I wanted
you to know why I'm still in the Open Source Stone Age on my web site.

You'll also note I have some real teeth in my no-commercial-use demand. The
penalty for license violation is "you should be ashamed of yourself".

That said, me designing/building a first prototype of a new car for OSE means
it'll be OSE's design -- if OSE is the client and paying for the materials,
then there's no question in my mind that OSE is the owner.** You clearly have
more Open Source expertise than I do, that sounds win-win to me. If I'm
credited for my contribution to the design effort (as described in the first
footnote) and the same rights to manufacture as everybody else (ditto 1st
footnote) I'll be happy.

-Jack

----

Hi Mark,

I'm immersed in TED so i haven't had time to report.

I have talked to Joe on the phone yesterday, and I am visiting with Joe Justice after TED on Sunday, after visiting with Brianna on the ironworker progress.

From what I have seen, Joe's car is entirely OSE Spec: open source, radical modularity, high performance. Availability is today, a build can happen in 2 months if Brianna takes it on at FeF. Further, he can contribute expertise on agile/lean/scrum that led to successfu deployment in 3 months, and his experience could lead to refining a method for a broader OS product development pipeline. His design allows 2 power cubes to be retrofitted in as is, making it a turnkey solution. I have discussed IP with Joe, he stated that he is fully willing to contribute all IP into open source.

I have not seen the modularity in Jack's car, which removes lifetime design or retrofittability of power cubes into the existing design. Further, he is promising 9 month deployment for his existing version, which does not meet timeline requirements for 3 prototypes.

It appears clear to me that Wikispeed is not interested in brands as much as creating value. Joe's solution appears to be a clear winner.

Joe made commitments to collaborate and be open.I do not doubt his integrity. Gotta run.

Marcin

----

On Tue, 28 Feb 2012 12:01:51 -0700, Matt Maier wrote
> The car absolutely should be road legal. In fact, I think one
> discussion we should have is about what sort of tricks we can pull
> to get a super-cheap car on the road.
That makes three "aye" and no "no" votes for road legal. Anybody else ready to
chime in on this?

Regarding the super-cheap discussion; dang, Matt, I wish you'd been here
sooner. This month has 29 hours to go (from where I'm sitting), and you raise
a fascinating subject, but for me, it would call for a complete rewrite of my
proposal, and I'll bet Team WikiSpeed is in the same boat. After the dust has
settled on Marcin's OS Car first prototype selection, I can give you my leads
on cheapmobiles. Or google "Grassroots $2012 Challenge"

>> There's no reason we can't prototype the car in a week by making a frame
>> out of square tubes, tossing a couple power cubes on top, and rolling on
>> 3-4 wheel units.
I think there's a significant difference between "a car" and "a thing that
moves". The prototype you're describing would be a good basis for an 1885 Benz
Motorwagen replica, but I don't see it as a step in the development of a
roadworthy prototype this year. Then again...

>> I would counel
>> focusing on a strategy of modularity and fast turn-around. It's the same
>> concept Wikispeed used to iterate their car so quickly
...you and Joe know things about fast turn-around that I don't; the one week
reiteration thing is out of my league. Still, if it was that easy, you'd think
somebody would have invested a week and built one, in the years since the OS
Car was announced.

>> Putting out a vehicle design that costs $5000 means we can get people to
>> replicate it and start the evolution. $15,000 means we need to include an
>> mp3 player and a warranty.
Good point. The cost of a finished car (presuming free labor) is pretty much
arbitrary--pick a target and design to it. I like $10k, but $12k was the
budget in the Design Criteria, and the best $12000 car will be better than the
best $10000 car. At $5k it's going to look like a Junkyard Wars winner and be
taking some efficiency hits because of it.

-Jack

----

I hope all is going well at TED.

I must admit that I'm a bit annoyed with you, Marcin. You asked me to step in and help mediate this OSE Car situation. I did and shared correspondence with you every step of the way. In return, you've negotiated a deal with Joe without bothering to inform me that it was under consideration. It certainly explains why Joe wasn't really responding to my concerns, questions, or suggestions - he was negotiating with you, not me.

While I certainly hope that Joe can deliver on his promises to design a car that will meet OSE requirements, I have come concerns. Actually, my concerns have less to do with Joe and more to how you will relate to and treat him. Just as you have expectations in what Joe will do for OSE, so too does Joe have expectations in you as the leader of OSE. I think that, in time, there will be a breakdown between you and Joe, just as there have been similar breakdowns between you and other strong technology leaders.

Have you, for example, clearly communicated to Joe what OSE's requirements in a GVCS Car are? If so, I have yet to see them fully published. Without clear requirements, you are setting him up for failure because he won't understand what you want him to do. Have you evaluated the existing WikiSpeed design to see if it will meet our needs? I doubt it, since no one outside of Team WikiSpeed has even seen the drawings yet.

There is another problem that you might want to give some consideration to. You are the charismatic leader of Open Source Ecology. You are the acknowledged vision holder for what OSE is trying to accomplish. Meanwhile, Joe Justice is the charismatic leader of a project at the cutting edge of vehicular technology. He is a brightly shining star in the OS hardware world. He is also a fellow TED alumnus. Are you willing to share the OSE spotlight with Joe? I hope so, because you are inviting him.

Since it seems that you have the situation well in hand, I don't think there is any need for me mediate the OSE Car project any longer. I will return to work on the Steam Engine and other projects that catch my eye.

- Mark Norton

----

Hi Mark,

Thanks for raising the concerns. I just spoke to Joe. I have been in contact with him. Joe is on the same page.

I am interested in a solution that bears fruit as quickly as possible. He is willing to share all plans right now. I suggest that you speak with him - (phone number redacted)

I think that we can transfer his CAD and build procedures within one month, and build the car within 3 months. The only requirement is clarity that IP is open under OSE License.

Brianna is interested in fabricating this at Factor e Farm. Perhaps Jack can make improvements on any of the modules, such as engine unit. At present, we could do 2 power cubes and 2 hydraulic motors on the back wheels. That would yield a solution quickly, at about $8500 total dedicated cost for the car (not counting power cubes, since they are interchangeable).

Marcin

----

Hello all;

"Street Legal"? Yes

My thoughts are for function over flare. While the racing car styles look nice, OSE
designs have been more focused on functionality. The should change with the car,
as its focus is the safe transport of passengers. I think that adding an attractive skin
could be a great for the OSE image.

What are the "official requirements" of an automobile? I've heard a variety of
things, some true some not. I'd also like to know other requirements, like seat
belts and airbags.

While I like the "publish early and often" as it applies to software, hardware
has limits with funding and cycle time. Waiting customers are good incentive,
with the prospect of $$$.

My concerns are more about the power delivery and the powertrain. I haven't
studied the Wikispeed car yet, but if we don't use their engine, we'll have to
figure out the powertrain. Should we do something wild like make an electric
drivetrain and modular wheel assemblies (some with electric motors, some
without) - for ease of maintenance?

Tom

----

Jack- I LOVE your train of thought. We should do more together, and I'm glad OSE has given us the opportunity!
Mark- yes, it's my expectation this design is open source, I think that's the whole point and value proposition here, and I'm all in. I'm hoping to leave the open source terms to OSE who is more experienced in open source agreements than I am.
Matt- that is EXACTLY how I feel- iterate frequently and start with the minimum product that achieves the minimum meaningful value. With Jack's ninja fabrication and design skills, OSE's open source distribution platform and tooling, and WIKISPEED's modularity we can quickly whip up, I hope, a MMF OSE car (minimum marketable feature, to use a Lean Startup term) that delivers 80% of the value with 20% of the complexity.

Jack, if that's cool with you, I have a roll bar sketch to send down. it requires almost 40' of 2" OD SAE4130, which is ~$500. :( Maybe you have some pipe stock that could approximate? I'd love to start with this super simple concept, and then have you help coach me on more optimum designs as we iterate. But let's start with this moon dune-buggy if that is at all interesting to you. Later, I'd like to make a geo engine module with you, that might be compatible with WIKISPEED AND Max, if we do it just right.

Matt, if this is cool with you, I'd like you to publish the WIKISPEED chassis CAD on OSE this week. Have I shared the WIKISPEED_CAD dropbox with you yet? THIS DOES NOT MEAN OSE HAS CHOSEN THE WIKISPEED CAR AS THE OSE CAR- personally I'm hoping the OSE car has Jack's design in it and WIKISPEED's modularity- and maybe a fast way to start with that is the WIKISPEED chassis. But Jack won't be able to iterate on the design much until it is published and open source, so what I'm saying is let's get the WIKISPEED chassis published in open source right away so folks can iterate modules, weather its ever gonna have the focuesed attention of being THE GVCS car or not, because the value is in getting the design out for folks to iterate and OSE is PERFECT FOR THAT.

Mark- would you help me create the open source terms for the WIKISPEED chassis, is that possible/responsibel do do this week?
Awesome,
Joe

----

FYI, here are the requirements for road legality in the United States: http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?sid=903344824fd0ffd46fa1dc5412540dc6&c=ecfr&tpl=/ecfrbrowse/Title49/49tab_02.tpl
See Chapter V and VI. These are MASSIVE. WIKISPEED created tests for these first before we started building cars, so we could get the benefits of focus that come with Test Driven Development.
Almost all of these can be side-stepped, however, if the customer puts in the engine (module, power cube, metro engine) themselves. But if we can meet the CFR road legality standards, all the better, right?
Awesome,
Joe

----

I had an interesting thought today during my drive home.

I was thinking about the outcome of this design work. You know, what OSE's car would look like, how it would perform, etc. Then I was thinking about how I would like to buy Wikispeed's car when they get a more practical model. Then I started thinking that the OSE car would be a lot uglier and would have less performance, but would be a lot cheaper. Maybe it would be about the cost of a motorcycle, but with a fully enclosed cab, and reasonable comfort, etc.

Then I had an amazing thought. It occurred to me that I was thinking something that very few people in the history of the human race had ever thought before.

That's pretty impressive when you put it in perspective. The general wisdom is that everything's already been thought of. Well, that's not entirely accurate. You see, open source cars didn't even exist as a concept until recently. And the idea that there would be OPTIONS, that I would get to compare models and decide which one better suited my needs, is truly novel. So when I thought about two open source cars from the point of view of actually getting one I got to take a tiny step forward for the whole human race. One small step for me, one giant leap for everyone. Or something like that.

What I mean is that we're really pushing boundaries here. The mere fact that, as a group, we don't seriously doubt the car(s) will get built, so we're free to argue over what they should do, is ground breaking in a geeky kind of way. And getting to be here at the beginning of an era when people can choose between different open source cars is awesome.

I'm probably overstating this a bit, but a little hyperbole never hurt anyone.

In terms of the actual, official design requirements, I suggest that we focus on doing the bare minimum. If (when) this works, we'll be able to do anything we want, and so will everyone else. We just need a proof of concept. Something we can point to and say, "There, you see that? That's what we're talking about. It totally works, now lets make it work better." Automobile design is a HUGE conceptual space. There will always be disagreements over what a vehicle should do, and how it should do it, and everyone will be right. We just have to pick ONE of those options and I suggest we pick the lowest hanging fruit. The rest of the fruit will still be there when we get back.

What's the absolute minimum we can get away with? How much can we cut out before the thing isn't safe or useful? Forget attractiveness, forget performance, forget even having a LIST of requirements. I think we can get away with three: Is it safe, is it legal, and does it do something useful? That's it.

Wikispeed hits 'em high, OSE hits 'em low, and we change the world.

-Matt

Car/Correspondence

2012-02-29T12:38:25Z

Mjn:

[Category:Car]

Some email about the car.

Car/Correspondence

2012-02-29T12:38:05Z

Mjn: Created page with "{Category:Car} Some email about the car."

{Category:Car}

Some email about the car.

Car/Design Criteria

2012-02-22T17:46:15Z

Mjn: Criteria gathered from other parts of the wiki and the forum.

=General Requirements=

* 1.1 The OSE Car is expected to meet general OSE guidelines for GVCS tools, equipment, and vehicles.

=Simplicity=

* 2.1 A person with reasonable skills with access to an equipped workshop should be able to build the OSE car.
* 2.2 Fabrication and assembly should require less than 1000 hours of work.

=Cost to Create=

* 3.1 Cost to build should be less than an inexpensive new car.
* 3.2 The intial goal is to build a car that costs less than $12,000 in parts and materials.

=Operation=

* 4.1 Meet legal requirements regulations to operate on public roads and highways.
* 4.2 Initial, U.S. regulations will be targeted. Later, other country regulations will be factored in.
* 4.3 Meet impact safety including a good frame, seat belts, bumpers, etc.
* 4.4 Meet operating requirements such as signal lights, head lights, running lights, brake lights, etc.
* 4.5 Meet established emission requirements - this is good for our planet, too.
* 4.6 Speed - must be capable of minimum road speeds for highway operation.
* 4.7 Reverse - pretty much a requirement to park it in a public place.

=Fuel, Economy, and Range=

* 5.1 In general, the OSE Car should be inexpensive or effectively free to operate.
* 5.2 In the first prototype, a gasoline or diesel fuel will be targeted.
* 5.3 50 miles per gallon will be the target for the first gas/diesel prototype.
* 5.4 The car should be design in a manner that facilitates other kinds of fuels and power sources that may include:
** Gas such as propane, methane, producer gas, etc.
** Wood pellets that fire a boiler that drives a turbine or steam engine.
** Stored electrical energy that drives electric motors.
* 5.5 Car should have an initial driving range of 500 miles.

=Other Considerations=

* 6.1 There is strong desire to use the existing PowerCube as a drive motor.
* 6.2 A custom vehicle PowerCube made be substituted based on OSE principles of modularity, repairability, etc.
* 6.3 The OSE Car should be comparable or lighter in overall weight than a compact car.
* 6.4 The size of the OSE Car should allow it to be parked in typical U.S. parking spaces.

Car/Kinentic Vehicles Proposal

2012-02-15T14:40:30Z

Mjn: Added link to MAX design. Broke out safety requirements.

Submitted by Jack McCornack of Kinetic Vehicles [http://www.kineticvehicles.com]

=Requirements=

The basic requirements for the OS Car are:
* Two passenger capacity,
* Ultra-high fuel economy (50+ MPG, city, 100+ MPG, highway),
* Ultra-long range (1000+ miles),
* Low Cost (less than $12,000),
* Ease of Construction (1000 hours of construction time. Can be constructed by one person in 1000 hours with a vertical mill, band saw, disc sander, grinding wheel, air compressor, welder).
* Use of OSE Power Cube
* Suspension - reasonable comfort

Safety Requirements
* Head lights with high and low beams
* Signal lights front and rear
* Running lights
* Brake lights
* Backup lights
* Mirrors - side and dash
* Foot operated brakes - XXX feet from 60mph
* Emergency hand brake
* Bumpers ???
* Windshield ???

=Proposed Budget=

$15000 by December of 2012
Assuming the project is started before the end of February.

=Qualifications=

MAX design [http://www.kineticvehicles.com/MAX10.html] for Mother Earth News

=Project Specifics=

==Low Budget==

$15000 total for a licensed, legal, functional running prototype
OS Car. I expect to provide 500 unpaid hours of engineering and prototyping to
keep the costs down. If I find I've underbid either cost or effort, I (or my
company) will make up the difference at no cost to OSE.

==Low Risk==
No money up front, payments phased with tasks accomplished. I
propose 10% ($1500) on completion of specifications, 30% ($4500) on completion
of a drivable chassis, 30% ($4500) on body installation, and 30% ($4500) on
delivery of finished prototype. As OSE will be the owner, licensing and
insurance fees to be paid by OSE.

==Fast Delivery==

Guaranteed delivery by 12/31/12 or no final payment. That
should motivate me, since I'll need that money to reimburse my costs of
construction.

Car/Kinentic Vehicles Proposal

2012-02-14T04:08:34Z

Mjn: Initial summary based on email to MJ.

Submitted by Jack McCornack of Kinetic Vehicles [http://www.kineticvehicles.com]

=Requirements=

The basic requirements for the OS Car are:
* Two passenger capacity,
* Ultra-high fuel economy (50+ MPG, city, 100+ MPG, highway),
* Ultra-long range (1000+ miles),
* Low Cost (less than $12,000),
* Ease of Construction (1000 hours of construction time. Can be constructed by one person in 1000 hours with a vertical mill, band saw, disc sander, grinding wheel, air compressor, welder).
* Use of OSE Power Cube
* Safety Requirements (TBD)

=Proposed Budget=

$15000 by December of 2012
Assuming the project is started before the end of February.

=Qualifications=

MAX design for Mother Earth News

=Project Specifics=

==Low Budget==

$15000 total for a licensed, legal, functional running prototype
OS Car. I expect to provide 500 unpaid hours of engineering and prototyping to
keep the costs down. If I find I've underbid either cost or effort, I (or my
company) will make up the difference at no cost to OSE.

==Low Risk==
No money up front, payments phased with tasks accomplished. I
propose 10% ($1500) on completion of specifications, 30% ($4500) on completion
of a drivable chassis, 30% ($4500) on body installation, and 30% ($4500) on
delivery of finished prototype. As OSE will be the owner, licensing and
insurance fees to be paid by OSE.

==Fast Delivery==

Guaranteed delivery by 12/31/12 or no final payment. That
should motivate me, since I'll need that money to reimburse my costs of
construction.

Steam Engine Research/Graphite Rings

2012-02-05T22:35:21Z

Mjn:

{{Category=Steam Engine}}
{{ToolTemplate|ToolName=Steam Engine}}

Carbon graphite rings have self lubricating properties and very little friction when coming in contact with metal. If we are planning on using wet steam then the water will also provide lubricating properties. In the case, you choose to use superheated dry steam then the graphite rings will work for that application as well. The goal is to eliminate oil. This will prevent the water tubes and condenser from getting clogged.

You can read more about carbon graphite. [http://www.engraphite.com/carbon-graphite.html]

Steam Engine Research/Graphite Rings

2012-02-05T22:35:05Z

Mjn:

Steam Engine Research/Graphite Rings

2012-02-05T22:34:43Z

Mjn: Created page with "{{Category=Steam Engine}} {{ToolTemplate|ToolName=Steam Engine}} Carbon graphite rings have self lubricating properties and very little friction when coming in contact with meta..."

Steam Engine/Index

2012-02-05T22:33:54Z

Mjn:

{{Category=Steam Engine}}
{{ToolTemplate|ToolName=Steam Engine}}

Wiki pages related to the OSE Steam Engine Project are organized by topics here. For an alphabetical index, see the "Steam Engine" link at the bottom of this page.

=Steam Engine Project=

* '''Theory and Research'''
** [[Steam Engine]] - technology entry page.
** Theory
*** [[Steam Engine Research/Carnot Cycle]]
*** [[Steam Engine Research/Books]]
** Engine Elements
*** [[Steam Engine Research/Lubrication]]
*** [[Steam Engine Research/Condenser]]
*** [[Steam Engine Research/Oil Separator]]
*** [[Steam Engine Research/Graphite Rings]]
** Design Notes
*** [[Steam Engine Research/Engine Design Notes]]
*** [[Steam Engine Research/Valve Design Notes]]
*** [[Steam Engines]]
*** [[Steam Engine Design/Historic]]
** Installations
*** White Cliffs Solar Power Station
**** [[Steam Engine Design/White Cliffs]]
**** [[Steam Engine Design/White Cliffs Report]]
**** [[Steam Engine Research/Power Kinetics]]
* '''Project Overview'''
** [[GVCS Tools Status]]
** [[Steam Engine/Things To Do]]
** [[Steam Engine Intro]]
** [[Steam Engine Concept]]
** [[Steam Engine Breakdown]]
** [[Steam Engine Correspondence]]
*** [[Steam Engine/Correspondence]]
*** [[Steam Engine Correspondence/Kennedy]]
*** [[Steam Engine Correspondence/SolarAndThermal.com]]
*** [[Steam Engine Correspondence/Josh Jordan]]
*** [[Steam Engine Correspondence/Damien Gendron]]
*** [[Steam Engine Correspondence/Ron Whaley]] - Principle steam engine designer for PKI/White Cliffs
** [[Steam Engine/Terminology]]
** [[Steam Engine Planning]]
** [[Steam Engine Questions]]
** [[Steam Engine Marketing Plan]]
** [[Steam Engine/Spec Metric]]
** [[OS2 Steam Engine Team]]
** [[Mark J Norton/OSE Work]]
** [[:Category: Steam_Engine_Images]]
** [[Steam Engine/Safety Issues]]
** [[Steam Engine/Others]] - Commercial providers of steam engines, etc.
** [[Steam Engine Status/Open Hardware Summit 2011]]
* '''Development'''
** [[Steam Engine Development]]
** [[Steam Engine Development/Schedule]]
* '''Design'''
** Engine Design
*** [[Steam Engine Design/2009]]
*** [[Steam Engine Design]] - Arrowhead Bump Valve
*** [[Mounster Design]] - Wally Mounster Design by way of SACA and Tom Kimmel
*** [[Electronic Valve Engine]]
*** [[Solenoid Design]]
*** [[Steam Engine Design/Multiple Cylinders]]
*** Motor Driven Rotating Valve
*** [[Steam Engine Design/Suggestions]]
** [[Steam Engine Design/Valves]] - Valve Design Patterns
*** [[Steam Engine Design/Bump Valve]]
*** [[Steam Engine Design/Piston Valve]]
*** [[Steam Engine Design/Slide Valve]]
*** [[Steam Engine Design/Solenoid]]
*** [[Steam Engine Design/Rotating Valve]]
*** [[Steam Engine Design/Pressure Relief Valve]]
*** [[Electric Valves for Steam Engine]]
** Crankshaft Designs
*** [[Steam Engine Crank]]
*** [[Steam Engine Crank/Eccentric]]
*** [[Steam Engine Crank/Return Crank]]
*** [[Steam Engine Design/Crankshaft]]
** Other Parts
*** [[Steam Engine Design/Oiler]]
*** [[Steam Engine Design/Boiler]]
*** [[Steam Engine Design/Stuffing Box]]
** [[Steam Engine Reviews]] - Design reviews, etc.
*** [[Steam Engine Reviews/Arrowhead Bump Valve Summary]]
*** [[Steam Engine Reviews/Arrowhead Bump Valve]]
*** [[Steam Engine Design/Gregor]]
*** [[Steam Engine Reviews/Piston Head Stress]]
*** [[Steam Engine Reviews/Mike Stone]]
* '''Specification'''
** [[Steam Engine Specifications]]
** [[Steam Engine Specifications/Geometry]]
** [[Steam Regulations]]
** [[Steam Fittings]]
*** [[Steam Fittings/Pressure Gauge]]
** Sources
*** [[Steam Engine Specifications/Piston Ring Sources]]
*** [[Steam Engine Specifications/Cylinder Liner Sources]]
*** [[Steam Engine Specifications/Bearing Sources]]
*** [[Steam Engine Specifications/Valve Spring Sources]]
*** [[Steam Engine Specifications/Pillow Block Sources]]
*** [[Steam Engine Specifications/Pressure Sensor Sources]]
** Calculations
*** [[Steam Engine Construction Set Calculations]]
*** [[Steam Engine Efficiency]]
*** [[Steam Engine Efficiency Calculations]]
*** [[Steam Engine Efficiency and Losses]]
*** [[Steam Engine Specifications/Indicator Diagrams]]
*** [[Steam Engine Specifications/Work Diagram Construction]]
*** [[Steam Engine Specifications/Work Diagrams]]
*** [[Steam Engine Specifications/Spreadsheet]]
** Parts
*** [[Steam Engine Specifications/Piston Rings]]
*** [[Steam Engine Specifications/Cylinder Liner]]
*** [[Steam Engine Specifications/Connector Rod Bearings]]
*** [[Steam Engine Specifications/Nuts and Bolts]]
*** [[Steam Engine Specifications/Valve Spring]]
*** [[Steam Engine Specifications/Oiler]]
*** [[Steam Engine Specifications/Flywheel]]
*** [[Steam Engine Specifications/Pillow Blocks]]
** Seals
*** [[High Temperature Thread Sealer]]
*** [[Graphite Impregnated String]]
* '''Bill of Materials'''
** [[Steam Engine Bill of Materials]]
** [[Steam Engine Bill of Materials/2009]]
* '''Build Instructions'''
** [[Steam Engine Build Instructions]]
** [[Steam Engine Build/Tools]]
** [[Steam Engine Build/Piston Rings]]
** [[Steam Engine Build/Piston Assembly]]
*** [[Steam Engine Build/Piston Head]]
*** [[Steam Engine Build/Bump Valve Pin]]
*** [[Steam Engine Build/Piston Connector Rod]]
** [[Steam Engine Build/Cylinder Assembly]]
*** [[Steam Engine Build/Cylinder Case]]
*** [[Steam Engine Build/Cylinder Liner Modifications]]
*** [[Steam Engine Build/Cylinder Valve Seats]]
*** [[Steam Engine Build/Cylinder End Mount]]
*** [[Steam Engine Build/Exhaust Plenum]]
** [[Steam Engine Build/Valve Assembly]]
*** [[Steam Engine Build/Valve]]
*** [[Steam Engine Build/Valve Cover]]
*** [[Steam Engine Build/Cylinder Mounting Bracket]] - Deprecated: this part has been merged into [[Steam Engine Build/Valve Cover]].
** [[Steam Engine Build/Base Plate Calculations]]
** [[Steam Engine Build/Base Plate]]
** [[Steam Engine Build/Oil Dribbler]]
** [[Steam Engine Build/Optional Sensor Vent]]
** [[Steam Engine Build/Crankshaft Assembly]]
*** [[Steam Engine Build/Shaft]]
*** [[Steam Engine Build/Crank]]
*** [[Steam Engine Build/Pillow Block]]
*** [[Steam Engine Build/Flywheel]]
* '''Buy It'''
** [[Buy Steam Engine]]
* '''User Manual'''
** [[Steam Engine user's manual]]

=Steam Engine Applications=

* [[Turn of the Century Farm Equipment]]
* [[Steam Cars]]
* [[Open Source Steam Power Generator]]
* [[Steam Hydrauilc Hybrid Electrical Generator]]
* [[Cyclone Engine]]
* [[Steam Powered Hydraulic Pump]]

=Steam Generators=

* [[Steam Generator]]
* [[Geo-thermal Power]]
* [[Natural Steam Sources]]
* [[CHP Stove Heat Exchanger]]
* [[Flash Steam Generator]]
* [[Solar Combined Heat Power System]]
* [[Tesla Turbine]]

=Steam and Steam Engine Technology=

* [[Crash Course in Steam]]
* [[Opposed piston opposed cylinder engine]]
* [[Brief History of the Steam Engine]]
* [[Steam Engineering Tutorial]]
* [[Steam Power Basics]]
* [[Uniflow Steam Engine]]
* [[Solar Steam Engine Selection Process]]
** [[Steam engine piston rings]]

=Other Steam Engines=

* [[Lynx Motors]]

=Steam Engine Organizations=

* Companies
** [[The Only Production Steam Engine in the World]]
** [[Tinytech]]
** Cyclone Power Technology
* Clubs
** [[Steam Automobile Club of America]]
** New England Model Engineering Society [http://www.neme-s.org/].
** Pennsylvania Live Steamers [http://www.palivesteamers.org/]
* [[Steam Engine/Museums]]
** New England Wireless and Steam Engine Museum, Rhode Island [http://www.newsm.org/].

[[Category:Steam Engine]]

Steam Engine/Index

2012-02-05T22:33:41Z

Mjn:

{{Category=Steam Engine}}
{{ToolTemplate|ToolName=Steam Engine}}

Wiki pages related to the OSE Steam Engine Project are organized by topics here. For an alphabetical index, see the "Steam Engine" link at the bottom of this page.

=Steam Engine Project=

* '''Theory and Research'''
** [[Steam Engine]] - technology entry page.
** Theory
*** [[Steam Engine Research/Carnot Cycle]]
*** [[Steam Engine Research/Books]]
** Engine Elements
*** [[Steam Engine Research/Lubrication]]
*** [[Steam Engine Research/Condenser]]
*** [[Steam Engine Research/Oil Separator]]
*** [[Steam Engnie Research/Graphite Rings]]
** Design Notes
*** [[Steam Engine Research/Engine Design Notes]]
*** [[Steam Engine Research/Valve Design Notes]]
*** [[Steam Engines]]
*** [[Steam Engine Design/Historic]]
** Installations
*** White Cliffs Solar Power Station
**** [[Steam Engine Design/White Cliffs]]
**** [[Steam Engine Design/White Cliffs Report]]
**** [[Steam Engine Research/Power Kinetics]]
* '''Project Overview'''
** [[GVCS Tools Status]]
** [[Steam Engine/Things To Do]]
** [[Steam Engine Intro]]
** [[Steam Engine Concept]]
** [[Steam Engine Breakdown]]
** [[Steam Engine Correspondence]]
*** [[Steam Engine/Correspondence]]
*** [[Steam Engine Correspondence/Kennedy]]
*** [[Steam Engine Correspondence/SolarAndThermal.com]]
*** [[Steam Engine Correspondence/Josh Jordan]]
*** [[Steam Engine Correspondence/Damien Gendron]]
*** [[Steam Engine Correspondence/Ron Whaley]] - Principle steam engine designer for PKI/White Cliffs
** [[Steam Engine/Terminology]]
** [[Steam Engine Planning]]
** [[Steam Engine Questions]]
** [[Steam Engine Marketing Plan]]
** [[Steam Engine/Spec Metric]]
** [[OS2 Steam Engine Team]]
** [[Mark J Norton/OSE Work]]
** [[:Category: Steam_Engine_Images]]
** [[Steam Engine/Safety Issues]]
** [[Steam Engine/Others]] - Commercial providers of steam engines, etc.
** [[Steam Engine Status/Open Hardware Summit 2011]]
* '''Development'''
** [[Steam Engine Development]]
** [[Steam Engine Development/Schedule]]
* '''Design'''
** Engine Design
*** [[Steam Engine Design/2009]]
*** [[Steam Engine Design]] - Arrowhead Bump Valve
*** [[Mounster Design]] - Wally Mounster Design by way of SACA and Tom Kimmel
*** [[Electronic Valve Engine]]
*** [[Solenoid Design]]
*** [[Steam Engine Design/Multiple Cylinders]]
*** Motor Driven Rotating Valve
*** [[Steam Engine Design/Suggestions]]
** [[Steam Engine Design/Valves]] - Valve Design Patterns
*** [[Steam Engine Design/Bump Valve]]
*** [[Steam Engine Design/Piston Valve]]
*** [[Steam Engine Design/Slide Valve]]
*** [[Steam Engine Design/Solenoid]]
*** [[Steam Engine Design/Rotating Valve]]
*** [[Steam Engine Design/Pressure Relief Valve]]
*** [[Electric Valves for Steam Engine]]
** Crankshaft Designs
*** [[Steam Engine Crank]]
*** [[Steam Engine Crank/Eccentric]]
*** [[Steam Engine Crank/Return Crank]]
*** [[Steam Engine Design/Crankshaft]]
** Other Parts
*** [[Steam Engine Design/Oiler]]
*** [[Steam Engine Design/Boiler]]
*** [[Steam Engine Design/Stuffing Box]]
** [[Steam Engine Reviews]] - Design reviews, etc.
*** [[Steam Engine Reviews/Arrowhead Bump Valve Summary]]
*** [[Steam Engine Reviews/Arrowhead Bump Valve]]
*** [[Steam Engine Design/Gregor]]
*** [[Steam Engine Reviews/Piston Head Stress]]
*** [[Steam Engine Reviews/Mike Stone]]
* '''Specification'''
** [[Steam Engine Specifications]]
** [[Steam Engine Specifications/Geometry]]
** [[Steam Regulations]]
** [[Steam Fittings]]
*** [[Steam Fittings/Pressure Gauge]]
** Sources
*** [[Steam Engine Specifications/Piston Ring Sources]]
*** [[Steam Engine Specifications/Cylinder Liner Sources]]
*** [[Steam Engine Specifications/Bearing Sources]]
*** [[Steam Engine Specifications/Valve Spring Sources]]
*** [[Steam Engine Specifications/Pillow Block Sources]]
*** [[Steam Engine Specifications/Pressure Sensor Sources]]
** Calculations
*** [[Steam Engine Construction Set Calculations]]
*** [[Steam Engine Efficiency]]
*** [[Steam Engine Efficiency Calculations]]
*** [[Steam Engine Efficiency and Losses]]
*** [[Steam Engine Specifications/Indicator Diagrams]]
*** [[Steam Engine Specifications/Work Diagram Construction]]
*** [[Steam Engine Specifications/Work Diagrams]]
*** [[Steam Engine Specifications/Spreadsheet]]
** Parts
*** [[Steam Engine Specifications/Piston Rings]]
*** [[Steam Engine Specifications/Cylinder Liner]]
*** [[Steam Engine Specifications/Connector Rod Bearings]]
*** [[Steam Engine Specifications/Nuts and Bolts]]
*** [[Steam Engine Specifications/Valve Spring]]
*** [[Steam Engine Specifications/Oiler]]
*** [[Steam Engine Specifications/Flywheel]]
*** [[Steam Engine Specifications/Pillow Blocks]]
** Seals
*** [[High Temperature Thread Sealer]]
*** [[Graphite Impregnated String]]
* '''Bill of Materials'''
** [[Steam Engine Bill of Materials]]
** [[Steam Engine Bill of Materials/2009]]
* '''Build Instructions'''
** [[Steam Engine Build Instructions]]
** [[Steam Engine Build/Tools]]
** [[Steam Engine Build/Piston Rings]]
** [[Steam Engine Build/Piston Assembly]]
*** [[Steam Engine Build/Piston Head]]
*** [[Steam Engine Build/Bump Valve Pin]]
*** [[Steam Engine Build/Piston Connector Rod]]
** [[Steam Engine Build/Cylinder Assembly]]
*** [[Steam Engine Build/Cylinder Case]]
*** [[Steam Engine Build/Cylinder Liner Modifications]]
*** [[Steam Engine Build/Cylinder Valve Seats]]
*** [[Steam Engine Build/Cylinder End Mount]]
*** [[Steam Engine Build/Exhaust Plenum]]
** [[Steam Engine Build/Valve Assembly]]
*** [[Steam Engine Build/Valve]]
*** [[Steam Engine Build/Valve Cover]]
*** [[Steam Engine Build/Cylinder Mounting Bracket]] - Deprecated: this part has been merged into [[Steam Engine Build/Valve Cover]].
** [[Steam Engine Build/Base Plate Calculations]]
** [[Steam Engine Build/Base Plate]]
** [[Steam Engine Build/Oil Dribbler]]
** [[Steam Engine Build/Optional Sensor Vent]]
** [[Steam Engine Build/Crankshaft Assembly]]
*** [[Steam Engine Build/Shaft]]
*** [[Steam Engine Build/Crank]]
*** [[Steam Engine Build/Pillow Block]]
*** [[Steam Engine Build/Flywheel]]
* '''Buy It'''
** [[Buy Steam Engine]]
* '''User Manual'''
** [[Steam Engine user's manual]]

=Steam Engine Applications=

* [[Turn of the Century Farm Equipment]]
* [[Steam Cars]]
* [[Open Source Steam Power Generator]]
* [[Steam Hydrauilc Hybrid Electrical Generator]]
* [[Cyclone Engine]]
* [[Steam Powered Hydraulic Pump]]

=Steam Generators=

* [[Steam Generator]]
* [[Geo-thermal Power]]
* [[Natural Steam Sources]]
* [[CHP Stove Heat Exchanger]]
* [[Flash Steam Generator]]
* [[Solar Combined Heat Power System]]
* [[Tesla Turbine]]

=Steam and Steam Engine Technology=

* [[Crash Course in Steam]]
* [[Opposed piston opposed cylinder engine]]
* [[Brief History of the Steam Engine]]
* [[Steam Engineering Tutorial]]
* [[Steam Power Basics]]
* [[Uniflow Steam Engine]]
* [[Solar Steam Engine Selection Process]]
** [[Steam engine piston rings]]

=Other Steam Engines=

* [[Lynx Motors]]

=Steam Engine Organizations=

* Companies
** [[The Only Production Steam Engine in the World]]
** [[Tinytech]]
** Cyclone Power Technology
* Clubs
** [[Steam Automobile Club of America]]
** New England Model Engineering Society [http://www.neme-s.org/].
** Pennsylvania Live Steamers [http://www.palivesteamers.org/]
* [[Steam Engine/Museums]]
** New England Wireless and Steam Engine Museum, Rhode Island [http://www.newsm.org/].

[[Category:Steam Engine]]

Open Source Water Tester

2012-01-16T14:21:31Z

Mjn: Created page with "Sonaar Luthra is a TED fellow who as developed an open source water tester. He is planning on building a small business to manufacture the Water Canary that will test water for ..."

Sonaar Luthra is a TED fellow who as developed an open source water tester. He is planning on building a small business to manufacture the Water Canary that will test water for bacteria and other contaminants. See [http://blog.ted.com/2012/01/13/waterwise-fellows-friday-with-sonaar-luthra/] for more information.

Steam Engine

2011-12-27T16:53:01Z

Mjn: /* Status */ Updated to reflect the Mounster Design

{{GVCS Header}}

==Overview==
[[Image:Design-7-A.png|400px|thumb|Current conceptual view]]

[[Steam Engine/Index]] - topical index to all steam engine pages.

The Open Source Ecology project seeks to develop a modular, scalable, open source steam engine capable of converting steam generated by a solar collector or boiler into power that can be used to generate electricity or drive machines found in the [[Global Village Construction Set]].

{{Video}}

==Details==

See [[Steam Engine Intro]] if you are interested in the current OSE steam engine project.

* [[Steam Engine Concept]] - a conceptual description of steam engines
* [[Steam Engine Breakdown]] -
* [[Steam Engine Specifications]]
* [[Steam Engine Specifications/Geometry]]
* [[Steam Engine/Terminology]] - terms used in steam engine technology

Steam engines take energy available as high pressure, high temperature steam and convert it into reciprocal motion. This motion can then be turned into rotational motion using a crankshaft. At the start of the twentieth century, steam engines provided power for farms, factories, and transportation. They were largely replaced by internal combustion engines. The Open Source Ecology project is interested in reviving steam technology to develop a modern steam engine to provide alternatives to engines driven by gasoline or diesel - which are becoming increasingly more expensive as our world passes the point of peak oil production.

==Product Ecology==
[[Image:Steam-Engine-Product-Ecology.png|thumb|600px|0Steam Engine [[Product Ecology]]]]

{{Product Ecology

|Product={{Steam Engine}}

|From=
*{{Induction Furnace}}
*[[Steel]]

|Uses=
*{{Gasifier}}
*{{Steam Generator}}
*{{Solar Concentrator}}
*[[Heat]]
*[[Steam]]

|Creates=
*[[Electricity]]

|Enables=
*{{Electric Generator}}
*[[Greenhouse]]
*[[Aquaponics]]

}}

==Status==
The previous steam engine design is on hold pending evaluation of the [[Mounster Design]]. Marcin favors this design, but the intellectual property rights to it are unclear at this time.
[[Subject Matter Experts]] or fabricators interested in making prototypes are encouraged to contact [[Mark Norton]].

==See Also==
*[[Steam Engine Archive]]
*[[Solar Combined Heat Power System]]

{{GVCS Footer}}

Steam Engine/Research Development

2011-12-27T16:50:23Z

Mjn:

{{GVCS Header}}

==Research==

* Theory
** [[Steam Engine Research/Carnot Cycle]]
** [[Steam Engine Research/Books]]
* Engine Elements
** [[Steam Engine Research/Lubrication]]
** [[Steam Engine Research/Condenser]]
** [[Steam Engine Research/Oil Separator]]
* Design Notes
** [[Steam Engine Research/Engine Design Notes]]
** [[Steam Engine Research/Valve Design Notes]]
** [[Steam Engines]]
** [[Steam Engine Design/Historic]]
** [[Mounster Design]]
* Installations
** White Cliffs Solar Power Station
*** [[Steam Engine Design/White Cliffs]]
*** [[Steam Engine Design/White Cliffs Report]]
*** [[Steam Engine Research/Power Kinetics]]

== Joining the Steam Engine Team==

OSE policies on GVCS projects specify that only active, contributing people are considered part of the project team. While we are always looking for people to help out, we need people who are committed to making real contributions. We do not need people who want to talk about building steam engines, we need people who want to design and actually build them. If you are such a person, please fill out the [[Team Culturing Survey]] and get yourself set up with accounts on the forum and wiki. All Steam Engine documentation is publicly posted on the OSE wiki.

After joining OSE, have a look at [[Steam Engine/Things To Do]] and the Steam Engine Pivotal Project [https://www.pivotaltracker.com/projects/300681#]. Pivotal is a project management tool that allows us to track tasks that need to be done. Figure out what you are interested and what matches your skills and experiences. Then get in touch with the Steam Engine Project Manager (Mark Norton - markjnorton (at) earthlink (dot) net).

You will be given one or two tasks to complete before being invited as a full project participant. To some degree, this is a test of your commitment. More than that, it is a way of building trust in your ability to make a meaningful contribution. OSE GVCS Project teams are deliberately lean and agile. The pace can be fast at times and we need you to adapt to the current rate of development.

{{GVCS Footer}}

Steam Engine

2011-12-27T16:47:59Z

Mjn:

{{GVCS Header}}

==Overview==
[[Image:Design-7-A.png|400px|thumb|Current conceptual view]]

[[Steam Engine/Index]] - topical index to all steam engine pages.

The Open Source Ecology project seeks to develop a modular, scalable, open source steam engine capable of converting steam generated by a solar collector or boiler into power that can be used to generate electricity or drive machines found in the [[Global Village Construction Set]].

{{Video}}

==Details==

See [[Steam Engine Intro]] if you are interested in the current OSE steam engine project.

* [[Steam Engine Concept]] - a conceptual description of steam engines
* [[Steam Engine Breakdown]] -
* [[Steam Engine Specifications]]
* [[Steam Engine Specifications/Geometry]]
* [[Steam Engine/Terminology]] - terms used in steam engine technology

Steam engines take energy available as high pressure, high temperature steam and convert it into reciprocal motion. This motion can then be turned into rotational motion using a crankshaft. At the start of the twentieth century, steam engines provided power for farms, factories, and transportation. They were largely replaced by internal combustion engines. The Open Source Ecology project is interested in reviving steam technology to develop a modern steam engine to provide alternatives to engines driven by gasoline or diesel - which are becoming increasingly more expensive as our world passes the point of peak oil production.

==Product Ecology==
[[Image:Steam-Engine-Product-Ecology.png|thumb|600px|0Steam Engine [[Product Ecology]]]]

{{Product Ecology

|Product={{Steam Engine}}

|From=
*{{Induction Furnace}}
*[[Steel]]

|Uses=
*{{Gasifier}}
*{{Steam Generator}}
*{{Solar Concentrator}}
*[[Heat]]
*[[Steam]]

|Creates=
*[[Electricity]]

|Enables=
*{{Electric Generator}}
*[[Greenhouse]]
*[[Aquaponics]]

}}

==Status==
The Steam Engine is nearing the [[Steam_Engine/Manufacturing_Instructions|Prototyping phase of product development]]. [[Subject Matter Experts]] or fabricators interested in fabricating prototypes are encouraged to contact [[Mark Norton]].

==See Also==
*[[Steam Engine Archive]]
*[[Solar Combined Heat Power System]]

{{GVCS Footer}}

Mounster Design

2011-12-27T16:45:19Z

Mjn:

[[FeF]] is currently pursuing the Wally Mounster modern steam engine:
*Poppet valves
*3D cam for full cutoff control and reverse
*Complete [[Intensive and Extensive Scalability]]

<html>
<iframe src="https://player.vimeo.com/video/6670938?title=0&byline=0&portrait=0" width="400" height="270" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe></html>

(You can purchase plans for this engine from [[SACA]] for $?)
(see corresponding blog post - [http://blog.opensourceecology.org/2009/09/steam-meet-report/])

Wally Mounster of Tasmania, Australia developed a steam engine with two cylinders and a cross head cam that operates poppet valves to control the engine. It is recommended a simple, easy to build engine by Tom Kimmel, President of the Steam Automobile Club of America (SACA).

The following images are provided by Tom Kimmel:

[[Image:mounster-1.jpg|600px]]

[[Image:mounster-2.jpg|600px]]

[[Image:mounster-3.jpg|600px]]

[[Image:mounster-4.jpg|600px]]

[[Image:mounster-5.jpg|600px]]

The IP status of this design is not known at this time pending reply from Tom Kimmel.

[[Category:Modern Steam Engine]]

File:Mounster-5.jpg

2011-12-27T16:43:08Z

Mjn:

File:Mounster-4.jpg

2011-12-27T16:42:34Z

Mjn:

File:Mounster-3.jpg

2011-12-27T16:42:02Z

Mjn:

File:Mounster-2.jpg

2011-12-27T16:41:33Z

Mjn:

Mounster Design

2011-12-27T16:41:10Z

Mjn:

Wally Mounster of Tasmania, Australia developed a steam engine with two cylinders and a cross head cam that operates poppet valves to control the engine. It is recommended a simple, easy to build engine by Tom Kimmel, President of the Steam Automobile Club of America (SACA).

The following images are provided by Tom Kimmel:

[[Image:mounster-1.jpg|600px]]

[[Image:mounster-2.jpg|600px]]

[[Image:mounster-3.jpg|600px]]

[[Image:mounster-4.jpg|600px]]

[[Image:mounster-5.jpg|600px]]

The IP status of this design is not known at this time pending reply from Tom Kimmel.

Mounster Design

2011-12-27T16:40:50Z

Mjn:

Wally Mounster of Tasmania, Australia developed a steam engine with two cylinders and a cross head cam that operates poppet valves to control the engine. It is recommended a simple, easy to build engine by Tom Kimmel, President of the Steam Automobile Club of America (SACA).

The following images are provided by Tom Kimmel:

[[Image:mounster-1.jpg|600px]]

[[Image:mounster-2.jpg]]

[[Image:mounster-3.jpg]]

[[Image:mounster-4.jpg]]

[[Image:mounster-5.jpg]]

The IP status of this design is not known at this time pending reply from Tom Kimmel.

File:Mounster-1.jpg

2011-12-27T16:40:19Z

Mjn:

Mounster Design

2011-12-27T16:39:52Z

Mjn: Created page with "Wally Mounster of Tasmania, Australia developed a steam engine with two cylinders and a cross head cam that operates poppet valves to control the engine. It is recommended a sim..."

Wally Mounster of Tasmania, Australia developed a steam engine with two cylinders and a cross head cam that operates poppet valves to control the engine. It is recommended a simple, easy to build engine by Tom Kimmel, President of the Steam Automobile Club of America (SACA).

The following images are provided by Tom Kimmel:

[[Image:mounster-1.jpg]]

[[Image:mounster-2.jpg]]

[[Image:mounster-3.jpg]]

[[Image:mounster-4.jpg]]

[[Image:mounster-5.jpg]]

The IP status of this design is not known at this time pending reply from Tom Kimmel.

Steam Engine/Index

2011-12-27T16:35:58Z

Mjn:

{{Category=Steam Engine}}
{{ToolTemplate|ToolName=Steam Engine}}

Wiki pages related to the OSE Steam Engine Project are organized by topics here. For an alphabetical index, see the "Steam Engine" link at the bottom of this page.

=Steam Engine Project=

* '''Theory and Research'''
** [[Steam Engine]] - technology entry page.
** Theory
*** [[Steam Engine Research/Carnot Cycle]]
*** [[Steam Engine Research/Books]]
** Engine Elements
*** [[Steam Engine Research/Lubrication]]
*** [[Steam Engine Research/Condenser]]
*** [[Steam Engine Research/Oil Separator]]
** Design Notes
*** [[Steam Engine Research/Engine Design Notes]]
*** [[Steam Engine Research/Valve Design Notes]]
*** [[Steam Engines]]
*** [[Steam Engine Design/Historic]]
** Installations
*** White Cliffs Solar Power Station
**** [[Steam Engine Design/White Cliffs]]
**** [[Steam Engine Design/White Cliffs Report]]
**** [[Steam Engine Research/Power Kinetics]]
* '''Project Overview'''
** [[GVCS Tools Status]]
** [[Steam Engine/Things To Do]]
** [[Steam Engine Intro]]
** [[Steam Engine Concept]]
** [[Steam Engine Breakdown]]
** [[Steam Engine Correspondence]]
*** [[Steam Engine/Correspondence]]
*** [[Steam Engine Correspondence/Kennedy]]
*** [[Steam Engine Correspondence/SolarAndThermal.com]]
*** [[Steam Engine Correspondence/Josh Jordan]]
*** [[Steam Engine Correspondence/Damien Gendron]]
*** [[Steam Engine Correspondence/Ron Whaley]] - Principle steam engine designer for PKI/White Cliffs
** [[Steam Engine/Terminology]]
** [[Steam Engine Planning]]
** [[Steam Engine Questions]]
** [[Steam Engine Marketing Plan]]
** [[Steam Engine/Spec Metric]]
** [[OS2 Steam Engine Team]]
** [[Mark J Norton/OSE Work]]
** [[:Category: Steam_Engine_Images]]
** [[Steam Engine/Safety Issues]]
** [[Steam Engine/Others]] - Commercial providers of steam engines, etc.
** [[Steam Engine Status/Open Hardware Summit 2011]]
* '''Development'''
** [[Steam Engine Development]]
** [[Steam Engine Development/Schedule]]
* '''Design'''
** Engine Design
*** [[Steam Engine Design/2009]]
*** [[Steam Engine Design]] - Arrowhead Bump Valve
*** [[Mounster Design]] - Wally Mounster Design by way of SACA and Tom Kimmel
*** [[Electronic Valve Engine]]
*** [[Solenoid Design]]
*** [[Steam Engine Design/Multiple Cylinders]]
*** Motor Driven Rotating Valve
*** [[Steam Engine Design/Suggestions]]
** [[Steam Engine Design/Valves]] - Valve Design Patterns
*** [[Steam Engine Design/Bump Valve]]
*** [[Steam Engine Design/Piston Valve]]
*** [[Steam Engine Design/Slide Valve]]
*** [[Steam Engine Design/Solenoid]]
*** [[Steam Engine Design/Rotating Valve]]
*** [[Steam Engine Design/Pressure Relief Valve]]
*** [[Electric Valves for Steam Engine]]
** Crankshaft Designs
*** [[Steam Engine Crank]]
*** [[Steam Engine Crank/Eccentric]]
*** [[Steam Engine Crank/Return Crank]]
*** [[Steam Engine Design/Crankshaft]]
** Other Parts
*** [[Steam Engine Design/Oiler]]
*** [[Steam Engine Design/Boiler]]
*** [[Steam Engine Design/Stuffing Box]]
** [[Steam Engine Reviews]] - Design reviews, etc.
*** [[Steam Engine Reviews/Arrowhead Bump Valve Summary]]
*** [[Steam Engine Reviews/Arrowhead Bump Valve]]
*** [[Steam Engine Design/Gregor]]
*** [[Steam Engine Reviews/Piston Head Stress]]
*** [[Steam Engine Reviews/Mike Stone]]
* '''Specification'''
** [[Steam Engine Specifications]]
** [[Steam Engine Specifications/Geometry]]
** [[Steam Regulations]]
** [[Steam Fittings]]
*** [[Steam Fittings/Pressure Gauge]]
** Sources
*** [[Steam Engine Specifications/Piston Ring Sources]]
*** [[Steam Engine Specifications/Cylinder Liner Sources]]
*** [[Steam Engine Specifications/Bearing Sources]]
*** [[Steam Engine Specifications/Valve Spring Sources]]
*** [[Steam Engine Specifications/Pillow Block Sources]]
*** [[Steam Engine Specifications/Pressure Sensor Sources]]
** Calculations
*** [[Steam Engine Construction Set Calculations]]
*** [[Steam Engine Efficiency]]
*** [[Steam Engine Efficiency Calculations]]
*** [[Steam Engine Efficiency and Losses]]
*** [[Steam Engine Specifications/Indicator Diagrams]]
*** [[Steam Engine Specifications/Work Diagram Construction]]
*** [[Steam Engine Specifications/Work Diagrams]]
*** [[Steam Engine Specifications/Spreadsheet]]
** Parts
*** [[Steam Engine Specifications/Piston Rings]]
*** [[Steam Engine Specifications/Cylinder Liner]]
*** [[Steam Engine Specifications/Connector Rod Bearings]]
*** [[Steam Engine Specifications/Nuts and Bolts]]
*** [[Steam Engine Specifications/Valve Spring]]
*** [[Steam Engine Specifications/Oiler]]
*** [[Steam Engine Specifications/Flywheel]]
*** [[Steam Engine Specifications/Pillow Blocks]]
** Seals
*** [[High Temperature Thread Sealer]]
*** [[Graphite Impregnated String]]
* '''Bill of Materials'''
** [[Steam Engine Bill of Materials]]
** [[Steam Engine Bill of Materials/2009]]
* '''Build Instructions'''
** [[Steam Engine Build Instructions]]
** [[Steam Engine Build/Tools]]
** [[Steam Engine Build/Piston Rings]]
** [[Steam Engine Build/Piston Assembly]]
*** [[Steam Engine Build/Piston Head]]
*** [[Steam Engine Build/Bump Valve Pin]]
*** [[Steam Engine Build/Piston Connector Rod]]
** [[Steam Engine Build/Cylinder Assembly]]
*** [[Steam Engine Build/Cylinder Case]]
*** [[Steam Engine Build/Cylinder Liner Modifications]]
*** [[Steam Engine Build/Cylinder Valve Seats]]
*** [[Steam Engine Build/Cylinder End Mount]]
*** [[Steam Engine Build/Exhaust Plenum]]
** [[Steam Engine Build/Valve Assembly]]
*** [[Steam Engine Build/Valve]]
*** [[Steam Engine Build/Valve Cover]]
*** [[Steam Engine Build/Cylinder Mounting Bracket]] - Deprecated: this part has been merged into [[Steam Engine Build/Valve Cover]].
** [[Steam Engine Build/Base Plate Calculations]]
** [[Steam Engine Build/Base Plate]]
** [[Steam Engine Build/Oil Dribbler]]
** [[Steam Engine Build/Optional Sensor Vent]]
** [[Steam Engine Build/Crankshaft Assembly]]
*** [[Steam Engine Build/Shaft]]
*** [[Steam Engine Build/Crank]]
*** [[Steam Engine Build/Pillow Block]]
*** [[Steam Engine Build/Flywheel]]
* '''Buy It'''
** [[Buy Steam Engine]]
* '''User Manual'''
** [[Steam Engine user's manual]]

=Steam Engine Applications=

* [[Turn of the Century Farm Equipment]]
* [[Steam Cars]]
* [[Open Source Steam Power Generator]]
* [[Steam Hydrauilc Hybrid Electrical Generator]]
* [[Cyclone Engine]]
* [[Steam Powered Hydraulic Pump]]

=Steam Generators=

* [[Steam Generator]]
* [[Geo-thermal Power]]
* [[Natural Steam Sources]]
* [[CHP Stove Heat Exchanger]]
* [[Flash Steam Generator]]
* [[Solar Combined Heat Power System]]
* [[Tesla Turbine]]

=Steam and Steam Engine Technology=

* [[Crash Course in Steam]]
* [[Opposed piston opposed cylinder engine]]
* [[Brief History of the Steam Engine]]
* [[Steam Engineering Tutorial]]
* [[Steam Power Basics]]
* [[Uniflow Steam Engine]]
* [[Solar Steam Engine Selection Process]]
** [[Steam engine piston rings]]

=Other Steam Engines=

* [[Lynx Motors]]

=Steam Engine Organizations=

* Companies
** [[The Only Production Steam Engine in the World]]
** [[Tinytech]]
** Cyclone Power Technology
* Clubs
** [[Steam Automobile Club of America]]
** New England Model Engineering Society [http://www.neme-s.org/].
** Pennsylvania Live Steamers [http://www.palivesteamers.org/]
* [[Steam Engine/Museums]]
** New England Wireless and Steam Engine Museum, Rhode Island [http://www.newsm.org/].

[[Category:Steam Engine]]

Modern Steam Engine Build

2011-12-27T16:16:40Z

Mjn: Spelling correction.

Talk:Civilization Starter Kit DVD v0.01

2011-12-26T15:34:02Z

Mjn:

heyo, so whats the plan with this page? are we trying to link to existing pages or create new ones? if new ones, should we make the links tree as shown? not really sure how to help. --[[User:Dorkmo|Dorkmo]] 08:54, 14 December 2011 (CET)

Yeah...I was wondering about the plan too. All I've been doing so far is trying to add links and sometimes copying text when it's not worth linking to a page with only one relevant paragraph. It looks like a lot of the headers can only be filled with content by the project managers since they're more theoretical. Personally I think it would make sense to use the index as a single-point-of-entry for a finished document, which would probably mean building exactly what you'd want printed out in a book. Let the rest of the wiki be free-form, but let this deliverable be frozen. After it's published you can always clone the entire thing into a new "index 0.02" section or whatever and put any updates or changes in that area. It's important to give people a finished document rather than make them search all over the wiki. --[[user:Matt_Maier|Matt_Maier]] 19:35z 15DEC2011

In terms of organization, maybe the actual construction steps should be front-and-center while all the supporting stuff (CAE analysis, cost comparison, etc) should be put in an appendix. The vast majority of people who are interested in this document aren't going to redesign the machine before they've even built the first one (the scaling equations are the first thing in the chapter). As it is organized now it looks like the actual construction steps, you know, the MEAT of the document, are buried in the middle of the chapter.--[[user:Matt_Maier|Matt_Maier]] 19:46z 15DEC2011

-----

I think the appendices should be shifted into the various chapters they are associated with, since there are four appendices - one for each major tool chapter. Why split up this material? It just makes it harder to use as a manual. [[User:Mjn|Mjn]] 16:34, 26 December 2011 (CET)

So, you want to build a new civilization?

2011-12-26T15:10:10Z

Mjn: Minor spelling correction.

last updated 12.25.2011

<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
<TITLE></TITLE>
<META NAME="GENERATOR" CONTENT="LibreOffice 3.3 (Unix)">
<META NAME="AUTHOR" CONTENT="Marcin ">
<META NAME="CREATED" CONTENT="20111226;353800">
<META NAME="CHANGEDBY" CONTENT="Marcin ">
<META NAME="CHANGED" CONTENT="20111226;1200900">
<STYLE TYPE="text/css">

</STYLE>
</HEAD>
<BODY LANG="en-US" DIR="LTR">
Getting
Involved
 


We
aim to make this one of the most collaborative projects in the world,
and we aim to train movement entrepreneurs dedicated to developing
distributive enterprise.
 

So,
You Want to Build a New Civilization?

 


All
right. Please go to the OSE Wiki and sign in. You will see a list of
the <A HREF="http://opensourceecology.org/wiki/GVCS">50 GVCS
technologies</A>, There is plenty of work left on the GVCS 50. Pick
one, and start contributing information. There is research and
development, where you can contribute conceptual design, analysis of
industry standards, diagrams, prior art, background research, and
other supporting information. Then comes the design stage – CAD,
calculations, simulations, CAE analysis, fabrication drawings, etc.
Peer review is useful. Then comes the build – which requires a bill
of materials., sourcing, and a facility to build. We encourage you to
work remotely and contribute test data. We invite you to write a
<A HREF="http://opensourceecology.org/wiki/Proposal_Template">Proposal
Brief</A>, and we can fund your work upon technical merit. Or you can
come for a <A HREF="http://opensourceecology.org/wiki/Dedicated_Project_Visits">Dedicated
Project Visit</A> to Factor e Farm.

 


The
first step you should take when you get involved is to fill out the
<A HREF="http://opensourceecology.org/wiki/Team_Culturing">Team
Culturing Survey</A>. This helps to provide transparency and to
introduce you to the rest of the global team. The beauty of the
project is that collaborative development is beginning to take place
24/7 around the world. We should also develop a better human
resources platform – where people are listed by their skills and
contributions, promises and delivered products – so it becomes
transparent who is doing work and fulfilling on their promises. This
applies to volunteers and paid people.

 


How
do you know what are the current priorities? First, see the Wiki, and
the basic approach is - “If it is not on the wiki, it doesn't
exist.” From this point, you have to analize the state of
development critically. If it is not clearly documented on the wiki,
it is probably in development or untested. Click on any device at the
<A HREF="http://opensourceecology.org/wiki/GVCS">50 GVCS technologies</A>
page. Ask yourself: Is there a project leader? What preliminary
research has been done? Does full CAD exist? Are full fabrication
procedures documented? Does a complete PDF of plans exist that you
can take to your local fabricator? Does economic analysis exist so
you can start your own enterprise? If not, those are to be completed
– and it is a chance for you to get involved.

 


Current
project leaders as of 12/25/11 include:

 

<OL>
<LI>
Yoonseo
Kang – CNC Circuit Mill, Inverter component of the Universal Power
Supply
<LI>
Brianna
Kufa – Ironworker Machine
<LI>
Mark
Norton – Modern Steam Engine
<LI>
Larry
Dobson – Gasifier Burner and Heat Exchanger
<LI>
James
Slade, Mike Apostol – CEB Press, LifeTrac
<LI>
Tom
Griffing – Power Cube
<LI>
Marcin
Jakubowski – CNC Torch Table, Induction Furnace
<LI>
Aaron
Makaruk – Resource Development
<LI>
Mike
Apostol – OS CAD/CAM solution


</OL>

Contact
these leaders on the latest progress.

 


The
wiki is a huge sandbox, and the magic of it is that over time, even
with many random contributions, editors organize content into a more
cohesive form. The basic product template for each of the
technologies at the <A HREF="http://opensourceecology.org/wiki/GVCS">GVCS
50</A> page contains general headings. You can search for information
on the wiki, and if you find something relevant to one of the
headings, you can edit to put the content at the right place.

 


Is
a technology of your choice not part of the official 50 GVCS list?
Then start new pages on the wiki for non-GVCS tools. The wiki is
infinitely expandable. The GVCS is only a limited but sufficient set
– limited so it remains a tractable project with a clear
deliverable. We don't really know if the choices made are the best –
but we will reevaluate after the set is done by year-end 2012. We
can't tell until we see all the devices work together as a complete
set. We just selected the 50 best ones according to <A HREF="http://opensourceecology.org/wiki/OSE_Specifications">OSE
Specifications</A> and the <A HREF="http://opensourceecology.org/wiki/Product_Selection_Metric">Product
Selection Metric</A> almost 4 years ago.

 


If
you are a subject matter expert, designer, video editor, CAD
draftsman, or other technical contributor in any of the 50
technologies – you are welcome to bid on work. We suggest you
submit a Proposal Brief. The key to the project is finding qualified
people – and we found that word of mouth and references from
trusted sources tend to provide best results. Help us find these
people. 


 


We
are also looking for full time people to join Factor e Farm –
master builder, farmer, fabrication manager, CEO, CTO, and
co-founder. With the farmer - we need to continue field testing the
equipment while feeding our team. With the builder, we want to
continue building out infrastructure, building out our electrical
grid. With the fabrication manager, we want to continue production
runs as a first-hand test of our economic significance, and to
continue building the tools that we use on site. We are looking for
startup instigators, not employees – as this type of risk-sharing
is part of the responsibility that we seek in our partners. 


 


There
are other support roles. We also welcome you to join us in resource
development – the OSE Enterprise is an open business plan that you
can use. We are working on developing remote video editing capacity,
where you can edit remotely after downloading footage from our
repository – such as YouTube. Our current plant is to use
smartphones for constant uploads of content – indexed by topic.
Then, remore editors can take the content to make quality videos from
the raw footage. We are also looking for ongoing CAD, fabrication
drawing, simulation, and analysis support for prototyping.

 


At
best, as the team grows at Factor e Farm, remote support functions
would include: 


 

<OL>
<LI>
video
editing support – ongoing instructionals
<LI>
CAD
support – converting videos with measurements into CAD files;
<LI>
Fabrication
drawings support – converting CAD files into fabrication drawings
that one can take to a local fabricator
</OL>
<OL START=3>
<LI>
CAE
support – converting CAD files into CAE analysis for structural,
thermal and other properties;
<LI>
modeling
support – animations modeling the function of machines, as part of
explanatory material 

<LI>
blogging
support – keeping track of a project with the project lead to
provide regular blog updates on a given project – such as checking
in ½ hour each week by phone and writing a blog post. Strong
journalism/reporting/creative writing skills are required to provide
context and to pique the reader's interest. This is critical as we
have a regular backlog of reporting from Factor e Farm and other
locations.
<LI>
collaboration
support – dedicated searching for allied efforts, collaborators,
peer reviewers, funding support, bidders, subject matter experts,
and any other support that 

<LI>
media
and music repository support – keeping a repository of <A HREF="http://opensourceecology.org/wiki/High_Resolution_GVCS_Media">high
resolution media</A>, graphics, diagrams, and other materials for
use in press releases, reports, and other publications; <A HREF="http://opensourceecology.org/wiki/Open_Source_Soundtracks">open
source soundtrack</A> repository for videos
<LI>
nonprofit
fundraising – join <A HREF="http://opensourceecology.org/wiki/Aaron_log">Aaron
Makaruk</A> in raising funds for OSE. See his <A HREF="http://opensourceecology.org/wiki/Contract_Aaron">sample
contract</A>.
</OL>

 

OSE
Branches and Allied Efforts

 


There
are 3 main forms of OSE-related operations: independent OSE efforts,
chartered OSE organizations, and certified OSE/GVCS Producers

 

<OL TYPE=I>
<LI>
Independent
OSE Efforts
</OL>

 


OSE
is a movement to create an open source economy by developing and
using economically significant, open source information (open product
and process design and techniques of production). OSE refers to more
than just an open source economy. The distinction is that OSE
produces not only open design, but also produces distributive
enterprise as the means to affect the economic process. On top of
this, it connects to environmental regeneration and social justice as
discussed at the OSE Paradigm section.

 


We
encourage that the OSE message be spread far and wide as the third
economic paradigm. To this end, we do not restrict anybody from using
the OSE name as long as they are following the OSE Paradigm. Others
are welcome to use the official OSE name or official logo in branding
their work or group as an independent OSE effort, without explicit
permission, if they are an individual, group, or organization.
Independent OSE Efforts are intended to promote that work of OSE,
while not demanding that any resources on the part of OSE
International.

 


To
be an independent OSE effort in good standing – the effort may be
one or more of the following:

 

<OL>
<LI>
A
user of GVCS technologies
<LI>
Doing
outreach about the OSE Paradigm
<LI>
Developer
or prototyper of GVCS technologies
<LI>
Engaging
in the development of any other, non-GVCS technologies while
publishing designs and open business models. We believe in open
everything, and the wiki is infinitely expandable. We recommend that
you publish on the <A HREF="http://opensourceecology.org/wiki/Main_Page">OSE
Wiki</A> for recognition
<LI>
An
effort for raising money (nonprofit sector or otherwise) by using
the OSE brand. In the case that you are raising money, we request
that if you use the OSE brand, that you contribute 25% of your net
funding raised to promote the work of OSE International. This money
will be used directly for GVCS prototyping in 2012, so your funding
will help the entire movement to achieve its goals faster.
</OL>

 


While
others are allowed to use the GVCS designs for profit - they are not
allowed to use the official OSE logo to brand their products. They
are welcome to sell products under their own label. If one wants to
sell products under the official OSE/GVCS label, then one is required
to become a certified OSE/GVCS producer, as discussed below.

 


If
you are using the OSE identity to run some form of operation or
effort, please let the greater community know as a matter of
courtesy, by posting your organization's name, date formed, contact
details, and activities at <A HREF="http://opensourceecology.org/wiki/Independent_OSE_Efforts">Independent
OSE Groups</A> on the wiki.

 

<OL TYPE=I START=2>
<LI>
Chartered
OSE Organizations – OSE Development Facilities
</OL>

 


OSE
has a good chance to change the world. To maintain and enhance a
strong identity as a world-changing organization that produces
transformation of economies, we are setting high standards for new
facilities. New facilities, if chartered as an official part of the
core development work of OSE, must comply with the distributive
economic goals of the OSE Paradigm. Moreover, if the OSE Paradigm is
indeed effective – then the new organization should have a
significant and visible effect on the economy – not only in terms
of achieving a post-scarcity economy on its own soil – but also in
instigating the same in surrounding communities. Visible economic and
political transformation should occur on sub-decade timescales in
these communities. A network of thousands of communities as such is
expected to arise within about 3 years of GVCS completion of year-end
2012. This is a seed for thorough global transition to the open
source economy, and to Open Source Ecology.

 


To
achieve this, a Chartered OSE Organization must be:

 

<OL>
<LI>
A
land-based facility, where the land is placed in a trust as a site
of permanent human heritage. This is intended to guarantee
continuity and significance to any new effort of this nature. 

<LI>
A
beacon of light for its local community, which demonstrates in
itself a functional community operating under the conditions of
material post-scarcity.
<LI>
A
development and education center and a place of lifelong learning,
with the ideal of creating the next generation of responsible
stewards of their communities and of the greater world in the
context of the open source economy.
<LI>
A
productive facility and a product development center capable of
producing all of its essential needs from local resources.
<LI>
A
change agent for surrounding communities, the success of which is
measured by the adoption of open source economic and OSE practices
in the surrounding communities
<LI>
Populated
by full-time individuals who live a post-scarcity economy lifestyle
– where a high standard of living is achieved from local
productivity.
</OL>

 


The
enabling technology base for such a community is the complete set of
50 GVCS tools, or a related infrastructure package that provides for
all of the community's material and energy resources.

 


The
above is not an easy task, and we are looking for initial discussions
with small core groups of movement entrepreneurs interested in
starting such new facilities. These core groups must have
demonstrated the practical, tactical, and people skills to organize
rapid learning and development efforts required for the successful
startup of such communities.

 


The
benefit of OSE-chartered status is the publicity, funding, and access
that comes from that relationship. We are willing to consider other
types of chartered organizations under specific terms. Otherwise,
another route is operating as an independent OSE effort as in the
previous section.

 


 

<OL TYPE=I START=3>
<LI>
Certified
OSE Producers


</OL>

OSE
International is currently developing training programs and
infrastructures for producer training. Typically, a producer is a
skilled craftsman who picks up additional skills during a build of
one or more complete machines as part of their training. Another
route to producer training is for independent producers to submit
finished copies of devices for quality control approval by members of
the OSE International certification committee. 


 


Certified
producers may sell under the OSE brand. OSE can provide marketing
assistance. In return for certification, OSE Certified Producers are
required to pay 5% of their net. This funding goes to support the
development of the GVCS and the replication of OSE Development
Facilities. Non-certified producers do not have to pay a license fee
if they sell under their own label. 


 

Chartered
OSE Organizations

 


Becoming
a chartered OSE Organization is not a task to be taken lightly, as
the goal of OSE as a movement is to produce disruptive change.
Starting a branch means creating the substance of the next economy.
Our goal is to create a strong identity for OSE as a clear and
positive change agent who delivers tangible results. Anything short
of this is diluting the message, and does not help the movement as a
whole.

 


If
you would like to be endorsed as an official OSE facility, the first
thing is a charter – defining your goals clearly. This includes the
resources you aim to secure, distributive enterprises that you aim to
develop – and the team that will help you get there.

 We
are interested in assisting startup facilities in the full
capitalization and infrastructure to create powerful development and
productive facilities – starting with land. To facilitate this –
we suggest that the timing for this would occur after the 50 GVCS
tools are developed, or after Dec. 21, 2012. The reason for this is
that once the 50 tools are available, startup costs will be decreased
significantly – perhaps from $1M for a new facility to $100k. 


 


We
aim to provide startup assistance in the form of immersion training
and capitalization assistance. We suggest that a core team of 2-4
people come to Factor e Farm for 6 months of immersion training. The
core team would pick up a wide range of practical village
construction skills – from digital fabrication, integrated
agriculture, renewable energy, housing construction, and others. This
training may be funded by grants or production earnings.
 

Capitalization
Assistance Model

 


During
the immersion training, trainees will have a chance to build real
products that can be sold. With the economic power of the GVCS and
social capital of OSE, marketing is not expected to be a barrier to
successful fundraising by production. We expect that a single trainee
should be able to generate $5k of value per month, assuming ½ time
participation in production at 50% capacity compared to a
professional fabricator. We have initial evidence that with proper
guidance and sound ergonomic design of the workshop – this is a
realistic proposition. For a 6 month duration, that is $30k value
generated per person. This is sufficient to generate significant
capital for startup. If the cost of training is $10k per person, then
a core team of 4 trainees can leave their 6 month immersion training
with: (1), a highly integrated, practical skill set covering all
sectors of the productive economy (agriculture, construction, energy,
technology); (2), connection to a network of change agents around the
globe; and (3), $80k of startup capital for their own facility.

 


This
is the type of commitment that we expect from startup instigators in
other locations around the world – if the expectation is full
endorsement and support from OSE headquarters.

 

Note
On Strategy
 


In
2013, we will be expanding to other goods and services, but for now,
we are focusing on the GVCS 50 as the strategic core. Once developed,
this will provide the track record, process, and economic power to
diversify into other products and to facilitate the creation of
communities, enterprises, and new countries. Remember that this is an
Apollo Program for the GVCS – and we expect to finish the 50 beta
product releases by December 21, 2012. If things continue as they are
now, we may be done ahead of schedule. Completion of the GVCS
provides everyone with a much larger index of possibilities for 2013.

 


Strategically,
OSE International is putting all its effort into securing and
allocating the $5.5M that it will take to develop the GVCS 50 by
year-end 2012. This is a monumental organizational task, and it
requires our full attention. Anything not related to this plan is a
distraction to the core effort. We ask the rest of the community to
help out in the GVCS 50, and in particular, in the Factor e Farm
experiment. This focus has to happen for only 1 year. Access to all
the 50 technologies will mean about a 10x reduction in startup cost
of any new OSE-related effort. The GVCS 50 is key to viral
replication. Therefore, it is better for the whole movement that all
effort is spent on the GVCS 50 – and get it done even ahead of
schedule. Then, the possibility of viral replication will be real. 


 


If
you are considering replication right now – you have to consider
that we have only 4 beta product releases – which does not address
fuel, power, or fabrication aspects of a robust community. Yes, new
facilities can be built right now – but at high startup costs. My
personal frustration is that everyone thinks that we have all the
technology already. We don't – we are in development – and
moreover, these products need to go through the thousands of hours
necessary for general adoption by the rest of the world. As such I
ask this Christmas day that we all work together to get there, and
magic will follow.

 


I
know that many people are itching to get involved – this was
exactly my state about 6 years ago. I found out that access to the
enabling tools crushed my whole initial plan. That is a condition
that anyone will still face today – until many more of the GVCS 50
tools are done. We have too few of the tools developed as of yet to
make replication a painless process. Even with all the tools
available – there are enough things that can go wrong – that my
best advice to anyone is not to do this until all the tools are
available. It will simply be easier for everybody involved.

 


We
would like to continue making this one of the most collaborative
projects in the world: open engineering, open economic development,
and distributive enterprise for the common good. Let's work together
to make this happen.

 

</BODY>
</HTML>
[[Category:Civilization Starter Kit DVD v0.01]]

IBM International Foundation

2011-12-06T17:58:44Z

Mjn: Added usings to facility size.

[http://opensourceecology.org/w/images/e/ea/Open_Source_Ecology_-_IBM_International_Foundation_-_Initial_Proposal.pdf IBM International Foundation - Initial Proposal.pdf]

[http://opensourceecology.org/w/images/1/1f/Open_Source_Ecology_-_IBM_International_Foundation_-_Initial_Proposal.odt IBM International Foundation - Initial Proposal.odt]

<center>'''[http://www.ibm.com/ibm/responsibility/grant_information.html IBM International Foundation] - $200,000'''
''by [http://opensourceecology.org/wiki/Aaron_Makaruk Aaron Makaruk]''

''Submitted 12/5/11''

</center>

'''Open Source Ecology''' (OSE) is a network of farmers, engineers, and supporters engaged in creating the Global Village Construction Set (GVCS), a low-cost, high-performance, open-source, do-it-yourself platform that allows for the easy fabrication of the 50 industrial machines that it takes to build a small civilization with modern comforts. The GVCS includes machinery, equipment, tools, components, and other infrastructures for creating a complete economy: food, fuel, energy, building materials, transportation, and fabrication.

Our goal is to encourage the development of localized industrial enterprises by simplifying the designs and lowering costs associated with fabricating productive machinery. For example, our designs can be created up to eight times more cheaply than it costs to purchase a retail counterpart and made with low-grade, abundant, local resources.

For each machine, through the open source platform, we include the following: (1) design rationale; (2) 3D CAD files; (3) 2D fabrication drawings; (4) CAE analyses; (5) CAM files (where applicable); (6) exploded parts diagrams; (7) bills of materials and sourcing information; (8) scaling calculations; (9) A-Z instructionals; and (10) cost and performance comparisons to industry standards. All documentation is openly available on our website, along with high-quality video tutorials showing how to fabricate the machinery. The website also includes a community-developed wiki, online forum, and blog for assisting independent replications of our designs.

Open Source Ecology was founded by Marcin Jakubowski, PhD in 2003. He is a graduate from Princeton University and a 2011 TED Fellow . OSE has successfully designed, prototyped, field-tested, and documented four of the 50 designs: the tractor, compressed earth brick press, soil pulverizer, and hydraulic power unit. We are finalizing construction of a 5,000 sq. ft. fabrication facility, using machinery we designed and built, in preparation for our rollout plan for the remaining GVCS machines throughout 2012.

Since many of our outputs and outcomes are tangible products, tracking our progress is fairly straightforward. We have established a ten-point standard for the GVCS: open-source, low-cost, modular, user-serviceable, do it yourself, closed loop manufacturing, high performance, flexible fabrication, distributive economics, and industrial efficiency. Furthermore, given the collaborative nature of open source design, quality control essentially takes place with multiple redundancies.

Open Source Ecology has partnered with The Terra Foundation of California as its 501c3 fiscal sponsor. We have diversified our income to include support from foundations, private contributors, and a micro-funding program called the True Fan campaign, where individuals pledge $10/month, which currently has over 440 members. We also were selected for a $60,000 grant from the Kauffman Foundation and received a $60,000 anonymous contribution to help construct our fabrication and training facilities. Further, we recently completed a successful Kickstarter campaign for $63,573, which we felt was a proud demonstration of our broad public support.

Our funding request covers partial completion of the Global Village Construction Set. This involves designing, prototyping, field-testing, and documenting the machinery as well as the material costs of the equipment. The following is a complete list of estimated costs associated with finalizing the entire GVCS set:

<div class="WordSection1">

 

Global
Village Construction Set – Design and Prototype Cost Estimates

<table class="MsoTableMediumShading1Accent5" border="1" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse;
border:none">
<tr>
<td width="50%" valign="top" style="width:50.0%;border:solid #78C0D4 1.0pt;
border-right:none;background:#4BACC6;padding:0in 5.4pt 0in 5.4pt">
Machine
</td>
<td width="50%" valign="top" style="width:50.0%;border:solid #78C0D4 1.0pt;
border-left:none;background:#4BACC6;padding:0in 5.4pt 0in 5.4pt">
Design/Prototype Costs
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
 
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
 
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
3D Printer
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
external design
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
3D Scanner
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Aluminum Extractor 
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Backhoe
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Bakery Oven
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Baler
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Bioplastic Extruder
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Bulldozer
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$105,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
CEB Press
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
completed
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Cement Mixer
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$9,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Chipper/Hammermill
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$15,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
CNC Circuit Mill
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$3,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
CNC Precision/Multi-machine
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$50,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
CNC Torch Table/Router Table
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$15,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Dairy Milker
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$30,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Dimensional Sawmill
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$29,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Electric/Motor Generator
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Gasifier Burner
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Hay Cutter
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$15,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Hay Rake
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$30,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Hydraulic Motors
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Induction Furnace
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Industrial Robot
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$22,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Ironworker Machine
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Laser Cutter
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Metal Rolling
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Micro-Combine
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$90,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
MicroTrac
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Modern Steam Engine
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$90,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Nickel-Iron Batteries
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$90,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Open Source Automobile
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$90,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Open Source Truck
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$90,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Pelletizer
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$9,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Plasma Cutter
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Power Cube
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
completed
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Press Forge
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Rod and Wire Mill
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Rototiller
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
completed
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Soil Pulverizer
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
completed
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Solar Concentrator
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$30,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Spader
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Steam Generator
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Tractor
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
completed
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Trencher
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$15,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Universal Auger
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$9,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Universal Power Supply
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Universal Seeder
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$30,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Universal Welder
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
Well-Drilling Rig
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
$45,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Wind Turbine – 50kW
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$150,000
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
padding:0in 5.4pt 0in 5.4pt">
 
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
padding:0in 5.4pt 0in 5.4pt">
 
</td>
</tr>
<tr>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
solid #78C0D4 1.0pt;border-bottom:solid #78C0D4 1.0pt;border-right:none;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
Total
</td>
<td width="50%" valign="top" style="width:50.0%;border-top:none;border-left:
none;border-bottom:solid #78C0D4 1.0pt;border-right:solid #78C0D4 1.0pt;
background:#D2EAF1;padding:0in 5.4pt 0in 5.4pt">
$2,531,000
</td>
</tr>
</table>

 

</div>

Our intention with the development of the Global Village Construction set is to create affordable industrial machinery that requires minimal upfront capital investments. As individuals and communities begin using these designs, our task is to train producers in the implementation of open source, distributive enterprises. We feel that this effort will ultimately reinvigorate the economy from the ground up, and we would like to invite The IBM International Foundation to partner with us in this endeavor.

Thank you for considering our request for a grant in the amount of '''$200,000'''.

[[Category:Funding]] [[Category:Grant Proposals]]

Talk:CEB 3D Printer

2011-11-07T20:37:21Z

Mjn: Created page with "Nice animation, but as the wall gets higher, picking up new bricks is a problem. The support lines for the grabber go through the wall in this video. In real life, they would g..."

Nice animation, but as the wall gets higher, picking up new bricks is a problem. The support lines for the grabber go through the wall in this video. In real life, they would get caught on the previously built wall. Naturally, if the support towers were high enough, you could probably get around this. Alternatively, you need some kind of x-y-z hoist. [[User:Mjn|Mjn]] 21:37, 7 November 2011 (CET)

File:Steam-hydraulic-pump-3.png

2011-11-07T20:28:52Z

Mjn:

File:Steam-hydraulic-pump-2.png

2011-11-07T20:28:15Z

Mjn:

Steam Powered Hydraulic Pump

2011-11-07T20:27:50Z

Mjn:

[[Category:Steam Engine]]

[[Image:steam-hydraulic-pump-1.png]]

[[Image:steam-hydraulic-pump-2.png]]

[[Image:steam-hydraulic-pump-3.png]]

Steam Powered Hydraulic Pump

2011-11-07T12:53:30Z

Mjn:

[[Category:Steam Engine]]

[[Image:steam-hydraulic-pump-1.png]]

File:Steam-hydraulic-pump-1.png

2011-11-07T12:53:11Z

Mjn:

Steam Powered Hydraulic Pump

2011-11-07T12:52:22Z

Mjn: Created page with "Category:Steam Engine Image:steam-hydraulic-pump.png"

[[Category:Steam Engine]]

[[Image:steam-hydraulic-pump.png]]

Steam Engine/Index

2011-11-07T12:50:03Z

Mjn: /* Steam Engine Applications */

{{Category=Steam Engine}}
{{ToolTemplate|ToolName=Steam Engine}}

Wiki pages related to the OSE Steam Engine Project are organized by topics here. For an alphabetical index, see the "Steam Engine" link at the bottom of this page.

=Steam Engine Project=

* '''Theory and Research'''
** [[Steam Engine]] - technology entry page.
** Theory
*** [[Steam Engine Research/Carnot Cycle]]
*** [[Steam Engine Research/Books]]
** Engine Elements
*** [[Steam Engine Research/Lubrication]]
*** [[Steam Engine Research/Condenser]]
*** [[Steam Engine Research/Oil Separator]]
** Design Notes
*** [[Steam Engine Research/Engine Design Notes]]
*** [[Steam Engine Research/Valve Design Notes]]
*** [[Steam Engines]]
*** [[Steam Engine Design/Historic]]
** Installations
*** White Cliffs Solar Power Station
**** [[Steam Engine Design/White Cliffs]]
**** [[Steam Engine Design/White Cliffs Report]]
**** [[Steam Engine Research/Power Kinetics]]
* '''Project Overview'''
** [[GVCS Tools Status]]
** [[Steam Engine/Things To Do]]
** [[Steam Engine Intro]]
** [[Steam Engine Concept]]
** [[Steam Engine Breakdown]]
** [[Steam Engine Correspondence]]
*** [[Steam Engine/Correspondence]]
*** [[Steam Engine Correspondence/Kennedy]]
*** [[Steam Engine Correspondence/SolarAndThermal.com]]
*** [[Steam Engine Correspondence/Josh Jordan]]
*** [[Steam Engine Correspondence/Damien Gendron]]
*** [[Steam Engine Correspondence/Ron Whaley]] - Principle steam engine designer for PKI/White Cliffs
** [[Steam Engine/Terminology]]
** [[Steam Engine Planning]]
** [[Steam Engine Questions]]
** [[Steam Engine Marketing Plan]]
** [[Steam Engine/Spec Metric]]
** [[OS2 Steam Engine Team]]
** [[Mark J Norton/OSE Work]]
** [[:Category: Steam_Engine_Images]]
** [[Steam Engine/Safety Issues]]
** [[Steam Engine/Others]] - Commercial providers of steam engines, etc.
** [[Steam Engine Status/Open Hardware Summit 2011]]
* '''Development'''
** [[Steam Engine Development]]
** [[Steam Engine Development/Schedule]]
* '''Design'''
** Engine Design
*** [[Steam Engine Design/2009]]
*** [[Steam Engine Design]] - Arrowhead Bump Valve
*** [[Electronic Valve Engine]]
*** [[Solenoid Design]]
*** [[Steam Engine Design/Multiple Cylinders]]
*** Motor Driven Rotating Valve
*** [[Steam Engine Design/Suggestions]]
** [[Steam Engine Design/Valves]] - Valve Design Patterns
*** [[Steam Engine Design/Bump Valve]]
*** [[Steam Engine Design/Piston Valve]]
*** [[Steam Engine Design/Slide Valve]]
*** [[Steam Engine Design/Solenoid]]
*** [[Steam Engine Design/Rotating Valve]]
*** [[Steam Engine Design/Pressure Relief Valve]]
*** [[Electric Valves for Steam Engine]]
** Crankshaft Designs
*** [[Steam Engine Crank]]
*** [[Steam Engine Crank/Eccentric]]
*** [[Steam Engine Crank/Return Crank]]
*** [[Steam Engine Design/Crankshaft]]
** Other Parts
*** [[Steam Engine Design/Oiler]]
*** [[Steam Engine Design/Boiler]]
*** [[Steam Engine Design/Stuffing Box]]
** [[Steam Engine Reviews]] - Design reviews, etc.
*** [[Steam Engine Reviews/Arrowhead Bump Valve Summary]]
*** [[Steam Engine Reviews/Arrowhead Bump Valve]]
*** [[Steam Engine Design/Gregor]]
*** [[Steam Engine Reviews/Piston Head Stress]]
*** [[Steam Engine Reviews/Mike Stone]]
* '''Specification'''
** [[Steam Engine Specifications]]
** [[Steam Engine Specifications/Geometry]]
** [[Steam Regulations]]
** [[Steam Fittings]]
*** [[Steam Fittings/Pressure Gauge]]
** Sources
*** [[Steam Engine Specifications/Piston Ring Sources]]
*** [[Steam Engine Specifications/Cylinder Liner Sources]]
*** [[Steam Engine Specifications/Bearing Sources]]
*** [[Steam Engine Specifications/Valve Spring Sources]]
*** [[Steam Engine Specifications/Pillow Block Sources]]
*** [[Steam Engine Specifications/Pressure Sensor Sources]]
** Calculations
*** [[Steam Engine Construction Set Calculations]]
*** [[Steam Engine Efficiency]]
*** [[Steam Engine Efficiency Calculations]]
*** [[Steam Engine Efficiency and Losses]]
*** [[Steam Engine Specifications/Indicator Diagrams]]
*** [[Steam Engine Specifications/Work Diagram Construction]]
*** [[Steam Engine Specifications/Work Diagrams]]
*** [[Steam Engine Specifications/Spreadsheet]]
** Parts
*** [[Steam Engine Specifications/Piston Rings]]
*** [[Steam Engine Specifications/Cylinder Liner]]
*** [[Steam Engine Specifications/Connector Rod Bearings]]
*** [[Steam Engine Specifications/Nuts and Bolts]]
*** [[Steam Engine Specifications/Valve Spring]]
*** [[Steam Engine Specifications/Oiler]]
*** [[Steam Engine Specifications/Flywheel]]
*** [[Steam Engine Specifications/Pillow Blocks]]
** Seals
*** [[High Temperature Thread Sealer]]
*** [[Graphite Impregnated String]]
* '''Bill of Materials'''
** [[Steam Engine Bill of Materials]]
** [[Steam Engine Bill of Materials/2009]]
* '''Build Instructions'''
** [[Steam Engine Build Instructions]]
** [[Steam Engine Build/Tools]]
** [[Steam Engine Build/Piston Rings]]
** [[Steam Engine Build/Piston Assembly]]
*** [[Steam Engine Build/Piston Head]]
*** [[Steam Engine Build/Bump Valve Pin]]
*** [[Steam Engine Build/Piston Connector Rod]]
** [[Steam Engine Build/Cylinder Assembly]]
*** [[Steam Engine Build/Cylinder Case]]
*** [[Steam Engine Build/Cylinder Liner Modifications]]
*** [[Steam Engine Build/Cylinder Valve Seats]]
*** [[Steam Engine Build/Cylinder End Mount]]
*** [[Steam Engine Build/Exhaust Plenum]]
** [[Steam Engine Build/Valve Assembly]]
*** [[Steam Engine Build/Valve]]
*** [[Steam Engine Build/Valve Cover]]
*** [[Steam Engine Build/Cylinder Mounting Bracket]] - Deprecated: this part has been merged into [[Steam Engine Build/Valve Cover]].
** [[Steam Engine Build/Base Plate Calculations]]
** [[Steam Engine Build/Base Plate]]
** [[Steam Engine Build/Oil Dribbler]]
** [[Steam Engine Build/Optional Sensor Vent]]
** [[Steam Engine Build/Crankshaft Assembly]]
*** [[Steam Engine Build/Shaft]]
*** [[Steam Engine Build/Crank]]
*** [[Steam Engine Build/Pillow Block]]
*** [[Steam Engine Build/Flywheel]]
* '''Buy It'''
** [[Buy Steam Engine]]
* '''User Manual'''
** [[Steam Engine user's manual]]

=Steam Engine Applications=

* [[Turn of the Century Farm Equipment]]
* [[Steam Cars]]
* [[Open Source Steam Power Generator]]
* [[Steam Hydrauilc Hybrid Electrical Generator]]
* [[Cyclone Engine]]
* [[Steam Powered Hydraulic Pump]]

=Steam Generators=

* [[Steam Generator]]
* [[Geo-thermal Power]]
* [[Natural Steam Sources]]
* [[CHP Stove Heat Exchanger]]
* [[Flash Steam Generator]]
* [[Solar Combined Heat Power System]]
* [[Tesla Turbine]]

=Steam and Steam Engine Technology=

* [[Crash Course in Steam]]
* [[Opposed piston opposed cylinder engine]]
* [[Brief History of the Steam Engine]]
* [[Steam Engineering Tutorial]]
* [[Steam Power Basics]]
* [[Uniflow Steam Engine]]
* [[Solar Steam Engine Selection Process]]
** [[Steam engine piston rings]]

=Other Steam Engines=

* [[Lynx Motors]]

=Steam Engine Organizations=

* Companies
** [[The Only Production Steam Engine in the World]]
** [[Tinytech]]
** Cyclone Power Technology
* Clubs
** [[Steam Automobile Club of America]]
** New England Model Engineering Society [http://www.neme-s.org/].
** Pennsylvania Live Steamers [http://www.palivesteamers.org/]
* [[Steam Engine/Museums]]
** New England Wireless and Steam Engine Museum, Rhode Island [http://www.newsm.org/].

[[Category:Steam Engine]]