Open Source Ecology TED Global 2012, 22 Jun 2012

Previous Meeting

⏯

youtube image

►

From YouTube: Workflow for open hardware development

Description

Gckjcjccckc

A

B

A

Builder okay, hold on so cesar. Tell me. Tell me a little bit about the tool chain that exists today. Okay,.

B

So we're talking about like how can we create an efficient workflow for open highway development, yeah from ideas to actual tests or even like manufacturing tests like a crash test? So basically, if you have an idea of you want to build a new car, you want to build a new machine. What are the tools exist today that can enable you to work with other people collaborative to develop this new technology? Okay, so today you have lots of different software.

B

You have some website that proposes the services, but the ideas, if there is an open hardware submit every year, is to focus this on creating apis or creating standards to let these different components work together. Apis.

A

That will allow us to use those existing resources.

B

As a workflow yeah, so integrate them because we nobody is going to make one software that has everything impossible right, but then we need to find one pass. That allows you to to do everything that you need so, for example, if you're doing parts, if you want to build your parts, you can you can use thingiverse or you can use eagle. You can use builder or alberto to say start to design new parts, electronics or mechanics yep or you can even use fritzing. If you want to start testing them.

A

What's that three.

B

Thing is uh you can design circuit boards, so you can? You can start, you can draw it and write the component and we'll export to automatically the board that you should etch, so you can send to factory. You can actually is that open source? I think it's pretty much open source and then, if you want to test your design, then you normally would use solidworks, for example, to test your mechanical design. But there's a new new thing called evolve from voltron system builder for system engineering yeah.

B

You could couple electric system with mechanical system with some systems. That's not open.

A

B

No not not alone, and then, when you're publishing, you want to use open hardware, creative commons and when you want to publish your environmental data, that's collected, for example, with your machines and you can use or like I don't know, if you, if you're producing bricks, for example- and you want to say how many bricks a minute you put your machine produce, you could actually plug this machine on patchbay and people will know by the second. How many bricks are coming out of the machine throughout platform patch bay?

B

Now it's called cousin, but they just changed names or matchups, p-a-c-h-u-b-e yeah. So basically, these are all like some of them open hardware. Some of them are not, but these are components that could that that are needed into a workflow. If you want to implement an idea into a real product that you can test.

A

Yeah so um catalina she's all over this discussion. She.

B

You haven't talked to her yet she's interested in this, but she.

C

She believed that it.

B

Should be a grassroots thing, so it should be us doing this rather than she's happy, like kind of curating, her she's she's over there. Oh we're talking about we're.

A

Just we're just talking about you, we're.

B

Just talking about this and.

D

About me about this, oh you have beautiful sketches so.

B

We're wondering if this is the work for open hardware, association or if this is the work that should be done by something somebody else who do you think should be doing that work. I.

D

Think that where the open hardware association comes is here, the.

B

D

The publishing is, how do you publish a result so that they're repeatable.

C

D

Like that's, that's the objective to reproduce hardware, so how can documentation be done in a way that is repeatable? And I think that which we, as an association shouldn't create? This is my opinion. Okay, we shouldn't create a platform.

B

D

Not even the whole system, we should create guidelines. That's.

B

D

Just say like this is what we recommend the.

A

Specification for that, because.

D

Everyone is going to do it their own way, but they can or cannot abide by the guidelines with their guidelines. There's something.

B

We were just asking him: what are the file format we should use to exchange from like like cat drinks or what are the best ones, and if you already have like a list and then you have three between each of these components, you have a list of the right formats.

B

It's already the beginning of a really good workflow, exactly exactly where'd.

A

You discuss that with tom.

B

Tom ego um online, we just created excel sheet, and then we just like exchange, we just like list the format for different between those those between those.

A

Is that just personal email? Is that a list no.

B

From them for now, just a discussion between the three person- just me tommy go and gabriella levine, another team member, but we should open this discussion. Gabrielle gabriel, she presented a protea at the bona hardware, excellence she's.

D

Also, an itp alum, that's right, um put.

A

Me in a list- let's, I want to join that discussion.

D

One thing that might be interesting to look at another person to involve in the discussion. So look up. I don't remember what it's called okay, so an adafruit.

D

There is a page called what is open source hardware and like if you scroll down um the more and phil they wrote the layers of open source hardware, like all.

B

Three components.

D

It's not called the send, which is just like all the files that you should publish not to the open source hardware in which formats you should publish them. So it's a start. It's not finished, but you know, filter out is probably someone who has opinions like you know, for example, like the gerber files are better than a bitmap. You.

B

D

Things like that- and I don't know if there's anything about cat there, but there's definitely some people who can get involved in this discussion. Okay, so.

C

As soon as we get into.

D

Formats and all that, so we just started, we just launched um a mailing list for oshawa. Anyone can join so this might be an interesting discussion. Let's.

A

Let's pump that in there as a discussion.

D

Yeah just like start a thread.

A

We're live on march and tv once again.

D

A

D

But I can't do you have my email.

A

D

So if you email me I'll email, you oh.

A

B

Can we can we go and take the picture? Yeah yeah, I'm ready. Okay,.

D

Yeah, I have the phone in my room, open materials.

C

D

Excellent and then like we just created the list, so there aren't that many people on it. So basically we need to get the right people to join the list and it's probably like a good platform to just discuss this and.

A

Thank you for laying the foundation of.

D

C

A

Source world and industrial economy 2.0.

D

Yeah we're all doing that.

D

It's exciting it's an interesting moment.

C

Caesar, where is this going where's this all going? Where do you see it going.

B

I I think this is this is this is really really exciting, but my position is also I mean, for example, auspicious in one specific field like I'm interested in open heart on the computer, social science you're, just an open heart of agriculture, I'm transferring foreign, so we all have like our like smaller fields and like- and I know we all have limited amount of time that we can actually dedicate to like this common goal of open heart and like it's going to be like how much time we're ready to spend on this and.

A

Okay, how about you guys help us, because we've got a budget, that we can hire documentaries, we're going through a massive documentation document or hiring spree. We can put in a budget for for a person to take that on like we're going to have the cat director person, we can possibly add another person to integrate this, because we're already going to define the cad statement with, of course, with everybody in the community. But the question is bigger: it's like the whole whole tool chain, not just cat. There's cad cam, basically cad cam.

A

I mean that's essentially what we're talking about. What's.

B

Happening is that, if we're doing, if we're, defining a workflow, what's gonna happen that we're gonna basically nominate who, in the industry who, in the in this slice, is.

D

Going to be standard yeah, it's going to be the standard.

B

It's super integrated. It's going to be a very difficult.

D

Discussion because people have preferences, like everyone, has a preference of an application they prefer to use. So there's going to be an intense discussion at one point which is going to say: okay, this, this application got all. This format got the most well.

A

We can generalize from there, we can go a higher level to say the function, the functional right.

D

It needs to have these characteristics and then.

A

Source, true specifications. You know like things like that.

D

Which one yeah I mean.

A

D

Might be the solution so right now, stl is the standard stl stl, yes seo for 3d uh and the except for um 2d. Those are the standards right now. Maybe we just adopt those.

A

D

Not implementable.

A

To the assembly level.

D

Oh, I see so that's.

A

So that's the next one we need exactly so that's one thing: we need.

D

To break out it was like I use open ascot, because you have the code, you can do whatever you want with it. It's like it's the source of the source, but not everyone uses openhab.

A

I think the discussion on just the standard itself without getting into specifications of formats will be easier. We can at least.

D

A

D

Without pissing everybody off exactly that's true, what should be the defining.

A

Well for the 3d files, it doesn't exist for the same at the assembly level, there's stl, but the next one for the open source standard. Full assemblies that doesn't exist so we're going to have to create that yeah.

B

And it's probably the most difficult one when you find a couple, not mechanical and electronic to mechanical to other stuff, they.

A

Call it dot cap for category code.cat.cat.

D

Yes, please create an extension with my name.

C