Issue link: https://resources.pcb.cadence.com/i/1180268
Working with IDF
Best Practices: Working with IDF
October 2019 12 Product Version 17.4-2019
© 1999-2019 All Rights Reserved.
The IDF translator performs the following checks when importing components:
■ If the reference designator matches a component instance in the Allegro PCB Editor
database and the component is not placed, IDF places it using the footprint specified in
the database. If the component is placed, IDF moves it if the ownership is set to MCAD.
■ If the reference designator is not part of the database, IDF imports the component as a
symbol using the package name specified in the IDF file, provided that such a symbol
can be found in the location specified by the PSMPATH variable.
Holes
The following example shows an IDF 3.0 drilled hole record, where each hole definition
follows this syntax:
DIA X Y PLATING ASSOC TYPE OWNER
.DRILLED_HOLES
40.00000 2000.00000 2000.00000 NPTH BOARD PIN MCAD
40.00000 2165.00000 2000.00000 PTH BOARD VIA MCAD
40.00000 2165.00000 2330.00000 NPTH BOARD MTG MCAD
40.00000 2000.00000 2330.00000 PTH BOARD TOOL MCAD
125.00000 9750.00000 250.00000 NPTH BOARD 150C125 MCAD
60.00000 750.00000 250.00000 NPTH P1 OTHER MCAD
60.00000 850.00000 250.00000 NPTH P1 OTHER MCAD
.END_DRILLED_HOLES
IDF 3.0 reserves VIA, PIN, MTG, TOOL, and OTHER. For backward compatibility Cadence
reserves TARGET. The following naming formula is used to create hole symbols in Allegro
PCB Editor.
<(N)on-plated or (P)lated> +