• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Creating complex shapes and importing them from .DXF ino...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 165
  • Views 13813
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating complex shapes and importing them from .DXF ino pad shapes...

UlfK
UlfK over 8 years ago

Sometimes I have to create complex pads for footprints (like the small AVX 9175 wire to board connectors).

In such cases, AutoCAD is my best friend. It handles "lines and stuff" in an excellent way and it is easy to create

complex shapes and "polyline them" which then can be easily imported into the Cadence PCB Editor environment

and then into the Padstack Editor. Also using drawings from connector manufacturers by extracting the

top view in an appropriate scale and then importing them as incremental and mapping the imported

.DXF layer to geometry/outline (or silk) saves hours of tedious work.

But:

Why does not Cadence PCB Editor honors the coordinate and origin settings in the imported .DXF?

I do set the 0,0 in the center of the shape .DXF. I do limit the extent of the .DXF to be just covering

the outlines of the polyline shape in AutoCAD before saving the .DXF for later Cadence Import.

When importing a .DXF polyline shape, the PCB Editor seems to randomly choose origin 0,0

and also the extents of the imported shape. When importing a complex figure such as a flat cable

connector outline or even an ordinary thing such as a large DSUB connector outline, all of a sudden

the extent of the editor canvas is enlarged and the imported .DXF ends up far away from the

"copper" or other parts of the footprint-in-creation.

This behavior is present in 17.20 as it was in 16.6

Has anyone else experienced this? Is there any way to correct it?

  • Cancel
  • steve
    steve over 8 years ago

    This just works for me and always comes in based on the origin point so make sure that 0,0 in AutoCAD is set correctly and also make sure you are running the latest hotfix for 16.6 (S089) or 17.2 (S015).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information