-
-The [nonetlist] patch adds an element flag that makes PCB ignore the marked
-element when dealing with netlists. This means connecting a net to a pin of
-a nonetlist element will not cause a short. The refdes of a nonetlist
-part is drawn with color element-color-nonetlist (ElementColor_nonetlist
-in the source; default value #777777, grey).
-
-Uses of the nonetlist feature:
-
-
smd jumper: Combined with the [intconn] patch, this
- solves the "0-ohm 1206 jumper" problem: the element should be marked
- as nonetlist, with both pins set intconn(1) - this will result in a 2
- pad element, pads internally connected, that can be part of any one network
- without causing short and passing the DRC.
-
mechanical parts that should not show up on the schematics:
-
-
mounting hole elements: single pin holes with silk marking the head of the screw
-
chassis (often with mounting holes or keep-out areas)
-
logos in footprints (no poly support in footprint - yet?)
-
mechanical parts which do not have solderable pins (plastic spacers, extra connector shields)
-
"spare connectors", e.g. unused/disconnected DIP sockets, pin grids, or connectors in the corner of the PCB for prototyping (dev-board style)
-
-
-
-Preservation: gsch2pcb-rnd leaves nonetlist elements in the PCB.
-
save/load and compatibility
-This patch introduces a new element flag. The following example demonstrates
-a 1206 jumper footprint:
-
-Mainline PCB will load the design ignoring internal connections and nonetlist
-flag - this will cause shorts on all connected pins/pads and will break
-the connection.
-
-Mainline PCB doesn't save nonetlist and elements are embedded in the file -
-once the design is loaded and saved with mainline PCB, the flag is lost.
-After reloading the file in pcb-rnd, the element causes the same shorts
-as in mainline PCB.
-
-
-
-There are parts with internal connections (e.g. pin 2 and 4 of a SO8
-package are internally connected). Mainline PCB can not handle this,
-leaving the following options:
-
-
connect both pins to the net from the schematics - this works if all the internally connected pins are required to connect to copper (common with GND or power pins) but is very inconvenient for signal pins where only one of them needs to be connected
-
back-annotate which pin is connected - there's no easy back annotation
-
one pin connected, the other is closer to the next target; PCB doesn't understand that they are already connected internally; normally one shouldn't use the internal connection of a component instead of copper; except for the common practice to use 0 ohm SMD resistors for jumping wires
-
-
-The patch introduces a new pin flag intconn(g) which marks the pin
-to have internal connections in group g. If there
-are multiple pins using the same g value within a single element, they
-are internally connected. In other words, g is a group (or net name)
-within the element and pins can join to one of the numbered groups (or internal
-nets). The value of g shall be between 1 and 255, 0 means no internal
-connection (equivalent to the case when intconn(0) is omitted).
-
-When pin numbers are displayed (key 'd'), internal connection groups are
-written in square brackets, e.g. "2 [9]" means "pin 2, internally connected
-to group 9".
-
-Combined with the [nonetlist] patch, this
-solves the "0-ohm 1206 jumper" problem: the element should be marked
-as nonetlist, with both pins set intconn(1) - this will result in a 2
-pad element, pads internally connected, that can be part of any one network
-without causing short.
-
Example
-The first image depicts crossing traces, a common problem encountered when rats
-nesting a new layout from a netlist. One method to resolve such issues is to
-use a zero ohm jumper resistor that allows one signal trace to 'jump' across
-another.
-
-The second image shows the layout routing the nonconflicting rats and a open
-unrouted point where the rat would require one trace to cross another.
-
-In the third image a 1206 SMD footprint for a 0 Ohm 1206 resistor called J1 is
-placed with an intconn between the two pads which resolves the final rat line.
-
-
-
-
-
-
-
-
-
-
-
save/load and compatibility
-This patch introduces a new pin flag. In the following example
-pin 2 and 4 are connected internally as group 9, while pin 3
-does not have any internal connections:
-
-Mainline PCB will load the design ignoring internal connections -
-this may introduce new rats.
-
-Mainline PCB doesn't save intconn() and elements are embedded in the file -
-once the design is loaded and saved with mainline PCB, internal connection
-info is lost.
-
-
plans
-No plans - this feature is fully implemented. There is no plan for implementing
-a GUI, internal connections should be hand-edited into the element.
-
-
Index: trunk/doc/features/intconn1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
Index: trunk/doc/features/intconn1.png
===================================================================
--- trunk/doc/features/intconn1.png (revision 15215)
+++ trunk/doc/features/intconn1.png (nonexistent)
Property changes on: trunk/doc/features/intconn1.png
___________________________________________________________________
Deleted: svn:mime-type
## -1 +0,0 ##
-application/octet-stream
\ No newline at end of property
Index: trunk/doc/features/README
===================================================================
--- trunk/doc/features/README (revision 15215)
+++ trunk/doc/features/README (nonexistent)
@@ -1,3 +0,0 @@
-The content of this obsolete directory is being moved into the pcb-rnd
-knowledge pool (accessible from http://pcb-rnd.repo.hu clicking on the pool
-in the menu)
Index: trunk/doc/features/intconn2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
Index: trunk/doc/features/intconn2.png
===================================================================
--- trunk/doc/features/intconn2.png (revision 15215)
+++ trunk/doc/features/intconn2.png (nonexistent)
Property changes on: trunk/doc/features/intconn2.png
___________________________________________________________________
Deleted: svn:mime-type
## -1 +0,0 ##
-application/octet-stream
\ No newline at end of property
Index: trunk/doc/features/jumper_1206.fp
===================================================================
--- trunk/doc/features/jumper_1206.fp (revision 15215)
+++ trunk/doc/features/jumper_1206.fp (nonexistent)
@@ -1,7 +0,0 @@
-Element["nonetlist" "1206 jumper, 0 ohm" "" "1206" 0 0 -3150 -3150 0 100 ""]
-(
- Pad[-5905 -1181 -5905 1181 5118 2000 5718 "1" "1" "square,intconn(1)"]
- Pad[5905 -1181 5905 1181 5118 2000 5718 "2" "2" "square,intconn(1)"]
- ElementLine[-2362 -3740 2362 -3740 800]
- ElementLine[-2362 3740 2362 3740 800]
-)
Index: trunk/doc/features/intconn3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
Index: trunk/doc/features/intconn3.png
===================================================================
--- trunk/doc/features/intconn3.png (revision 15215)
+++ trunk/doc/features/intconn3.png (nonexistent)
Property changes on: trunk/doc/features/intconn3.png
___________________________________________________________________
Deleted: svn:mime-type
## -1 +0,0 ##
-application/octet-stream
\ No newline at end of property
Index: trunk/doc/README
===================================================================
--- trunk/doc/README (revision 15215)
+++ trunk/doc/README (revision 15216)
@@ -3,7 +3,6 @@
Most notable subdirectories:
developer/ documentation for developers
user/ user reference manual
- features/ details of pcb-rnd features
conf/ documentation of the configuration system
devlog/ random thoughts and articles
man/ UNIX manual pages
Index: trunk/doc/datasheet.html
===================================================================
--- trunk/doc/datasheet.html (revision 15215)
+++ trunk/doc/datasheet.html (revision 15216)
@@ -73,8 +73,6 @@
modularity (most code implemented in plugins)
slim code, reduced external dependency, portability
-