Data Exchange from design to RP&M

From: André Dolenc (Helsinki University of Technology)
To: RP-ML
Date: Tuesday, May 24, 1994
Subject: Data Exchange from design to RP&M
Mr. Joppe has many questions!  8-)
Marcus Joppe writes:
 > 1. Existing Data Exchange Concepts for RP&M (Developed)
 > - Which Concepts of Data Exchange from design to RP&M beside      
 > facetted, sliced or neutral graphic (VDA-FS, IGES) models do you      
 > know ?
     I did not really understand this question. Let me ellaborate on possible interpretations. In the context of RPT, one can discuss direct vs. indirect interfaces. Assuming that layers are the "assembly language" of RP machines, there are very few direct interfaces around, ie. software tools that can generate layer information directly from the original model. Using this terminology, an STL file is an indirect interface because usually the original model is a surface model.
     On the other hand, one can talk about passive vs. active interface. The possibilities listed in the question are all passive. An example of an active interface is PostScript.
     Joppe, BIBA was in the same project we were. Ask Mr. Hans Muller for the report titled "Data Exchange Formats for LMT Processes" from WA1+WP3 (Dear readers, the classification of this report is Open, so copies are available upon request.)
 > - Which File-Formats for Data Exchange from design to RP&M beside 
 > STL, CFL, LEAF, CLI, SLC, VDA-FS, IGES do you know ?
     HPGL. There is German machine vendor that uses that one. Sparx also used to use, but it seems like they are no longer with us.
 > - Which Interfaces for Data Exchange from design to RP&M beside 
 > vda2tr, vdafs2stl, vdafs2cli, CATslice do you know ?
     igs2tr.
 > - Which activitys and results (Projects, Software-Tools) do you have in 
 > this context ?
     We have four project at our Institute:
 - software development
 - technology transfer to industry
 - technology transfer to the medical community and software development for medical applications
 - process development
     In the medical project, we are dealing with the same problems you are.  8-)
 > - How would you descripe the situation of Data Exchange today ?
     Under control. We are falling from the 20th floor, and we are still near the 15th floor, so as long as we are not approaching the 1st floor, nothing will happen in this area.
 > - What are the main problems with existing concepts or Interfaces 
 > today ?
     Poor design, cannot accomodate future needs, inefficient, biases torwards the vendor (the receiver of the data).
 > 2. Future Data Exchange Concepts for RP&M (Under Development)
 > - Which future Concepts of Data Exchange from design to RP&M beside 
 > direct sliced models do you know or heared about ?
     Sliced data is the closest we will get to the machine. The vendors will disclose nothing more. One could envision a process that operated using bitmaps.
 > - Which future File-Formats for Data Exchange from design to RP&M 
 > beside STEP, LEAF or CLI (Brite Euram Layer Format) do you know or 
 > heared about ?
     None.
 > - Which future Interfaces for Data Exchange from design to RP&M do 
 > you know or heared about ?
     Clemson University has done some work on slicing.
 > - What are your activitys in this context ?
     See above.
 > - What do you think about the concept of direct slicing ? 
     It is an important tool which should be available to those who have a machine.
 > - What do you think about STEP ?
     Do you want flame wars in this mailing list?
 > - Which way would be the best for Data Exchange for RP&M in your 
 > opinion ?
     We are going to discuss this in our next EARP meeting. You got a previous posting of mine?
 > 3. Process dependent "Third Party" Software Tools for RP&M 
 > - Which Process dependent Functions for RP&M beside Supports, 
 > Offsets, Visualisation, Verifying, Positioning do you know ?
 > - Which Process dependent "Third Party" software Tools for RP&M 
 > beside MAGICS, ISTOFFSET, STL-CAD, HUTPP, RAPID TOOLS, 
 > Intelligent Design Editor, RAPITO-Toolset, Layout, Bridgeworks do you 
 > know ?
     Delete HUTPP. It is now called 'tr2stl' in RAPID TOOLS.
 > - Which activitys and results (Projects, Software-Tools) do you have in 
 > this context ?
     See above.
 > - What are the main problems in this context ?
     Now, this is a loooooooooooooooooooonnng one!
 > - What do you think about Functions for later manufacturing process 
 > (like Casting, Moulding etc.) and which would be important for this ?
     We are working on these.
 > - What do you think about an integrated RP-Workbench to solve most of 
 > the existing problems and what would be important for it ?
     You should see the latest version of RAPID TOOLS!
Regards,
Andre'