On Tue, Jun 14, 2011 at 10:24 PM, Xiaofan Chen wrote: > Not so sure about DipTrace. However, normally if you want > to reuse the same layout blocks, then you create a library > part to encompass multiple items. > > Hierarchical schematics may be a bit different, since the > blocks may have different layout design. > > BTW, we sometimes actually have to flat hierarchical > schematics into normal ones since it is easier for the viewers > of the schematics, this is especially true for not-so-complicated > designs. Personally I also avoid the use of bus when it is not > really a bus. For example, if a design has 8 channels of similar > blocks, I actually prefer to copy 8 times the designs and > not try to use hierarchy. And I will avoid to use Bus for the > signals in this case. In this case, you may need more pages > for the schematics but then it is less error-prone. > > Well, this is specifically what I mean by hierarchical schematic: 1. You make a frequently used set of components. In this example, I'm referring to an LED block with a transistor and a resistor. Everything you see here is a "block". Note the block's ports that I have named: collector, VCC, and GND. Pic: http://postimage.org/image/nv8sbo/ 2. The blocks can then be reused as many times as you like in your main schematic (just as if they were an IC). The ports show up nice and neatly. No mess from multiple components. Keeps everything neat and readable - less chance of error. Pic: http://postimage.org/image/pis4tg/ --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .