5 ms·
One of the more interesting things about 3D printing is that it is igniting this sort of issue. A long time ago (like 1991) I was a working for Sun and represen
by ChuckMcM 12y ago
One of the more interesting things about 3D printing is that it is igniting this sort of issue. A long time ago (like 1991) I was a working for Sun and representing them at the "CAD Framework Initiative" efforts or CFI. The express goal of this was to create a set of interchange formats for CAD tools so that you could move things from one system to another, you could store and diff changes, and even if your vendor went out of business you could use your designs in another vendor's tool if it was CFI compliant.
Now the irritating part was that Apollo Computer turned it into a DCE RPC vs ONC RPC thing when the committee started leaning toward the simpler RPC/XDR format that Sun had offered. The criminal part was that as soon as it became clear that the group was actually going to succeed nearly all support was yanked. The simple reality was that CAD tools cost literally hundreds of thousands of dollars for a large shop and those vendors desperately needed the 'lock in' effect of a propietary data format and tool chain to keep themselves in play during the inevitable periods where their tools totally sucked (waterfall development at its finest). It still bugs me when I think about it over 20 years later!
So to say I would be a huge supporter of an open CAD standard is an understatement. And now that there is a fairly large body of people who are both code capable and desirous of such a standard in order to create, share, and modify 3D designs, there might be enough energy to make it happen.
- sitkack 12y agoWe don't need a standard so much as both a plethora of special purpose tools (these are already here and more are in the works) AND an n:m pandoc style conversion utility. DXF/DWG will be with us for a long while.
- krick 12y agoThe open standard would be pretty helpful, if not sufficient for both. There even are no open source viewers for DWG files for the time being, so if I'm working on some new tool it is woth nothing to me that DWG is popular, because I can't use it without tons of effort.
- brudgers 12y agoRobust open-source CAD software would clearly fill a niche. The problem however, is not so much CAD as the schemas for the data that at gets attached to the models...IGES has been around for many decades, but what one engineer needs for FEA is not what the machinist needs for making the die or the Architect for making pretty pictures.
- eliasmacpherson 12y agohttps://en.wikipedia.org/wiki/Wavefront_.obj_file https://en.wikipedia.org/wiki/Wavefront_.obj_file open source data formats are more important than programs initially, the above is for 3d models. "— namely, the position of each vertex, the UV position of each texture coordinate vertex, vertex normals, and the faces that make each polygon defined as a list of vertices, and texture vertices. " I'm sure there's one for the edge based models too. I can see an UrStandard developing, which while probably inefficient, can describe necessary attributes for all practical applications and export into the open standardised format for the field at hand. XML for objects in 3d space.
- raverbashing 12y agoThe texture thing just solved the 3D drawing problem, not the FEA problem, or the machinist/CNC problem You don't care about vertexes when you're spinning things in a lathe
- lmz 12y agoCollada? http://en.wikipedia.org/wiki/COLLADA http://en.wikipedia.org/wiki/COLLADA
- brudgers 12y agoThe defacto standards for geometric data are driven by the dominate commercial software packages, e.g. ESRI's formats for geospatial information or AutoDesk's DXF for Orthogonal data [ and here I am lumping CAD and GIS under the scope of any universal standard ]. The issue with creating a standard is that to a first approximation every CAD or GIS program creates and operates on a unique set of meta-data...this is what gives each piece of software it's distinguishing features [ sure there are possible algorithmic efficiencies, but these are not an issue that a data interchange standard ought to treat as a primary concern ]. The wonderful thing about standards for 3d data is that there are so many to choose from. [1] There have been massive projects to create standards, and many of them have completed their work, only to see time march on. In AEC, the National Cad Standard was created in the 1980's [2]. It still locks the 3d description of designs to their 2d representation as drawings. The Army Corps of Engineers implements NCS. Their document is 450 pages [3]. To be comprehensible by humans, it is based on the idea: CAD levels or layers are analogous to overlays in manual drafting systems and serve to separate graphic elements (lines, shapes, and text) according to the design discipline they represent. Why, because unlike a computer program, the artifact it describes cannot be assumed to be directly manifested in meat-space without human involvement...e.g. buildings require construction crews and machine parts require someone pour raw material into the hopper and put finished goods on a truck, transport them, unload and install them for their next use...a design for a kitchen renovation doesn't compile into a new cabinet configuration. So the fundamental issue for developing creating a useful 3d data model is not a document, but a way of creating the data model that is attractive to people who create 3d data models. The prototype is JavaScript not ADA. [1] With perhaps disputed apologies to Grace Hopper. http://en.wikiquote.org/wiki/Grace_Hopper#Disputed http://en.wikiquote.org/wiki/Grace_Hopper#Disputed [2] http://www.nationalcadstandard.org/ncs6/about.php http://www.nationalcadstandard.org/ncs6/about.php [3] http://www.saj.usace.army.mil/Portals/44/docs/Engineering/AECStandardR5.pdf http://www.saj.usace.army.mil/Portals/44/docs/Engineering/AE...
- rjsw 12y agoPlenty of money and effort was going into STEP [1] in the same timeframe, it is still in use for designing anything that flies. I'm the editor of one of the parts of it and we are seeing increasing interest from other industry sectors. [1] https://en.wikipedia.org/wiki/ISO_10303 https://en.wikipedia.org/wiki/ISO_10303
- kanzure 12y ago> I'm the editor of one of the parts of it Any thoughts about or contributions to http://stepcode.org/ http://stepcode.org/ by any chance?
- rjsw 12y agoI have helped a little bit with checking their compliance to the standards. I modified the compiler that is in stepcode many years ago to generate ASN.1 definitions for the STEP models, the idea was to define some RPC operations to allow the kind of thing that ChuckMcM describes but I couldn't find anybody interested in it at the time. It would have been easy enough to write another compiler back end to generate XDR. I guess I would prefer to be paid to work on STEP, there is a fair bit of politics involved in it and I'm already involved with several opensource projects that are more fun. Also, if I'm looking for an opensource project to contribute to then I wouldn't pick one that used C++ and git, sorry. I have got some diffs to Express Engine [1] that I need to send in though. [1] http://sourceforge.net/projects/exp-engine/ http://sourceforge.net/projects/exp-engine/
- ultimape 12y agoIts a pretty big rift from my perspective. We were right alongside mechanical and architectural majore at VTC, they all learned some really crufty cad programs. The worst was SolidWworks, scripting that thing is a pig if damn near impossible. As a wanna-be tech startup in the field, I'd stay away from those tools like a plague. I heard there was way to do it, but its the kind of thing hiding behind their coprorate pay-wall and for profit training material. I've been impressed with tools like freecad - Its all implemented on top of a great Python API and lets you run code against some of their core modules. Developing procedural and programatically (parametrically?) designed hardware is much easier - and you can still interface with the average CAD worker / engineer. That being said, the average designer is SOL in this workchain. Still haven't found a good mix.