Open Source Ecology - User contributions [en]

Infirmation Architect

2012-08-03T21:34:32Z

Jetbeard: moved Infirmation Architect to Information Architect

#REDIRECT [[Information Architect]]

Information Architect

2012-08-03T21:34:32Z

Jetbeard: moved Infirmation Architect to Information Architect

=Information Architect=

*Follows up with FeF development team and organizes all documentation for transparency, review, and access to external audiences
*Works with remote developers to organize their documentation on OSE wiki for transparency, review, and access to external audiences
*Develops information architecture for Control Panel
*Focuses on access, clarification, refactoring, and collation of information as opposed to content creation
*Collects readily-available documentation/diagrams/explanations and adapts it to OSE wiki as supporting documentation
*Works with [[Learning Facilitator]] to develop OSE Campus curriculum
*Excellent proficiency in open source graphics software: diagramming software, Gimp, Inkscape or willingness to learn them
*Consults with development team for explanations and upgrades to existing documentation, diagrams, graphics, etc.

[[Category:Distillations]][[Category:Recruiting]]

Car/Correspondence

2012-08-03T10:37:47Z

Jetbeard: Fixed broken category.

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

=March 6, 2012=

I got an email today from a guy who'd run across this press release link:

https://docs.google.com/document/d/1hocj_UERHhz2XX6YDfRM6ELfI2Wr60VBbkp38Nv9rLg/edit

In brief, it announces the OSE partnership with Wikispeed re the OS Car, it quotes Joe Justice and Marcin and it's dated February 24. So it looks like the decision was made a good while ago. It would have saved the rest of us some time if we'd known, but such is life.

If you're wondering about the non sequiturs, and why some of us were still discussing points that had been settled, it's because the majority of contributors to this discussion weren't privy to the upper levels of correspondence and weren't getting cc'ed as the decisions were made.

This post may mark the end of the Car/Correspondence page. I suspect it is far from a complete record of the car correspondence, and with the subject of the discussion determined, missing messages are moot and there's not much left to dicuss.
[JackMcCornack 3/6/2012]

PS--Here's the text of the press release, but you'll need to click the link above to see the illustrations and get access to the other links.

Enabling Emerging Markets to Manufacture Their Own Ultra-efficient
Transportation, WIKISPEED and Open Source Ecology Announce Partnership
in Open-Hardware Movement

Seattle, WA, and Maysville, MO, USA (February 24, 2012)

The open-hardware movement got a tremendous boost today when WIKISPEED,
an innovative automotive company building modular, high-performance cars
using agile design principles, and Open Source Ecology (OSE), a group
committed to providing free plans and processes necessary for building
the global economy, announced that they are teaming up to revolutionize
transportation in the developing world.

Taking on traditional, proprietary manufacturing R & D, the two
companies aim to create an open-source product-development methodology
that would allow communities around the world to quickly develop their
own machinery and processes to support themselves, removing a dependency
on industrialized nations for costly solutions.

OSE CEO Marcin Jakubowski is developing the Global Village Construction
Set, identifying essential machines that are required to build and
maintain an entire economy. Jakubowski’s work includes publishing the
blueprints for each piece of equipment and making the plans available
for free via the Internet.

Above: Open Source Ecology is developing the Global Village Construction
Set, the minimum set of tools and machinery for any community to produce
and maintain a modern infrastructure in its entirety.

For his part, Joe Justice, founder and team lead of WIKISPEED, has
pioneered the use of agile rapid-delivery processes (the same method
used by leading software companies) for physical manufacturing and
complex problem solving. This application has been highly successful,
allowing Justice to design and build a high-performance modular car that
gets 100 mpg and meets all U.S. safety standards, using a globally
distributed team, of volunteers in just three months.

Above: The Roadster is only one of WIKISPEED’s modular, configurable cars.

Together, Jakubowski and Justice will collaborate on a modular car,
which can be manufactured globally using only the Global Village
Construction Set (GVCS). OSE will adapt WIKISPEED’s current car designs,
making them compatible with their GVCS manufacturing infrastructure,
while WIKISPEED will provide automotive design, CAD for their current
ultra-efficient car, agile training, and efficiency consulting to
expedite design and development. The finished plans will be open-source
and available to anyone. The car will target the needs of developing
countries and economy transport while retaining U.S. automotive safety
standards.

According to Justice, “This is clearly the right thing to do. OSE is
creating a new template for a global village, built around devices and
equipment that even small, remote communities can maintain themselves.
The modular WIKISPEED car makes sense in a community like this, and with
OSE we will be developing a version of the car able to be produced and
maintained with the OSE Global Village Construction Set anywhere in the
world. The GVCS is completely revolutionary in enabling even small
communities to create and maintain every piece of a thriving modern
economy with contemporary comforts. Team WIKISPEED is very pleased to be
helping reduce the environmental footprint while accelerating innovation
and business productivity.”

Jakubowski calls the new collaboration a “bold and noteworthy step
toward the open-source economy, and it will serve to encourage other
change-makers to join the effort to invent distributive enterprise.”
Together, the companies will work to “unleash the collaborative
potential of the open-source hardware movement—Industry 2.0. We are
pursuing a system of optimized production where everyone has free access
to state-of-the-art product designs and blueprints, which they can, in
turn, produce within their local economy. It’s an idea whose time has come.”
About WIKISPEED
Team WIKISPEED is a green automotive-development company that builds
cars utilizing agile methodology and has prototyped a
mass-manufacturable, ultra-low-cost, 100-mpg commuter car. Based in
Seattle and led by Joe Justice, WIKISPEED is an all-volunteer
distributed agile/scrum team: members contribute their work from various
locations globally and iteratively enhance the vehicle every two weeks.
This model allows extremely high-speed development, especially when
paired with rapid-prototyping manufacturing tools.
About Open Source Ecology
Open Source Ecology, founded in 2004 by Marcin Jakubowski, Ph.D., has a
stated mission to create the open-source economy, which, according to
Jakubowski, “optimizes both production and distribution by publishing
its trade secrets openly.” Jakubowski has recently been distinguished as
a 2012 TED Senior Fellow and a Shuttleworth Foundation Fellow for his
work on the Global Village Construction Set (GVCS), an open
technological platform that allows for the easy fabrication of the fifty
different industrial machines necessary to building a small civilization
with modern comforts.

For More information:
Jakubowski’s TED talk
Justice’s TEDx talk
OSE website
Team WIKISPEED website
Shuttleworth Foundation website

[[Category:Car]]

File:Edit-copy green.svg

2012-08-03T10:34:12Z

Jetbeard: Imported from Mediawiki.

Imported from Mediawiki.

File:Ambox notice.png

2012-08-03T10:25:00Z

Jetbeard: Imported from Mediawiki.

Imported from Mediawiki.

Robert Cote

2012-08-03T10:22:20Z

Jetbeard: Remove dead image.

==Team Culturing Information==
[[File:Robert-headshot.jpg|thumb|Robert Cote]]
==='''WHO''' are you?===
*'''Robert Cote'''
*''Chandler, AZ, USA''
*''Email: robertcote@cox.net, Mobile: 480-244-7137''
*''Resume/CV -- see below''

==='''WHY''' are you motivated to support/develop this work?===
*''Do you endorse open source culture?''
Yes, whole-heartedly. My feeling is that the model of industry according to profit-based corporations has gotten out of hand. The typical modern industrial focus is on short-term profits – and the future, of our planet and our children and theirs – be damned.

Open source culture provides for putting the power back into the hands of the people. There is nothing wrong with realizing an honest profit in business, but things get out of hand when one is forced to buy certain specialized (and overpriced) products or services. And perhaps this would normalize if the currency of exchange were goods for goods, as in bartering. There is too much focus and energy put on getting rich with money, and too little on the richness of an honest, hard-working lifestyle.

*''Why are you interested in collaborating with us?''
I want to collaborate because I feel this is an idea whose time has come. I work for a military contractor, and I go to work every day for someone else’s profit, and put my energy into a cause that I don’t believe in – just to get paid and receive benefits. I am at a point in my life where I feel the quality of what I do matters to me and to the world. I want to become part of the solution, and cease to be – as I feel I am – part of the problem.

*''How do you think that the GVCS can address pressing world issues?''
I believe that the US is necessarily in the path of a major cultural change when our economy falters with the weakening of US currency. The present-day “fix” of injecting more fiat currency can only go so far before the US dollar is worthless, and the long-standing position (or illusion) of power falters. Our goods and services will become too expensive for the average person, and the gulf between the ‘haves’ and ‘have-nots’ will widen further.

The situation worsens when peak oil is considered. Our modern culture is based, more than most realize, on cheap fuel – fuel that is dwindling, and therefore will not remain cheap. The staggering scale of all this is what brings a plethora of goods to market, allows suburbs to exist for commuters, and many petroleum-based products like plastics, tires, and many others. But it also means choked freeways, planned obsolescence of vehicles, and pollution that threatens life on our planet.

*''What should happen so that you become more involved with the project?''
I am interested in finding out how I could replace my corporate job with doing an OSE-type activity, yet still provide for my family. I am not about high wages, but I do wish to be able to afford adequate medical coverage. I am wondering if there is a kind of transition program, whereby one who is “stuck” in a corporate job situation can break out gradually into the OSE culture.

Could it be possible for one, as me, to produce parts needed for one or more of the OSE Fifty Machines in my spare time? I have work space and could tool up to do so.

*''What is missing in the project?''
The only thing that I have not seen in the wiki is any reference to the music or arts as necessities of life. I know these are not skills considered necessary for survival as are food and warmth, yet you speak of the need for psychiatrists or counselors. This tells me you value those who can touch the non-physical parts of humanity, and I would argue that music and art does precisely that. I, for one, can state without hesitation that making (and listening) to music has done a great deal to maintain my sanity over the years.

Beyond that, I am confident that, given the OSE community mindset, any shortcoming would quickly be identified and addressed. There is no greater way to find what may be missing than to launch a project, during which any unfilled holes will soon become apparent.

*''What are your suggestions for improvement of the project?''
One idea for an improvement is this: Since it seems optimal to be able to attend the Factor E Farm in order to learn the skills and be steeped in the culture of the OSE, it would be good if there were a chance to do one- or two-week visits to aggregate the one-month training. This would allow persons as me who, due to present work constraints, are unable to take off four contiguous weeks, and aid in the transition from the corporate work paradigm to a community-based work situation.

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

*'''List all of your skills in these areas: Communications - Organizational - Computer Support - Finances - Design - Natural Building - Electronics - Automation - Metallurgy - Engineering - Fabrication - Agriculture - Energy - Architecture - Video/Graphics/Art - PR/Marketing - Education - Construction - Industry - CNC - Chemistry - Product Design - Other'''
As is indicated in my resume (below), I hold a BSEE degree, and am a 20-plus-year software designer/developer/tester of embedded processing systems. (I was trained in circuit design, but my first job was as embedded SW, and I have been there since.) I have used numerous real-time operating systems (RTOS), as vxWorks, Green Hills, and pSOS+. I have developed code from low-level drivers to application-level code, using C, C++, and some assembly code. I have also written a few Visual C++ GUIs. I also enjoy scripting languages as Perl, Python and Bash shell scripting.

In 2010, I earned a certification for Permaculture Design, and have applied many of the concepts and techniques in my back yard. I am dealing with the many challenges of trying to grow food plants in the desert.

Also in 2010, I attended a 7-day intensive, build-from-scratch wind turbine seminar. This was held off-grid in the mountains just west of Fort Collins, CO. A team of 7 built a 6-foot, 3-phase, axial-flux alternator. The emphasis in the class was to use easy-to-obtain materials and common construction methods, like welding and common fasteners. I purchased this unit, and it is currently in storage.

I am a life-long musician, and have played an array of instruments over the years. Most notably, I have played (and still play) the keyboards and 5-string electric bass guitar.

*''How have you already contributed to the project?''
Besides signing up as a True Fan, nothing yet.

===HOW can you help?===

*''How are you interested in contributing to the work of GVCS development?''
I would like to transition to an OSE community by gradually weaning myself from my current corporate culture work. I envision producing some needed part or parts by setting up a small “factory” in my home work space. My goal is to replace my current means of income.

Alternately, I am good with documentation, and would be willing to edit or create word processing documents, adding drawings in same, if required.

*''Can you volunteer to work with us, and if so, how many hours per week?''
I could volunteer about 5 hours a week.

*''Are you interested in working with us for pay? If so, what services can you offer, and what is your hourly or per-project rate?''
Yes, I am interested in working for pay, in an effort to gauge what would be needed to replace my current means of income.

The services I can offer are producing parts. I am skilled at optimizing a task, and creating jigs, etc., for repetitive (mass) production.

It is difficult to give an hourly rate, because I feel that my effectiveness will vary from task to task, depending upon the nature of the work. I would like to discuss this matter.

*''Are you interested in a [[Dedicated Project Visit]]?
Yes, the interest is there. However, with work and familial constraints, I am presently unable to be absent for a solid month.

*''Are you interested in purchasing equipment from us to help bootstrap development?''
Yes. I would want to discuss this. I am planning a move soon, and would want to wait until settled at the new location.

*''Are you interested in bidding for consulting/design/prototyping work?''
Yes, prototyping. Of course there are a lot of variables here, so I would want to discuss this.

*''Are you a [[True Fans|True Fan]]? If not, why not?''
Yes. I just signed up to contribute monthly.

*''Would you like to see yourself working with us on a full-time basis?''
Yes. I would work, if not physically on the Factor E Farm, then local to my own community. The OSE village concept is adaptable to any area. No offense, but Kansas City area is not my first choice.

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

If it is possible to include my family (provided they are on board with the idea), and I am not bound by a job scenario (that is, if by 2013 I am not working a corporate job), I would be quite interested. I realize these are two rather large “ifs.”

'''My Resume'''

Robert P. Cote

2338 W. Rockwell Ct

Chandler AZ 85224

480-899-6636/480-244-7137

robertcote@cox.net

Summary

Twenty years of experience in these areas:

• C Language in various OS/embedded programming environments as UNIX, Linux, Green Hills Integrity, pSOSystem and VxWorks

• Application, library and test embedded software for Analog Devices SHARC, Hammerhead, and TigerSharc DSP boards in various PCI-bus form factors

• Motorola MVME-1xx 680x0, MC68360 and MCP750 embedded, general purpose microcontrollers

• Software/Hardware interfacing (Device Drivers) for VMEbus- and PCI-bus based hardware

• Embedded Software Design and Implementation in Software Defined Radio (SDR) systems, including General Dynamics’ Digital Modular Radio (DMR), and JTRS HMS Rifleman radio

5 years of experience in:

• Relational database development for Novell PC network, using DataFlex by Data Access Corporation

Mr. Cote has more than 20 years experience in software design, development and testing for stand-alone, PCI-bus and VMEbus based systems, working with ANSI C cross compilers on UNIX, Linux and Windows hosts. Mr. Cote has also written application, production-test and device driver-level software for embedded targets such as the Analog Devices SHARC, Hammerhead and TigerSharc digital signal processors, Motorola 680x0 and MCP750 microcontrollers, and the Mercury Computer, Inc. multiple Intel I-860 compute environments. With a five-year foundation in programming custom relational database systems, Robert has well-rounded software designing, programming, and testing background.

Professional Experience

Jan 2003 to General Dynamics Decision Systems Scottsdale, AZ
Present Senior Software Engineer

Over the last three years, Robert has been an important team player in the development of a Manet (Mobile ad hoc network) radio system into a hand-held radio known as the Rifleman, being developed on the Marvell (Intel) PXA-320 General Purpose Processor using Green Hills Integrity, MULTI tool set and probes. This radio system was built on top of the JTRS HMS platform, in which multiple radios are joined in a self forming, self-regulating network, and act as conduit for voice, data and reporting of GPS position-location information.
Besides developing C++ application software for the radio, Robert implemented a Visual C++ GUI application for configuring the radios in a network, assigning frequencies, power, etc. on a per-preset basis. After creating the configuration files, this application was able to act as a FTP client and upload configuration files to the radios.
In September of 2008, Robert was assigned as Technical Task Lead to the Rifleman (version 1) team, overseeing and advising the daily work activities for a group of 12-14 software developers. Task Lead duties were staffing, feature coverage, scheduling, Change Request resolution, and integration builds management.
Current work duties include training, oversight and management of process and source code control in the Rifleman SW effort, in accord with Quality Control objectives. Rational Clear Case and Clear Quest tools are used for version control and tracking features and defect correction.
Previously at GD, Robert assisted on the Digital Modular Radio (DMR) effort as a waveform programmer with AM, FM, SINCGARS, Havequick and ATC waveforms. Mr. Cote implemented a Regenerative Repeating feature for the AM and FM waveforms, including formal design, documentation, implementation and unit testing on both a simulated environment, and on laboratory radios.

Apr 2002 to Self Employed Scottsdale, AZ
Dec 2002 Proprietor

Mr. Cote worked a home-based business during this time period. The business involved sales, marketing and management of time and resources.

Jan 2000 to Bittware, Inc. Scottsdale, AZ
Apr 2002 Senior Software Engineer

Mr. Cote worked as a Field Applications Engineer, assisting customers with Analog Devices SHARC and Hammerhead embedded DSP applications programming and debugging, by telephone and email, and on customers’ sites.
Robert also performed test embedded software design and implementation for in-house DSP board production testing, and created various software libraries and numerous example programs to add value to Bittware's line of DSP board products.

1999 - 2000 Wavo, Inc. Phoenix, AZ
Software Engineer

At Wavo, Robert inherited a VxWorks software application project from a former employee. The software controlled a box that was able to receive content data serially over a communications port or from a TCP/IP port and, in real time, inject the data into a television signal using the video blanking interval (VBI) lines. The application was an enhancement to an existing video product manufactured by Techtronix in order to add to its value.
Robert programmed the distribution of video data internally, as well as the front-panel control display, and the interface between the existing system and the added subsystem.

1997 - 1999 Ixthos, Inc. Leesburg, VA
Software Engineer

Robert's primary duty was to design, write, test and document software libraries for I/O mezzanines used on VMEbus-based Analog Devices SHARC DSP board products. Programming was done either in C or in SHARC assembler. Mezzanine types were primarily ADC and DAC of varying speed and accuracy, and digital I/O. User manuals for the I/O boards were provided with each, also written by Mr. Cote.

1996 - 1997 GRC International, Telecommunications Division Vienna VA
Software Engineer

Robert Cote worked with GRCI on a contract to Lucent Technologies, Indian Hill IL, to add features to their DACS II Digital Cross Connect product line. The features include Hybrid DS3 signal capabilities targeted at European and Asian markets. The pSOS real-time operating system kernel was employed, and debugging done with pROBE.

Mr. Cote assisted in the development of the OSU, GRCI's telecommunications management tool. The systems were developed using the pSOSystem real-time, multitasking OS kernel, and tested employing various industry standard SONET and SDH test units. Mr. Cote wrote production test software to test the OSU mother boards, including DRAM, NVRAM and FLASH memories, real time clock, I/O via a Motorola MC68360 (running in companion mode to a MC68040), as well as the optical (OC3) subsystems resident on the board.

1991 - 1996 Radix Systems, Inc. Rockville MD
Electrical Engineer

In 1995, Robert worked with a colleague on code to interface the Mercury CE environment to a SUN Sparc host. The Mercury system handled 512 simultaneous channels of real time Digital Signal Processing.
During 1994-95, Mr. Cote worked on a VME-based and FDDI networked data acquisition/signal generation system.
During 1992-93, Robert wrote the embedded control software for a simultaneous 64-channel data acquisition and 8-channel signal-generation system.
In 1991, Mr. Cote wrote the embedded code for a programmable acoustic pulse simulation unit, which was used in U. S. Navy Acoustic Research and Development.

1985 - 1990 Retail Detail, Inc. Birmingham MI
Data Processing Manager

Automated major company computational operations using DataFlex by Data Access Corp., and trained operators in both applications software and in network use. Designed and implemented custom multi-file relational databases, including applications, reports, and utilities. Supervised and maintained a Novell PC network, versions 2.14 and 3.12.

Education
2010 Wind Turbine building workshop Fort Collins CO
7-day intensive, build-from-scratch axial flux, 3-phase, wind-powered alternator

2010 DSP for Engineering Scottsdale AZ
3-day training in practical DSP

2007 Digital Communications Scottsdale AZ
3-day training in concepts of modern communication modalities

2007 Understanding TCP/IP Scottsdale AZ
2-day training in Internet Protocols and technology

2007 Intro to VHDL Programming Scottsdale AZ
4-day training in introductory gate array programming

1999 VxWorks 5-Day Training Alameda CA
Training in VxWorks and Tornado at Wind River corporate headquarters

1993 pSOS+ 2-Day Seminar Santa Clara CA
pSOS+ OS kernel and the pSOSystem components

1992 Motorola 5-Day Seminar Columbia MD
Motorola 68040 assembly language and concepts

1990 Lawrence Technological University Southfield MI
Bachelor of Science, Electrical Engineering
Focus on circuit design and hardware/software interfacing
GPA of 3.85 on a 4-point scale; Summa cum Laude

1988 Oakland Community College Oakland County MI
Pre-Engineering Curriculum
GPA of 4.00 on a 4-point scale

Security Clearance

Active Secret security clearance, granted by DISCO, June 2003.

[[Category: Team Culturing]]

File talk:Template-info.svg

2012-08-03T10:19:40Z

Jetbeard: Created page with "I just uploaded this and then it went missing. I suspect something's wrong with the wiki install. ~~~~"

I just uploaded this and then it went missing. I suspect something's wrong with the wiki install. [[User:Jetbeard|Jetbeard]] 12:19, 3 August 2012 (CEST)

File:Template-info.svg

2012-08-03T10:16:20Z

Jetbeard: uploaded a new version of "File:Template-info.svg"

Import from Mediawiki.

File:Imbox notice.png

2012-08-03T10:13:55Z

Jetbeard: Import from Mediawiki.

Import from Mediawiki.

File:Template-info.svg

2012-08-03T10:11:38Z

Jetbeard: Import from Mediawiki.

Import from Mediawiki.

Solar Concentrator

2012-08-03T00:12:05Z

Jetbeard: Wiki syntax.

{{GVCS Header}}

==Overview==
[[Image:SolarConcentrator.png|right|400px|Solar Concentrator]]

Concentrated solar power (CSP) systems, are systems that use mirrors or lenses to concentrate a large area of sunlight, or solar thermal energy, onto a small area. Electrical power is produced when the concentrated light is converted to heat which drives a heat engine (usually a steam turbine) connected to an electrical power generator.

{{Video}}

==Details==

'''Solar Concentrators'''
* [[Solar Concentrators]]
** [[Solar Concentrator Tracking]]
** [[Solar Concentrator Resources]]
** [[Solar Concentrator Links]]
** [[Solar Concentrator Reviews]]
** [[Solar Concentrator Resource Map]]
** [[Solar Concentrator Red Pages]]

'''Categories'''
*[[:Category:Solar Power]]
*[[:Category:Solar Turbine]]

==Product Ecology==
[[Image:3b-Solarenergyeco.png|right|600px]]
[[Image:SolarEconomy.jpg|right|400px]]

{{Product Ecology
|From=
* {{Induction Furnace}}
* {{Electric Motor}}
* {{Bioplastic Extruder}}

|Uses=
* [[Sunlight]]
* [[Heat]]
* [[Heat Transfer Fluid]]

|Creates=
* [[Steam]]
* [[Power]]
* [[Heat]]

|Enables=
* {{Steam Generator}}
* {{Steam Engine}}
* {{UPS}}
* [[Sintering]]
* [[CHP]]

|Components=
* [[Mirrors]]
* [[Pipe]]
* [[Fluid]]
}}

==Components==
*Mirrors
*Tubes
*Boiler
*Turbine

==Status==

The Solar Concentrator is currently in the [[Solar Concentrator/Research Development|research phase of product development.]]

==See Also==
*[[Solar Fire]]
*[[Solar Collector Calculations]]

*[http://en.wikipedia.org/wiki/Solar_concentrator Wikipedia: Solar Concentrator]
*[http://en.wikipedia.org/wiki/Solar_thermal_energy Wikipedia: Solar Thermal Energy]

{{GVCS Footer}}

Biogas

2012-08-03T00:07:44Z

Jetbeard: Wiki syntax.

{{Category=Biofuel}}
== Challenges ==
Biogas production can be problematic in temperate climates: low temperatures may lead to breakdown of microbial populations. This can potentially be overcome with insulation or earth sheltering.

Biogas can be dirty (high sulfur content etc.) Use of biogas: when used for combustion, no upgrading necessary. When intended use is internal combustion engine (transportation), biogas may need to be upgraded (cleaned).

[[File:Cooking_with_biogas.jpg|300px|thumb|right|Cooking with biogas]]

[[File:Construction_of_digester.jpg|300px|thumb|right|Construction of underground digester with bricks. This is common in rural India and China]]

==Simple Open Source Biogas System==
[http://www.supergas.dk/ Supergas] - In 1996-97 [http://www.superflex.net/ Superflex] collaborated with biogas engineer Jan Mallan to construct a simple, portable biogas unit that can produce sufficient gas for the cooking and lighting needs of an African family. The system has been adapted to meet the efficiency and style demands of a modern African consumer. It is intended to match the needs and economic resources that we believe exist in small-scale economies. The orange biogas plant produces biogas from organic materials, such as human and animal stools. For a modest sum, a family will be able to buy such a biogas system and achieve self-sufficiency in energy. The plant produces approx. 3-4 cubic meters of gas per day of the dung from 2-3 cattle. This is enough for a family of 8-10 members for cooking purposes and to run one gas lamp in the evening.

== Applications and Product Ecology ==
* biogas for cooking, heating
* [[CEB Vaults|Guastavino masonry]] or plain CEBs to build biogas digester and holding tank for stored biogas. One holding tank could be used for the storage of biogas and [[Compressed Fuel Gas|Compressed fuel gas]].
* methane for the production of [[Direct Reduced Iron|Direct reduced iron]] from rust or high-grade iron ore.
* compressed biogas for transportation / internal combustion engine
* liquid slurry from biogas tank can be used to fertilize [[duckweed]] pond
* solid contents coming out of digester can be composted (vermicompost, BSF compost, [[biochar]] compost)
* when biogas is burned inside a greenhouse, the CO2 enrichment can provide a boost to plant growth (CO2 concentrations up to 1500ppm are beneficial). This is effect widely used by commercial growers, but unfortunately they are using mostly fossil methane.
* various uses in [[:Category:Metalworks|metallurgy]]
* process bulky biomass before it can go into a digester, using [[Hammer Mill|hammer mill]]

== External Links ==
* [[appropedia:Category:Biogas|Appropedia Category: Biogas]]
* [[appropedia:Biogas_and_liquid_biofuels|Appropedia main biogas page]]
* Wikipedia: [http://en.wikipedia.org/wiki/Biogas Biogas]
* [http://p2pfoundation.net/Category:Biofuel p2pfoundation Category:Biofuel]
* [http://diy-biogas.org/ DIY Biogas] - Germany

==See Also==
* [[Biogas start up]]
* [[Biofuel]]
* [[Gasifier]]

Direct Reduced Iron (DRI)

2012-08-03T00:04:00Z

Jetbeard: moved Direct Reduced Iron (DRI) to Direct Reduced Iron: Redundant acronym in page title.

#REDIRECT [[Direct Reduced Iron]]

Direct Reduced Iron

2012-08-03T00:04:00Z

Jetbeard: moved Direct Reduced Iron (DRI) to Direct Reduced Iron: Redundant acronym in page title.

[[File:Small rotary kiln.jpg|400px|thumb|right|Small rotary kiln, Brazos County TX, 1966 (image from: Cushing Memorial Library and Archives, Texas A&M via CC license)]]

'''Direct-reduced iron (DRI)''' is a metallic material formed by the reduction (removal of oxygen) of iron oxide (iron ore) at temperatures ''below the melting point'' of iron. DRI is produced by the use of a reducing gas (mostly a mixture of hydrogen and carbon monoxide). The temperatures for this process are significantly lower than those in a blast furnace, and capital requirements are also lower. DRI may have a sponge-like structure, leading to the alternative name "sponge iron".

Suitable starting materials are very high-grade iron ores (70% iron content and up) or rusted scrap steel, which is mostly iron. These could not yet be used in an [[induction furnace]], as the reduction is a chemical reaction while induction only melts the already-reduced pure metal. India is one of the global leaders in sponge iron production, having numerous small or medium-sized facilities. DRI is commonly manufactured in a rotary kiln.

HDRI ("hot direct reduced iron"): when the still-hot iron is immediately moved for melting into an electric arc furnace or [[induction furnace]], to save energy. Caution: when HDRI is exposed to air, it may rapidly oxidize (=explode!).

==Product ecology==
* first, metal oxides would be '''extracted from clay''', possibly by using hydrofluoric acid
* reduction of metals could also be accomplished in a '''solar carbothermic''' manner (see [[Metal_Refining|metal refining]] for details)
* '''[[Induction furnace]]''' -- could be fed with HDRI for energy-efficient steel production (rapid melting because metal is already hot)
* '''[[Gasifier]]''' -- to create the reducing gas: [[Compressed_Fuel_Gas|syngas]], a mixture of H and CO
* '''[[Biogas]]''' -- methane from biogas can be turned into the H/CO mix. Globally, fossil gas (a.k.a. "natural" gas) is the most commonly used fuel for DRI, therefore biogas is a possible replacement, although it may have to be upgraded first (often contains sulfur compounds, likely a problem; abundant CO2 in biogas limits energy yield).
* '''[[Biochar]]''' -- is a charcoal-like soil amendment. It is resistant to biodegradation, i.e. it is carbon that has been permanently removed from the atmosphere. The syngas that is released during pyrolysis could be used to make DRI. If these processes are combined, with biochar as a by-product, the whole process can become '''carbon negative''' (carbon re-fossilization). Biochar could be co-composted with spent slurry from a [[biogas]] digester, generating an excellent soil amendment.
* '''Waste heat''' -- The DRI process generates waste heat that can potentially be used for pyrolyzing further biomass (pyrolysis = heating in absence of oxygen). Pyrolysis releases yet more '''syngas''' which can be fed back into the process. Everything is thus powered by biomass, generating '''[[biochar]]'''. In cold climates, any kind of waste heat can obviously be useful for heating winter greenhouses.

==Further information is needed !==
;Is this actually feasible on the small scale?
: Sure
;Does the process take place at normal atmospheric pressure?
: Yes, it can
;Can a rotary kiln be designed for the village scale?
: Yes, but this process does not have to take place in rotary kiln; the only thing that matters is good mixing.
;Are sufficient amounts of high-grade ores or rusted steel available?
: It doesn't matter. If we get the metal extraction from clays working, then we can concentrate most clays into high-grade ores.
: Scalability is feasible, but efficiency may not be as good. The processes of the largest plants can also be done on a table top. The question is - at what point does it still make sense to do so? If we have access to abundant energy, feasibility may occur at a village scale (added: CSP can serve as heat source; needs methane atmosphere).

This appears to be a good alternative for smaller scale, lower-cost process, worth adding to our general awareness.

==Other Metals==
*paper: [http://openfarmtech.org/w/images/c/c9/Halman.pdf Carbothermal reduction of alumina: Thermochemical equilibrium calculations and experimental investigation]
*paper: [http://openfarmtech.org/w/images/c/c3/Lvov.pdf Mechanism of carbothermal reduction of iron, cobalt, nickel and copper oxides]

==See Also==
* [[Metal]]
* [[Metal Refining]]
* [[Kiln]]

==External links==
* [[Wikipedia: Direct reduced iron]]
* [[Wikipedia: Sponge iron reaction]]
* [[Wikipedia: Water gas]] shift -> a way to increase the hydrogen content in syngas
* [http://www.time.com/time/magazine/article/0,9171,796046,00.html WW2-era (1942) TIME Magazine article on sponge iron]

[[Category: Materials]]
[[Category:Metalworks]]

Cement Mixer

2012-07-24T08:32:45Z

Jetbeard:

{{ToolTemplate|ToolName=Cement Mixer}}
[[Category:GVCS]]
[[Image:CementMixer.png|thumb|400px|Cement Mixer]]

==Overview==

A '''Cement Mixer''' (also commonly named a concrete mixer) is a device that homogeneously combines cement, aggregate such as sand or gravel, and water to form concrete. <ref name="Concrete Mixer">{{cite web |url=http://en.wikipedia.org/wiki/Concrete_mixer |title=Cement Mixer |publisher=Wikimedia Foundation, Inc}}</ref>

{{Video}}

==Detailed Description==
A concrete mixer (also commonly called a cement mixer) is a device used to automate the preparation of cement by mixing it with other aggregates such as sand or gravel and water to form concrete. A typical concrete mixer uses a revolving drum in which the components are automatically mixed. The resulting mix is used as on of the most important elements on construction.

[[Concrete]] is used more than any other man-made material in the world. As a part of the [[GVCS]], it unlocks a range of building techniques and methods, depending on characteristics of the environment and type of structure to be built.

==Product Ecology==
{{Product Ecology
|Product={{Cement Mixer}}
|From=
*{{Lathe}}
*{{Motor}}
*{{LifeTrac}} - Mounting
*{{Furnace}} - Steel
*{{Torch Table}} - Cutting
*{{Ironworker}} - Holes

|Uses=
*{{Power Cube}}
*[[Lime]]

|Creates=
*[[Cement]]

|Enables=
*[[Workshop]]
*[[Greenhouse]]
*[[HabLab]]
*[[Foundations]]
*{{Multimachine}}
*[[Foundry]]

|Components=
*Drum
*Frame
*Motor
*Water Feed
*Hinge

}}

==OSE Project Status/Schedule==

The concrete mixer is currently in development and is undergoing CAD stages of design. It is considered a priority for the [[2011 Infrastructure Buildout]], as a part of the [[GVCS Rollout]]

==See Also==
*[[Cement]]
*[[Ferrocement]]
*[[Geopolymers]]
*[[Monolithic Dome]]
*[[Kiln]]

==Links==
*[http://en.wikipedia.org/wiki/Concrete_mixer Concrete Mixer]
*[http://concretelathe.wikispaces.com/Concrete Concrete Lathe]

----
[[Category:GVCS]]
{{GVCS Footer}}

Cement Mixer

2012-07-24T08:31:56Z

Jetbeard: Undo revision 61187 by Teardrop (talk)

CNC Circuit Mill

2012-07-24T08:25:31Z

Jetbeard: wikisyntax

The '''CNC Circuit Mill''' is a tool for automatically constructing circuit boards from bare metal-clad boards using a fine milling bit.

The Circuit Mill consists of a head that can move in three dimensions and a table that can hold the board in place. Attached to the head is a detachable module with can rotate the milling bit. [[/Understand|Further information is available]].

Work has been done on prototyping version 1 of the Circuit Mill, and work designing version 2 is under way.

=Version 2=

==Background==

* [[/Status Brief|Status Brief]]
* [[CNCCMV2/Systems Engineering Breakdown Diagram|Systems Engineering Breakdown Diagram]]
* [[/Industry Standards|Industry Standards Analysis]]

==Active Development==

* [[/Collaboration|Development Team]]
* [[/Subject Matter Experts|Subject Matter Experts]]

==Design==

* [[CNCCMV2/Overview|Overview]]
* [[/V2 Design Rationale|Design Rationale]]
* [[CNCCMV2/CAD|Structure]]
* [[CNCCMV2/Electronics|Electronics]]
* [[CNCCMV2/Software|Software]]

==Replication==

* [[CNCCMV2/Sourcing|Sourcing]]
* [[CNCCMV2/Build Rationale|Build Rationale]]
* [[CNCCMV2/Build Instructions|Build Instructions]]
* [[CNCCMV2/Testing|Testing]]
* [[CNCCMV2/Usage|Usage]]
* [[CNCCMV2/Maintenance|Maintenance]]

==Distributive Enterprise==

*Economic Analysis
*Training
*Capitalization Assistance
*Sourcing Assistance

=Archives=

* [[/History|Version Repository]]

[[Category:Circuit Board Fabrication]]

{{GVCS Footer}}

Category:Torch Table

2012-07-24T08:04:07Z

Jetbeard: wikisyntax

=Introduction=

This page keeps track of all the pages related to the open source CNC torch table, and serves as an annotated bibliography for all the torch table pages.

'''The current design can be found here [[CNC Torch Table]] and currently work is being done here: [[Open Source Torch Table Prototype II]]'''

[[Category: RepLab Tools]]

Template:Category=Torch Table

2012-07-24T08:00:13Z

Jetbeard: Now the template doesn't show up in the category itself.

'''[[Main Page|Main]]''' > '''[[:Category:Digital Fabrication|Digital Fabrication]]''' > '''[[RepLab#Tools|RepLab Tools]]''' > '''[[:Category:Torch Table|Torch Table]]'''
<includeonly>[[Category:Torch Table]]</includeonly>
----

Telecommunication

2012-07-23T22:17:09Z

Jetbeard: Wiki syntax.

=Guide=

Get WRT54GL Router [http://www.amazon.com/Cisco-Linksys-WRT54GL-Wireless-G-Broadband-Router/dp/B000BTL0OA Source]

Get Tomato Firmware [http://www.polarcloud.com/tomato Tomato]

[[File: publicprivate.png]]

=a=

http://forum.ih8mud.com/workshop-home-improvement/400291-power-cat-5-coax-phone-same-trench.html

=Power and Telecom Line Spacing=

Northern Telecom IBDN User Manual contains an Appendix D titled ''UTP Separation Guidelines From EMI Sources''. The values are the same as the cabling pathways standard, EIA-569, table 4.8-5.

{| class="wikitable"
|-
!rowspan=2| Condition
!colspan=3| Minimum Separation Distance from Power Source at 480V or less
|-
!<2kVA !! 2-5kVA !! >5kVA
|-
| Unshielded power lines or electrical equipment in proximity to open or non-metal pathways || 5 in. (12.7cm) || 12 in. (30.5cm) || 24 in. (61cm)
|-
| Unshielded power lines or electrical equipment in proximity to grounded metal conduit pathway || 2.5 in. (6.4cm) || 6 in. (15.2cm) || 12 in. (30.5cm)
|-
| Power lines enclosed in a grounded metal conduit (or equivalent shielding) in proximity to grounded metal conduit pathway || - || 6 in. (15.2cm) || 12 in. (30.5cm)
|-
| Transformers & electric motors ||colspan=3| 40 in. (1.02m)
|-
| Fluorescent lighting ||colspan=3| 12 in. (30.5cm)
|}

Source: Integrated Building Distribution Network (IBDN) User Manual - Northern Telecom, doc # IBDN-UM-9105, 1991.

=Infrastructure=

Our telecommunication infrastructure consists of:

*1 coaxial cable connected to the hardware of our Internet Service Provider (ISP)

*1 DSL filter

*1 6P6C phone cable (3ft each)

*1 modem

*3 WRT54GL routers ([http://www.amazon.com/Cisco-Linksys-WRT54GL-Wireless-G-Broadband-Router/dp/B000BTL0OA Source])

*1 indoor Cat5e cable (3ft each)

*2 outdoor waterproof direct burial Cat5e cables (200ft each) ([http://www.amazon.com/Outdoor-Waterproof-Ethernet-Direct-Burial/dp/B001B6FY4O/ref=sr_1_1?ie=UTF8&qid=1338504293&sr=8-1 Source])

=Hardware Setup=

*The ISP's coaxial cable connects to the DSL filter.

*The DSL filter connects via 6P6C phone cable to the modem's DSL port.

*1 of the modem's Uplink ports connects via indoor 3ft Cat5e cable to the Internet port of the wireless router (Base Router).

*1 of the base router's LAN ports connects via outdoor 200ft Cat5e cable to 1 of the LAN ports of another wireless router (Primary Boost Router).

*1 of the primary boost router's LAN ports connects via outdoor 200ft Cat5e cable to 1 of the LAN ports of another wireless router (Secondary Boost Router).

=Software Setup=

*Router firmware: [http://www.polarcloud.com/tomato Tomato]

*How to Use Tomato Quality of Service [http://tomatousb.org/tut:using-tomato-s-qos-system Tomato QoS Guide]

'''Base router's settings:'''

Network: PPPoE

DHCP Server: Enabled; 192.168.1.100 to 192.168.1.199

Router IP Address: 192.168.1.1

SSID: 1 OSE Base

(all other settings should be default)

'''Boost routers' settings:'''

Network: Disabled

DHCP Server: Disabled

Router IP Address: 192.168.1.3 (second router); 192.168.1.4 (third router)

SSID: 3 OSE SolarCube, 4 OSE Hablab

(all other settings should be default)

=Replication=

*'''How to Connect 2 Routers with an Ethernet Cable:''' (thanks to [http://homecommunity.cisco.com/t5/Wireless-Routers/Connecting-two-routers-wired-the-definitive-answer/td-p/47006 Cisco Forums])

Assume you have 2 routers, the first already connected to the internet.

# Power on the second router without anything connected to its ports. Connect a single computer to the router. Do not connect the second router to the first at the moment!
# Configure the router at http://192.168.1.1/
# Change the LAN IP address of the second router from 192.168.1.1 to a free address in your LAN (e.g. 192.168.1.2 should be O.K. if the first router is also a Linksys router). The address you change to (192.168.1.2) must not be used by any other device with static IP address in your network nor should be assigned by the DHCP server your network. A default Linksys router uses 192.168.1.1 itself and the DHCP server assigns 192.168.1.100-149.
# Turn off the DHCP server on the second router.
# Save the setting.
# Unplug the computer from the second router.
# Connect an ethernet cable from a numbered LAN port of the first router to a numbered LAN port of the second router. Do not use the Internet/WAN port on the second router!
# That's it! If you don't know or don't want to know more about networking you don't have to read the rest here.

'''What do you have now?'''

The second router is connected through a LAN port to your existing network. This basically means that the router part of the device is actually not used. So you have a router device that you don't operate as router in your network. Whatever you connect to the second router either through one of the remaining LAN ports or through a wireless if it has one, is directly connected to your LAN. Devices connected to the second router use the DHCP server of the first router to get an IP address. They use the first router directly for internet access. Everything is connected to a single larger ethernet network. Everything is in a single "broadcast" domain. This is called [[Wikipedia:Bridging (networking)|bridging]].

If the second router is not a wireless one, you basically have a few more ports in your network. In that case it might have been cheaper to get a simple switch/hub instead to extend your network.

Please remember: as the second router is not connected through the Internet/WAN port many configurations and functions of the second router won't work simply because they require an internet connection on the router itself. Some examples are: access restrictions, dynamic DNS service, port forwardings, MAC address clone, the firewall... All these things must be configured on the first router and only there.

'''Why is this better than connecting the second router with the Internet port?'''

If you have a second router connected via the Internet port...

A router is a separating network element. It separates two networks and allows certain traffic to cross. Sometimes this is necessary in a network setup but for most home networks it only creates a lot of obstacles.

# In default Gateway mode the second router does network address translation (NAT). This means computers connected to the second router can connect to computers connected to the first router but not in the opposite direction.
# If you use Router mode on the second router: you have to configure "routes" on the first router and possibly your computer connected to the first router so that IP packets find their way into the subnet of the second router.
# You have two separate ethernet networks and thus two "broadcast" domains. A broadcast in the first router's subnet reaches all computers connected there. The same applies to the second router. A broadcast will never cross the second router, though. This is an obstacle for applications that depend on broadcasting to locate other computers and services. Windows file and printer sharing is one example here. With the second router in between, computers on one side do not know about computers on the other side. You cannot search your workgroup for the computer on the other side even when they use the identical workgroup name. You will be able to access the other computer using the IP address directly (e.g. \\192.168.1.100\share) but that's usually a hassle and the IP address may change if it is assigned by the DHCP server to the computer. There are ways to deal with some of these issues (e.g. save the host names in lmhosts files...) but all this requires more effort and attention to keep everything up-to-date.
# Port forwardings become more complicated. If you need a port forwarding (i.e. you want a port on a computer in your network to be accessible from the internet) on a computer connected to the second router you have to setup two forwardings: one on the first router to the second router and one on the second router to the computer.
# If you have two wireless routers: you cannot roam between both routers without loosing the connection. This is simply because if a wireless computers moves from one router to the other it needs a different IP address.
# The whole configuration becomes more complicated: you always have to think about where to configure what, e.g. dynamic DNS service, access restrictions, ...

Bottom line: unless you have good reasons why you must have some computers separated from the other computers in your network, there is no good reason to in a home network to do so. For normal home networking with simple to use file and printer sharing it is better to connect the second router as suggested in this post...

Application Technologies

2012-07-23T22:02:01Z

Jetbeard: Wiki-syntax'd up the whole thing. I'm not even sure this page is necessary but if so it should be neat.

=Critical Infrastructure=

* [[Water]]
* [[Food]]
* [[Energy]]
* [[Telecommunication]]
* [[Recycling]]
* [[Shelter]]
* [[Recreation infrastructure|Recreation]]
* [[First Aid Kit]]
* [[Personnel Safety]]
* [[Clothing]]
* [[Transportation]]

[[Factor E Farm Site Plan#FeF Ecological Site Plan|Site Plan]]

=Materials=

This section should contain links on how to produce various materials, especially those with low information density such as materials with relatively homogenous compositions. Ex. iron (pure element), steel (compound), wood (organic molecules)

* [[Wood]]
* [[Iron]]
* [[Steel]]
* [[Copper]]
* [[Aluminum]]
* [[Solder|Silver Bearing Tin (Electrical Solder)]]
* [[Low-density polyethylene|LDPE (Low-density polyethylene)]]
* [http://www.amazonsupply.com/s/16310191?searchBinNameList=feature_seven_browse-bin&field_feature_seven_browse-bin=5485488011&ref_=sp_s_st_16310191 HDPE Source]
* [[Polycarbonate]]
* [[Nylon]]
* [[Polyester]]
* [[Rubber]]s
* [[Chemicals]]

=Compression=

* [[Flexible Clamp]]
* [[CEB Press]]

=Cutting=

* [https://github.com/openspeed/Cold-Saw Cold Saw]
* [[Ironworker]]
* [[Dimensional Sawmill]]
* [[Oxyacetylene Torch]]
* [[Plasma Cutter]]
* [[Laser Cutter]]
* [[Water Stream]]

=Module Rotation and Movement=

* [[CNC Circuit Mill]]
* [[Multimachine]]
* [[Lathe]]
* [[Mill]]
* [[Industrial Robot]]

=Heating=

* [[Soldering Iron]]
* [[Heat Gun]]
* [[Welder]]
* [[Induction Furnace]]

=Sensor-based Control=

* [https://github.com/openspeed/temperature-switch Temperature Switch]

=Observation Instruments=

* [[Electrical Meter]]
* [[Mass Scale]]
* [[Thermometer]]
* [[Distance Measure]]

=Observation Modules=

* Temperature
* Ultrasonic
* Infrared
* Visible Light
* Pressure
* Humidity
* Flow
* Audible Sound
* Wireless Communication

=Energy Storage=

* [[Batteries]]

=Light=

* [[Headlight]]

=Fluid Flow=

* [[Vacuum Cleaner]]
* [[Fan]]
* [[Submersible Pump]]

=Filtration=

* [http://www.amazon.com/dp/B005C5HUI8/ Carbon Filter Source]

=Code-based Control=

* [[Arduino]]
* [[Computer Aided Manufacturing]]

=Electrical Power Control and Amplifier=

* [[CEB Press/Manufacturing Instructions/Detroit Fab Lab Solenoid Driver v4|Teensy Compatible Solenoid Driver Board]]
* [[Stepper Driver]]

=Electrical Conduction=

* [[Portable Cord]]
* [[Splitter]]
* [[Male Plug]]
* [[Female Plug]]
* [[USB Cable]]
* [[Wire]]
* [[Terminal Case]]
* [[Float Switch]]
* [http://www.amazon.com/dp/B0002ZPBRA/ Light Duty Switch Source]

=Electrical Insulation=

* [http://www.amazon.com/dp/B005W42SW2/ Shrink Tubing Source]

=Electrical Sense=

* [[GFCI|Ground Fault Circuit Interrupt]]
* [[Surge Protector]]
* [http://www.amazon.com/dp/B000M61JFC/ Fuses Source]

=Electrostatic Discharge Protection=

* [http://www.esdmat.com/detail.php?pid=182625 ESD Mat]
* [http://www.amazon.com/dp/B0042TLA90/ ESD Wriststrap]
* [[ESD Smock]]

=Electrical Transformation=

* [http://www.circuitspecialists.com/dc-bench-power-supply-csi3005x5.html CSI3005x5: Benchtop Power Supply 120VAC 60Hz to 0-30V voltage setting 0-5A current limiting]
* [http://www.amazon.com/dp/B006GEPUYA/ 120VAC 60Hz to 12V Power Supply]
* [http://www.amazon.com/dp/B000RSOV50/ 4 AA/AAA Battery Charger]

=Discrete Electrical Components=

* [http://www.amazon.com/dp/B003UC4FSS/ Resistors Source]
* [http://www.amazon.com/dp/B007SVHFXO/ Capacitors Source]
* [http://www.amazon.com/dp/B007L4DX6Q/ Diodes source]

=Flow Channel=

* [[Bulkhead]]

=More Technologies (all to be organized later)=

* [[Website Setup]]
* [[Using Github]]
* [[Electronics Workstation]]
* [[Conformal Coating]]
* [[Flux]]
* [[Magnets]]
* [[Hoses]]
* Hydraulic Transmission: [[Hydraulic Connector#Male Plug|Male Plug]], [[Hydraulic Connector#Female Plug|Female Plug]]

=Further Categories to be Site System'd=

* [[Nanotechnology]]
* [[Brain-Computer Interfaces]]
* [[Synthetic Biology]]
* [[Space Technologies]]
* [[Artificial Intelligence]]