User Tools

Site Tools


pcb:drc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pcb:drc [2019/02/13 13:20]
cparker [New DRC Violations]
pcb:drc [2020/06/28 12:37] (current)
cparker [DRC bugs]
Line 64: Line 64:
   * Pin/pad exit violations   * Pin/pad exit violations
   * Silk screen over pins/pads   * Silk screen over pins/pads
 +  * Overlapping elements
 ====DRC tests==== ====DRC tests====
 This is to describe ways of testing the DRC code, not things the DRC should check for. This is to describe ways of testing the DRC code, not things the DRC should check for.
Line 92: Line 93:
   * Put the testing into a background thread so that the GUI is still responsive while the test is executing   * Put the testing into a background thread so that the GUI is still responsive while the test is executing
  
 +====Online DRC====
 +The online part of the DRC is that part that is active during normal design activities. It does things like preventing you from drawing traces too close together.
 +
 +Right now this functionality exists only for lines and is present in the line.c source file.
 +
 +====Multi-clearance====
 +One of the primary hurdles with implementing multi-clearance DRC, or, different DRC requirements for different traces or nets, is the way in which our DRC is implemented. Presently we use an algorithm that bloats or shrinks the objects we're testing, and looks for changes in connectivity. In a multi-clearance DRC environment,​ the amount that you would need to bloat your object now depends on the objects around it, which may not have been discovered yet.
 ====DRC interface==== ====DRC interface====
   * Create a DRC panel in the preferences window that allows for adjusting settings (possibly with image descriptions of the violations) and running specific tests individually. This will require that parameterization in the back-end work to be finished first.   * Create a DRC panel in the preferences window that allows for adjusting settings (possibly with image descriptions of the violations) and running specific tests individually. This will require that parameterization in the back-end work to be finished first.
  
 ====DRC bugs==== ====DRC bugs====
-  * Highlight both offending objects instead of just one (done: 4.2.0) 
   * Find more than one "​insufficient overlap"​ or "​insufficient gap" per pin/pad/via \\ The insufficient overlap case cannot propagate, due to the nature of how it works, however, the insufficient gap one can, and it does now as of the 4.2.0 release.   * Find more than one "​insufficient overlap"​ or "​insufficient gap" per pin/pad/via \\ The insufficient overlap case cannot propagate, due to the nature of how it works, however, the insufficient gap one can, and it does now as of the 4.2.0 release.
-  * Check for duplicate DRC errors before appending a new one (can happen if more than one pin is connected to an object) (done: 4.2.0) 
   * On MacOS the images in the DRC window of the GTK HID are garbled   * On MacOS the images in the DRC window of the GTK HID are garbled
 +  * The pixmap renderer (gtk) should consider the size of the violation when deciding what area to render for the preview image.
pcb/drc.1550082016.txt.gz ยท Last modified: 2019/02/13 13:20 by cparker