Index: index.html =================================================================== --- index.html (revision 5590) +++ index.html (revision 5591) @@ -292,11 +292,61 @@ the same metadata and capabilities as pins. Overlapping pads are supported. A pad is always on either the top or the bottom copper layer group. -
+The netlist assumes element refdes are unique. If an element has multiple +instances of the same pin (or pad) number, the engine picks one randomly and +assumes there's an inivisible, internal connection within the element. +
+Rat lines can be regenerated from the current netlist for missing connections. +Connections that are realized in copper but not present on the netlist, pcb-rnd +gives a "short circuit" warning. Both happens when the net is "optimized" +(upon user request). +
+The netlist is typically derived from a schematics by external tools +(such as gnetlist). The netlist can be imported (updated) any time. This +process is called "forward annotation". +
+It is also possible to make changes to the netlist from within pcb-rnd:
+pins can be swapped, element packages replaced using back annotation
+actions. Such actions will keep a list of intended netlist and element
+changes, called the netlist patch. Pcb-rnd will keep these changes even
+if a new version of the netlist is imported. It is possible to export the
+netlist patch that can be imported in the schematics editor to change the
+schematics - this process is called "back annotation". A new forward
+annotation from the schematics editor to pcb-rnd will then cancel
+the netlist/element changes as the new netlist import netlist matches
+the intended (changed) netlist.
-
2.5. comparison of terms