| Author |
 Topic  |
|
|
Peter Johnson
United Kingdom
501 Posts |
 Posted - 31 Jan 2006 : 11:07:23
|
>Does version 8 support multi sheets for schematics? What is the > >correct way to asign nets to labels in the schematic?
>
Yes, it does. You need to use a project. What will happen is that when you've created a project, you can add files using the [Project] menu. As you add the files, any conflicts of net names, component numbers, etc. are resolved. If you've already got a pcb design, it becomes rather more tricky, as there's a relatively high risk of tracks being unrouted as Easy-PC tries to resolve any differences. The biggest risk is as you add the second schematic design, for this
reason.
Within a project, any named nets are considered to apply globally across the project, so interconnections between sheets are possible. Any nets of the same format as the auto-generated ones (N???? where ? is a digit) are local to the individual schematic. That means that potentially, there could be several unrelated nets in the pcb with the same net number. This is resolved by adding a suffix to each numbered net to identify its source schematic. It's not necessary with a single schematic, so it only applies to projects with 2 or more schematic sheets. Now in the process of adding the second sheet, sometimes the program doesn't get it right, and tries to delete numbered nets, and replace them with identical nets, with the suffix,
but unrouted.
Labels are just that - labels. They have no power to force a connection in version 8. Version 9 introduced the possibility of permanently assigning a fixed net name to designated component pins, so in that version it's possible to design active labels, but you don't need to worry about that in version 8. A useful one is a 'T' shape with no text, but a connection point at the bottom, as you can use the 'Display Net Name' function to give a label that can be positioned over the top of the 'T'.
Peter Johnson
Technical Support
Number One Systems |
|
|
DavidM
United Kingdom
458 Posts |
Posted - 31 Jan 2006 : 11:22:28
|
Definitely worth understanding the difference between the 'terminal name' in the component (which are labels generally used to describe the functionality of each pin), and the netname. A pin can only have a netname by connecting or adding it to a net. This is independent of the name on the pin in the component.
Also, the netname does not have to be displayed on the pin to make it connected, although we would tend to recommend that you show the netname for all "named" nets (nets like CLK, RESET, etc) to make the schematic drawing easier to read.
David Manns
Technical Support
Number One Systems
|
 |
|
|
Tedgo
United Kingdom
11 Posts |
Posted - 29 Jan 2007 : 13:39:37
|
I noticed the facility to assign a net name to a component pin when I upgraded to version 10. My only worry with it is that the assignment it is not permanent. If you make a connection to the pin and then rub the connection out, perhaps to insert another component etc, and then remake the original pin connection the assigned net name is lost.
I haven't checked to see if one gets an error message if one tries to connect two pins together which have different assignments.
The assigned pins has potential with say connector on VME backplanes etc, but the assignment should be permanent. |
|
|
| |
Topic |
|
|
|
Creating a new project