Author Topic: Multi body parts  (Read 1394 times)

0 Members and 1 Guest are viewing this topic.

Offline owieccTopic starter

  • Frequent Contributor
  • **
  • Posts: 315
  • Country: dk
    • Google scholar profile
Multi body parts
« on: October 23, 2018, 02:06:06 pm »
How do you handle parts that are somehow physically connected together. I mean e.g. a PICe connector, card latch and PCIe card itself.

In schematic I would prefer to have the card pins and its designators visible.
In PCB editor I need to have the correct distance between the PCIe connector and edge latch.
For production I would need two separate components because I need to buy them separately and assemble them separately.

Is there a smart way out (single component that has two parts included) or do you just have two separate components (connector and latch) and annotate the pinout in the schematic?
 

Offline ajb

  • Super Contributor
  • ***
  • Posts: 2601
  • Country: us
Re: Multi body parts
« Reply #1 on: October 24, 2018, 08:44:38 pm »
It's strictly one component, one part unfortunately.  You could use snippets to sort-of simplify placement, but that's about it.  Or maybe include some reference markers in a mechanical layer within the footprint to make alignment on the board easier.
 

Online T3sl4co1l

  • Super Contributor
  • ***
  • Posts: 21675
  • Country: us
  • Expert, Analog Electronics, PCB Layout, EMC
    • Seven Transistor Labs
Re: Multi body parts
« Reply #2 on: October 25, 2018, 04:47:04 am »
Multiple parts on the schematic, to generate multiple parts in the BOM.  If you like, you can attach a [mechanical, no pins] footprint and position it over the main component, so the 3D model looks right and the pick-and-place file agrees.

Set the Description, or a Note or something, on the mechanical parts, so the BOM says where they are to be assembled (e.g., "ATTACH TO J5").

Alternately, create a second-level BOM that lists everything that plugs into the board after soldering.  And so on, into the box build, if applicable.  Components on this level are beyond board scope, so shouldn't be managed in Altium anyway -- a separate spreadsheet or database or MCAD or whatever system would handle that.

Or make schematics for everything and generate them from Altium, what do I care? ;D

Tim
« Last Edit: October 25, 2018, 04:49:14 am by T3sl4co1l »
Seven Transistor Labs, LLC
Electronic design, from concept to prototype.
Bringing a project to life?  Send me a message!
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf