Stats

  • Replies 3
  • Subscribers 160
  • Views 6931
  • Members are here 0
More Content

How to define a socket header between PCB and plugin module?

FormerMember
FormerMember

We have designs that use plugin DIP modules similar to arduino nanos where a PCB has two parallel rows of headers plugs into my design. In my schematic I create a symbol for the actual part with all the pin functions and typically create a footprint with both rows so that the spacing and place bound is fixed during layout. This would all be fine if we just solder the module in, but we really want two rows of socket headers to plug the module in. We also use CIS so the database part calls out the actual module to be ordered in the BOM. I'm not seeing how to properly call out the socket headers.

Options I've considered are: 

1) add a manufacturer part for the socket header to the module database part so the BOM will call out headers instead of the module, then create another database part for the module itself to be called out in the BOM for purchase

2) add the socket header to the part as a mechanical part and call out some assembly instruction to use the header (seems wrong as I type it)

3) place the header parts as a separate footprint on top of the module footprint

Is 1 the cleanest option?

On a related note, if I socket header parts that are the exact number of pins per row, how do I tell CIP that it will need a qty of 2 for that one database part?

  • You mention that you have CIP so open the part in CIP and you should see a Mechanical Parts tab for each part. You can add Mechanical Parts to your database (Mechanical table) then add these to your header part. When you output a BOM enable the "Output Mechanical Part Data" checkbox in CIS - Reports - Standard and they are included.

  • FormerMember
    FormerMember in reply to steve

    I can see how using mechanical parts will allow calling out 2 headers in the BOM. In this case, the module would be called out in the BOM with a refdes like U1 while the headers are not directly associate to a footprint. So would you use assembly notes to make sure the headers are applied to U1 instead of the module being soldered directly?

  • Hi

    We had done similar things in the past & this may help.

    So the first consideration is the pinning. Since your PCB footprint will have more physical pins due to the need to plug in extra things this would normally mean the schematic symbol would also require the same number of pins so you could package the sch symbol to the footprint.

    There is a way around this and a picture might help.

    So the PCB Footprint is a DIP16 which could be say a module or a DIP16 IC Too. The extra pads you see are actually Vias which could represent the modules or connectors you wish to plug in.
    You represent the extra needed pads with Vias. They can be wired in to the DIP16 in the picture after netlisting, but on the physical board that can afford plugging things in too.

    On your schematic you could go the road of having three individual part numbers that all package to the same footprint, that would be three different symbols or you could use the description filed in CIS
    to stuff an alternate module etc or have a different field in CIS to handle that.

    We had good success using this method. If going this road or similar when creating the pcb footprint it is a good idea to fix the vias in place. The footprint is created as a standard PSM.

    The main advantage here is no excess pins required in the sch symbol to represent pads on the board & reliable packaging and netlisting.

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.