Skip to main content
1-Visitor
February 13, 2014
Question

ECAD related Document Types ECAD Neutral

  • February 13, 2014
  • 1 reply
  • 6514 views

Hello ECAD users

We started the implementation of Windchill in our company a couple of weeks ago.

In our company, we use Zuken CADSTAR for schematic and PCB. Well, CADSTAR ist not supported with a WGM, so we need to use the ECAD Neutral.

Right now, i'm trying to identificate what each of the ECAD related CAD Document types does.

ECAD related CAD Document Templates

  • ECAD - BOM Attributes Mapping <= mapping file between Windchill BOM and ECAD Software
  • ECAD - BOM Filter Definition <= Filter file for BOM, like Attrivutes we don't want to map to Windchill
  • ECAD - Content <= ? don't know what this one does
  • ECAD - Content Definition <= document pointer, like "in this folder is a file is a *.pdf file. Use it as content"
  • ECAD - Documentation Data <= ? don't know what this one does (Blueprint PCB Software)
  • ECAD - Drawing <= <= ? don't know what this one does
  • ECAD - Manufacturing Data <= ? don't know what this one does (CAM350 Software)
  • ECAD - MCAD Exchange Data <= Derived Data , we use it for IDF data
  • ECAD - Packaged View <= ? don't know what this one does

Hope someone can explain what the other document types do. I'm specially interested in ECAD - Content. Whats the difference to ECAD - Content Definition?

Best regards

M.Suarez


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

1-Visitor
February 13, 2014

I hope to be following up with documentation soon but for now I hope this helps.

  • ECAD - BOM Attributes Mapping <= mapping file between Windchill BOM and ECAD Software
    DAVE: Mapping the fields ( Column Headers)
  • ECAD - BOM Filter Definition <= Filter file for BOM, like Attributes we don't want to map to Windchill
    DAVE: Correct
  • ECAD - Content <= ? don't know what this one does
    DAVE: this document is a container for data that is created from the ECAD database and associated to a design .
    Example:
    MFG data, Test Data, ASSY data.
  • ECAD - Content Definition <= document pointer, like "in this folder is a file is a *.pdf file. Use it as content"
    DAVE: I would describe that as the instruction of what to collect and attach to Content.
    Example
    Content = MFG data,
    Content Definition = from this location c:\abc\desin\output\ collect *.GER, *DRL, drill .pdf.
  • ECAD - Documentation Data <= ? don't know what this one does (Blueprint PCB Software)
    DAVE: Blueprint-PCB is a documentation tool from Downstream Technologies http://downstreamtech.com/
    the document is a container for Blueprint-PCB
  • ECAD - Drawing <= <= ? don't know what this one does
    DAVE: this is kind of a generic document container you may want to collect misc. document and have them be checked in.
  • ECAD - Manufacturing Data <= ? don't know what this one does (CAM350 Software)
    DAVE: CAM350is a Gerber management/visualization tool from Downstream Technologies http://downstreamtech.com/
    the document is a container for CAM350
  • ECAD - MCAD Exchange Data <= Derived Data , we use it for IDF data
    DAVE: you are using it as expected.
  • ECAD - Packaged View <= ? don't know what this one does
    DAVE: I don’t have firsthand knowledge but looking into it.
1-Visitor
February 14, 2014

Hi Dave,

thank you for your reply.

greetings Marcos

1-Visitor
February 17, 2014
Marcos,

With regard to your ECAD data model question;

I gave a discussion last year at PTC Live. This Presentation might be of use to you and your team for some good graphic presentation of how the items configure and interact.


Regards,Scott Claes

info@claes.biz www.claes.biz

Twitter LinkedIn