Cadence PCB Best Practices

Working with IDF

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

Contents of this Issue

Navigation

Page 12 of 39

Working with IDF Best Practices: Working with IDF October 2019 9 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Note: 1. The IDF import program never alters an Allegro PCB Editor object with IDF_OWNER=ECAD. 2. The rules in Table 1-3 can be directly applied to any IDF-related object that has a unique identifier, or unique instance, including: ❑ BOARD_OUTLINE (only one allowed per design) ❑ PANEL_OUTLINE (only one allowed per design; only recognized by IDF Version 3.0). ❑ ROUTE_OUTLINE (only one allowed; layers always set to ALL) ❑ PLACE_OUTLINE (only one allowed; layers always set to ALL; height property does not apply in Allegro PCB Editor) ❑ PLACE_REGION (identified by name) ❑ PLACEMENT (identified by reference designator) 3. If the object is an IDF PLACEMENT object, the effective action is to move the symbol, based on ownership relations shown in Table 1-3. ECAD Shows the object without an IDF_OWNER property Imports the object and sets IDF_OWNER=ECAD. UNOWNED Shows the object ownership as MCAD Deletes the existing PCB Editor, APD object. It then imports the object and sets IDF_OWNER=MCAD. UNOWNED Shows the object ownership as ECAD Rejects the IDF object and reports the rejection in the log file. UNOWNED Shows the object without an IDF_OWNER property Deletes the PCB Editor, APD object. It then imports the object and sets IDF_OWNER=MCAD. Table 1-3 IDF-In Owner Action Map If the IDF Object Owner Is… And Allegro PCB Editor… Then, Allegro PCB Editor…

Articles in this issue

view archives of Cadence PCB Best Practices - Working with IDF