Stats

  • State Not Answered
  • Replies 3
  • Subscribers 67
  • Views 7812
  • Members are here 0
More Content

Varying height properties for single footprint

jryucurrent

Version: Orcad 17.4

Licenses: Capture & CIS, EDM, CIP, PCB Editor professional

We currnetly use CIP to manage part information with EDM managed projects, symbols and footprints.

Most of the time we draw part information from CIP distributor search, which can auto-fill certain properties like ratings, part value, and height property. 

We would like to take advantage of having height properties set for passive components, and link the property to automatically populate 3D model with accurate height representation for PCBs 

I have followed this thread for in order to do this, and this works for the Allegro 3D Canvas. However the MCAD export does not reflect this and sets equal heights for each footprints.

3D Canvas view:

Exported 3D model:

Notice that R415 and C417 in the Canvas both have same 0805 footprint with different height definiition, but exported model do not.

How can this be resolved so that the exported models have accurate (varying) height representation for passive components?

  • 0

    It doesn't look like you are using step parts for your passives.

    I suspect the only way we can accomplish this by adding a suffix to passive footprint names.

    I use Alt_Symbol data stored in CIP to swap in the same footprint but with varying heights by a suffix in the symbol name.  Controls which step part is exported.   

    For RF designs, we need partial design reuse (thank you CircuitSpace)  That 0201 C may turn into an L once we test the boards.  We use other layout tools but the only library worth setting up step parts in is Cadence.

  • 0 in reply to RFinley

    Hi, 

    Thanks for the reply. To clarify, what you're saying is that PCB Footprint file needs to be seperated (by suffix)? 

    Rather than using step parts, I would like to use generic default model for passive components, ideally which will draw max_height property from the schematic properties I've set up. 

  • 0 in reply to jryucurrent

    Until I find a better way, I add a height as a suffix, like C0201N_p3 as nominal IPC7351 rev C that is p3mm height.   

    QFNs, SOICs, etc. have height in the IPC7351 naming standard. 

    CAPC60X30L15L is an IPC name for 0201 (0.6mm x 0.3mm) at 0.15mm tall.   But, that causes questions. 

    So, C0201_p15 it is.  Not delighted to have multiple C0201 footprints for heights, but it keeps complaints to a minimum.

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.