Cadence PCB Best Practices

Working with IDF

Issue link: https://resources.pcb.cadence.com/i/1180268

Contents of this Issue

Navigation

Page 11 of 39

Working with IDF Best Practices: Working with IDF October 2019 8 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Rules for IDF Import to Allegro PCB Editor Since the IDF 3.0 Specification introduces object ownership (MCAD, ECAD and UNOWNED), the IDF translator follows a revised rule set for importing IDF data into Allegro PCB Editor. Table 1-3 shows the action taken based on object ownerships. Table 1-3 IDF-In Owner Action Map If the IDF Object Owner Is… And Allegro PCB Editor… Then, Allegro PCB Editor… MCAD Has no existing object because this is a new design Imports the object and sets IDF_OWNER=MCAD. ECAD Has no existing object because this is a new design Imports the object and sets IDF_OWNER=ECAD. UNOWNED Has no existing object because this is a new design Imports the object and sets IDF_OWNER=MCAD. MCAD Shows the object ownership as MCAD Deletes the existing PCB Editor, APD object. It imports the object and sets IDF_OWNER=MCAD. MCAD Shows the object ownership as ECAD Rejects the IDF object and reports the rejection in the log file. MCAD Shows the object without an IDF_OWNER property Deletes the PCB Editor, APD object. It then imports the object and sets IDF_OWNER=MCAD. ECAD Shows the object ownership as MCAD Deletes the existing PCB Editor, APD object. It imports the object and sets IDF_OWNER=ECAD. ECAD Shows the object ownership as ECAD Rejects the IDF object and reports the rejection in the log file.

Articles in this issue

view archives of Cadence PCB Best Practices - Working with IDF