How to Draw Off Board Components

This is PCB design software - schematics represents what's have to be on a board. You can create just a schematics for any other purpuses and have schematics + board layout for PCB. Or you can use "fake" components on the schematics(components drawn in "Symbols" layer for example).

On Sun, 08 Jul 2012 15:25:17 +0000, fanat9 wrote:

This is PCB design software - schematics represents what's have to be on

a board. You can create just a schematics for any other purpuses and

have schematics + board layout for PCB. Or you can use "fake" components

on the schematics(components drawn in "Symbols" layer for example).

Or you can make a library component that has the symbol that you want,

but that actually causes a connector to be laid down on the board.

There's no good way to do it, but I would lean toward just putting down a

regular old connector (not one that's pretending to be something else)

and annotating the schematic with some text ("resistor", "transistor",

etc.)

--

Tim Wescott

Control system and signal processing consulting

www.wescottdesign.com

Tim Wescott <tim@seemywebsite.please> wrote:

>On Sun, 08 Jul 2012 15:25:17 +0000, fanat9 wrote:

>> This is PCB design software - schematics represents what's have

>> to be on a board. You can create just a schematics for any other

>> purpuses and have schematics + board layout for PCB. Or you can

>> use "fake" components on the schematics(components drawn in

>> "Symbols" layer for example).

>Or you can make a library component that has the symbol that you want,

>but that actually causes a connector to be laid down on the board.

>There's no good way to do it, but I would lean toward just putting down a

>regular old connector (not one that's pretending to be something else)

>and annotating the schematic with some text ("resistor", "transistor",

>etc.)

Another method is to define a package for the device to be the

same as such a common connector which will provide connection to the

device. Keep notes on that package to detail the actual device

package so that the BOM will be useful for e.g. purchasing.

--

/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia

\ /  ASCII ribbon campaign | For every complex problem there is an

X   against HTML mail     | answer that is clear, simple, and wrong.

/ \  and postings          |  --HL Mencken

On 07/09/2012 06:18 AM, Bernd Felsche wrote:

Tim Wescott <tim@seemywebsite.please> wrote:

>> On Sun, 08 Jul 2012 15:25:17 +0000, fanat9 wrote:

>>> This is PCB design software - schematics represents what's have

>>> to be on a board. You can create just a schematics for any other

>>> purpuses and have schematics + board layout for PCB. Or you can

>>> use "fake" components on the schematics(components drawn in

>>> "Symbols" layer for example).

>> Or you can make a library component that has the symbol that you want,

>> but that actually causes a connector to be laid down on the board.

>> There's no good way to do it, but I would lean toward just putting down a

>> regular old connector (not one that's pretending to be something else)

>> and annotating the schematic with some text ("resistor", "transistor",

>> etc.)

 

Another method is to define a package for the device to be the

same as such a common connector which will provide connection to the

device. Keep notes on that package to detail the actual device

package so that the BOM will be useful for e.g. purchasing.

 

Sometimes I find it useful to have a "symbol/device" that does nothing

else than allowing the net to change name from one label to another on

the same schematic. It might sound stupid at first but in the company

where I work for the moment they have very large schematics which is

integrated with other companies schematics. And here they use a special

symbol for connecting two net with different names without requiring a

0R resistor, for example...

Here it is handy to be able to switch from one net name to another in

the same net to be able to follow designations used in both systems.

But, in the layout program the net appear as one. I think they use

mentor-graphic. I am not a part of the HW team here though (sadly), so I

am not 100% sure of how it works. Never used MG my self.

However, I see that for example it would be handy when you use the same

CPU pin for multipurpose usage. And there is many other cases it would

be useful as well.

Breg

Vidar (Z)

This is how I did my off board parts and wiring on schematic made a dashed line around all items and I have an off board library. The pad that goes to wiring off board has dashed line up to it on both sides on schematic then you know when you leave the board and and the color changes to off board layer, net is green....

On 08/07/2012 13:58, Paul Sturpe wrote:

How do I draw a schematic to show components that are not on the PC board itself?

 

Several approaches have been suggested.

Personally I have an "OFFBOARD" part (as part of my

frames/document-fields/documentation library) which has a symbol

containing only its name and value and a package containing the same (on

the Documentation layer).

This allows me to build a list of off-board parts on both the schematic

and PCB, which I typically put in a corner of the frame, along with any

notes.

The benefit of doing this, rather than just adding text notes, is that

the off-board parts can be assigned attributes, such as order numbers,

so that they can be automatically added to the BoM along with the

on-board components.

Just my 2c.

Andrew

0xADF

Thanks for the suggestions from all.  I haven't figured out how to create the symbols so they will show up only in the schematic and not propagate to the board, but I'll work on it.

Do I have to create the symbols from scratch, or is there a way to copy an existing symbol and save it in a different layer so that adding it to my schematic will not add a component to the board?  If so, can someone give me a little more detail on how to do it or point me the area of the help file to study?

As you can probably tell, I'm pretty new at this!

Paul

Take the attached lbr as an idea-source

r