Although nets should ideally be named with information that conveys each net's role in the design, there is often no meaningful name that can be assigned. For this reason, nets do not have to be named—eXpress analyses will produce identical results regardless of whether nets have been named. Although there are no inherent restrictions on the specific names (abbreviations) that are assigned to nets, reports that contain information about test locations (such as the Test Point Placement report) can be difficult to interpret if unique names are not assigned to each net.
The use of duplicate net names can also have an effect upon analysis results when "Automatic Port Naming" is employed (since duplicate port names can result in duplicate function names).When a net is named, any port connected to that net whose name is not Analyst-specified will be automatically named based on the net name. While this feature can be helpful, it raises the question as to the most optimal way to name ports and nets. For some designs, it may be preferable to leave most ports unnamed and use net naming to label the ports, whereas with other designs it may be better to explicitly name every port to match a schematic and label only those nets that are most useful. The decision between these two styles largely depends on the design.
Net descriptions only appear in the design window for stubbed nets. The names will not appear, however, when ports on the same side of an object are placed so closely together that the names on the net stubs would overlap to the point of being unreadable.
On the Details panel, edit the name by typing or pasting into the Abbreviation field.
Precautions
If you choose to allow nets to name all the ports, and the net happens to connect to more than one output port on the same object, it will create duplicate port names which may result in undesirable behavior during analysis.
