Adding this into the netlist opens a can of worms in that any change could break existing code.
Add it as a new file and nothing breaks because no one is currently reading that file.
You could combine this with position info like the initial location and orientation for the components
Engineer creates a list of "legs" with unique names. Each leg is a pair of pins connected to the same node.
The engineer can then create a set of rules.
1) Length of any leg must be greater,less or equal to a constant value
2) Difference of any two leg lengths must be less ,greater or equal to a constant value
3) Leg can have a minimum current rating to ensure trace width and number of vias.
4) Separation between two legs must be less ,greater or equal to a constant. * can be used for one
leg to force a minimum separation for hi voltage traces. A maximum can be used to minimize loop
area from two traces.
5) The number of traces for that leg can be set to 1 to force a single point connection or 4 to
force a grid.
Adding this into the netlist opens a can of worms in that any change could break existing code.
Add it as a new file and nothing breaks because no one is currently reading that file.
You could combine this with position info like the initial location and orientation for the components
Engineer creates a list of "legs" with unique names. Each leg is a pair of pins connected to the same node.
The engineer can then create a set of rules.
1) Length of any leg must be greater,less or equal to a constant value
2) Difference of any two leg lengths must be less ,greater or equal to a constant value
3) Leg can have a minimum current rating to ensure trace width and number of vias.
4) Separation between two legs must be less ,greater or equal to a constant. * can be used for one
leg to force a minimum separation for hi voltage traces. A maximum can be used to minimize loop
area from two traces.
5) The number of traces for that leg can be set to 1 to force a single point connection or 4 to
force a grid.
John Eaton