Quote:
|
Originally Posted by petrv What about defining the prototype area as an Eagle component (in a library) ?
Just create a package with a lot of pads (looking a bit like a PGA) - then you can easily place it on any board layout you need. And it won't disappear when ripping up traces.
Petr |
A very good idea! Don't forget to create a symbol as well. That way you can create a device which can be used in any circuit where it is necessary.
I doubt that the posted example of 3v0 has a schematic. All parts look pretty much like a sole PCB. For a PCB there is no ERC, just a DRC, and that's where it might get confusing not to know exactly which parts are connected. No cross-check is possible.
Creating a package with a certain amount of "vias" isn't flexible enough, e.g. it contains 50, but all of a sudden your application requires more than those. There is no other way than copying and pasting and make a new package. Editing the existing one is impossible. You'll be confronted with the message: "package in use".
Using my method of creating a device with just one "via" you are free to add or erase any one. If erased in the schematic they will also be erased on the PCB because of a valid forward- backward annotation with the schematic and the board loaded.
There is another disadvantage to just adding "vias" which in reality are pads. Only the maker can read that schematic and PCB.
Hans